drivers/block/Kconfig

   1 #
   2 # Block device driver configuration
   3 #
   4
   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.
  12
  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.
  15
  16 if BLK_DEV
  17
  18 config BLK_DEV_NULL_BLK
  19         tristate "Null test block driver"
  20
  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.
  32
  33           To compile this driver as a module, choose M here: the
  34           module will be called floppy.
  35
  36 config AMIGA_FLOPPY
  37         tristate "Amiga floppy support"
  38         depends on AMIGA
  39
  40 config ATARI_FLOPPY
  41         tristate "Atari floppy support"
  42         depends on ATARI
  43
  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.
  50
  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.
  57
  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.
  65
  66           To compile this driver as a module, choose M here: the
  67           module will be called z2ram.
  68
  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.
  79
  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.
  89
  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.
  99
 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.).
 106
 107 source "drivers/block/paride/Kconfig"
 108
 109 source "drivers/block/mtip32xx/Kconfig"
 110
 111 source "drivers/block/zram/Kconfig"
 112
 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.
 122
 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.
 133
 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.)
 142
 143           "SCSI support" and "SCSI tape support" must also be enabled for this
 144           option to work.
 145
 146           When this option is disabled (N), the SCSI portion of the driver
 147           is not compiled.
 148
 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.
 157
 158           To compile this driver as a module, choose M here: the
 159           module will be called DAC960.
 160
 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           <http://www.umem.com/>
 168
 169           The cards appear as block devices that can be partitioned into
 170           as many as 15 partitions.
 171
 172           To compile this driver as a module, choose M here: the
 173           module will be called umem.
 174
 175           The umem driver has not yet been allocated a MAJOR number, so
 176           one is chosen dynamically.
 177
 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.
 186
 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.
 195
 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.
 200
 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.
 206
 207 config BLK_DEV_COW_COMMON
 208         bool
 209         default BLK_DEV_UBD
 210
 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.
 220
 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.
 227
 228           To use the loop device, you need the losetup utility, found in the
 229           util-linux package, see
 230           <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
 231
 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.
 237
 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.
 245
 246           Note that this loop device has nothing to do with the loopback
 247           device used for network connections from the machine to itself.
 248
 249           To compile this driver as a module, choose M here: the
 250           module will be called loop.
 251
 252           Most users will answer N here.
 253
 254 config BLK_DEV_LOOP_MIN_COUNT
 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.
 261
 262           This default value can be overwritten on the kernel command
 263           line or with module-parameter loop.max_loop.
 264
 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.
 268
 269 config BLK_DEV_CRYPTOLOOP
 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.
 278
 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.
 283
 284 source "drivers/block/drbd/Kconfig"
 285
 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.
 296
 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).
 300
 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.
 304
 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.
 307
 308           To compile this driver as a module, choose M here: the
 309           module will be called nbd.
 310
 311           If unsure, say N.
 312
 313 config BLK_DEV_SKD
 314         tristate "STEC S1120 Block Driver"
 315         depends on PCI
 316         depends on 64BIT
 317         ---help---
 318         Saying Y or M here will enable support for the
 319         STEC, Inc. S1120 PCIe SSD.
 320
 321         Use device /dev/skd$N amd /dev/skd$Np$M.
 322
 323 config BLK_DEV_OSD
 324         tristate "OSD object-as-blkdev support"
 325         depends on SCSI_OSD_ULD
 326         ---help---
 327           Saying Y or M here will allow the exporting of a single SCSI
 328           OSD (object-based storage) object as a Linux block device.
 329
 330           For example, if you create a 2G object on an OSD device,
 331           you can then use this module to present that 2G object as
 332           a Linux block device.
 333
 334           To compile this driver as a module, choose M here: the
 335           module will be called osdblk.
 336
 337           If unsure, say N.
 338
 339 config BLK_DEV_SX8
 340         tristate "Promise SATA SX8 support"
 341         depends on PCI
 342         ---help---
 343           Saying Y or M here will enable support for the
 344           Promise SATA SX8 controllers.
 345
 346           Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
 347
 348 config BLK_DEV_RAM
 349         tristate "RAM block device support"
 350         ---help---
 351           Saying Y here will allow you to use a portion of your RAM memory as
 352           a block device, so that you can make file systems on it, read and
 353           write to it and do all the other things that you can do with normal
 354           block devices (such as hard drives). It is usually used to load and
 355           store a copy of a minimal root file system off of a floppy into RAM
 356           during the initial install of Linux.
 357
 358           Note that the kernel command line option "ramdisk=XX" is now obsolete.
 359           For details, read <file:Documentation/blockdev/ramdisk.txt>.
 360
 361           To compile this driver as a module, choose M here: the
 362           module will be called brd. An alias "rd" has been defined
 363           for historical reasons.
 364
 365           Most normal users won't need the RAM disk functionality, and can
 366           thus say N here.
 367
 368 config BLK_DEV_RAM_COUNT
 369         int "Default number of RAM disks"
 370         default "16"
 371         depends on BLK_DEV_RAM
 372         help
 373           The default value is 16 RAM disks. Change this if you know what you
 374           are doing. If you boot from a filesystem that needs to be extracted
 375           in memory, you will need at least one RAM disk (e.g. root on cramfs).
 376
 377 config BLK_DEV_RAM_SIZE
 378         int "Default RAM disk size (kbytes)"
 379         depends on BLK_DEV_RAM
 380         default "4096"
 381         help
 382           The default value is 4096 kilobytes. Only change this if you know
 383           what you are doing.
 384
 385 config BLK_DEV_RAM_DAX
 386         bool "Support Direct Access (DAX) to RAM block devices"
 387         depends on BLK_DEV_RAM && FS_DAX
 388         default n
 389         help
 390           Support filesystems using DAX to access RAM block devices.  This
 391           avoids double-buffering data in the page cache before copying it
 392           to the block device.  Answering Y will slightly enlarge the kernel,
 393           and will prevent RAM block device backing store memory from being
 394           allocated from highmem (only a problem for highmem systems).
 395
 396 config CDROM_PKTCDVD
 397         tristate "Packet writing on CD/DVD media"
 398         depends on !UML
 399         help
 400           If you have a CDROM/DVD drive that supports packet writing, say
 401           Y to include support. It should work with any MMC/Mt Fuji
 402           compliant ATAPI or SCSI drive, which is just about any newer
 403           DVD/CD writer.
 404
 405           Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
 406           is possible.
 407           DVD-RW disks must be in restricted overwrite mode.
 408
 409           See the file <file:Documentation/cdrom/packet-writing.txt>
 410           for further information on the use of this driver.
 411
 412           To compile this driver as a module, choose M here: the
 413           module will be called pktcdvd.
 414
 415 config CDROM_PKTCDVD_BUFFERS
 416         int "Free buffers for data gathering"
 417         depends on CDROM_PKTCDVD
 418         default "8"
 419         help
 420           This controls the maximum number of active concurrent packets. More
 421           concurrent packets can increase write performance, but also require
 422           more memory. Each concurrent packet will require approximately 64Kb
 423           of non-swappable kernel memory, memory which will be allocated when
 424           a disc is opened for writing.
 425
 426 config CDROM_PKTCDVD_WCACHE
 427         bool "Enable write caching"
 428         depends on CDROM_PKTCDVD
 429         help
 430           If enabled, write caching will be set for the CD-R/W device. For now
 431           this option is dangerous unless the CD-RW media is known good, as we
 432           don't do deferred write error handling yet.
 433
 434 config ATA_OVER_ETH
 435         tristate "ATA over Ethernet support"
 436         depends on NET
 437         help
 438         This driver provides Support for ATA over Ethernet block
 439         devices like the Coraid EtherDrive (R) Storage Blade.
 440
 441 config MG_DISK
 442         tristate "mGine mflash, gflash support"
 443         depends on ARM && GPIOLIB
 444         help
 445           mGine mFlash(gFlash) block device driver
 446
 447 config MG_DISK_RES
 448         int "Size of reserved area before MBR"
 449         depends on MG_DISK
 450         default 0
 451         help
 452           Define size of reserved area that usually used for boot. Unit is KB.
 453           All of the block device operation will be taken this value as start
 454           offset
 455           Examples:
 456                         1024 => 1 MB
 457
 458 config SUNVDC
 459         tristate "Sun Virtual Disk Client support"
 460         depends on SUN_LDOMS
 461         help
 462           Support for virtual disk devices as a client under Sun
 463           Logical Domains.
 464
 465 source "drivers/s390/block/Kconfig"
 466
 467 config XILINX_SYSACE
 468         tristate "Xilinx SystemACE support"
 469         depends on 4xx || MICROBLAZE
 470         help
 471           Include support for the Xilinx SystemACE CompactFlash interface
 472
 473 config XEN_BLKDEV_FRONTEND
 474         tristate "Xen virtual block device support"
 475         depends on XEN
 476         default y
 477         select XEN_XENBUS_FRONTEND
 478         help
 479           This driver implements the front-end of the Xen virtual
 480           block device driver.  It communicates with a back-end driver
 481           in another domain which drives the actual block device.
 482
 483 config XEN_BLKDEV_BACKEND
 484         tristate "Xen block-device backend driver"
 485         depends on XEN_BACKEND
 486         help
 487           The block-device backend driver allows the kernel to export its
 488           block devices to other guests via a high-performance shared-memory
 489           interface.
 490
 491           The corresponding Linux frontend driver is enabled by the
 492           CONFIG_XEN_BLKDEV_FRONTEND configuration option.
 493
 494           The backend driver attaches itself to a any block device specified
 495           in the XenBus configuration. There are no limits to what the block
 496           device as long as it has a major and minor.
 497
 498           If you are compiling a kernel to run in a Xen block backend driver
 499           domain (often this is domain 0) you should say Y here. To
 500           compile this driver as a module, chose M here: the module
 501           will be called xen-blkback.
 502
 503
 504 config VIRTIO_BLK
 505         tristate "Virtio block driver"
 506         depends on VIRTIO
 507         ---help---
 508           This is the virtual block driver for virtio.  It can be used with
 509           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
 510
 511 config BLK_DEV_HD
 512         bool "Very old hard disk (MFM/RLL/IDE) driver"
 513         depends on HAVE_IDE
 514         depends on !ARM || ARCH_RPC || BROKEN
 515         help
 516           This is a very old hard disk driver that lacks the enhanced
 517           functionality of the newer ones.
 518
 519           It is required for systems with ancient MFM/RLL/ESDI drives.
 520
 521           If unsure, say N.
 522
 523 config BLK_DEV_RBD
 524         tristate "Rados block device (RBD)"
 525         depends on INET && BLOCK
 526         select CEPH_LIB
 527         select LIBCRC32C
 528         select CRYPTO_AES
 529         select CRYPTO
 530         default n
 531         help
 532           Say Y here if you want include the Rados block device, which stripes
 533           a block device over objects stored in the Ceph distributed object
 534           store.
 535
 536           More information at http://ceph.newdream.net/.
 537
 538           If unsure, say N.
 539
 540 config BLK_DEV_RSXX
 541         tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
 542         depends on PCI
 543         help
 544           Device driver for IBM's high speed PCIe SSD
 545           storage device: Flash Adapter 900GB Full Height.
 546
 547           To compile this driver as a module, choose M here: the
 548           module will be called rsxx.
 549
 550 endif # BLK_DEV