Version:  2.0.40 2.2.26 2.4.37 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1


  1 #
  2 # Block device driver configuration
  3 #
  5 menuconfig BLK_DEV
  6         bool "Block devices"
  7         depends on BLOCK
  8         default y
  9         ---help---
 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.
 16 if BLK_DEV
 18 config BLK_DEV_NULL_BLK
 19         tristate "Null test block driver"
 21 config BLK_DEV_FD
 22         tristate "Normal floppy disk support"
 23         depends on ARCH_MAY_HAVE_PC_FDC
 24         ---help---
 25           If you want to use the floppy disk drive(s) of your PC under Linux,
 26           say Y. Information about this driver, especially important for IBM
 27           Thinkpad users, is contained in
 28           <file:Documentation/blockdev/floppy.txt>.
 29           That file also contains the location of the Floppy driver FAQ as
 30           well as location of the fdutils package used to configure additional
 31           parameters of the driver at run time.
 33           To compile this driver as a module, choose M here: the
 34           module will be called floppy.
 36 config AMIGA_FLOPPY
 37         tristate "Amiga floppy support"
 38         depends on AMIGA
 40 config ATARI_FLOPPY
 41         tristate "Atari floppy support"
 42         depends on ATARI
 44 config MAC_FLOPPY
 45         tristate "Support for PowerMac floppy"
 46         depends on PPC_PMAC && !PPC_PMAC64
 47         help
 48           If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
 49           floppy controller, say Y here. Most commonly found in PowerMacs.
 51 config BLK_DEV_SWIM
 52         tristate "Support for SWIM Macintosh floppy"
 53         depends on M68K && MAC
 54         help
 55           You should select this option if you want floppy support
 56           and you don't have a II, IIfx, Q900, Q950 or AV series.
 58 config AMIGA_Z2RAM
 59         tristate "Amiga Zorro II ramdisk support"
 60         depends on ZORRO
 61         help
 62           This enables support for using Chip RAM and Zorro II RAM as a
 63           ramdisk or as a swap partition. Say Y if you want to include this
 64           driver in the kernel.
 66           To compile this driver as a module, choose M here: the
 67           module will be called z2ram.
 69 config GDROM
 70         tristate "SEGA Dreamcast GD-ROM drive"
 71         depends on SH_DREAMCAST
 72         help
 73           A standard SEGA Dreamcast comes with a modified CD ROM drive called a
 74           "GD-ROM" by SEGA to signify it is capable of reading special disks
 75           with up to 1 GB of data. This drive will also read standard CD ROM
 76           disks. Select this option to access any disks in your GD ROM drive.
 77           Most users will want to say "Y" here.
 78           You can also build this as a module which will be called gdrom.
 80 config PARIDE
 81         tristate "Parallel port IDE device support"
 82         depends on PARPORT_PC
 83         ---help---
 84           There are many external CD-ROM and disk devices that connect through
 85           your computer's parallel port. Most of them are actually IDE devices
 86           using a parallel port IDE adapter. This option enables the PARIDE
 87           subsystem which contains drivers for many of these external drives.
 88           Read <file:Documentation/blockdev/paride.txt> for more information.
 90           If you have said Y to the "Parallel-port support" configuration
 91           option, you may share a single port between your printer and other
 92           parallel port devices. Answer Y to build PARIDE support into your
 93           kernel, or M if you would like to build it as a loadable module. If
 94           your parallel port support is in a loadable module, you must build
 95           PARIDE as a module. If you built PARIDE support into your kernel,
 96           you may still build the individual protocol modules and high-level
 97           drivers as loadable modules. If you build this support as a module,
 98           it will be called paride.
