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