drivers/block/Kconfig

   1 #
   2 # Block device driver configuration
   3 #
   4
   5 if BLOCK
   6
   7 menu "Block devices"
   8
   9 config BLK_DEV_FD
  10         tristate "Normal floppy disk support"
  11         depends on ARCH_MAY_HAVE_PC_FDC
  12         ---help---
  13           If you want to use the floppy disk drive(s) of your PC under Linux,
  14           say Y. Information about this driver, especially important for IBM
  15           Thinkpad users, is contained in <file:Documentation/floppy.txt>.
  16           That file also contains the location of the Floppy driver FAQ as
  17           well as location of the fdutils package used to configure additional
  18           parameters of the driver at run time.
  19
  20           To compile this driver as a module, choose M here: the
  21           module will be called floppy.
  22
  23 config AMIGA_FLOPPY
  24         tristate "Amiga floppy support"
  25         depends on AMIGA
  26
  27 config ATARI_FLOPPY
  28         tristate "Atari floppy support"
  29         depends on ATARI
  30
  31 config BLK_DEV_SWIM_IOP
  32         bool "Macintosh IIfx/Quadra 900/Quadra 950 floppy support (EXPERIMENTAL)"
  33         depends on MAC && EXPERIMENTAL && BROKEN
  34         help
  35           Say Y here to support the SWIM (Super Woz Integrated Machine) IOP
  36           floppy controller on the Macintosh IIfx and Quadra 900/950.
  37
  38 config MAC_FLOPPY
  39         tristate "Support for PowerMac floppy"
  40         depends on PPC_PMAC && !PPC_PMAC64
  41         help
  42           If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
  43           floppy controller, say Y here. Most commonly found in PowerMacs.
  44
  45 config BLK_DEV_PS2
  46         tristate "PS/2 ESDI hard disk support"
  47         depends on MCA && MCA_LEGACY && BROKEN
  48         help
  49           Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
  50           hard disk.
  51
  52           To compile this driver as a module, choose M here: the
  53           module will be called ps2esdi.
  54
  55 config AMIGA_Z2RAM
  56         tristate "Amiga Zorro II ramdisk support"
  57         depends on ZORRO
  58         help
  59           This enables support for using Chip RAM and Zorro II RAM as a
  60           ramdisk or as a swap partition. Say Y if you want to include this
  61           driver in the kernel.
  62
  63           To compile this driver as a module, choose M here: the
  64           module will be called z2ram.
  65
  66 config ATARI_ACSI
  67         tristate "Atari ACSI support"
  68         depends on ATARI && BROKEN
  69         ---help---
  70           This enables support for the Atari ACSI interface. The driver
  71           supports hard disks and CD-ROMs, which have 512-byte sectors, or can
  72           be switched to that mode. Due to the ACSI command format, only disks
  73           up to 1 GB are supported. Special support for certain ACSI to SCSI
  74           adapters, which could relax that, isn't included yet. The ACSI
  75           driver is also the basis for certain other drivers for devices
  76           attached to the ACSI bus: Atari SLM laser printer, BioNet-100
  77           Ethernet, and PAMsNet Ethernet. If you want to use one of these
  78           devices, you need ACSI support, too.
  79
  80           To compile this driver as a module, choose M here: the
  81           module will be called acsi.
  82
  83 comment "Some devices (e.g. CD jukebox) support multiple LUNs"
  84         depends on ATARI && ATARI_ACSI
  85
  86 config ACSI_MULTI_LUN
  87         bool "Probe all LUNs on each ACSI device"
  88         depends on ATARI_ACSI
  89         help
  90           If you have a ACSI device that supports more than one LUN (Logical
  91           Unit Number), e.g. a CD jukebox, you should say Y here so that all
  92           will be found by the ACSI driver. An ACSI device with multiple LUNs
  93           acts logically like multiple ACSI devices. The vast majority of ACSI
  94           devices have only one LUN, and so most people can say N here and
  95           should in fact do so, because it is safer.
  96
  97 config ATARI_SLM
  98         tristate "Atari SLM laser printer support"
  99         depends on ATARI && ATARI_ACSI!=n
 100         help
 101           If you have an Atari SLM laser printer, say Y to include support for
 102           it in the kernel. Otherwise, say N. This driver is also available as
 103           a module ( = code which can be inserted in and removed from the
 104           running kernel whenever you want). The module will be called
 105           acsi_slm. Be warned: the driver needs much ST-RAM and can cause
 106           problems due to that fact!
 107
 108 config BLK_DEV_XD
 109         tristate "XT hard disk support"
 110         depends on ISA && ISA_DMA_API
 111         help
 112           Very old 8 bit hard disk controllers used in the IBM XT computer
 113           will be supported if you say Y here.
 114
 115           To compile this driver as a module, choose M here: the
 116           module will be called xd.
 117
 118           It's pretty unlikely that you have one of these: say N.
 119
 120 config PARIDE
 121         tristate "Parallel port IDE device support"
 122         depends on PARPORT_PC
 123         ---help---
 124           There are many external CD-ROM and disk devices that connect through
 125           your computer's parallel port. Most of them are actually IDE devices
 126           using a parallel port IDE adapter. This option enables the PARIDE
 127           subsystem which contains drivers for many of these external drives.
 128           Read <file:Documentation/paride.txt> for more information.
 129
 130           If you have said Y to the "Parallel-port support" configuration
 131           option, you may share a single port between your printer and other
 132           parallel port devices. Answer Y to build PARIDE support into your
 133           kernel, or M if you would like to build it as a loadable module. If
 134           your parallel port support is in a loadable module, you must build
 135           PARIDE as a module. If you built PARIDE support into your kernel,
 136           you may still build the individual protocol modules and high-level
 137           drivers as loadable modules. If you build this support as a module,
 138           it will be called paride.
 139
 140           To use the PARIDE support, you must say Y or M here and also to at
 141           least one high-level driver (e.g. "Parallel port IDE disks",
 142           "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
 143           to at least one protocol driver (e.g. "ATEN EH-100 protocol",
 144           "MicroSolutions backpack protocol", "DataStor Commuter protocol"
 145           etc.).
 146
 147 source "drivers/block/paride/Kconfig"
 148
 149 config BLK_CPQ_DA
 150         tristate "Compaq SMART2 support"
 151         depends on PCI
 152         help
 153           This is the driver for Compaq Smart Array controllers.  Everyone
 154           using these boards should say Y here.  See the file
 155           <file:Documentation/cpqarray.txt> for the current list of boards
 156           supported by this driver, and for further information on the use of
 157           this driver.
 158
 159 config BLK_CPQ_CISS_DA
 160         tristate "Compaq Smart Array 5xxx support"
 161         depends on PCI
 162         help
 163           This is the driver for Compaq Smart Array 5xxx controllers.
 164           Everyone using these boards should say Y here.
 165           See <file:Documentation/cciss.txt> for the current list of
 166           boards supported by this driver, and for further information
 167           on the use of this driver.
 168
 169 config CISS_SCSI_TAPE
 170         bool "SCSI tape drive support for Smart Array 5xxx"
 171         depends on BLK_CPQ_CISS_DA && SCSI && PROC_FS
 172         help
 173           When enabled (Y), this option allows SCSI tape drives and SCSI medium
 174           changers (tape robots) to be accessed via a Compaq 5xxx array
 175           controller.  (See <file:Documentation/cciss.txt> for more details.)
 176
 177           "SCSI support" and "SCSI tape support" must also be enabled for this
 178           option to work.
 179
 180           When this option is disabled (N), the SCSI portion of the driver
 181           is not compiled.
 182
 183 config BLK_DEV_DAC960
 184         tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
 185         depends on PCI
 186         help
 187           This driver adds support for the Mylex DAC960, AcceleRAID, and
 188           eXtremeRAID PCI RAID controllers.  See the file
 189           <file:Documentation/README.DAC960> for further information about
 190           this driver.
 191
 192           To compile this driver as a module, choose M here: the
 193           module will be called DAC960.
 194
 195 config BLK_DEV_UMEM
 196         tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
 197         depends on PCI && EXPERIMENTAL
 198         ---help---
 199           Saying Y here will include support for the MM5415 family of
 200           battery backed (Non-volatile) RAM cards.
 201           <http://www.umem.com/>
 202
 203           The cards appear as block devices that can be partitioned into
 204           as many as 15 partitions.
 205
 206           To compile this driver as a module, choose M here: the
 207           module will be called umem.
 208
 209           The umem driver has not yet been allocated a MAJOR number, so
 210           one is chosen dynamically.
 211
 212 config BLK_DEV_UBD
 213         bool "Virtual block device"
 214         depends on UML
 215         ---help---
 216           The User-Mode Linux port includes a driver called UBD which will let
 217           you access arbitrary files on the host computer as block devices.
 218           Unless you know that you do not need such virtual block devices say
 219           Y here.
 220
 221 config BLK_DEV_UBD_SYNC
 222         bool "Always do synchronous disk IO for UBD"
 223         depends on BLK_DEV_UBD
 224         ---help---
 225           Writes to the virtual block device are not immediately written to the
 226           host's disk; this may cause problems if, for example, the User-Mode
 227           Linux 'Virtual Machine' uses a journalling filesystem and the host
 228           computer crashes.
 229
 230           Synchronous operation (i.e. always writing data to the host's disk
 231           immediately) is configurable on a per-UBD basis by using a special
 232           kernel command line option.  Alternatively, you can say Y here to
 233           turn on synchronous operation by default for all block devices.
 234
 235           If you're running a journalling file system (like reiserfs, for
 236           example) in your virtual machine, you will want to say Y here.  If
 237           you care for the safety of the data in your virtual machine, Y is a
 238           wise choice too.  In all other cases (for example, if you're just
 239           playing around with User-Mode Linux) you can choose N.
 240
 241 config BLK_DEV_COW_COMMON
 242         bool
 243         default BLK_DEV_UBD
 244
 245 config MMAPPER
 246         tristate "Example IO memory driver (BROKEN)"
 247         depends on UML && BROKEN
 248         ---help---
 249           The User-Mode Linux port can provide support for IO Memory
 250           emulation with this option.  This allows a host file to be
 251           specified as an I/O region on the kernel command line. That file
 252           will be mapped into UML's kernel address space where a driver can
 253           locate it and do whatever it wants with the memory, including
 254           providing an interface to it for UML processes to use.
 255
 256           For more information, see
 257           <http://user-mode-linux.sourceforge.net/iomem.html>.
 258
 259           If you'd like to be able to provide a simulated IO port space for
 260           User-Mode Linux processes, say Y.  If unsure, say N.
 261
 262 config BLK_DEV_LOOP
 263         tristate "Loopback device support"
 264         ---help---
 265           Saying Y here will allow you to use a regular file as a block
 266           device; you can then create a file system on that block device and
 267           mount it just as you would mount other block devices such as hard
 268           drive partitions, CD-ROM drives or floppy drives. The loop devices
 269           are block special device files with major number 7 and typically
 270           called /dev/loop0, /dev/loop1 etc.
 271
 272           This is useful if you want to check an ISO 9660 file system before
 273           burning the CD, or if you want to use floppy images without first
 274           writing them to floppy. Furthermore, some Linux distributions avoid
 275           the need for a dedicated Linux partition by keeping their complete
 276           root file system inside a DOS FAT file using this loop device
 277           driver.
 278
 279           To use the loop device, you need the losetup utility, found in the
 280           util-linux package, see
 281           <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
 282
 283           The loop device driver can also be used to "hide" a file system in
 284           a disk partition, floppy, or regular file, either using encryption
 285           (scrambling the data) or steganography (hiding the data in the low
 286           bits of, say, a sound file). This is also safe if the file resides
 287           on a remote file server.
 288
 289           There are several ways of encrypting disks. Some of these require
 290           kernel patches. The vanilla kernel offers the cryptoloop option
 291           and a Device Mapper target (which is superior, as it supports all
 292           file systems). If you want to use the cryptoloop, say Y to both
 293           LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
 294           or later) version of util-linux. Additionally, be aware that
 295           the cryptoloop is not safe for storing journaled filesystems.
 296
 297           Note that this loop device has nothing to do with the loopback
 298           device used for network connections from the machine to itself.
 299
 300           To compile this driver as a module, choose M here: the
 301           module will be called loop.
 302
 303           Most users will answer N here.
 304
 305 config BLK_DEV_CRYPTOLOOP
 306         tristate "Cryptoloop Support"
 307         select CRYPTO
 308         depends on BLK_DEV_LOOP
 309         ---help---
 310           Say Y here if you want to be able to use the ciphers that are
 311           provided by the CryptoAPI as loop transformation. This might be
 312           used as hard disk encryption.
 313
 314           WARNING: This device is not safe for journaled file systems like
 315           ext3 or Reiserfs. Please use the Device Mapper crypto module
 316           instead, which can be configured to be on-disk compatible with the
 317           cryptoloop device.
 318
 319 config BLK_DEV_NBD
 320         tristate "Network block device support"
 321         depends on NET
 322         ---help---
 323           Saying Y here will allow your computer to be a client for network
 324           block devices, i.e. it will be able to use block devices exported by
 325           servers (mount file systems on them etc.). Communication between
 326           client and server works over TCP/IP networking, but to the client
 327           program this is hidden: it looks like a regular local file access to
 328           a block device special file such as /dev/nd0.
 329
 330           Network block devices also allows you to run a block-device in
 331           userland (making server and client physically the same computer,
 332           communicating using the loopback network device).
 333
 334           Read <file:Documentation/nbd.txt> for more information, especially
 335           about where to find the server code, which runs in user space and
 336           does not need special kernel support.
 337
 338           Note that this has nothing to do with the network file systems NFS
 339           or Coda; you can say N here even if you intend to use NFS or Coda.
 340
 341           To compile this driver as a module, choose M here: the
 342           module will be called nbd.
 343
 344           If unsure, say N.
 345
 346 config BLK_DEV_SX8
 347         tristate "Promise SATA SX8 support"
 348         depends on PCI
 349         ---help---
 350           Saying Y or M here will enable support for the
 351           Promise SATA SX8 controllers.
 352
 353           Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
 354
 355 config BLK_DEV_UB
 356         tristate "Low Performance USB Block driver"
 357         depends on USB
 358         help
 359           This driver supports certain USB attached storage devices
 360           such as flash keys.
 361
 362           If you enable this driver, it is recommended to avoid conflicts
 363           with usb-storage by enabling USB_LIBUSUAL.
 364
 365           If unsure, say N.
 366
 367 config BLK_DEV_RAM
 368         tristate "RAM disk support"
 369         ---help---
 370           Saying Y here will allow you to use a portion of your RAM memory as
 371           a block device, so that you can make file systems on it, read and
 372           write to it and do all the other things that you can do with normal
 373           block devices (such as hard drives). It is usually used to load and
 374           store a copy of a minimal root file system off of a floppy into RAM
 375           during the initial install of Linux.
 376
 377           Note that the kernel command line option "ramdisk=XX" is now
 378           obsolete. For details, read <file:Documentation/ramdisk.txt>.
 379
 380           To compile this driver as a module, choose M here: the
 381           module will be called rd.
 382
 383           Most normal users won't need the RAM disk functionality, and can
 384           thus say N here.
 385
 386 config BLK_DEV_RAM_COUNT
 387         int "Default number of RAM disks"
 388         default "16"
 389         depends on BLK_DEV_RAM
 390         help
 391           The default value is 16 RAM disks. Change this if you know what
 392           are doing. If you boot from a filesystem that needs to be extracted
 393           in memory, you will need at least one RAM disk (e.g. root on cramfs).
 394
 395 config BLK_DEV_RAM_SIZE
 396         int "Default RAM disk size (kbytes)"
 397         depends on BLK_DEV_RAM
 398         default "4096"
 399         help
 400           The default value is 4096 kilobytes. Only change this if you know
 401           what are you doing. If you are using IBM S/390, then set this to
 402           8192.
 403
 404 config BLK_DEV_RAM_BLOCKSIZE
 405         int "Default RAM disk block size (bytes)"
 406         depends on BLK_DEV_RAM
 407         default "1024"
 408         help
 409           The default value is 1024 bytes.  PAGE_SIZE is a much more
 410           efficient choice however.  The default is kept to ensure initrd
 411           setups function - apparently needed by the rd_load_image routine
 412           that supposes the filesystem in the image uses a 1024 blocksize.
 413
 414 config BLK_DEV_INITRD
 415         bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
 416         depends on BROKEN || !FRV
 417         help
 418           The initial RAM filesystem is a ramfs which is loaded by the
 419           boot loader (loadlin or lilo) and that is mounted as root
 420           before the normal boot procedure. It is typically used to
 421           load modules needed to mount the "real" root file system,
 422           etc. See <file:Documentation/initrd.txt> for details.
 423
 424           If RAM disk support (BLK_DEV_RAM) is also included, this
 425           also enables initial RAM disk (initrd) support.
 426
 427
 428 config CDROM_PKTCDVD
 429         tristate "Packet writing on CD/DVD media"
 430         depends on !UML
 431         help
 432           If you have a CDROM drive that supports packet writing, say Y to
 433           include preliminary support. It should work with any MMC/Mt Fuji
 434           compliant ATAPI or SCSI drive, which is just about any newer CD
 435           writer.
 436
 437           Currently only writing to CD-RW, DVD-RW and DVD+RW discs is possible.
 438           DVD-RW disks must be in restricted overwrite mode.
 439
 440           To compile this driver as a module, choose M here: the
 441           module will be called pktcdvd.
 442
 443 config CDROM_PKTCDVD_BUFFERS
 444         int "Free buffers for data gathering"
 445         depends on CDROM_PKTCDVD
 446         default "8"
 447         help
 448           This controls the maximum number of active concurrent packets. More
 449           concurrent packets can increase write performance, but also require
 450           more memory. Each concurrent packet will require approximately 64Kb
 451           of non-swappable kernel memory, memory which will be allocated when
 452           a disc is opened for writing.
 453
 454 config CDROM_PKTCDVD_WCACHE
 455         bool "Enable write caching (EXPERIMENTAL)"
 456         depends on CDROM_PKTCDVD && EXPERIMENTAL
 457         help
 458           If enabled, write caching will be set for the CD-R/W device. For now
 459           this option is dangerous unless the CD-RW media is known good, as we
 460           don't do deferred write error handling yet.
 461
 462 source "drivers/s390/block/Kconfig"
 463
 464 config ATA_OVER_ETH
 465         tristate "ATA over Ethernet support"
 466         depends on NET
 467         help
 468         This driver provides Support for ATA over Ethernet block
 469         devices like the Coraid EtherDrive (R) Storage Blade.
 470
 471 endmenu
 472
 473 endif