1# 2# Block device driver configuration 3# 4 5menuconfig 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 16if BLK_DEV 17 18config BLK_DEV_FD 19 tristate "Normal floppy disk support" 20 depends on ARCH_MAY_HAVE_PC_FDC 21 ---help--- 22 If you want to use the floppy disk drive(s) of your PC under Linux, 23 say Y. Information about this driver, especially important for IBM 24 Thinkpad users, is contained in 25 <file:Documentation/blockdev/floppy.txt>. 26 That file also contains the location of the Floppy driver FAQ as 27 well as location of the fdutils package used to configure additional 28 parameters of the driver at run time. 29 30 To compile this driver as a module, choose M here: the 31 module will be called floppy. 32 33config AMIGA_FLOPPY 34 tristate "Amiga floppy support" 35 depends on AMIGA 36 37config ATARI_FLOPPY 38 tristate "Atari floppy support" 39 depends on ATARI 40 41config MAC_FLOPPY 42 tristate "Support for PowerMac floppy" 43 depends on PPC_PMAC && !PPC_PMAC64 44 help 45 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple) 46 floppy controller, say Y here. Most commonly found in PowerMacs. 47 48config BLK_DEV_SWIM 49 tristate "Support for SWIM Macintosh floppy" 50 depends on M68K && MAC 51 help 52 You should select this option if you want floppy support 53 and you don't have a II, IIfx, Q900, Q950 or AV series. 54 55config 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 66config GDROM 67 tristate "SEGA Dreamcast GD-ROM drive" 68 depends on SH_DREAMCAST 69 help 70 A standard SEGA Dreamcast comes with a modified CD ROM drive called a 71 "GD-ROM" by SEGA to signify it is capable of reading special disks 72 with up to 1 GB of data. This drive will also read standard CD ROM 73 disks. Select this option to access any disks in your GD ROM drive. 74 Most users will want to say "Y" here. 75 You can also build this as a module which will be called gdrom. 76 77config PARIDE 78 tristate "Parallel port IDE device support" 79 depends on PARPORT_PC 80 ---help--- 81 There are many external CD-ROM and disk devices that connect through 82 your computer's parallel port. Most of them are actually IDE devices 83 using a parallel port IDE adapter. This option enables the PARIDE 84 subsystem which contains drivers for many of these external drives. 85 Read <file:Documentation/blockdev/paride.txt> for more information. 86 87 If you have said Y to the "Parallel-port support" configuration 88 option, you may share a single port between your printer and other 89 parallel port devices. Answer Y to build PARIDE support into your 90 kernel, or M if you would like to build it as a loadable module. If 91 your parallel port support is in a loadable module, you must build 92 PARIDE as a module. If you built PARIDE support into your kernel, 93 you may still build the individual protocol modules and high-level 94 drivers as loadable modules. If you build this support as a module, 95 it will be called paride. 96 97 To use the PARIDE support, you must say Y or M here and also to at 98 least one high-level driver (e.g. "Parallel port IDE disks", 99 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and 100 to at least one protocol driver (e.g. "ATEN EH-100 protocol", 101 "MicroSolutions backpack protocol", "DataStor Commuter protocol" 102 etc.). 103 104source "drivers/block/paride/Kconfig" 105 106source "drivers/block/mtip32xx/Kconfig" 107 108source "drivers/block/zram/Kconfig" 109 110config BLK_CPQ_DA 111 tristate "Compaq SMART2 support" 112 depends on PCI && VIRT_TO_BUS 113 help 114 This is the driver for Compaq Smart Array controllers. Everyone 115 using these boards should say Y here. See the file 116 <file:Documentation/blockdev/cpqarray.txt> for the current list of 117 boards supported by this driver, and for further information on the 118 use of this driver. 119 120config BLK_CPQ_CISS_DA 121 tristate "Compaq Smart Array 5xxx support" 122 depends on PCI 123 select CHECK_SIGNATURE 124 help 125 This is the driver for Compaq Smart Array 5xxx controllers. 126 Everyone using these boards should say Y here. 127 See <file:Documentation/blockdev/cciss.txt> for the current list of 128 boards supported by this driver, and for further information 129 on the use of this driver. 130 131config CISS_SCSI_TAPE 132 bool "SCSI tape drive support for Smart Array 5xxx" 133 depends on BLK_CPQ_CISS_DA && PROC_FS 134 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA 135 help 136 When enabled (Y), this option allows SCSI tape drives and SCSI medium 137 changers (tape robots) to be accessed via a Compaq 5xxx array 138 controller. (See <file:Documentation/blockdev/cciss.txt> for more details.) 139 140 "SCSI support" and "SCSI tape support" must also be enabled for this 141 option to work. 142 143 When this option is disabled (N), the SCSI portion of the driver 144 is not compiled. 145 146config BLK_DEV_DAC960 147 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support" 148 depends on PCI 149 help 150 This driver adds support for the Mylex DAC960, AcceleRAID, and 151 eXtremeRAID PCI RAID controllers. See the file 152 <file:Documentation/blockdev/README.DAC960> for further information 153 about this driver. 154 155 To compile this driver as a module, choose M here: the 156 module will be called DAC960. 157 158config BLK_DEV_UMEM 159 tristate "Micro Memory MM5415 Battery Backed RAM support" 160 depends on PCI 161 ---help--- 162 Saying Y here will include support for the MM5415 family of 163 battery backed (Non-volatile) RAM cards. 164 <http://www.umem.com/> 165 166 The cards appear as block devices that can be partitioned into 167 as many as 15 partitions. 168 169 To compile this driver as a module, choose M here: the 170 module will be called umem. 171 172 The umem driver has not yet been allocated a MAJOR number, so 173 one is chosen dynamically. 174 175config BLK_DEV_UBD 176 bool "Virtual block device" 177 depends on UML 178 ---help--- 179 The User-Mode Linux port includes a driver called UBD which will let 180 you access arbitrary files on the host computer as block devices. 181 Unless you know that you do not need such virtual block devices say 182 Y here. 183 184config BLK_DEV_UBD_SYNC 185 bool "Always do synchronous disk IO for UBD" 186 depends on BLK_DEV_UBD 187 ---help--- 188 Writes to the virtual block device are not immediately written to the 189 host's disk; this may cause problems if, for example, the User-Mode 190 Linux 'Virtual Machine' uses a journalling filesystem and the host 191 computer crashes. 192 193 Synchronous operation (i.e. always writing data to the host's disk 194 immediately) is configurable on a per-UBD basis by using a special 195 kernel command line option. Alternatively, you can say Y here to 196 turn on synchronous operation by default for all block devices. 197 198 If you're running a journalling file system (like reiserfs, for 199 example) in your virtual machine, you will want to say Y here. If 200 you care for the safety of the data in your virtual machine, Y is a 201 wise choice too. In all other cases (for example, if you're just 202 playing around with User-Mode Linux) you can choose N. 203 204config BLK_DEV_COW_COMMON 205 bool 206 default BLK_DEV_UBD 207 208config BLK_DEV_LOOP 209 tristate "Loopback device support" 210 ---help--- 211 Saying Y here will allow you to use a regular file as a block 212 device; you can then create a file system on that block device and 213 mount it just as you would mount other block devices such as hard 214 drive partitions, CD-ROM drives or floppy drives. The loop devices 215 are block special device files with major number 7 and typically 216 called /dev/loop0, /dev/loop1 etc. 217 218 This is useful if you want to check an ISO 9660 file system before 219 burning the CD, or if you want to use floppy images without first 220 writing them to floppy. Furthermore, some Linux distributions avoid 221 the need for a dedicated Linux partition by keeping their complete 222 root file system inside a DOS FAT file using this loop device 223 driver. 224 225 To use the loop device, you need the losetup utility, found in the 226 util-linux package, see 227 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>. 228 229 The loop device driver can also be used to "hide" a file system in 230 a disk partition, floppy, or regular file, either using encryption 231 (scrambling the data) or steganography (hiding the data in the low 232 bits of, say, a sound file). This is also safe if the file resides 233 on a remote file server. 234 235 There are several ways of encrypting disks. Some of these require 236 kernel patches. The vanilla kernel offers the cryptoloop option 237 and a Device Mapper target (which is superior, as it supports all 238 file systems). If you want to use the cryptoloop, say Y to both 239 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12 240 or later) version of util-linux. Additionally, be aware that 241 the cryptoloop is not safe for storing journaled filesystems. 242 243 Note that this loop device has nothing to do with the loopback 244 device used for network connections from the machine to itself. 245 246 To compile this driver as a module, choose M here: the 247 module will be called loop. 248 249 Most users will answer N here. 250 251config BLK_DEV_LOOP_MIN_COUNT 252 int "Number of loop devices to pre-create at init time" 253 depends on BLK_DEV_LOOP 254 default 8 255 help 256 Static number of loop devices to be unconditionally pre-created 257 at init time. 258 259 This default value can be overwritten on the kernel command 260 line or with module-parameter loop.max_loop. 261 262 The historic default is 8. If a late 2011 version of losetup(8) 263 is used, it can be set to 0, since needed loop devices can be 264 dynamically allocated with the /dev/loop-control interface. 265 266config BLK_DEV_CRYPTOLOOP 267 tristate "Cryptoloop Support" 268 select CRYPTO 269 select CRYPTO_CBC 270 depends on BLK_DEV_LOOP 271 ---help--- 272 Say Y here if you want to be able to use the ciphers that are 273 provided by the CryptoAPI as loop transformation. This might be 274 used as hard disk encryption. 275 276 WARNING: This device is not safe for journaled file systems like 277 ext3 or Reiserfs. Please use the Device Mapper crypto module 278 instead, which can be configured to be on-disk compatible with the 279 cryptoloop device. 280 281source "drivers/block/drbd/Kconfig" 282 283config BLK_DEV_NBD 284 tristate "Network block device support" 285 depends on NET 286 ---help--- 287 Saying Y here will allow your computer to be a client for network 288 block devices, i.e. it will be able to use block devices exported by 289 servers (mount file systems on them etc.). Communication between 290 client and server works over TCP/IP networking, but to the client 291 program this is hidden: it looks like a regular local file access to 292 a block device special file such as /dev/nd0. 293 294 Network block devices also allows you to run a block-device in 295 userland (making server and client physically the same computer, 296 communicating using the loopback network device). 297 298 Read <file:Documentation/blockdev/nbd.txt> for more information, 299 especially about where to find the server code, which runs in user 300 space and does not need special kernel support. 301 302 Note that this has nothing to do with the network file systems NFS 303 or Coda; you can say N here even if you intend to use NFS or Coda. 304 305 To compile this driver as a module, choose M here: the 306 module will be called nbd. 307 308 If unsure, say N. 309 310config BLK_DEV_NVME 311 tristate "NVM Express block device" 312 depends on PCI 313 ---help--- 314 The NVM Express driver is for solid state drives directly 315 connected to the PCI or PCI Express bus. If you know you 316 don't have one of these, it is safe to answer N. 317 318 To compile this driver as a module, choose M here: the 319 module will be called nvme. 320 321config BLK_DEV_OSD 322 tristate "OSD object-as-blkdev support" 323 depends on SCSI_OSD_ULD 324 ---help--- 325 Saying Y or M here will allow the exporting of a single SCSI 326 OSD (object-based storage) object as a Linux block device. 327 328 For example, if you create a 2G object on an OSD device, 329 you can then use this module to present that 2G object as 330 a Linux block device. 331 332 To compile this driver as a module, choose M here: the 333 module will be called osdblk. 334 335 If unsure, say N. 336 337config BLK_DEV_SX8 338 tristate "Promise SATA SX8 support" 339 depends on PCI 340 ---help--- 341 Saying Y or M here will enable support for the 342 Promise SATA SX8 controllers. 343 344 Use devices /dev/sx8/$N and /dev/sx8/$Np$M. 345 346config BLK_DEV_RAM 347 tristate "RAM block device support" 348 ---help--- 349 Saying Y here will allow you to use a portion of your RAM memory as 350 a block device, so that you can make file systems on it, read and 351 write to it and do all the other things that you can do with normal 352 block devices (such as hard drives). It is usually used to load and 353 store a copy of a minimal root file system off of a floppy into RAM 354 during the initial install of Linux. 355 356 Note that the kernel command line option "ramdisk=XX" is now obsolete. 357 For details, read <file:Documentation/blockdev/ramdisk.txt>. 358 359 To compile this driver as a module, choose M here: the 360 module will be called rd. 361 362 Most normal users won't need the RAM disk functionality, and can 363 thus say N here. 364 365config BLK_DEV_RAM_COUNT 366 int "Default number of RAM disks" 367 default "16" 368 depends on BLK_DEV_RAM 369 help 370 The default value is 16 RAM disks. Change this if you know what you 371 are doing. If you boot from a filesystem that needs to be extracted 372 in memory, you will need at least one RAM disk (e.g. root on cramfs). 373 374config BLK_DEV_RAM_SIZE 375 int "Default RAM disk size (kbytes)" 376 depends on BLK_DEV_RAM 377 default "4096" 378 help 379 The default value is 4096 kilobytes. Only change this if you know 380 what you are doing. 381 382config BLK_DEV_XIP 383 bool "Support XIP filesystems on RAM block device" 384 depends on BLK_DEV_RAM 385 default n 386 help 387 Support XIP filesystems (such as ext2 with XIP support on) on 388 top of block ram device. This will slightly enlarge the kernel, and 389 will prevent RAM block device backing store memory from being 390 allocated from highmem (only a problem for highmem systems). 391 392config CDROM_PKTCDVD 393 tristate "Packet writing on CD/DVD media" 394 depends on !UML 395 help 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 411config 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 422config 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 430config 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 437config MG_DISK 438 tristate "mGine mflash, gflash support" 439 depends on ARM && GPIOLIB 440 help 441 mGine mFlash(gFlash) block device driver 442 443config 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 454config 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 461source "drivers/s390/block/Kconfig" 462 463config XILINX_SYSACE 464 tristate "Xilinx SystemACE support" 465 depends on 4xx || MICROBLAZE 466 help 467 Include support for the Xilinx SystemACE CompactFlash interface 468 469config 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 479config 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 500config VIRTIO_BLK 501 tristate "Virtio block driver" 502 depends on VIRTIO 503 ---help--- 504 This is the virtual block driver for virtio. It can be used with 505 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 506 507config BLK_DEV_HD 508 bool "Very old hard disk (MFM/RLL/IDE) driver" 509 depends on HAVE_IDE 510 depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN 511 help 512 This is a very old hard disk driver that lacks the enhanced 513 functionality of the newer ones. 514 515 It is required for systems with ancient MFM/RLL/ESDI drives. 516 517 If unsure, say N. 518 519config BLK_DEV_RBD 520 tristate "Rados block device (RBD)" 521 depends on INET && BLOCK 522 select CEPH_LIB 523 select LIBCRC32C 524 select CRYPTO_AES 525 select CRYPTO 526 default n 527 help 528 Say Y here if you want include the Rados block device, which stripes 529 a block device over objects stored in the Ceph distributed object 530 store. 531 532 More information at http://ceph.newdream.net/. 533 534 If unsure, say N. 535 536config BLK_DEV_RSXX 537 tristate "IBM FlashSystem 70/80 PCIe SSD Device Driver" 538 depends on PCI 539 help 540 Device driver for IBM's high speed PCIe SSD 541 storage devices: FlashSystem-70 and FlashSystem-80. 542 543 To compile this driver as a module, choose M here: the 544 module will be called rsxx. 545 546endif # BLK_DEV 547