2 # Block device driver configuration
10 Say Y here to get to see options for various different block device
11 drivers. This option alone does not add any kernel code.
13 If you say N, all options in this submenu will be skipped and disabled;
14 only do this if you know what you are doing.
19 tristate "Normal floppy disk support"
20 depends on ARCH_MAY_HAVE_PC_FDC
22 If you want to use the floppy disk drive(s) of your PC under Linux,
23 say Y. Information about this driver, especially important for IBM
24 Thinkpad users, is contained in
25 <file:Documentation/blockdev/floppy.txt>.
26 That file also contains the location of the Floppy driver FAQ as
27 well as location of the fdutils package used to configure additional
28 parameters of the driver at run time.
30 To compile this driver as a module, choose M here: the
31 module will be called floppy.
34 tristate "Amiga floppy support"
38 tristate "Atari floppy support"
42 tristate "Support for PowerMac floppy"
43 depends on PPC_PMAC && !PPC_PMAC64
45 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
46 floppy controller, say Y here. Most commonly found in PowerMacs.
49 tristate "Support for SWIM Macintosh floppy"
50 depends on M68K && MAC
52 You should select this option if you want floppy support
53 and you don't have a II, IIfx, Q900, Q950 or AV series.
56 tristate "Amiga Zorro II ramdisk support"
59 This enables support for using Chip RAM and Zorro II RAM as a
60 ramdisk or as a swap partition. Say Y if you want to include this
63 To compile this driver as a module, choose M here: the
64 module will be called z2ram.
67 tristate "SEGA Dreamcast GD-ROM drive"
68 depends on SH_DREAMCAST
70 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
71 "GD-ROM" by SEGA to signify it is capable of reading special disks
72 with up to 1 GB of data. This drive will also read standard CD ROM
73 disks. Select this option to access any disks in your GD ROM drive.
74 Most users will want to say "Y" here.
75 You can also build this as a module which will be called gdrom.
78 tristate "Parallel port IDE device support"
81 There are many external CD-ROM and disk devices that connect through
82 your computer's parallel port. Most of them are actually IDE devices
83 using a parallel port IDE adapter. This option enables the PARIDE
84 subsystem which contains drivers for many of these external drives.
85 Read <file:Documentation/blockdev/paride.txt> for more information.
87 If you have said Y to the "Parallel-port support" configuration
88 option, you may share a single port between your printer and other
89 parallel port devices. Answer Y to build PARIDE support into your
90 kernel, or M if you would like to build it as a loadable module. If
91 your parallel port support is in a loadable module, you must build
92 PARIDE as a module. If you built PARIDE support into your kernel,
93 you may still build the individual protocol modules and high-level
94 drivers as loadable modules. If you build this support as a module,
95 it will be called paride.
97 To use the PARIDE support, you must say Y or M here and also to at
98 least one high-level driver (e.g. "Parallel port IDE disks",
99 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
100 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
101 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
104 source "drivers/block/paride/Kconfig"
106 source "drivers/block/mtip32xx/Kconfig"
108 source "drivers/block/zram/Kconfig"
111 tristate "Compaq SMART2 support"
112 depends on PCI && VIRT_TO_BUS
114 This is the driver for Compaq Smart Array controllers. Everyone
115 using these boards should say Y here. See the file
116 <file:Documentation/blockdev/cpqarray.txt> for the current list of
117 boards supported by this driver, and for further information on the
120 config BLK_CPQ_CISS_DA
121 tristate "Compaq Smart Array 5xxx support"
123 select CHECK_SIGNATURE
125 This is the driver for Compaq Smart Array 5xxx controllers.
126 Everyone using these boards should say Y here.
127 See <file:Documentation/blockdev/cciss.txt> for the current list of
128 boards supported by this driver, and for further information
129 on the use of this driver.
131 config CISS_SCSI_TAPE
132 bool "SCSI tape drive support for Smart Array 5xxx"
133 depends on BLK_CPQ_CISS_DA && PROC_FS
134 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
136 When enabled (Y), this option allows SCSI tape drives and SCSI medium
137 changers (tape robots) to be accessed via a Compaq 5xxx array
138 controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
140 "SCSI support" and "SCSI tape support" must also be enabled for this
143 When this option is disabled (N), the SCSI portion of the driver
146 config BLK_DEV_DAC960
147 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
150 This driver adds support for the Mylex DAC960, AcceleRAID, and
151 eXtremeRAID PCI RAID controllers. See the file
152 <file:Documentation/blockdev/README.DAC960> for further information
155 To compile this driver as a module, choose M here: the
156 module will be called DAC960.
159 tristate "Micro Memory MM5415 Battery Backed RAM support"
162 Saying Y here will include support for the MM5415 family of
163 battery backed (Non-volatile) RAM cards.
164 <http://www.umem.com/>
166 The cards appear as block devices that can be partitioned into
167 as many as 15 partitions.
169 To compile this driver as a module, choose M here: the
170 module will be called umem.
172 The umem driver has not yet been allocated a MAJOR number, so
173 one is chosen dynamically.
176 bool "Virtual block device"
179 The User-Mode Linux port includes a driver called UBD which will let
180 you access arbitrary files on the host computer as block devices.
181 Unless you know that you do not need such virtual block devices say
184 config BLK_DEV_UBD_SYNC
185 bool "Always do synchronous disk IO for UBD"
186 depends on BLK_DEV_UBD
188 Writes to the virtual block device are not immediately written to the
189 host's disk; this may cause problems if, for example, the User-Mode
190 Linux 'Virtual Machine' uses a journalling filesystem and the host
193 Synchronous operation (i.e. always writing data to the host's disk
194 immediately) is configurable on a per-UBD basis by using a special
195 kernel command line option. Alternatively, you can say Y here to
196 turn on synchronous operation by default for all block devices.
198 If you're running a journalling file system (like reiserfs, for
199 example) in your virtual machine, you will want to say Y here. If
200 you care for the safety of the data in your virtual machine, Y is a
201 wise choice too. In all other cases (for example, if you're just
202 playing around with User-Mode Linux) you can choose N.
204 config BLK_DEV_COW_COMMON
209 tristate "Loopback device support"
211 Saying Y here will allow you to use a regular file as a block
212 device; you can then create a file system on that block device and
213 mount it just as you would mount other block devices such as hard
214 drive partitions, CD-ROM drives or floppy drives. The loop devices
215 are block special device files with major number 7 and typically
216 called /dev/loop0, /dev/loop1 etc.
218 This is useful if you want to check an ISO 9660 file system before
219 burning the CD, or if you want to use floppy images without first
220 writing them to floppy. Furthermore, some Linux distributions avoid
221 the need for a dedicated Linux partition by keeping their complete
222 root file system inside a DOS FAT file using this loop device
225 To use the loop device, you need the losetup utility, found in the
226 util-linux package, see
227 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
229 The loop device driver can also be used to "hide" a file system in
230 a disk partition, floppy, or regular file, either using encryption
231 (scrambling the data) or steganography (hiding the data in the low
232 bits of, say, a sound file). This is also safe if the file resides
233 on a remote file server.
235 There are several ways of encrypting disks. Some of these require
236 kernel patches. The vanilla kernel offers the cryptoloop option
237 and a Device Mapper target (which is superior, as it supports all
238 file systems). If you want to use the cryptoloop, say Y to both
239 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
240 or later) version of util-linux. Additionally, be aware that
241 the cryptoloop is not safe for storing journaled filesystems.
243 Note that this loop device has nothing to do with the loopback
244 device used for network connections from the machine to itself.
246 To compile this driver as a module, choose M here: the
247 module will be called loop.
249 Most users will answer N here.
251 config BLK_DEV_LOOP_MIN_COUNT
252 int "Number of loop devices to pre-create at init time"
253 depends on BLK_DEV_LOOP
256 Static number of loop devices to be unconditionally pre-created
259 This default value can be overwritten on the kernel command
260 line or with module-parameter loop.max_loop.
262 The historic default is 8. If a late 2011 version of losetup(8)
263 is used, it can be set to 0, since needed loop devices can be
264 dynamically allocated with the /dev/loop-control interface.
266 config BLK_DEV_CRYPTOLOOP
267 tristate "Cryptoloop Support"
270 depends on BLK_DEV_LOOP
272 Say Y here if you want to be able to use the ciphers that are
273 provided by the CryptoAPI as loop transformation. This might be
274 used as hard disk encryption.
276 WARNING: This device is not safe for journaled file systems like
277 ext3 or Reiserfs. Please use the Device Mapper crypto module
278 instead, which can be configured to be on-disk compatible with the
281 source "drivers/block/drbd/Kconfig"
284 tristate "Network block device support"
287 Saying Y here will allow your computer to be a client for network
288 block devices, i.e. it will be able to use block devices exported by
289 servers (mount file systems on them etc.). Communication between
290 client and server works over TCP/IP networking, but to the client
291 program this is hidden: it looks like a regular local file access to
292 a block device special file such as /dev/nd0.
294 Network block devices also allows you to run a block-device in
295 userland (making server and client physically the same computer,
296 communicating using the loopback network device).
298 Read <file:Documentation/blockdev/nbd.txt> for more information,
299 especially about where to find the server code, which runs in user
300 space and does not need special kernel support.
302 Note that this has nothing to do with the network file systems NFS
303 or Coda; you can say N here even if you intend to use NFS or Coda.
305 To compile this driver as a module, choose M here: the
306 module will be called nbd.
311 tristate "NVM Express block device"
314 The NVM Express driver is for solid state drives directly
315 connected to the PCI or PCI Express bus. If you know you
316 don't have one of these, it is safe to answer N.
318 To compile this driver as a module, choose M here: the
319 module will be called nvme.
322 tristate "OSD object-as-blkdev support"
323 depends on SCSI_OSD_ULD
325 Saying Y or M here will allow the exporting of a single SCSI
326 OSD (object-based storage) object as a Linux block device.
328 For example, if you create a 2G object on an OSD device,
329 you can then use this module to present that 2G object as
330 a Linux block device.
332 To compile this driver as a module, choose M here: the
333 module will be called osdblk.
338 tristate "Promise SATA SX8 support"
341 Saying Y or M here will enable support for the
342 Promise SATA SX8 controllers.
344 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
347 tristate "RAM block device support"
349 Saying Y here will allow you to use a portion of your RAM memory as
350 a block device, so that you can make file systems on it, read and
351 write to it and do all the other things that you can do with normal
352 block devices (such as hard drives). It is usually used to load and
353 store a copy of a minimal root file system off of a floppy into RAM
354 during the initial install of Linux.
356 Note that the kernel command line option "ramdisk=XX" is now obsolete.
357 For details, read <file:Documentation/blockdev/ramdisk.txt>.
359 To compile this driver as a module, choose M here: the
360 module will be called rd.
362 Most normal users won't need the RAM disk functionality, and can
365 config BLK_DEV_RAM_COUNT
366 int "Default number of RAM disks"
368 depends on BLK_DEV_RAM
370 The default value is 16 RAM disks. Change this if you know what you
371 are doing. If you boot from a filesystem that needs to be extracted
372 in memory, you will need at least one RAM disk (e.g. root on cramfs).
374 config BLK_DEV_RAM_SIZE
375 int "Default RAM disk size (kbytes)"
376 depends on BLK_DEV_RAM
379 The default value is 4096 kilobytes. Only change this if you know
383 bool "Support XIP filesystems on RAM block device"
384 depends on BLK_DEV_RAM
387 Support XIP filesystems (such as ext2 with XIP support on) on
388 top of block ram device. This will slightly enlarge the kernel, and
389 will prevent RAM block device backing store memory from being
390 allocated from highmem (only a problem for highmem systems).
393 tristate "Packet writing on CD/DVD media"
396 If you have a CDROM/DVD drive that supports packet writing, say
397 Y to include support. It should work with any MMC/Mt Fuji
398 compliant ATAPI or SCSI drive, which is just about any newer
401 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
403 DVD-RW disks must be in restricted overwrite mode.
405 See the file <file:Documentation/cdrom/packet-writing.txt>
406 for further information on the use of this driver.
408 To compile this driver as a module, choose M here: the
409 module will be called pktcdvd.
411 config CDROM_PKTCDVD_BUFFERS
412 int "Free buffers for data gathering"
413 depends on CDROM_PKTCDVD
416 This controls the maximum number of active concurrent packets. More
417 concurrent packets can increase write performance, but also require
418 more memory. Each concurrent packet will require approximately 64Kb
419 of non-swappable kernel memory, memory which will be allocated when
420 a disc is opened for writing.
422 config CDROM_PKTCDVD_WCACHE
423 bool "Enable write caching"
424 depends on CDROM_PKTCDVD
426 If enabled, write caching will be set for the CD-R/W device. For now
427 this option is dangerous unless the CD-RW media is known good, as we
428 don't do deferred write error handling yet.
431 tristate "ATA over Ethernet support"
434 This driver provides Support for ATA over Ethernet block
435 devices like the Coraid EtherDrive (R) Storage Blade.
438 tristate "mGine mflash, gflash support"
439 depends on ARM && GPIOLIB
441 mGine mFlash(gFlash) block device driver
444 int "Size of reserved area before MBR"
448 Define size of reserved area that usually used for boot. Unit is KB.
449 All of the block device operation will be taken this value as start
455 tristate "Sun Virtual Disk Client support"
458 Support for virtual disk devices as a client under Sun
461 source "drivers/s390/block/Kconfig"
464 tristate "Xilinx SystemACE support"
465 depends on 4xx || MICROBLAZE
467 Include support for the Xilinx SystemACE CompactFlash interface
469 config XEN_BLKDEV_FRONTEND
470 tristate "Xen virtual block device support"
473 select XEN_XENBUS_FRONTEND
475 This driver implements the front-end of the Xen virtual
476 block device driver. It communicates with a back-end driver
477 in another domain which drives the actual block device.
479 config XEN_BLKDEV_BACKEND
480 tristate "Xen block-device backend driver"
481 depends on XEN_BACKEND
483 The block-device backend driver allows the kernel to export its
484 block devices to other guests via a high-performance shared-memory
487 The corresponding Linux frontend driver is enabled by the
488 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
490 The backend driver attaches itself to a any block device specified
491 in the XenBus configuration. There are no limits to what the block
492 device as long as it has a major and minor.
494 If you are compiling a kernel to run in a Xen block backend driver
495 domain (often this is domain 0) you should say Y here. To
496 compile this driver as a module, chose M here: the module
497 will be called xen-blkback.
501 tristate "Virtio block driver"
504 This is the virtual block driver for virtio. It can be used with
505 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
508 bool "Very old hard disk (MFM/RLL/IDE) driver"
510 depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
512 This is a very old hard disk driver that lacks the enhanced
513 functionality of the newer ones.
515 It is required for systems with ancient MFM/RLL/ESDI drives.
520 tristate "Rados block device (RBD)"
521 depends on INET && BLOCK
528 Say Y here if you want include the Rados block device, which stripes
529 a block device over objects stored in the Ceph distributed object
532 More information at http://ceph.newdream.net/.
537 tristate "IBM FlashSystem 70/80 PCIe SSD Device Driver"
540 Device driver for IBM's high speed PCIe SSD
541 storage devices: FlashSystem-70 and FlashSystem-80.
543 To compile this driver as a module, choose M here: the
544 module will be called rsxx.