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