Lines Matching +full:on +full:- +full:device
1 # SPDX-License-Identifier: GPL-2.0
3 # Block device driver configuration
8 depends on BLOCK
11 Say Y here to get to see options for various different block device
25 depends on BLK_DEV_NULL_BLK && FAULT_INJECTION
29 depends on ARCH_MAY_HAVE_PC_FDC
34 <file:Documentation/admin-guide/blockdev/floppy.rst>.
44 depends on BLK_DEV_FD
47 special low-level hardware accesses to them (access and use
48 non-standard formats, for example), then enable this.
60 depends on AMIGA
64 depends on ATARI
68 depends on PPC_PMAC && !PPC_PMAC64
70 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
75 depends on M68K && MAC
82 depends on ZORRO
96 tristate "SEGA Dreamcast GD-ROM drive"
97 depends on SH_DREAMCAST
101 "GD-ROM" by SEGA to signify it is capable of reading special disks
108 tristate "Parallel port IDE device support"
109 depends on PARPORT_PC
111 There are many external CD-ROM and disk devices that connect through
115 Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information.
117 If you have said Y to the "Parallel-port support" configuration
123 you may still build the individual protocol modules and high-level
128 least one high-level driver (e.g. "Parallel port IDE disks",
129 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
130 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
142 depends on PCI
145 battery backed (Non-volatile) RAM cards.
158 bool "Virtual block device"
159 depends on UML
161 The User-Mode Linux port includes a driver called UBD which will let
162 you access arbitrary files on the host computer as block devices.
168 depends on BLK_DEV_UBD
170 Writes to the virtual block device are not immediately written to the
171 host's disk; this may cause problems if, for example, the User-Mode
176 immediately) is configurable on a per-UBD basis by using a special
178 turn on synchronous operation by default for all block devices.
184 playing around with User-Mode Linux) you can choose N.
191 tristate "Loopback device support"
194 device; you can then create a file system on that block device and
196 drive partitions, CD-ROM drives or floppy drives. The loop devices
197 are block special device files with major number 7 and typically
204 root file system inside a DOS FAT file using this loop device
207 To use the loop device, you need the losetup utility, found in the
208 util-linux package, see
209 <https://www.kernel.org/pub/linux/utils/util-linux/>.
211 The loop device driver can also be used to "hide" a file system in
215 on a remote file server.
219 and a Device Mapper target (which is superior, as it supports all
222 or later) version of util-linux. Additionally, be aware that
225 Note that this loop device has nothing to do with the loopback
226 device used for network connections from the machine to itself.
234 int "Number of loop devices to pre-create at init time"
235 depends on BLK_DEV_LOOP
238 Static number of loop devices to be unconditionally pre-created
241 This default value can be overwritten on the kernel command
242 line or with module-parameter loop.max_loop.
246 dynamically allocated with the /dev/loop-control interface.
252 depends on BLK_DEV_LOOP
258 WARNING: This device is not safe for journaled file systems like
259 ext3 or Reiserfs. Please use the Device Mapper crypto module
260 instead, which can be configured to be on-disk compatible with the
261 cryptoloop device. cryptoloop support will be removed in Linux 5.16.
266 tristate "Network block device support"
267 depends on NET
271 servers (mount file systems on them etc.). Communication between
274 a block device special file such as /dev/nd0.
276 Network block devices also allows you to run a block-device in
278 communicating using the loopback network device).
280 Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
294 depends on PCI
295 depends on 64BIT
300 Use device /dev/skd$N amd /dev/skd$Np$M.
304 depends on PCI
312 tristate "RAM block device support"
315 a block device, so that you can make file systems on it, read and
322 For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
334 depends on BLK_DEV_RAM
338 in memory, you will need at least one RAM disk (e.g. root on cramfs).
342 depends on BLK_DEV_RAM
349 tristate "Packet writing on CD/DVD media (DEPRECATED)"
350 depends on !UML
362 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
364 DVD-RW disks must be in restricted overwrite mode.
366 See the file <file:Documentation/cdrom/packet-writing.rst>
367 for further information on the use of this driver.
374 depends on CDROM_PKTCDVD
380 of non-swappable kernel memory, memory which will be allocated when
385 depends on CDROM_PKTCDVD
387 If enabled, write caching will be set for the CD-R/W device. For now
388 this option is dangerous unless the CD-RW media is known good, as we
393 depends on NET
400 depends on SUN_LDOMS
409 depends on 4xx || MICROBLAZE
414 tristate "Xen virtual block device support"
415 depends on XEN
419 This driver implements the front-end of the Xen virtual
420 block device driver. It communicates with a back-end driver
421 in another domain which drives the actual block device.
424 tristate "Xen block-device backend driver"
425 depends on XEN_BACKEND
427 The block-device backend driver allows the kernel to export its
428 block devices to other guests via a high-performance shared-memory
434 The backend driver attaches itself to a any block device specified
436 device as long as it has a major and minor.
441 will be called xen-blkback.
446 depends on VIRTIO
452 tristate "Rados block device (RBD)"
453 depends on INET && BLOCK
459 Say Y here if you want include the Rados block device, which stripes
460 a block device over objects stored in the Ceph distributed object
468 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
469 depends on PCI
472 Device driver for IBM's high speed PCIe SSD
473 storage device: Flash Adapter 900GB Full Height.