1# SPDX-License-Identifier: GPL-2.0 2# 3# Block device driver configuration 4# 5 6menuconfig BLK_DEV 7 bool "Block devices" 8 depends on BLOCK 9 default y 10 ---help--- 11 Say Y here to get to see options for various different block device 12 drivers. This option alone does not add any kernel code. 13 14 If you say N, all options in this submenu will be skipped and disabled; 15 only do this if you know what you are doing. 16 17if BLK_DEV 18 19config BLK_DEV_NULL_BLK 20 tristate "Null test block driver" 21 select CONFIGFS_FS 22 23config BLK_DEV_NULL_BLK_FAULT_INJECTION 24 bool "Support fault injection for Null test block driver" 25 depends on BLK_DEV_NULL_BLK && FAULT_INJECTION 26 27config BLK_DEV_FD 28 tristate "Normal floppy disk support" 29 depends on ARCH_MAY_HAVE_PC_FDC 30 ---help--- 31 If you want to use the floppy disk drive(s) of your PC under Linux, 32 say Y. Information about this driver, especially important for IBM 33 Thinkpad users, is contained in 34 <file:Documentation/blockdev/floppy.txt>. 35 That file also contains the location of the Floppy driver FAQ as 36 well as location of the fdutils package used to configure additional 37 parameters of the driver at run time. 38 39 To compile this driver as a module, choose M here: the 40 module will be called floppy. 41 42config AMIGA_FLOPPY 43 tristate "Amiga floppy support" 44 depends on AMIGA 45 46config ATARI_FLOPPY 47 tristate "Atari floppy support" 48 depends on ATARI 49 50config MAC_FLOPPY 51 tristate "Support for PowerMac floppy" 52 depends on PPC_PMAC && !PPC_PMAC64 53 help 54 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple) 55 floppy controller, say Y here. Most commonly found in PowerMacs. 56 57config BLK_DEV_SWIM 58 tristate "Support for SWIM Macintosh floppy" 59 depends on M68K && MAC 60 help 61 You should select this option if you want floppy support 62 and you don't have a II, IIfx, Q900, Q950 or AV series. 63 64config AMIGA_Z2RAM 65 tristate "Amiga Zorro II ramdisk support" 66 depends on ZORRO 67 help 68 This enables support for using Chip RAM and Zorro II RAM as a 69 ramdisk or as a swap partition. Say Y if you want to include this 70 driver in the kernel. 71 72 To compile this driver as a module, choose M here: the 73 module will be called z2ram. 74 75config CDROM 76 tristate 77 select BLK_SCSI_REQUEST 78 79config GDROM 80 tristate "SEGA Dreamcast GD-ROM drive" 81 depends on SH_DREAMCAST 82 select CDROM 83 help 84 A standard SEGA Dreamcast comes with a modified CD ROM drive called a 85 "GD-ROM" by SEGA to signify it is capable of reading special disks 86 with up to 1 GB of data. This drive will also read standard CD ROM 87 disks. Select this option to access any disks in your GD ROM drive. 88 Most users will want to say "Y" here. 89 You can also build this as a module which will be called gdrom. 90 91config PARIDE 92 tristate "Parallel port IDE device support" 93 depends on PARPORT_PC 94 ---help--- 95 There are many external CD-ROM and disk devices that connect through 96 your computer's parallel port. Most of them are actually IDE devices 97 using a parallel port IDE adapter. This option enables the PARIDE 98 subsystem which contains drivers for many of these external drives. 99 Read <file:Documentation/blockdev/paride.txt> for more information. 100 101 If you have said Y to the "Parallel-port support" configuration 102 option, you may share a single port between your printer and other 103 parallel port devices. Answer Y to build PARIDE support into your 104 kernel, or M if you would like to build it as a loadable module. If 105 your parallel port support is in a loadable module, you must build 106 PARIDE as a module. If you built PARIDE support into your kernel, 107 you may still build the individual protocol modules and high-level 108 drivers as loadable modules. If you build this support as a module, 109 it will be called paride. 110 111 To use the PARIDE support, you must say Y or M here and also to at 112 least one high-level driver (e.g. "Parallel port IDE disks", 113 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and 114 to at least one protocol driver (e.g. "ATEN EH-100 protocol", 115 "MicroSolutions backpack protocol", "DataStor Commuter protocol" 116 etc.). 117 118source "drivers/block/paride/Kconfig" 119 120source "drivers/block/mtip32xx/Kconfig" 121 122source "drivers/block/zram/Kconfig" 123 124config BLK_DEV_DAC960 125 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support" 126 depends on PCI 127 help 128 This driver adds support for the Mylex DAC960, AcceleRAID, and 129 eXtremeRAID PCI RAID controllers. See the file 130 <file:Documentation/blockdev/README.DAC960> for further information 131 about this driver. 132 133 To compile this driver as a module, choose M here: the 134 module will be called DAC960. 135 136config BLK_DEV_UMEM 137 tristate "Micro Memory MM5415 Battery Backed RAM support" 138 depends on PCI 139 ---help--- 140 Saying Y here will include support for the MM5415 family of 141 battery backed (Non-volatile) RAM cards. 142 <http://www.umem.com/> 143 144 The cards appear as block devices that can be partitioned into 145 as many as 15 partitions. 146 147 To compile this driver as a module, choose M here: the 148 module will be called umem. 149 150 The umem driver has not yet been allocated a MAJOR number, so 151 one is chosen dynamically. 152 153config BLK_DEV_UBD 154 bool "Virtual block device" 155 depends on UML 156 ---help--- 157 The User-Mode Linux port includes a driver called UBD which will let 158 you access arbitrary files on the host computer as block devices. 159 Unless you know that you do not need such virtual block devices say 160 Y here. 161 162config BLK_DEV_UBD_SYNC 163 bool "Always do synchronous disk IO for UBD" 164 depends on BLK_DEV_UBD 165 ---help--- 166 Writes to the virtual block device are not immediately written to the 167 host's disk; this may cause problems if, for example, the User-Mode 168 Linux 'Virtual Machine' uses a journalling filesystem and the host 169 computer crashes. 170 171 Synchronous operation (i.e. always writing data to the host's disk 172 immediately) is configurable on a per-UBD basis by using a special 173 kernel command line option. Alternatively, you can say Y here to 174 turn on synchronous operation by default for all block devices. 175 176 If you're running a journalling file system (like reiserfs, for 177 example) in your virtual machine, you will want to say Y here. If 178 you care for the safety of the data in your virtual machine, Y is a 179 wise choice too. In all other cases (for example, if you're just 180 playing around with User-Mode Linux) you can choose N. 181 182config BLK_DEV_COW_COMMON 183 bool 184 default BLK_DEV_UBD 185 186config BLK_DEV_LOOP 187 tristate "Loopback device support" 188 ---help--- 189 Saying Y here will allow you to use a regular file as a block 190 device; you can then create a file system on that block device and 191 mount it just as you would mount other block devices such as hard 192 drive partitions, CD-ROM drives or floppy drives. The loop devices 193 are block special device files with major number 7 and typically 194 called /dev/loop0, /dev/loop1 etc. 195 196 This is useful if you want to check an ISO 9660 file system before 197 burning the CD, or if you want to use floppy images without first 198 writing them to floppy. Furthermore, some Linux distributions avoid 199 the need for a dedicated Linux partition by keeping their complete 200 root file system inside a DOS FAT file using this loop device 201 driver. 202 203 To use the loop device, you need the losetup utility, found in the 204 util-linux package, see 205 <https://www.kernel.org/pub/linux/utils/util-linux/>. 206 207 The loop device driver can also be used to "hide" a file system in 208 a disk partition, floppy, or regular file, either using encryption 209 (scrambling the data) or steganography (hiding the data in the low 210 bits of, say, a sound file). This is also safe if the file resides 211 on a remote file server. 212 213 There are several ways of encrypting disks. Some of these require 214 kernel patches. The vanilla kernel offers the cryptoloop option 215 and a Device Mapper target (which is superior, as it supports all 216 file systems). If you want to use the cryptoloop, say Y to both 217 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12 218 or later) version of util-linux. Additionally, be aware that 219 the cryptoloop is not safe for storing journaled filesystems. 220 221 Note that this loop device has nothing to do with the loopback 222 device used for network connections from the machine to itself. 223 224 To compile this driver as a module, choose M here: the 225 module will be called loop. 226 227 Most users will answer N here. 228 229config BLK_DEV_LOOP_MIN_COUNT 230 int "Number of loop devices to pre-create at init time" 231 depends on BLK_DEV_LOOP 232 default 8 233 help 234 Static number of loop devices to be unconditionally pre-created 235 at init time. 236 237 This default value can be overwritten on the kernel command 238 line or with module-parameter loop.max_loop. 239 240 The historic default is 8. If a late 2011 version of losetup(8) 241 is used, it can be set to 0, since needed loop devices can be 242 dynamically allocated with the /dev/loop-control interface. 243 244config BLK_DEV_CRYPTOLOOP 245 tristate "Cryptoloop Support" 246 select CRYPTO 247 select CRYPTO_CBC 248 depends on BLK_DEV_LOOP 249 ---help--- 250 Say Y here if you want to be able to use the ciphers that are 251 provided by the CryptoAPI as loop transformation. This might be 252 used as hard disk encryption. 253 254 WARNING: This device is not safe for journaled file systems like 255 ext3 or Reiserfs. Please use the Device Mapper crypto module 256 instead, which can be configured to be on-disk compatible with the 257 cryptoloop device. 258 259source "drivers/block/drbd/Kconfig" 260 261config BLK_DEV_NBD 262 tristate "Network block device support" 263 depends on NET 264 ---help--- 265 Saying Y here will allow your computer to be a client for network 266 block devices, i.e. it will be able to use block devices exported by 267 servers (mount file systems on them etc.). Communication between 268 client and server works over TCP/IP networking, but to the client 269 program this is hidden: it looks like a regular local file access to 270 a block device special file such as /dev/nd0. 271 272 Network block devices also allows you to run a block-device in 273 userland (making server and client physically the same computer, 274 communicating using the loopback network device). 275 276 Read <file:Documentation/blockdev/nbd.txt> for more information, 277 especially about where to find the server code, which runs in user 278 space and does not need special kernel support. 279 280 Note that this has nothing to do with the network file systems NFS 281 or Coda; you can say N here even if you intend to use NFS or Coda. 282 283 To compile this driver as a module, choose M here: the 284 module will be called nbd. 285 286 If unsure, say N. 287 288config BLK_DEV_SKD 289 tristate "STEC S1120 Block Driver" 290 depends on PCI 291 depends on 64BIT 292 ---help--- 293 Saying Y or M here will enable support for the 294 STEC, Inc. S1120 PCIe SSD. 295 296 Use device /dev/skd$N amd /dev/skd$Np$M. 297 298config BLK_DEV_SX8 299 tristate "Promise SATA SX8 support" 300 depends on PCI 301 ---help--- 302 Saying Y or M here will enable support for the 303 Promise SATA SX8 controllers. 304 305 Use devices /dev/sx8/$N and /dev/sx8/$Np$M. 306 307config BLK_DEV_RAM 308 tristate "RAM block device support" 309 ---help--- 310 Saying Y here will allow you to use a portion of your RAM memory as 311 a block device, so that you can make file systems on it, read and 312 write to it and do all the other things that you can do with normal 313 block devices (such as hard drives). It is usually used to load and 314 store a copy of a minimal root file system off of a floppy into RAM 315 during the initial install of Linux. 316 317 Note that the kernel command line option "ramdisk=XX" is now obsolete. 318 For details, read <file:Documentation/blockdev/ramdisk.txt>. 319 320 To compile this driver as a module, choose M here: the 321 module will be called brd. An alias "rd" has been defined 322 for historical reasons. 323 324 Most normal users won't need the RAM disk functionality, and can 325 thus say N here. 326 327config BLK_DEV_RAM_COUNT 328 int "Default number of RAM disks" 329 default "16" 330 depends on BLK_DEV_RAM 331 help 332 The default value is 16 RAM disks. Change this if you know what you 333 are doing. If you boot from a filesystem that needs to be extracted 334 in memory, you will need at least one RAM disk (e.g. root on cramfs). 335 336config BLK_DEV_RAM_SIZE 337 int "Default RAM disk size (kbytes)" 338 depends on BLK_DEV_RAM 339 default "4096" 340 help 341 The default value is 4096 kilobytes. Only change this if you know 342 what you are doing. 343 344config CDROM_PKTCDVD 345 tristate "Packet writing on CD/DVD media (DEPRECATED)" 346 depends on !UML 347 select CDROM 348 select BLK_SCSI_REQUEST 349 help 350 Note: This driver is deprecated and will be removed from the 351 kernel in the near future! 352 353 If you have a CDROM/DVD drive that supports packet writing, say 354 Y to include support. It should work with any MMC/Mt Fuji 355 compliant ATAPI or SCSI drive, which is just about any newer 356 DVD/CD writer. 357 358 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs 359 is possible. 360 DVD-RW disks must be in restricted overwrite mode. 361 362 See the file <file:Documentation/cdrom/packet-writing.txt> 363 for further information on the use of this driver. 364 365 To compile this driver as a module, choose M here: the 366 module will be called pktcdvd. 367 368config CDROM_PKTCDVD_BUFFERS 369 int "Free buffers for data gathering" 370 depends on CDROM_PKTCDVD 371 default "8" 372 help 373 This controls the maximum number of active concurrent packets. More 374 concurrent packets can increase write performance, but also require 375 more memory. Each concurrent packet will require approximately 64Kb 376 of non-swappable kernel memory, memory which will be allocated when 377 a disc is opened for writing. 378 379config CDROM_PKTCDVD_WCACHE 380 bool "Enable write caching" 381 depends on CDROM_PKTCDVD 382 help 383 If enabled, write caching will be set for the CD-R/W device. For now 384 this option is dangerous unless the CD-RW media is known good, as we 385 don't do deferred write error handling yet. 386 387config ATA_OVER_ETH 388 tristate "ATA over Ethernet support" 389 depends on NET 390 help 391 This driver provides Support for ATA over Ethernet block 392 devices like the Coraid EtherDrive (R) Storage Blade. 393 394config SUNVDC 395 tristate "Sun Virtual Disk Client support" 396 depends on SUN_LDOMS 397 help 398 Support for virtual disk devices as a client under Sun 399 Logical Domains. 400 401source "drivers/s390/block/Kconfig" 402 403config XILINX_SYSACE 404 tristate "Xilinx SystemACE support" 405 depends on 4xx || MICROBLAZE 406 help 407 Include support for the Xilinx SystemACE CompactFlash interface 408 409config XEN_BLKDEV_FRONTEND 410 tristate "Xen virtual block device support" 411 depends on XEN 412 default y 413 select XEN_XENBUS_FRONTEND 414 help 415 This driver implements the front-end of the Xen virtual 416 block device driver. It communicates with a back-end driver 417 in another domain which drives the actual block device. 418 419config XEN_BLKDEV_BACKEND 420 tristate "Xen block-device backend driver" 421 depends on XEN_BACKEND 422 help 423 The block-device backend driver allows the kernel to export its 424 block devices to other guests via a high-performance shared-memory 425 interface. 426 427 The corresponding Linux frontend driver is enabled by the 428 CONFIG_XEN_BLKDEV_FRONTEND configuration option. 429 430 The backend driver attaches itself to a any block device specified 431 in the XenBus configuration. There are no limits to what the block 432 device as long as it has a major and minor. 433 434 If you are compiling a kernel to run in a Xen block backend driver 435 domain (often this is domain 0) you should say Y here. To 436 compile this driver as a module, chose M here: the module 437 will be called xen-blkback. 438 439 440config VIRTIO_BLK 441 tristate "Virtio block driver" 442 depends on VIRTIO 443 ---help--- 444 This is the virtual block driver for virtio. It can be used with 445 QEMU based VMMs (like KVM or Xen). Say Y or M. 446 447config VIRTIO_BLK_SCSI 448 bool "SCSI passthrough request for the Virtio block driver" 449 depends on VIRTIO_BLK 450 select BLK_SCSI_REQUEST 451 ---help--- 452 Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on 453 virtio-blk devices. This is only supported for the legacy 454 virtio protocol and not enabled by default by any hypervisor. 455 You probably want to use virtio-scsi instead. 456 457config BLK_DEV_RBD 458 tristate "Rados block device (RBD)" 459 depends on INET && BLOCK 460 select CEPH_LIB 461 select LIBCRC32C 462 select CRYPTO_AES 463 select CRYPTO 464 default n 465 help 466 Say Y here if you want include the Rados block device, which stripes 467 a block device over objects stored in the Ceph distributed object 468 store. 469 470 More information at http://ceph.newdream.net/. 471 472 If unsure, say N. 473 474config BLK_DEV_RSXX 475 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver" 476 depends on PCI 477 help 478 Device driver for IBM's high speed PCIe SSD 479 storage device: Flash Adapter 900GB Full Height. 480 481 To compile this driver as a module, choose M here: the 482 module will be called rsxx. 483 484endif # BLK_DEV 485