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
23 depends on ARCH_MAY_HAVE_PC_FDC
28 <file:Documentation/admin-guide/blockdev/floppy.rst>.
38 depends on BLK_DEV_FD
41 special low-level hardware accesses to them (access and use
42 non-standard formats, for example), then enable this.
54 depends on AMIGA
58 depends on ATARI
62 depends on PPC_PMAC && !PPC_PMAC64
64 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
69 depends on M68K && MAC && !HIGHMEM
76 depends on ZORRO
87 depends on MACH_NINTENDO64
95 tristate "SEGA Dreamcast GD-ROM drive"
96 depends on SH_DREAMCAST
100 "GD-ROM" by SEGA to signify it is capable of reading special disks
111 bool "Virtual block device"
112 depends on UML
114 The User-Mode Linux port includes a driver called UBD which will let
115 you access arbitrary files on the host computer as block devices.
121 depends on BLK_DEV_UBD
123 Writes to the virtual block device are not immediately written to the
124 host's disk; this may cause problems if, for example, the User-Mode
129 immediately) is configurable on a per-UBD basis by using a special
131 turn on synchronous operation by default for all block devices.
137 playing around with User-Mode Linux) you can choose N.
144 tristate "Loopback device support"
147 device; you can then create a file system on that block device and
149 drive partitions, CD-ROM drives or floppy drives. The loop devices
150 are block special device files with major number 7 and typically
157 root file system inside a DOS FAT file using this loop device
160 To use the loop device, you need the losetup utility, found in the
161 util-linux package, see
162 <https://www.kernel.org/pub/linux/utils/util-linux/>.
164 The loop device driver can also be used to "hide" a file system in
168 on a remote file server.
170 Note that this loop device has nothing to do with the loopback
171 device used for network connections from the machine to itself.
179 int "Number of loop devices to pre-create at init time"
180 depends on BLK_DEV_LOOP
183 Static number of loop devices to be unconditionally pre-created
186 This default value can be overwritten on the kernel command
187 line or with module-parameter loop.max_loop.
191 dynamically allocated with the /dev/loop-control interface.
196 tristate "Network block device support"
197 depends on NET
201 servers (mount file systems on them etc.). Communication between
204 a block device special file such as /dev/nd0.
206 Network block devices also allows you to run a block-device in
208 communicating using the loopback network device).
210 Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information,
223 tristate "RAM block device support"
226 a block device, so that you can make file systems on it, read and
233 For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>.
245 depends on BLK_DEV_RAM
249 in memory, you will need at least one RAM disk (e.g. root on cramfs).
253 depends on BLK_DEV_RAM
260 tristate "Packet writing on CD/DVD media (DEPRECATED)"
261 depends on !UML
262 depends on SCSI
273 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
275 DVD-RW disks must be in restricted overwrite mode.
277 See the file <file:Documentation/cdrom/packet-writing.rst>
278 for further information on the use of this driver.
285 depends on CDROM_PKTCDVD
291 of non-swappable kernel memory, memory which will be allocated when
296 depends on CDROM_PKTCDVD
298 If enabled, write caching will be set for the CD-R/W device. For now
299 this option is dangerous unless the CD-RW media is known good, as we
304 depends on NET
311 depends on SUN_LDOMS
319 tristate "Xen virtual block device support"
320 depends on XEN
324 This driver implements the front-end of the Xen virtual
325 block device driver. It communicates with a back-end driver
326 in another domain which drives the actual block device.
329 tristate "Xen block-device backend driver"
330 depends on XEN_BACKEND
332 The block-device backend driver allows the kernel to export its
333 block devices to other guests via a high-performance shared-memory
339 The backend driver attaches itself to a any block device specified
341 device as long as it has a major and minor.
346 will be called xen-blkback.
351 depends on VIRTIO
359 depends on RUST
367 tristate "Rados block device (RBD)"
368 depends on INET && BLOCK
374 Say Y here if you want include the Rados block device, which stripes
375 a block device over objects stored in the Ceph distributed object
399 depends on BLK_DEV_UBLK