100           To use the PARIDE support, you must say Y or M here and also to at
101           least one high-level driver (e.g. "Parallel port IDE disks",
102           "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
103           to at least one protocol driver (e.g. "ATEN EH-100 protocol",
104           "MicroSolutions backpack protocol", "DataStor Commuter protocol"
105           etc.).
107 source "drivers/block/paride/Kconfig"
109 source "drivers/block/mtip32xx/Kconfig"
111 source "drivers/block/zram/Kconfig"
113 config BLK_CPQ_DA
114         tristate "Compaq SMART2 support"
115         depends on PCI && VIRT_TO_BUS && 0
116         help
117           This is the driver for Compaq Smart Array controllers.  Everyone
118           using these boards should say Y here.  See the file
119           <file:Documentation/blockdev/cpqarray.txt> for the current list of
120           boards supported by this driver, and for further information on the
121           use of this driver.
123 config BLK_CPQ_CISS_DA
124         tristate "Compaq Smart Array 5xxx support"
125         depends on PCI
126         select CHECK_SIGNATURE
127         help
128           This is the driver for Compaq Smart Array 5xxx controllers.
129           Everyone using these boards should say Y here.
130           See <file:Documentation/blockdev/cciss.txt> for the current list of
131           boards supported by this driver, and for further information
132           on the use of this driver.
134 config CISS_SCSI_TAPE
135         bool "SCSI tape drive support for Smart Array 5xxx"
136         depends on BLK_CPQ_CISS_DA && PROC_FS
137         depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
138         help
139           When enabled (Y), this option allows SCSI tape drives and SCSI medium
140           changers (tape robots) to be accessed via a Compaq 5xxx array 
141           controller.  (See <file:Documentation/blockdev/cciss.txt> for more details.)
143           "SCSI support" and "SCSI tape support" must also be enabled for this 
144           option to work.
146           When this option is disabled (N), the SCSI portion of the driver 
147           is not compiled.
149 config BLK_DEV_DAC960
150         tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
151         depends on PCI
152         help
153           This driver adds support for the Mylex DAC960, AcceleRAID, and
154           eXtremeRAID PCI RAID controllers.  See the file
155           <file:Documentation/blockdev/README.DAC960> for further information
156           about this driver.
158           To compile this driver as a module, choose M here: the
159           module will be called DAC960.
161 config BLK_DEV_UMEM
162         tristate "Micro Memory MM5415 Battery Backed RAM support"
163         depends on PCI
164         ---help---
165           Saying Y here will include support for the MM5415 family of
166           battery backed (Non-volatile) RAM cards.
167           <>
169           The cards appear as block devices that can be partitioned into
170           as many as 15 partitions.
172           To compile this driver as a module, choose M here: the
173           module will be called umem.
175           The umem driver has not yet been allocated a MAJOR number, so
176           one is chosen dynamically.
178 config BLK_DEV_UBD
179         bool "Virtual block device"
180         depends on UML
181         ---help---
182           The User-Mode Linux port includes a driver called UBD which will let
183           you access arbitrary files on the host computer as block devices.
184           Unless you know that you do not need such virtual block devices say
185           Y here.
187 config BLK_DEV_UBD_SYNC
188         bool "Always do synchronous disk IO for UBD"
189         depends on BLK_DEV_UBD
190         ---help---
191           Writes to the virtual block device are not immediately written to the
192           host's disk; this may cause problems if, for example, the User-Mode
193           Linux 'Virtual Machine' uses a journalling filesystem and the host
194           computer crashes.
196           Synchronous operation (i.e. always writing data to the host's disk
197           immediately) is configurable on a per-UBD basis by using a special
198           kernel command line option.  Alternatively, you can say Y here to
199           turn on synchronous operation by default for all block devices.
201           If you're running a journalling file system (like reiserfs, for
202           example) in your virtual machine, you will want to say Y here.  If
203           you care for the safety of the data in your virtual machine, Y is a
204           wise choice too.  In all other cases (for example, if you're just
205           playing around with User-Mode Linux) you can choose N.
208         bool
209         default BLK_DEV_UBD
211 config BLK_DEV_LOOP
212         tristate "Loopback device support"
213         ---help---
214           Saying Y here will allow you to use a regular file as a block
215           device; you can then create a file system on that block device and
216           mount it just as you would mount other block devices such as hard
217           drive partitions, CD-ROM drives or floppy drives. The loop devices
218           are block special device files with major number 7 and typically
219           called /dev/loop0, /dev/loop1 etc.
221           This is useful if you want to check an ISO 9660 file system before
222           burning the CD, or if you want to use floppy images without first
223           writing them to floppy. Furthermore, some Linux distributions avoid
224           the need for a dedicated Linux partition by keeping their complete
225           root file system inside a DOS FAT file using this loop device
226           driver.
228           To use the loop device, you need the losetup utility, found in the
229           util-linux package, see
230           <>.
232           The loop device driver can also be used to "hide" a file system in
233           a disk partition, floppy, or regular file, either using encryption
234           (scrambling the data) or steganography (hiding the data in the low
235           bits of, say, a sound file). This is also safe if the file resides
236           on a remote file server.
238           There are several ways of encrypting disks. Some of these require
239           kernel patches. The vanilla kernel offers the cryptoloop option
240           and a Device Mapper target (which is superior, as it supports all
241           file systems). If you want to use the cryptoloop, say Y to both
242           LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
243           or later) version of util-linux. Additionally, be aware that
244           the cryptoloop is not safe for storing journaled filesystems.
246           Note that this loop device has nothing to do with the loopback
247           device used for network connections from the machine to itself.
249           To compile this driver as a module, choose M here: the
250           module will be called loop.
252           Most users will answer N here.
255         int "Number of loop devices to pre-create at init time"
256         depends on BLK_DEV_LOOP
257         default 8
258         help
259           Static number of loop devices to be unconditionally pre-created
260           at init time.
262           This default value can be overwritten on the kernel command
263           line or with module-parameter loop.max_loop.
265           The historic default is 8. If a late 2011 version of losetup(8)
266           is used, it can be set to 0, since needed loop devices can be
267           dynamically allocated with the /dev/loop-control interface.
270         tristate "Cryptoloop Support"
271         select CRYPTO
272         select CRYPTO_CBC
273         depends on BLK_DEV_LOOP
274         ---help---
275           Say Y here if you want to be able to use the ciphers that are 
276           provided by the CryptoAPI as loop transformation. This might be
277           used as hard disk encryption.
279           WARNING: This device is not safe for journaled file systems like
280           ext3 or Reiserfs. Please use the Device Mapper crypto module
281           instead, which can be configured to be on-disk compatible with the
282           cryptoloop device.
284 source "drivers/block/drbd/Kconfig"
286 config BLK_DEV_NBD
287         tristate "Network block device support"
288         depends on NET
289         ---help---
290           Saying Y here will allow your computer to be a client for network
291           block devices, i.e. it will be able to use block devices exported by
292           servers (mount file systems on them etc.). Communication between
293           client and server works over TCP/IP networking, but to the client
294           program this is hidden: it looks like a regular local file access to
295           a block device special file such as /dev/nd0.
297           Network block devices also allows you to run a block-device in
298           userland (making server and client physically the same computer,
299           communicating using the loopback network device).
301           Read <file:Documentation/blockdev/nbd.txt> for more information,
302           especially about where to find the server code, which runs in user
303           space and does not need special kernel support.
305           Note that this has nothing to do with the network file systems NFS
306           or Coda; you can say N here even if you intend to use NFS or Coda.
308           To compile this driver as a module, choose M here: the
309           module will be called nbd.
311           If unsure, say N.
313 config BLK_DEV_NVME
314         tristate "NVM Express block device"
315         depends on PCI
316         ---help---
317           The NVM Express driver is for solid state drives directly
318           connected to the PCI or PCI Express bus.  If you know you
319           don't have one of these, it is safe to answer N.
321           To compile this driver as a module, choose M here: the
322           module will be called nvme.
324 config BLK_DEV_SKD
325         tristate "STEC S1120 Block Driver"
326         depends on PCI
327         depends on 64BIT
328         ---help---
329         Saying Y or M here will enable support for the
330         STEC, Inc. S1120 PCIe SSD.
332         Use device /dev/skd$N amd /dev/skd$Np$M.
334 config BLK_DEV_OSD
335         tristate "OSD object-as-blkdev support"
336         depends on SCSI_OSD_ULD
337         ---help---
338           Saying Y or M here will allow the exporting of a single SCSI
339           OSD (object-based storage) object as a Linux block device.
341           For example, if you create a 2G object on an OSD device,
342           you can then use this module to present that 2G object as
343           a Linux block device.
345           To compile this driver as a module, choose M here: the
346           module will be called osdblk.
348           If unsure, say N.
350 config BLK_DEV_SX8
351         tristate "Promise SATA SX8 support"
352         depends on PCI
353         ---help---
354           Saying Y or M here will enable support for the 
355           Promise SATA SX8 controllers.
357           Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
359 config BLK_DEV_RAM
360         tristate "RAM block device support"
361         ---help---
362           Saying Y here will allow you to use a portion of your RAM memory as
363           a block device, so that you can make file systems on it, read and
364           write to it and do all the other things that you can do with normal
365           block devices (such as hard drives). It is usually used to load and
366           store a copy of a minimal root file system off of a floppy into RAM
367           during the initial install of Linux.
369           Note that the kernel command line option "ramdisk=XX" is now obsolete.
370           For details, read <file:Documentation/blockdev/ramdisk.txt>.
372           To compile this driver as a module, choose M here: the
373           module will be called brd. An alias "rd" has been defined
374           for historical reasons.
376           Most normal users won't need the RAM disk functionality, and can
377           thus say N here.
379 config BLK_DEV_RAM_COUNT
380         int "Default number of RAM disks"
381         default "16"
382         depends on BLK_DEV_RAM
383         help
384           The default value is 16 RAM disks. Change this if you know what you
385           are doing. If you boot from a filesystem that needs to be extracted
386           in memory, you will need at least one RAM disk (e.g. root on cramfs).
388 config BLK_DEV_RAM_SIZE
389         int "Default RAM disk size (kbytes)"
390         depends on BLK_DEV_RAM
391         default "4096"
392         help
393           The default value is 4096 kilobytes. Only change this if you know
394           what you are doing.
396 config BLK_DEV_RAM_DAX
397         bool "Support Direct Access (DAX) to RAM block devices"
398         depends on BLK_DEV_RAM && FS_DAX
399         default n
400         help
401           Support filesystems using DAX to access RAM block devices.  This
402           avoids double-buffering data in the page cache before copying it
403           to the block device.  Answering Y will slightly enlarge the kernel,
404           and will prevent RAM block device backing store memory from being
405           allocated from highmem (only a problem for highmem systems).
407 config BLK_DEV_PMEM
408         tristate "Persistent memory block device support"
409         depends on HAS_IOMEM
410         help
411           Saying Y here will allow you to use a contiguous range of reserved
412           memory as one or more persistent block devices.
414           To compile this driver as a module, choose M here: the module will be
415           called 'pmem'.
417           If unsure, say N.
419 config CDROM_PKTCDVD
420         tristate "Packet writing on CD/DVD media"
421         depends on !UML
422         help
423           If you have a CDROM/DVD drive that supports packet writing, say
424           Y to include support. It should work with any MMC/Mt Fuji
425           compliant ATAPI or SCSI drive, which is just about any newer
426           DVD/CD writer.
428           Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
429           is possible.
430           DVD-RW disks must be in restricted overwrite mode.
432           See the file <file:Documentation/cdrom/packet-writing.txt>
433           for further information on the use of this driver.
435           To compile this driver as a module, choose M here: the
436           module will be called pktcdvd.
439         int "Free buffers for data gathering"
440         depends on CDROM_PKTCDVD
441         default "8"
442         help
443           This controls the maximum number of active concurrent packets. More
444           concurrent packets can increase write performance, but also require
445           more memory. Each concurrent packet will require approximately 64Kb
446           of non-swappable kernel memory, memory which will be allocated when
447           a disc is opened for writing.
450         bool "Enable write caching"
451         depends on CDROM_PKTCDVD
452         help
453           If enabled, write caching will be set for the CD-R/W device. For now
454           this option is dangerous unless the CD-RW media is known good, as we
455           don't do deferred write error handling yet.
457 config ATA_OVER_ETH
458         tristate "ATA over Ethernet support"
459         depends on NET
460         help
461         This driver provides Support for ATA over Ethernet block
462         devices like the Coraid EtherDrive (R) Storage Blade.
464 config MG_DISK
465         tristate "mGine mflash, gflash support"
466         depends on ARM && GPIOLIB
467         help
468           mGine mFlash(gFlash) block device driver
470 config MG_DISK_RES
471         int "Size of reserved area before MBR"
472         depends on MG_DISK
473         default 0
474         help
475           Define size of reserved area that usually used for boot. Unit is KB.
476           All of the block device operation will be taken this value as start
477           offset
478           Examples:
479                         1024 => 1 MB
481 config SUNVDC
482         tristate "Sun Virtual Disk Client support"
483         depends on SUN_LDOMS
484         help
485           Support for virtual disk devices as a client under Sun
486           Logical Domains.
488 source "drivers/s390/block/Kconfig"
490 config XILINX_SYSACE
491         tristate "Xilinx SystemACE support"
492         depends on 4xx || MICROBLAZE
493         help
494           Include support for the Xilinx SystemACE CompactFlash interface
497         tristate "Xen virtual block device support"
498         depends on XEN
499         default y
500         select XEN_XENBUS_FRONTEND
501         help
502           This driver implements the front-end of the Xen virtual
503           block device driver.  It communicates with a back-end driver
504           in another domain which drives the actual block device.
507         tristate "Xen block-device backend driver"
508         depends on XEN_BACKEND
509         help
510           The block-device backend driver allows the kernel to export its
511           block devices to other guests via a high-performance shared-memory
512           interface.
514           The corresponding Linux frontend driver is enabled by the
515           CONFIG_XEN_BLKDEV_FRONTEND configuration option.
517           The backend driver attaches itself to a any block device specified
518           in the XenBus configuration. There are no limits to what the block
519           device as long as it has a major and minor.
521           If you are compiling a kernel to run in a Xen block backend driver
522           domain (often this is domain 0) you should say Y here. To
523           compile this driver as a module, chose M here: the module
524           will be called xen-blkback.
527 config VIRTIO_BLK
528         tristate "Virtio block driver"
529         depends on VIRTIO
530         ---help---
531           This is the virtual block driver for virtio.  It can be used with
532           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
534 config BLK_DEV_HD
535         bool "Very old hard disk (MFM/RLL/IDE) driver"
536         depends on HAVE_IDE
537         depends on !ARM || ARCH_RPC || BROKEN
538         help
539           This is a very old hard disk driver that lacks the enhanced
540           functionality of the newer ones.
542           It is required for systems with ancient MFM/RLL/ESDI drives.
544           If unsure, say N.
546 config BLK_DEV_RBD
547         tristate "Rados block device (RBD)"
548         depends on INET && BLOCK
549         select CEPH_LIB
550         select LIBCRC32C
551         select CRYPTO_AES
552         select CRYPTO
553         default n
554         help
555           Say Y here if you want include the Rados block device, which stripes
556           a block device over objects stored in the Ceph distributed object
557           store.
559           More information at
561           If unsure, say N.
563 config BLK_DEV_RSXX
564         tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
565         depends on PCI
566         help
567           Device driver for IBM's high speed PCIe SSD
568           storage device: Flash Adapter 900GB Full Height.
570           To compile this driver as a module, choose M here: the
571           module will be called rsxx.
573 endif # BLK_DEV

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us