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 78config GDROM 79 tristate "SEGA Dreamcast GD-ROM drive" 80 depends on SH_DREAMCAST 81 select CDROM 82 help 83 A standard SEGA Dreamcast comes with a modified CD ROM drive called a 84 "GD-ROM" by SEGA to signify it is capable of reading special disks 85 with up to 1 GB of data. This drive will also read standard CD ROM 86 disks. Select this option to access any disks in your GD ROM drive. 87 Most users will want to say "Y" here. 88 You can also build this as a module which will be called gdrom. 89 90config PARIDE 91 tristate "Parallel port IDE device support" 92 depends on PARPORT_PC 93 help 94 There are many external CD-ROM and disk devices that connect through 95 your computer's parallel port. Most of them are actually IDE devices 96 using a parallel port IDE adapter. This option enables the PARIDE 97 subsystem which contains drivers for many of these external drives. 98 Read <file:Documentation/admin-guide/blockdev/paride.rst> for more information. 99 100 If you have said Y to the "Parallel-port support" configuration 101 option, you may share a single port between your printer and other 102 parallel port devices. Answer Y to build PARIDE support into your 103 kernel, or M if you would like to build it as a loadable module. If 104 your parallel port support is in a loadable module, you must build 105 PARIDE as a module. If you built PARIDE support into your kernel, 106 you may still build the individual protocol modules and high-level 107 drivers as loadable modules. If you build this support as a module, 108 it will be called paride. 109 110 To use the PARIDE support, you must say Y or M here and also to at 111 least one high-level driver (e.g. "Parallel port IDE disks", 112 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and 113 to at least one protocol driver (e.g. "ATEN EH-100 protocol", 114 "MicroSolutions backpack protocol", "DataStor Commuter protocol" 115 etc.). 116 117source "drivers/block/paride/Kconfig" 118 119source "drivers/block/mtip32xx/Kconfig" 120 121source "drivers/block/zram/Kconfig" 122 123config BLK_DEV_UBD 124 bool "Virtual block device" 125 depends on UML 126 help 127 The User-Mode Linux port includes a driver called UBD which will let 128 you access arbitrary files on the host computer as block devices. 129 Unless you know that you do not need such virtual block devices say 130 Y here. 131 132config BLK_DEV_UBD_SYNC 133 bool "Always do synchronous disk IO for UBD" 134 depends on BLK_DEV_UBD 135 help 136 Writes to the virtual block device are not immediately written to the 137 host's disk; this may cause problems if, for example, the User-Mode 138 Linux 'Virtual Machine' uses a journalling filesystem and the host 139 computer crashes. 140 141 Synchronous operation (i.e. always writing data to the host's disk 142 immediately) is configurable on a per-UBD basis by using a special 143 kernel command line option. Alternatively, you can say Y here to 144 turn on synchronous operation by default for all block devices. 145 146 If you're running a journalling file system (like reiserfs, for 147 example) in your virtual machine, you will want to say Y here. If 148 you care for the safety of the data in your virtual machine, Y is a 149 wise choice too. In all other cases (for example, if you're just 150 playing around with User-Mode Linux) you can choose N. 151 152config BLK_DEV_COW_COMMON 153 bool 154 default BLK_DEV_UBD 155 156config BLK_DEV_LOOP 157 tristate "Loopback device support" 158 help 159 Saying Y here will allow you to use a regular file as a block 160 device; you can then create a file system on that block device and 161 mount it just as you would mount other block devices such as hard 162 drive partitions, CD-ROM drives or floppy drives. The loop devices 163 are block special device files with major number 7 and typically 164 called /dev/loop0, /dev/loop1 etc. 165 166 This is useful if you want to check an ISO 9660 file system before 167 burning the CD, or if you want to use floppy images without first 168 writing them to floppy. Furthermore, some Linux distributions avoid 169 the need for a dedicated Linux partition by keeping their complete 170 root file system inside a DOS FAT file using this loop device 171 driver. 172 173 To use the loop device, you need the losetup utility, found in the 174 util-linux package, see 175 <https://www.kernel.org/pub/linux/utils/util-linux/>. 176 177 The loop device driver can also be used to "hide" a file system in 178 a disk partition, floppy, or regular file, either using encryption 179 (scrambling the data) or steganography (hiding the data in the low 180 bits of, say, a sound file). This is also safe if the file resides 181 on a remote file server. 182 183 Note that this loop device has nothing to do with the loopback 184 device used for network connections from the machine to itself. 185 186 To compile this driver as a module, choose M here: the 187 module will be called loop. 188 189 Most users will answer N here. 190 191config BLK_DEV_LOOP_MIN_COUNT 192 int "Number of loop devices to pre-create at init time" 193 depends on BLK_DEV_LOOP 194 default 8 195 help 196 Static number of loop devices to be unconditionally pre-created 197 at init time. 198 199 This default value can be overwritten on the kernel command 200 line or with module-parameter loop.max_loop. 201 202 The historic default is 8. If a late 2011 version of losetup(8) 203 is used, it can be set to 0, since needed loop devices can be 204 dynamically allocated with the /dev/loop-control interface. 205 206source "drivers/block/drbd/Kconfig" 207 208config BLK_DEV_NBD 209 tristate "Network block device support" 210 depends on NET 211 help 212 Saying Y here will allow your computer to be a client for network 213 block devices, i.e. it will be able to use block devices exported by 214 servers (mount file systems on them etc.). Communication between 215 client and server works over TCP/IP networking, but to the client 216 program this is hidden: it looks like a regular local file access to 217 a block device special file such as /dev/nd0. 218 219 Network block devices also allows you to run a block-device in 220 userland (making server and client physically the same computer, 221 communicating using the loopback network device). 222 223 Read <file:Documentation/admin-guide/blockdev/nbd.rst> for more information, 224 especially about where to find the server code, which runs in user 225 space and does not need special kernel support. 226 227 Note that this has nothing to do with the network file systems NFS 228 or Coda; you can say N here even if you intend to use NFS or Coda. 229 230 To compile this driver as a module, choose M here: the 231 module will be called nbd. 232 233 If unsure, say N. 234 235config BLK_DEV_SX8 236 tristate "Promise SATA SX8 support" 237 depends on PCI 238 help 239 Saying Y or M here will enable support for the 240 Promise SATA SX8 controllers. 241 242 Use devices /dev/sx8/$N and /dev/sx8/$Np$M. 243 244config BLK_DEV_RAM 245 tristate "RAM block device support" 246 help 247 Saying Y here will allow you to use a portion of your RAM memory as 248 a block device, so that you can make file systems on it, read and 249 write to it and do all the other things that you can do with normal 250 block devices (such as hard drives). It is usually used to load and 251 store a copy of a minimal root file system off of a floppy into RAM 252 during the initial install of Linux. 253 254 Note that the kernel command line option "ramdisk=XX" is now obsolete. 255 For details, read <file:Documentation/admin-guide/blockdev/ramdisk.rst>. 256 257 To compile this driver as a module, choose M here: the 258 module will be called brd. An alias "rd" has been defined 259 for historical reasons. 260 261 Most normal users won't need the RAM disk functionality, and can 262 thus say N here. 263 264config BLK_DEV_RAM_COUNT 265 int "Default number of RAM disks" 266 default "16" 267 depends on BLK_DEV_RAM 268 help 269 The default value is 16 RAM disks. Change this if you know what you 270 are doing. If you boot from a filesystem that needs to be extracted 271 in memory, you will need at least one RAM disk (e.g. root on cramfs). 272 273config BLK_DEV_RAM_SIZE 274 int "Default RAM disk size (kbytes)" 275 depends on BLK_DEV_RAM 276 default "4096" 277 help 278 The default value is 4096 kilobytes. Only change this if you know 279 what you are doing. 280 281config CDROM_PKTCDVD 282 tristate "Packet writing on CD/DVD media (DEPRECATED)" 283 depends on !UML 284 depends on SCSI 285 select CDROM 286 help 287 Note: This driver is deprecated and will be removed from the 288 kernel in the near future! 289 290 If you have a CDROM/DVD drive that supports packet writing, say 291 Y to include support. It should work with any MMC/Mt Fuji 292 compliant ATAPI or SCSI drive, which is just about any newer 293 DVD/CD writer. 294 295 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs 296 is possible. 297 DVD-RW disks must be in restricted overwrite mode. 298 299 See the file <file:Documentation/cdrom/packet-writing.rst> 300 for further information on the use of this driver. 301 302 To compile this driver as a module, choose M here: the 303 module will be called pktcdvd. 304 305config CDROM_PKTCDVD_BUFFERS 306 int "Free buffers for data gathering" 307 depends on CDROM_PKTCDVD 308 default "8" 309 help 310 This controls the maximum number of active concurrent packets. More 311 concurrent packets can increase write performance, but also require 312 more memory. Each concurrent packet will require approximately 64Kb 313 of non-swappable kernel memory, memory which will be allocated when 314 a disc is opened for writing. 315 316config CDROM_PKTCDVD_WCACHE 317 bool "Enable write caching" 318 depends on CDROM_PKTCDVD 319 help 320 If enabled, write caching will be set for the CD-R/W device. For now 321 this option is dangerous unless the CD-RW media is known good, as we 322 don't do deferred write error handling yet. 323 324config ATA_OVER_ETH 325 tristate "ATA over Ethernet support" 326 depends on NET 327 help 328 This driver provides Support for ATA over Ethernet block 329 devices like the Coraid EtherDrive (R) Storage Blade. 330 331config SUNVDC 332 tristate "Sun Virtual Disk Client support" 333 depends on SUN_LDOMS 334 help 335 Support for virtual disk devices as a client under Sun 336 Logical Domains. 337 338source "drivers/s390/block/Kconfig" 339 340config XEN_BLKDEV_FRONTEND 341 tristate "Xen virtual block device support" 342 depends on XEN 343 default y 344 select XEN_XENBUS_FRONTEND 345 help 346 This driver implements the front-end of the Xen virtual 347 block device driver. It communicates with a back-end driver 348 in another domain which drives the actual block device. 349 350config XEN_BLKDEV_BACKEND 351 tristate "Xen block-device backend driver" 352 depends on XEN_BACKEND 353 help 354 The block-device backend driver allows the kernel to export its 355 block devices to other guests via a high-performance shared-memory 356 interface. 357 358 The corresponding Linux frontend driver is enabled by the 359 CONFIG_XEN_BLKDEV_FRONTEND configuration option. 360 361 The backend driver attaches itself to a any block device specified 362 in the XenBus configuration. There are no limits to what the block 363 device as long as it has a major and minor. 364 365 If you are compiling a kernel to run in a Xen block backend driver 366 domain (often this is domain 0) you should say Y here. To 367 compile this driver as a module, chose M here: the module 368 will be called xen-blkback. 369 370 371config VIRTIO_BLK 372 tristate "Virtio block driver" 373 depends on VIRTIO 374 select SG_POOL 375 help 376 This is the virtual block driver for virtio. It can be used with 377 QEMU based VMMs (like KVM or Xen). Say Y or M. 378 379config BLK_DEV_RBD 380 tristate "Rados block device (RBD)" 381 depends on INET && BLOCK 382 select CEPH_LIB 383 select LIBCRC32C 384 select CRYPTO_AES 385 select CRYPTO 386 help 387 Say Y here if you want include the Rados block device, which stripes 388 a block device over objects stored in the Ceph distributed object 389 store. 390 391 More information at http://ceph.newdream.net/. 392 393 If unsure, say N. 394 395source "drivers/block/rnbd/Kconfig" 396 397endif # BLK_DEV 398