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         select BLK_SCSI_REQUEST # only for the generic cdrom code
  73         help
  74           A standard SEGA Dreamcast comes with a modified CD ROM drive called a
  75           "GD-ROM" by SEGA to signify it is capable of reading special disks
  76           with up to 1 GB of data. This drive will also read standard CD ROM
  77           disks. Select this option to access any disks in your GD ROM drive.
  78           Most users will want to say "Y" here.
  79           You can also build this as a module which will be called gdrom.
  80
  81 config PARIDE
  82         tristate "Parallel port IDE device support"
  83         depends on PARPORT_PC
  84         ---help---
  85           There are many external CD-ROM and disk devices that connect through
  86           your computer's parallel port. Most of them are actually IDE devices
  87           using a parallel port IDE adapter. This option enables the PARIDE
  88           subsystem which contains drivers for many of these external drives.
  89           Read <file:Documentation/blockdev/paride.txt> for more information.
  90
  91           If you have said Y to the "Parallel-port support" configuration
  92           option, you may share a single port between your printer and other
  93           parallel port devices. Answer Y to build PARIDE support into your
  94           kernel, or M if you would like to build it as a loadable module. If
  95           your parallel port support is in a loadable module, you must build
  96           PARIDE as a module. If you built PARIDE support into your kernel,
  97           you may still build the individual protocol modules and high-level
  98           drivers as loadable modules. If you build this support as a module,
  99           it will be called paride.
 100
 101           To use the PARIDE support, you must say Y or M here and also to at
 102           least one high-level driver (e.g. "Parallel port IDE disks",
 103           "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
 104           to at least one protocol driver (e.g. "ATEN EH-100 protocol",
 105           "MicroSolutions backpack protocol", "DataStor Commuter protocol"
 106           etc.).
 107
 108 source "drivers/block/paride/Kconfig"
 109
 110 source "drivers/block/mtip32xx/Kconfig"
 111
 112 source "drivers/block/zram/Kconfig"
 113
 114 config BLK_CPQ_CISS_DA
 115         tristate "Compaq Smart Array 5xxx support"
 116         depends on PCI
 117         select CHECK_SIGNATURE
 118         select BLK_SCSI_REQUEST
 119         help
 120           This is the driver for Compaq Smart Array 5xxx controllers.
 121           Everyone using these boards should say Y here.
 122           See <file:Documentation/blockdev/cciss.txt> for the current list of
 123           boards supported by this driver, and for further information
 124           on the use of this driver.
 125
 126 config CISS_SCSI_TAPE
 127         bool "SCSI tape drive support for Smart Array 5xxx"
 128         depends on BLK_CPQ_CISS_DA && PROC_FS
 129         depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
 130         help
 131           When enabled (Y), this option allows SCSI tape drives and SCSI medium
 132           changers (tape robots) to be accessed via a Compaq 5xxx array
 133           controller.  (See <file:Documentation/blockdev/cciss.txt> for more details.)
 134
 135           "SCSI support" and "SCSI tape support" must also be enabled for this
 136           option to work.
 137
 138           When this option is disabled (N), the SCSI portion of the driver
 139           is not compiled.
 140
 141 config BLK_DEV_DAC960
 142         tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
 143         depends on PCI
 144         help
 145           This driver adds support for the Mylex DAC960, AcceleRAID, and
 146           eXtremeRAID PCI RAID controllers.  See the file
 147           <file:Documentation/blockdev/README.DAC960> for further information
 148           about this driver.
 149
 150           To compile this driver as a module, choose M here: the
 151           module will be called DAC960.
 152
 153 config BLK_DEV_UMEM
 154         tristate "Micro Memory MM5415 Battery Backed RAM support"
 155         depends on PCI
 156         ---help---
 157           Saying Y here will include support for the MM5415 family of
 158           battery backed (Non-volatile) RAM cards.
 159           <http://www.umem.com/>
 160
 161           The cards appear as block devices that can be partitioned into
 162           as many as 15 partitions.
 163
 164           To compile this driver as a module, choose M here: the
 165           module will be called umem.
 166
 167           The umem driver has not yet been allocated a MAJOR number, so
 168           one is chosen dynamically.
 169
 170 config BLK_DEV_UBD
 171         bool "Virtual block device"
 172         depends on UML
 173         ---help---
 174           The User-Mode Linux port includes a driver called UBD which will let
 175           you access arbitrary files on the host computer as block devices.
 176           Unless you know that you do not need such virtual block devices say
 177           Y here.
 178
 179 config BLK_DEV_UBD_SYNC
 180         bool "Always do synchronous disk IO for UBD"
 181         depends on BLK_DEV_UBD
 182         ---help---
 183           Writes to the virtual block device are not immediately written to the
 184           host's disk; this may cause problems if, for example, the User-Mode
 185           Linux 'Virtual Machine' uses a journalling filesystem and the host
 186           computer crashes.
 187
 188           Synchronous operation (i.e. always writing data to the host's disk
 189           immediately) is configurable on a per-UBD basis by using a special
 190           kernel command line option.  Alternatively, you can say Y here to
 191           turn on synchronous operation by default for all block devices.
 192
 193           If you're running a journalling file system (like reiserfs, for
 194           example) in your virtual machine, you will want to say Y here.  If
 195           you care for the safety of the data in your virtual machine, Y is a
 196           wise choice too.  In all other cases (for example, if you're just
 197           playing around with User-Mode Linux) you can choose N.
 198
 199 config BLK_DEV_COW_COMMON
 200         bool
 201         default BLK_DEV_UBD
 202
 203 config BLK_DEV_LOOP
 204         tristate "Loopback device support"
 205         ---help---
 206           Saying Y here will allow you to use a regular file as a block
 207           device; you can then create a file system on that block device and
 208           mount it just as you would mount other block devices such as hard
 209           drive partitions, CD-ROM drives or floppy drives. The loop devices
 210           are block special device files with major number 7 and typically
 211           called /dev/loop0, /dev/loop1 etc.
 212
 213           This is useful if you want to check an ISO 9660 file system before
 214           burning the CD, or if you want to use floppy images without first
 215           writing them to floppy. Furthermore, some Linux distributions avoid
 216           the need for a dedicated Linux partition by keeping their complete
 217           root file system inside a DOS FAT file using this loop device
 218           driver.
 219
 220           To use the loop device, you need the losetup utility, found in the
 221           util-linux package, see
 222           <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
 223
 224           The loop device driver can also be used to "hide" a file system in
 225           a disk partition, floppy, or regular file, either using encryption
 226           (scrambling the data) or steganography (hiding the data in the low
 227           bits of, say, a sound file). This is also safe if the file resides
 228           on a remote file server.
 229
 230           There are several ways of encrypting disks. Some of these require
 231           kernel patches. The vanilla kernel offers the cryptoloop option
 232           and a Device Mapper target (which is superior, as it supports all
 233           file systems). If you want to use the cryptoloop, say Y to both
 234           LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
 235           or later) version of util-linux. Additionally, be aware that
 236           the cryptoloop is not safe for storing journaled filesystems.
 237
 238           Note that this loop device has nothing to do with the loopback
 239           device used for network connections from the machine to itself.
 240
 241           To compile this driver as a module, choose M here: the
 242           module will be called loop.
 243
 244           Most users will answer N here.
 245
 246 config BLK_DEV_LOOP_MIN_COUNT
 247         int "Number of loop devices to pre-create at init time"
 248         depends on BLK_DEV_LOOP
 249         default 8
 250         help
 251           Static number of loop devices to be unconditionally pre-created
 252           at init time.
 253
 254           This default value can be overwritten on the kernel command
 255           line or with module-parameter loop.max_loop.
 256
 257           The historic default is 8. If a late 2011 version of losetup(8)
 258           is used, it can be set to 0, since needed loop devices can be
 259           dynamically allocated with the /dev/loop-control interface.
 260
 261 config BLK_DEV_CRYPTOLOOP
 262         tristate "Cryptoloop Support"
 263         select CRYPTO
 264         select CRYPTO_CBC
 265         depends on BLK_DEV_LOOP
 266         ---help---
 267           Say Y here if you want to be able to use the ciphers that are
 268           provided by the CryptoAPI as loop transformation. This might be
 269           used as hard disk encryption.
 270
 271           WARNING: This device is not safe for journaled file systems like
 272           ext3 or Reiserfs. Please use the Device Mapper crypto module
 273           instead, which can be configured to be on-disk compatible with the
 274           cryptoloop device.
 275
 276 source "drivers/block/drbd/Kconfig"
 277
 278 config BLK_DEV_NBD
 279         tristate "Network block device support"
 280         depends on NET
 281         ---help---
 282           Saying Y here will allow your computer to be a client for network
 283           block devices, i.e. it will be able to use block devices exported by
 284           servers (mount file systems on them etc.). Communication between
 285           client and server works over TCP/IP networking, but to the client
 286           program this is hidden: it looks like a regular local file access to
 287           a block device special file such as /dev/nd0.
 288
 289           Network block devices also allows you to run a block-device in
 290           userland (making server and client physically the same computer,
 291           communicating using the loopback network device).
 292
 293           Read <file:Documentation/blockdev/nbd.txt> for more information,
 294           especially about where to find the server code, which runs in user
 295           space and does not need special kernel support.
 296
 297           Note that this has nothing to do with the network file systems NFS
 298           or Coda; you can say N here even if you intend to use NFS or Coda.
 299
 300           To compile this driver as a module, choose M here: the
 301           module will be called nbd.
 302
 303           If unsure, say N.
 304
 305 config BLK_DEV_SKD
 306         tristate "STEC S1120 Block Driver"
 307         depends on PCI
 308         depends on 64BIT
 309         ---help---
 310         Saying Y or M here will enable support for the
 311         STEC, Inc. S1120 PCIe SSD.
 312
 313         Use device /dev/skd$N amd /dev/skd$Np$M.
 314
 315 config BLK_DEV_OSD
 316         tristate "OSD object-as-blkdev support"
 317         depends on SCSI_OSD_ULD
 318         ---help---
 319           Saying Y or M here will allow the exporting of a single SCSI
 320           OSD (object-based storage) object as a Linux block device.
 321
 322           For example, if you create a 2G object on an OSD device,
 323           you can then use this module to present that 2G object as
 324           a Linux block device.
 325
 326           To compile this driver as a module, choose M here: the
 327           module will be called osdblk.
 328
 329           If unsure, say N.
 330
 331 config BLK_DEV_SX8
 332         tristate "Promise SATA SX8 support"
 333         depends on PCI
 334         ---help---
 335           Saying Y or M here will enable support for the
 336           Promise SATA SX8 controllers.
 337
 338           Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
 339
 340 config BLK_DEV_RAM
 341         tristate "RAM block device support"
 342         ---help---
 343           Saying Y here will allow you to use a portion of your RAM memory as
 344           a block device, so that you can make file systems on it, read and
 345           write to it and do all the other things that you can do with normal
 346           block devices (such as hard drives). It is usually used to load and
 347           store a copy of a minimal root file system off of a floppy into RAM
 348           during the initial install of Linux.
 349
 350           Note that the kernel command line option "ramdisk=XX" is now obsolete.
 351           For details, read <file:Documentation/blockdev/ramdisk.txt>.
 352
 353           To compile this driver as a module, choose M here: the
 354           module will be called brd. An alias "rd" has been defined
 355           for historical reasons.
 356
 357           Most normal users won't need the RAM disk functionality, and can
 358           thus say N here.
 359
 360 config BLK_DEV_RAM_COUNT
 361         int "Default number of RAM disks"
 362         default "16"
 363         depends on BLK_DEV_RAM
 364         help
 365           The default value is 16 RAM disks. Change this if you know what you
 366           are doing. If you boot from a filesystem that needs to be extracted
 367           in memory, you will need at least one RAM disk (e.g. root on cramfs).
 368
 369 config BLK_DEV_RAM_SIZE
 370         int "Default RAM disk size (kbytes)"
 371         depends on BLK_DEV_RAM
 372         default "4096"
 373         help
 374           The default value is 4096 kilobytes. Only change this if you know
 375           what you are doing.
 376
 377 config BLK_DEV_RAM_DAX
 378         bool "Support Direct Access (DAX) to RAM block devices"
 379         depends on BLK_DEV_RAM && FS_DAX
 380         default n
 381         help
 382           Support filesystems using DAX to access RAM block devices.  This
 383           avoids double-buffering data in the page cache before copying it
 384           to the block device.  Answering Y will slightly enlarge the kernel,
 385           and will prevent RAM block device backing store memory from being
 386           allocated from highmem (only a problem for highmem systems).
 387
 388 config CDROM_PKTCDVD
 389         tristate "Packet writing on CD/DVD media (DEPRECATED)"
 390         depends on !UML
 391         select BLK_SCSI_REQUEST
 392         help
 393           Note: This driver is deprecated and will be removed from the
 394           kernel in the near future!
 395
 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
 399           DVD/CD writer.
 400
 401           Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
 402           is possible.
 403           DVD-RW disks must be in restricted overwrite mode.
 404
 405           See the file <file:Documentation/cdrom/packet-writing.txt>
 406           for further information on the use of this driver.
 407
 408           To compile this driver as a module, choose M here: the
 409           module will be called pktcdvd.
 410
 411 config CDROM_PKTCDVD_BUFFERS
 412         int "Free buffers for data gathering"
 413         depends on CDROM_PKTCDVD
 414         default "8"
 415         help
 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.
 421
 422 config CDROM_PKTCDVD_WCACHE
 423         bool "Enable write caching"
 424         depends on CDROM_PKTCDVD
 425         help
 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.
 429
 430 config ATA_OVER_ETH
 431         tristate "ATA over Ethernet support"
 432         depends on NET
 433         help
 434         This driver provides Support for ATA over Ethernet block
 435         devices like the Coraid EtherDrive (R) Storage Blade.
 436
 437 config MG_DISK
 438         tristate "mGine mflash, gflash support"
 439         depends on ARM && GPIOLIB
 440         help
 441           mGine mFlash(gFlash) block device driver
 442
 443 config MG_DISK_RES
 444         int "Size of reserved area before MBR"
 445         depends on MG_DISK
 446         default 0
 447         help
 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
 450           offset
 451           Examples:
 452                         1024 => 1 MB
 453
 454 config SUNVDC
 455         tristate "Sun Virtual Disk Client support"
 456         depends on SUN_LDOMS
 457         help
 458           Support for virtual disk devices as a client under Sun
 459           Logical Domains.
 460
 461 source "drivers/s390/block/Kconfig"
 462
 463 config XILINX_SYSACE
 464         tristate "Xilinx SystemACE support"
 465         depends on 4xx || MICROBLAZE
 466         help
 467           Include support for the Xilinx SystemACE CompactFlash interface
 468
 469 config XEN_BLKDEV_FRONTEND
 470         tristate "Xen virtual block device support"
 471         depends on XEN
 472         default y
 473         select XEN_XENBUS_FRONTEND
 474         help
 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.
 478
 479 config XEN_BLKDEV_BACKEND
 480         tristate "Xen block-device backend driver"
 481         depends on XEN_BACKEND
 482         help
 483           The block-device backend driver allows the kernel to export its
 484           block devices to other guests via a high-performance shared-memory
 485           interface.
 486
 487           The corresponding Linux frontend driver is enabled by the
 488           CONFIG_XEN_BLKDEV_FRONTEND configuration option.
 489
 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.
 493
 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.
 498
 499
 500 config VIRTIO_BLK
 501         tristate "Virtio block driver"
 502         depends on VIRTIO
 503         select BLK_SCSI_REQUEST
 504         ---help---
 505           This is the virtual block driver for virtio.  It can be used with
 506           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
 507
 508 config BLK_DEV_HD
 509         bool "Very old hard disk (MFM/RLL/IDE) driver"
 510         depends on HAVE_IDE
 511         depends on !ARM || ARCH_RPC || BROKEN
 512         help
 513           This is a very old hard disk driver that lacks the enhanced
 514           functionality of the newer ones.
 515
 516           It is required for systems with ancient MFM/RLL/ESDI drives.
 517
 518           If unsure, say N.
 519
 520 config BLK_DEV_RBD
 521         tristate "Rados block device (RBD)"
 522         depends on INET && BLOCK
 523         select CEPH_LIB
 524         select LIBCRC32C
 525         select CRYPTO_AES
 526         select CRYPTO
 527         default n
 528         help
 529           Say Y here if you want include the Rados block device, which stripes
 530           a block device over objects stored in the Ceph distributed object
 531           store.
 532
 533           More information at http://ceph.newdream.net/.
 534
 535           If unsure, say N.
 536
 537 config BLK_DEV_RSXX
 538         tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
 539         depends on PCI
 540         help
 541           Device driver for IBM's high speed PCIe SSD
 542           storage device: Flash Adapter 900GB Full Height.
 543
 544           To compile this driver as a module, choose M here: the
 545           module will be called rsxx.
 546
 547 endif # BLK_DEV