Version:  2.0.40 2.2.26 2.4.37 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10


  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_CISS_DA
114         tristate "Compaq Smart Array 5xxx support"
115         depends on PCI
116         select CHECK_SIGNATURE
117         help
118           This is the driver for Compaq Smart Array 5xxx controllers.
119           Everyone using these boards should say Y here.
120           See <file:Documentation/blockdev/cciss.txt> for the current list of
121           boards supported by this driver, and for further information
122           on the use of this driver.
124 config CISS_SCSI_TAPE
125         bool "SCSI tape drive support for Smart Array 5xxx"
126         depends on BLK_CPQ_CISS_DA && PROC_FS
127         depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
128         help
129           When enabled (Y), this option allows SCSI tape drives and SCSI medium
130           changers (tape robots) to be accessed via a Compaq 5xxx array 
131           controller.  (See <file:Documentation/blockdev/cciss.txt> for more details.)
133           "SCSI support" and "SCSI tape support" must also be enabled for this 
134           option to work.
136           When this option is disabled (N), the SCSI portion of the driver 
137           is not compiled.
139 config BLK_DEV_DAC960
140         tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
141         depends on PCI
142         help
143           This driver adds support for the Mylex DAC960, AcceleRAID, and
144           eXtremeRAID PCI RAID controllers.  See the file
145           <file:Documentation/blockdev/README.DAC960> for further information
146           about this driver.
148           To compile this driver as a module, choose M here: the
149           module will be called DAC960.
151 config BLK_DEV_UMEM
152         tristate "Micro Memory MM5415 Battery Backed RAM support"
153         depends on PCI
154         ---help---
155           Saying Y here will include support for the MM5415 family of
156           battery backed (Non-volatile) RAM cards.
157           <>
159           The cards appear as block devices that can be partitioned into
160           as many as 15 partitions.
162           To compile this driver as a module, choose M here: the
163           module will be called umem.
165           The umem driver has not yet been allocated a MAJOR number, so
166           one is chosen dynamically.
168 config BLK_DEV_UBD
169         bool "Virtual block device"
170         depends on UML
171         ---help---
172           The User-Mode Linux port includes a driver called UBD which will let
173           you access arbitrary files on the host computer as block devices.
174           Unless you know that you do not need such virtual block devices say
175           Y here.
177 config BLK_DEV_UBD_SYNC
178         bool "Always do synchronous disk IO for UBD"
179         depends on BLK_DEV_UBD
180         ---help---
181           Writes to the virtual block device are not immediately written to the
182           host's disk; this may cause problems if, for example, the User-Mode
183           Linux 'Virtual Machine' uses a journalling filesystem and the host
184           computer crashes.
186           Synchronous operation (i.e. always writing data to the host's disk
187           immediately) is configurable on a per-UBD basis by using a special
188           kernel command line option.  Alternatively, you can say Y here to
189           turn on synchronous operation by default for all block devices.
191           If you're running a journalling file system (like reiserfs, for
192           example) in your virtual machine, you will want to say Y here.  If
193           you care for the safety of the data in your virtual machine, Y is a
194           wise choice too.  In all other cases (for example, if you're just
195           playing around with User-Mode Linux) you can choose N.
198         bool
199         default BLK_DEV_UBD
201 config BLK_DEV_LOOP
202         tristate "Loopback device support"
203         ---help---
204           Saying Y here will allow you to use a regular file as a block
205           device; you can then create a file system on that block device and
206           mount it just as you would mount other block devices such as hard
207           drive partitions, CD-ROM drives or floppy drives. The loop devices
208           are block special device files with major number 7 and typically
209           called /dev/loop0, /dev/loop1 etc.
211           This is useful if you want to check an ISO 9660 file system before
212           burning the CD, or if you want to use floppy images without first
213           writing them to floppy. Furthermore, some Linux distributions avoid
214           the need for a dedicated Linux partition by keeping their complete
215           root file system inside a DOS FAT file using this loop device
216           driver.
218           To use the loop device, you need the losetup utility, found in the
219           util-linux package, see
220           <>.
222           The loop device driver can also be used to "hide" a file system in
223           a disk partition, floppy, or regular file, either using encryption
224           (scrambling the data) or steganography (hiding the data in the low
225           bits of, say, a sound file). This is also safe if the file resides
226           on a remote file server.
228           There are several ways of encrypting disks. Some of these require
229           kernel patches. The vanilla kernel offers the cryptoloop option
230           and a Device Mapper target (which is superior, as it supports all
231           file systems). If you want to use the cryptoloop, say Y to both
232           LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
233           or later) version of util-linux. Additionally, be aware that
234           the cryptoloop is not safe for storing journaled filesystems.
236           Note that this loop device has nothing to do with the loopback
237           device used for network connections from the machine to itself.
239           To compile this driver as a module, choose M here: the
240           module will be called loop.
242           Most users will answer N here.
245         int "Number of loop devices to pre-create at init time"
246         depends on BLK_DEV_LOOP
247         default 8
248         help
249           Static number of loop devices to be unconditionally pre-created
250           at init time.
252           This default value can be overwritten on the kernel command
253           line or with module-parameter loop.max_loop.
255           The historic default is 8. If a late 2011 version of losetup(8)
256           is used, it can be set to 0, since needed loop devices can be
257           dynamically allocated with the /dev/loop-control interface.
260         tristate "Cryptoloop Support"
261         select CRYPTO
262         select CRYPTO_CBC
263         depends on BLK_DEV_LOOP
264         ---help---
265           Say Y here if you want to be able to use the ciphers that are 
266           provided by the CryptoAPI as loop transformation. This might be
267           used as hard disk encryption.
269           WARNING: This device is not safe for journaled file systems like
270           ext3 or Reiserfs. Please use the Device Mapper crypto module
271           instead, which can be configured to be on-disk compatible with the
272           cryptoloop device.
274 source "drivers/block/drbd/Kconfig"
276 config BLK_DEV_NBD
277         tristate "Network block device support"
278         depends on NET
279         ---help---
280           Saying Y here will allow your computer to be a client for network
281           block devices, i.e. it will be able to use block devices exported by
282           servers (mount file systems on them etc.). Communication between
283           client and server works over TCP/IP networking, but to the client
284           program this is hidden: it looks like a regular local file access to
285           a block device special file such as /dev/nd0.
287           Network block devices also allows you to run a block-device in
288           userland (making server and client physically the same computer,
289           communicating using the loopback network device).
291           Read <file:Documentation/blockdev/nbd.txt> for more information,
292           especially about where to find the server code, which runs in user
293           space and does not need special kernel support.
295           Note that this has nothing to do with the network file systems NFS
296           or Coda; you can say N here even if you intend to use NFS or Coda.
298           To compile this driver as a module, choose M here: the
299           module will be called nbd.
301           If unsure, say N.
303 config BLK_DEV_SKD
304         tristate "STEC S1120 Block Driver"
305         depends on PCI
306         depends on 64BIT
307         ---help---
308         Saying Y or M here will enable support for the
309         STEC, Inc. S1120 PCIe SSD.
311         Use device /dev/skd$N amd /dev/skd$Np$M.
313 config BLK_DEV_OSD
314         tristate "OSD object-as-blkdev support"
315         depends on SCSI_OSD_ULD
316         ---help---
317           Saying Y or M here will allow the exporting of a single SCSI
318           OSD (object-based storage) object as a Linux block device.
320           For example, if you create a 2G object on an OSD device,
321           you can then use this module to present that 2G object as
322           a Linux block device.
324           To compile this driver as a module, choose M here: the
325           module will be called osdblk.
327           If unsure, say N.
329 config BLK_DEV_SX8
330         tristate "Promise SATA SX8 support"
331         depends on PCI
332         ---help---
333           Saying Y or M here will enable support for the 
334           Promise SATA SX8 controllers.
336           Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
338 config BLK_DEV_RAM
339         tristate "RAM block device support"
340         ---help---
341           Saying Y here will allow you to use a portion of your RAM memory as
342           a block device, so that you can make file systems on it, read and
343           write to it and do all the other things that you can do with normal
344           block devices (such as hard drives). It is usually used to load and
345           store a copy of a minimal root file system off of a floppy into RAM
346           during the initial install of Linux.
348           Note that the kernel command line option "ramdisk=XX" is now obsolete.
349           For details, read <file:Documentation/blockdev/ramdisk.txt>.
351           To compile this driver as a module, choose M here: the
352           module will be called brd. An alias "rd" has been defined
353           for historical reasons.
355           Most normal users won't need the RAM disk functionality, and can
356           thus say N here.
358 config BLK_DEV_RAM_COUNT
359         int "Default number of RAM disks"
360         default "16"
361         depends on BLK_DEV_RAM
362         help
363           The default value is 16 RAM disks. Change this if you know what you
364           are doing. If you boot from a filesystem that needs to be extracted
365           in memory, you will need at least one RAM disk (e.g. root on cramfs).
367 config BLK_DEV_RAM_SIZE
368         int "Default RAM disk size (kbytes)"
369         depends on BLK_DEV_RAM
370         default "4096"
371         help
372           The default value is 4096 kilobytes. Only change this if you know
373           what you are doing.
375 config BLK_DEV_RAM_DAX
376         bool "Support Direct Access (DAX) to RAM block devices"
377         depends on BLK_DEV_RAM && FS_DAX
378         default n
379         help
380           Support filesystems using DAX to access RAM block devices.  This
381           avoids double-buffering data in the page cache before copying it
382           to the block device.  Answering Y will slightly enlarge the kernel,
383           and will prevent RAM block device backing store memory from being
384           allocated from highmem (only a problem for highmem systems).
386 config CDROM_PKTCDVD
387         tristate "Packet writing on CD/DVD media (DEPRECATED)"
388         depends on !UML
389         help
390           Note: This driver is deprecated and will be removed from the
391           kernel in the near future!
393           If you have a CDROM/DVD drive that supports packet writing, say
394           Y to include support. It should work with any MMC/Mt Fuji
395           compliant ATAPI or SCSI drive, which is just about any newer
396           DVD/CD writer.
398           Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
399           is possible.
400           DVD-RW disks must be in restricted overwrite mode.
402           See the file <file:Documentation/cdrom/packet-writing.txt>
403           for further information on the use of this driver.
405           To compile this driver as a module, choose M here: the
406           module will be called pktcdvd.
409         int "Free buffers for data gathering"
410         depends on CDROM_PKTCDVD
411         default "8"
412         help
413           This controls the maximum number of active concurrent packets. More
414           concurrent packets can increase write performance, but also require
415           more memory. Each concurrent packet will require approximately 64Kb
416           of non-swappable kernel memory, memory which will be allocated when
417           a disc is opened for writing.
420         bool "Enable write caching"
421         depends on CDROM_PKTCDVD
422         help
423           If enabled, write caching will be set for the CD-R/W device. For now
424           this option is dangerous unless the CD-RW media is known good, as we
425           don't do deferred write error handling yet.
427 config ATA_OVER_ETH
428         tristate "ATA over Ethernet support"
429         depends on NET
430         help
431         This driver provides Support for ATA over Ethernet block
432         devices like the Coraid EtherDrive (R) Storage Blade.
434 config MG_DISK
435         tristate "mGine mflash, gflash support"
436         depends on ARM && GPIOLIB
437         help
438           mGine mFlash(gFlash) block device driver
440 config MG_DISK_RES
441         int "Size of reserved area before MBR"
442         depends on MG_DISK
443         default 0
444         help
445           Define size of reserved area that usually used for boot. Unit is KB.
446           All of the block device operation will be taken this value as start
447           offset
448           Examples:
449                         1024 => 1 MB
451 config SUNVDC
452         tristate "Sun Virtual Disk Client support"
453         depends on SUN_LDOMS
454         help
455           Support for virtual disk devices as a client under Sun
456           Logical Domains.
458 source "drivers/s390/block/Kconfig"
460 config XILINX_SYSACE
461         tristate "Xilinx SystemACE support"
462         depends on 4xx || MICROBLAZE
463         help
464           Include support for the Xilinx SystemACE CompactFlash interface
467         tristate "Xen virtual block device support"
468         depends on XEN
469         default y
470         select XEN_XENBUS_FRONTEND
471         help
472           This driver implements the front-end of the Xen virtual
473           block device driver.  It communicates with a back-end driver
474           in another domain which drives the actual block device.
477         tristate "Xen block-device backend driver"
478         depends on XEN_BACKEND
479         help
480           The block-device backend driver allows the kernel to export its
481           block devices to other guests via a high-performance shared-memory
482           interface.
484           The corresponding Linux frontend driver is enabled by the
485           CONFIG_XEN_BLKDEV_FRONTEND configuration option.
487           The backend driver attaches itself to a any block device specified
488           in the XenBus configuration. There are no limits to what the block
489           device as long as it has a major and minor.
491           If you are compiling a kernel to run in a Xen block backend driver
492           domain (often this is domain 0) you should say Y here. To
493           compile this driver as a module, chose M here: the module
494           will be called xen-blkback.
497 config VIRTIO_BLK
498         tristate "Virtio block driver"
499         depends on VIRTIO
500         ---help---
501           This is the virtual block driver for virtio.  It can be used with
502           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
504 config BLK_DEV_HD
505         bool "Very old hard disk (MFM/RLL/IDE) driver"
506         depends on HAVE_IDE
507         depends on !ARM || ARCH_RPC || BROKEN
508         help
509           This is a very old hard disk driver that lacks the enhanced
510           functionality of the newer ones.
512           It is required for systems with ancient MFM/RLL/ESDI drives.
514           If unsure, say N.
516 config BLK_DEV_RBD
517         tristate "Rados block device (RBD)"
518         depends on INET && BLOCK
519         select CEPH_LIB
520         select LIBCRC32C
521         select CRYPTO_AES
522         select CRYPTO
523         default n
524         help
525           Say Y here if you want include the Rados block device, which stripes
526           a block device over objects stored in the Ceph distributed object
527           store.
529           More information at
531           If unsure, say N.
533 config BLK_DEV_RSXX
534         tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
535         depends on PCI
536         help
537           Device driver for IBM's high speed PCIe SSD
538           storage device: Flash Adapter 900GB Full Height.
540           To compile this driver as a module, choose M here: the
541           module will be called rsxx.
543 endif # BLK_DEV

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