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/admin-guide/blockdev/floppy.rst>. 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/admin-guide/blockdev/paride.rst> 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_UMEM 125 tristate "Micro Memory MM5415 Battery Backed RAM support" 126 depends on PCI 127 ---help--- 128 Saying Y here will include support for the MM5415 family of 129 battery backed (Non-volatile) RAM cards. 130 <http://www.umem.com/> 131 132 The cards appear as block devices that can be partitioned into 133 as many as 15 partitions. 134 135 To compile this driver as a module, choose M here: the 136 module will be called umem. 137 138 The umem driver has not yet been allocated a MAJOR number, so 139 one is chosen dynamically. 140 141config BLK_DEV_UBD 142 bool "Virtual block device" 143 depends on UML 144 ---help--- 145 The User-Mode Linux port includes a driver called UBD which will let 146 you access arbitrary files on the host computer as block devices. 147 Unless you know that you do not need such virtual block devices say 148 Y here. 149 150config BLK_DEV_UBD_SYNC 151 bool "Always do synchronous disk IO for UBD" 152 depends on BLK_DEV_UBD 153 ---help--- 154 Writes to the virtual block device are not immediately written to the 155 host's disk; this may cause problems if, for example, the User-Mode 156 Linux 'Virtual Machine' uses a journalling filesystem and the host 157 computer crashes. 158 159 Synchronous operation (i.e. always writing data to the host's disk 160 immediately) is configurable on a per-UBD basis by using a special 161 kernel command line option. Alternatively, you can say Y here to 162 turn on synchronous operation by default for all block devices. 163 164 If you're running a journalling file system (like reiserfs, for 165 example) in your virtual machine, you will want to say Y here. If 166 you care for the safety of the data in your virtual machine, Y is a 167 wise choice too. In all other cases (for example, if you're just 168 playing around with User-Mode Linux) you can choose N. 169 170config BLK_DEV_COW_COMMON 171 bool 172 default BLK_DEV_UBD 173 174config BLK_DEV_LOOP 175 tristate "Loopback device support" 176 ---help--- 177 Saying Y here will allow you to use a regular file as a block 178 device; you can then create a file system on that block device and 179 mount it just as you would mount other block devices such as hard 180 drive partitions, CD-ROM drives or floppy drives. The loop devices 181 are block special device files with major number 7 and typically 182 called /dev/loop0, /dev/loop1 etc. 183 184 This is useful if you want to check an ISO 9660 file system before 185 burning the CD, or if you want to use floppy images without first 186 writing them to floppy. Furthermore, some Linux distributions avoid 187 the need for a dedicated Linux partition by keeping their complete 188 root file system inside a DOS FAT file using this loop device 189 driver. 190 191 To use the loop device, you need the losetup utility, found in the 192 util-linux package, see 193 <https://www.kernel.org/pub/linux/utils/util-linux/>. 194 195 The loop device driver can also be used to "hide" a file system in 196 a disk partition, floppy, or regular file, either using encryption 197 (scrambling the data) or steganography (hiding the data in the low 198 bits of, say, a sound file). This is also safe if the file resides 199 on a remote file server. 200 201 There are several ways of encrypting disks. Some of these require 202 kernel patches. The vanilla kernel offers the cryptoloop option 203 and a Device Mapper target (which is superior, as it supports all 204 file systems). If you want to use the cryptoloop, say Y to both 205 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12 206 or later) version of util-linux. Additionally, be aware that 207 the cryptoloop is not safe for storing journaled filesystems. 208 209 Note that this loop device has nothing to do with the loopback 210 device used for network connections from the machine to itself. 211 212 To compile this driver as a module, choose M here: the 213 module will be called loop. 214 215 Most users will answer N here. 216 217config BLK_DEV_LOOP_MIN_COUNT 218 int "Number of loop devices to pre-create at init time" 219 depends on BLK_DEV_LOOP 220 default 8 221 help 222 Static number of loop devices to be unconditionally pre-created 223 at init time. 224 225 This default value can be overwritten on the kernel command 226 line or with module-parameter loop.max_loop. 227 228 The historic default is 8. If a late 2011 version of losetup(8) 229 is used, it can be set to 0, since needed loop devices can be 230 dynamically allocated with the /dev/loop-control interface. 231 232config BLK_DEV_CRYPTOLOOP 233 tristate "Cryptoloop Support" 234 select CRYPTO 235 select CRYPTO_CBC 236 depends on BLK_DEV_LOOP 237 ---help--- 238 Say Y here if you want to be able to use the ciphers that are 239 provided by the CryptoAPI as loop transformation. This might be 240 used as hard disk encryption. 241 242 WARNING: This device is not safe for journaled file systems like 243 ext3 or Reiserfs. Please use the Device Mapper crypto module 244 instead, which can be configured to be on-disk compatible with the 245 cryptoloop device. 246 247source "drivers/block/drbd/Kconfig" 248 249config BLK_DEV_NBD 250 tristate "Network block device support" 251 depends on NET 252 ---help--- 253 Saying Y here will allow your computer to be a client for network 254 block devices, i.e. it will be able to use block devices exported by 255 servers (mount file systems on them etc.). Communication between 256 client and server works over TCP/IP networking, but to the client 257 program this is hidden: it looks like a regular local file access to 258 a block device special file such as /dev/nd0. 259 260 Network block devices also allows you to run a block-device in 261 userland (making server and client physically the same computer, 262 communicating using the loopback network device). 263 264 Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information, 265 especially about where to find the server code, which runs in user 266 space and does not need special kernel support. 267 268 Note that this has nothing to do with the network file systems NFS 269 or Coda; you can say N here even if you intend to use NFS or Coda. 270 271 To compile this driver as a module, choose M here: the 272 module will be called nbd. 273 274 If unsure, say N. 275 276config BLK_DEV_SKD 277 tristate "STEC S1120 Block Driver" 278 depends on PCI 279 depends on 64BIT 280 ---help--- 281 Saying Y or M here will enable support for the 282 STEC, Inc. S1120 PCIe SSD. 283 284 Use device /dev/skd$N amd /dev/skd$Np$M. 285 286config BLK_DEV_SX8 287 tristate "Promise SATA SX8 support" 288 depends on PCI 289 ---help--- 290 Saying Y or M here will enable support for the 291 Promise SATA SX8 controllers. 292 293 Use devices /dev/sx8/$N and /dev/sx8/$Np$M. 294 295config BLK_DEV_RAM 296 tristate "RAM block device support" 297 ---help--- 298 Saying Y here will allow you to use a portion of your RAM memory as 299 a block device, so that you can make file systems on it, read and 300 write to it and do all the other things that you can do with normal 301 block devices (such as hard drives). It is usually used to load and 302 store a copy of a minimal root file system off of a floppy into RAM 303 during the initial install of Linux. 304 305 Note that the kernel command line option "ramdisk=XX" is now obsolete. 306 For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>. 307 308 To compile this driver as a module, choose M here: the 309 module will be called brd. An alias "rd" has been defined 310 for historical reasons. 311 312 Most normal users won't need the RAM disk functionality, and can 313 thus say N here. 314 315config BLK_DEV_RAM_COUNT 316 int "Default number of RAM disks" 317 default "16" 318 depends on BLK_DEV_RAM 319 help 320 The default value is 16 RAM disks. Change this if you know what you 321 are doing. If you boot from a filesystem that needs to be extracted 322 in memory, you will need at least one RAM disk (e.g. root on cramfs). 323 324config BLK_DEV_RAM_SIZE 325 int "Default RAM disk size (kbytes)" 326 depends on BLK_DEV_RAM 327 default "4096" 328 help 329 The default value is 4096 kilobytes. Only change this if you know 330 what you are doing. 331 332config CDROM_PKTCDVD 333 tristate "Packet writing on CD/DVD media (DEPRECATED)" 334 depends on !UML 335 select CDROM 336 select BLK_SCSI_REQUEST 337 help 338 Note: This driver is deprecated and will be removed from the 339 kernel in the near future! 340 341 If you have a CDROM/DVD drive that supports packet writing, say 342 Y to include support. It should work with any MMC/Mt Fuji 343 compliant ATAPI or SCSI drive, which is just about any newer 344 DVD/CD writer. 345 346 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs 347 is possible. 348 DVD-RW disks must be in restricted overwrite mode. 349 350 See the file <file:Documentation/cdrom/packet-writing.rst> 351 for further information on the use of this driver. 352 353 To compile this driver as a module, choose M here: the 354 module will be called pktcdvd. 355 356config CDROM_PKTCDVD_BUFFERS 357 int "Free buffers for data gathering" 358 depends on CDROM_PKTCDVD 359 default "8" 360 help 361 This controls the maximum number of active concurrent packets. More 362 concurrent packets can increase write performance, but also require 363 more memory. Each concurrent packet will require approximately 64Kb 364 of non-swappable kernel memory, memory which will be allocated when 365 a disc is opened for writing. 366 367config CDROM_PKTCDVD_WCACHE 368 bool "Enable write caching" 369 depends on CDROM_PKTCDVD 370 help 371 If enabled, write caching will be set for the CD-R/W device. For now 372 this option is dangerous unless the CD-RW media is known good, as we 373 don't do deferred write error handling yet. 374 375config ATA_OVER_ETH 376 tristate "ATA over Ethernet support" 377 depends on NET 378 help 379 This driver provides Support for ATA over Ethernet block 380 devices like the Coraid EtherDrive (R) Storage Blade. 381 382config SUNVDC 383 tristate "Sun Virtual Disk Client support" 384 depends on SUN_LDOMS 385 help 386 Support for virtual disk devices as a client under Sun 387 Logical Domains. 388 389source "drivers/s390/block/Kconfig" 390 391config XILINX_SYSACE 392 tristate "Xilinx SystemACE support" 393 depends on 4xx || MICROBLAZE 394 help 395 Include support for the Xilinx SystemACE CompactFlash interface 396 397config XEN_BLKDEV_FRONTEND 398 tristate "Xen virtual block device support" 399 depends on XEN 400 default y 401 select XEN_XENBUS_FRONTEND 402 help 403 This driver implements the front-end of the Xen virtual 404 block device driver. It communicates with a back-end driver 405 in another domain which drives the actual block device. 406 407config XEN_BLKDEV_BACKEND 408 tristate "Xen block-device backend driver" 409 depends on XEN_BACKEND 410 help 411 The block-device backend driver allows the kernel to export its 412 block devices to other guests via a high-performance shared-memory 413 interface. 414 415 The corresponding Linux frontend driver is enabled by the 416 CONFIG_XEN_BLKDEV_FRONTEND configuration option. 417 418 The backend driver attaches itself to a any block device specified 419 in the XenBus configuration. There are no limits to what the block 420 device as long as it has a major and minor. 421 422 If you are compiling a kernel to run in a Xen block backend driver 423 domain (often this is domain 0) you should say Y here. To 424 compile this driver as a module, chose M here: the module 425 will be called xen-blkback. 426 427 428config VIRTIO_BLK 429 tristate "Virtio block driver" 430 depends on VIRTIO 431 ---help--- 432 This is the virtual block driver for virtio. It can be used with 433 QEMU based VMMs (like KVM or Xen). Say Y or M. 434 435config VIRTIO_BLK_SCSI 436 bool "SCSI passthrough request for the Virtio block driver" 437 depends on VIRTIO_BLK 438 select BLK_SCSI_REQUEST 439 ---help--- 440 Enable support for SCSI passthrough (e.g. the SG_IO ioctl) on 441 virtio-blk devices. This is only supported for the legacy 442 virtio protocol and not enabled by default by any hypervisor. 443 You probably want to use virtio-scsi instead. 444 445config BLK_DEV_RBD 446 tristate "Rados block device (RBD)" 447 depends on INET && BLOCK 448 select CEPH_LIB 449 select LIBCRC32C 450 select CRYPTO_AES 451 select CRYPTO 452 help 453 Say Y here if you want include the Rados block device, which stripes 454 a block device over objects stored in the Ceph distributed object 455 store. 456 457 More information at http://ceph.newdream.net/. 458 459 If unsure, say N. 460 461config BLK_DEV_RSXX 462 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver" 463 depends on PCI 464 help 465 Device driver for IBM's high speed PCIe SSD 466 storage device: Flash Adapter 900GB Full Height. 467 468 To compile this driver as a module, choose M here: the 469 module will be called rsxx. 470 471endif # BLK_DEV 472