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