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