2 # Block device driver configuration
8 tristate "Normal floppy disk support"
9 depends on (!ARCH_S390 && !M68K && !IA64 && !USERMODE) || Q40 || (SUN3X && BROKEN)
11 If you want to use the floppy disk drive(s) of your PC under Linux,
12 say Y. Information about this driver, especially important for IBM
13 Thinkpad users, is contained in <file:Documentation/floppy.txt>.
14 That file also contains the location of the Floppy driver FAQ as
15 well as location of the fdutils package used to configure additional
16 parameters of the driver at run time.
18 To compile this driver as a module, choose M here: the
19 module will be called floppy.
22 tristate "Amiga floppy support"
26 tristate "Atari floppy support"
29 config BLK_DEV_SWIM_IOP
30 bool "Macintosh IIfx/Quadra 900/Quadra 950 floppy support (EXPERIMENTAL)"
31 depends on MAC && EXPERIMENTAL && BROKEN
33 Say Y here to support the SWIM (Super Woz Integrated Machine) IOP
34 floppy controller on the Macintosh IIfx and Quadra 900/950.
37 tristate "Support for PowerMac floppy"
38 depends on PPC_PMAC && !PPC_PMAC64
40 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
41 floppy controller, say Y here. Most commonly found in PowerMacs.
44 tristate "PS/2 ESDI hard disk support"
45 depends on MCA && MCA_LEGACY
47 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
50 To compile this driver as a module, choose M here: the
51 module will be called ps2esdi.
54 tristate "Amiga Zorro II ramdisk support"
57 This enables support for using Chip RAM and Zorro II RAM as a
58 ramdisk or as a swap partition. Say Y if you want to include this
61 To compile this driver as a module, choose M here: the
62 module will be called z2ram.
65 tristate "Atari ACSI support"
66 depends on ATARI && BROKEN
68 This enables support for the Atari ACSI interface. The driver
69 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
70 be switched to that mode. Due to the ACSI command format, only disks
71 up to 1 GB are supported. Special support for certain ACSI to SCSI
72 adapters, which could relax that, isn't included yet. The ACSI
73 driver is also the basis for certain other drivers for devices
74 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
75 Ethernet, and PAMsNet Ethernet. If you want to use one of these
76 devices, you need ACSI support, too.
78 To compile this driver as a module, choose M here: the
79 module will be called acsi.
81 comment "Some devices (e.g. CD jukebox) support multiple LUNs"
82 depends on ATARI && ATARI_ACSI
85 bool "Probe all LUNs on each ACSI device"
88 If you have a ACSI device that supports more than one LUN (Logical
89 Unit Number), e.g. a CD jukebox, you should say Y here so that all
90 will be found by the ACSI driver. An ACSI device with multiple LUNs
91 acts logically like multiple ACSI devices. The vast majority of ACSI
92 devices have only one LUN, and so most people can say N here and
93 should in fact do so, because it is safer.
96 tristate "Atari SLM laser printer support"
97 depends on ATARI && ATARI_ACSI!=n
99 If you have an Atari SLM laser printer, say Y to include support for
100 it in the kernel. Otherwise, say N. This driver is also available as
101 a module ( = code which can be inserted in and removed from the
102 running kernel whenever you want). The module will be called
103 acsi_slm. Be warned: the driver needs much ST-RAM and can cause
104 problems due to that fact!
107 tristate "XT hard disk support"
110 Very old 8 bit hard disk controllers used in the IBM XT computer
111 will be supported if you say Y here.
113 To compile this driver as a module, choose M here: the
114 module will be called xd.
116 It's pretty unlikely that you have one of these: say N.
119 tristate "Parallel port IDE device support"
122 There are many external CD-ROM and disk devices that connect through
123 your computer's parallel port. Most of them are actually IDE devices
124 using a parallel port IDE adapter. This option enables the PARIDE
125 subsystem which contains drivers for many of these external drives.
126 Read <file:Documentation/paride.txt> for more information.
128 If you have said Y to the "Parallel-port support" configuration
129 option, you may share a single port between your printer and other
130 parallel port devices. Answer Y to build PARIDE support into your
131 kernel, or M if you would like to build it as a loadable module. If
132 your parallel port support is in a loadable module, you must build
133 PARIDE as a module. If you built PARIDE support into your kernel,
134 you may still build the individual protocol modules and high-level
135 drivers as loadable modules. If you build this support as a module,
136 it will be called paride.
138 To use the PARIDE support, you must say Y or M here and also to at
139 least one high-level driver (e.g. "Parallel port IDE disks",
140 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
141 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
142 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
145 source "drivers/block/paride/Kconfig"
148 tristate "Compaq SMART2 support"
151 This is the driver for Compaq Smart Array controllers. Everyone
152 using these boards should say Y here. See the file
153 <file:Documentation/cpqarray.txt> for the current list of boards
154 supported by this driver, and for further information on the use of
157 config BLK_CPQ_CISS_DA
158 tristate "Compaq Smart Array 5xxx support"
161 This is the driver for Compaq Smart Array 5xxx controllers.
162 Everyone using these boards should say Y here.
163 See <file:Documentation/cciss.txt> for the current list of
164 boards supported by this driver, and for further information
165 on the use of this driver.
167 config CISS_SCSI_TAPE
168 bool "SCSI tape drive support for Smart Array 5xxx"
169 depends on BLK_CPQ_CISS_DA && SCSI && PROC_FS
171 When enabled (Y), this option allows SCSI tape drives and SCSI medium
172 changers (tape robots) to be accessed via a Compaq 5xxx array
173 controller. (See <file:Documentation/cciss.txt> for more details.)
175 "SCSI support" and "SCSI tape support" must also be enabled for this
178 When this option is disabled (N), the SCSI portion of the driver
181 config BLK_DEV_DAC960
182 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
185 This driver adds support for the Mylex DAC960, AcceleRAID, and
186 eXtremeRAID PCI RAID controllers. See the file
187 <file:Documentation/README.DAC960> for further information about
190 To compile this driver as a module, choose M here: the
191 module will be called DAC960.
194 tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
195 depends on PCI && EXPERIMENTAL
197 Saying Y here will include support for the MM5415 family of
198 battery backed (Non-volatile) RAM cards.
199 <http://www.umem.com/>
201 The cards appear as block devices that can be partitioned into
202 as many as 15 partitions.
204 To compile this driver as a module, choose M here: the
205 module will be called umem.
207 The umem driver has not yet been allocated a MAJOR number, so
208 one is chosen dynamically. Use "devfs" or look in /proc/devices
209 for the device number
212 bool "Virtual block device"
215 The User-Mode Linux port includes a driver called UBD which will let
216 you access arbitrary files on the host computer as block devices.
217 Unless you know that you do not need such virtual block devices say
220 config BLK_DEV_UBD_SYNC
221 bool "Always do synchronous disk IO for UBD"
222 depends on BLK_DEV_UBD
224 Writes to the virtual block device are not immediately written to the
225 host's disk; this may cause problems if, for example, the User-Mode
226 Linux 'Virtual Machine' uses a journalling filesystem and the host
229 Synchronous operation (i.e. always writing data to the host's disk
230 immediately) is configurable on a per-UBD basis by using a special
231 kernel command line option. Alternatively, you can say Y here to
232 turn on synchronous operation by default for all block devices.
234 If you're running a journalling file system (like reiserfs, for
235 example) in your virtual machine, you will want to say Y here. If
236 you care for the safety of the data in your virtual machine, Y is a
237 wise choice too. In all other cases (for example, if you're just
238 playing around with User-Mode Linux) you can choose N.
240 config BLK_DEV_COW_COMMON
245 tristate "Example IO memory driver (BROKEN)"
246 depends on USERMODE && BROKEN
248 The User-Mode Linux port can provide support for IO Memory
249 emulation with this option. This allows a host file to be
250 specified as an I/O region on the kernel command line. That file
251 will be mapped into UML's kernel address space where a driver can
252 locate it and do whatever it wants with the memory, including
253 providing an interface to it for UML processes to use.
255 For more information, see
256 <http://user-mode-linux.sourceforge.net/iomem.html>.
258 If you'd like to be able to provide a simulated IO port space for
259 User-Mode Linux processes, say Y. If unsure, say N.
262 tristate "Loopback device support"
264 Saying Y here will allow you to use a regular file as a block
265 device; you can then create a file system on that block device and
266 mount it just as you would mount other block devices such as hard
267 drive partitions, CD-ROM drives or floppy drives. The loop devices
268 are block special device files with major number 7 and typically
269 called /dev/loop0, /dev/loop1 etc.
271 This is useful if you want to check an ISO 9660 file system before
272 burning the CD, or if you want to use floppy images without first
273 writing them to floppy. Furthermore, some Linux distributions avoid
274 the need for a dedicated Linux partition by keeping their complete
275 root file system inside a DOS FAT file using this loop device
278 To use the loop device, you need the losetup utility, found in the
279 util-linux package, see
280 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
282 The loop device driver can also be used to "hide" a file system in
283 a disk partition, floppy, or regular file, either using encryption
284 (scrambling the data) or steganography (hiding the data in the low
285 bits of, say, a sound file). This is also safe if the file resides
286 on a remote file server.
288 There are several ways of encrypting disks. Some of these require
289 kernel patches. The vanilla kernel offers the cryptoloop option
290 and a Device Mapper target (which is superior, as it supports all
291 file systems). If you want to use the cryptoloop, say Y to both
292 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
293 or later) version of util-linux. Additionally, be aware that
294 the cryptoloop is not safe for storing journaled filesystems.
296 Note that this loop device has nothing to do with the loopback
297 device used for network connections from the machine to itself.
299 To compile this driver as a module, choose M here: the
300 module will be called loop.
302 Most users will answer N here.
304 config BLK_DEV_CRYPTOLOOP
305 tristate "Cryptoloop Support"
307 depends on BLK_DEV_LOOP
309 Say Y here if you want to be able to use the ciphers that are
310 provided by the CryptoAPI as loop transformation. This might be
311 used as hard disk encryption.
313 WARNING: This device is not safe for journaled file systems like
314 ext3 or Reiserfs. Please use the Device Mapper crypto module
315 instead, which can be configured to be on-disk compatible with the
319 tristate "Virtual Root device support"
321 Saying Y here will allow you to use quota/fs ioctls on a shared
322 partition within a virtual server without compromising security.
325 tristate "Network block device support"
328 Saying Y here will allow your computer to be a client for network
329 block devices, i.e. it will be able to use block devices exported by
330 servers (mount file systems on them etc.). Communication between
331 client and server works over TCP/IP networking, but to the client
332 program this is hidden: it looks like a regular local file access to
333 a block device special file such as /dev/nd0.
335 Network block devices also allows you to run a block-device in
336 userland (making server and client physically the same computer,
337 communicating using the loopback network device).
339 Read <file:Documentation/nbd.txt> for more information, especially
340 about where to find the server code, which runs in user space and
341 does not need special kernel support.
343 Note that this has nothing to do with the network file systems NFS
344 or Coda; you can say N here even if you intend to use NFS or Coda.
346 To compile this driver as a module, choose M here: the
347 module will be called nbd.
352 tristate "Promise SATA SX8 support"
355 Saying Y or M here will enable support for the
356 Promise SATA SX8 controllers.
358 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
361 tristate "Low Performance USB Block driver"
364 This driver supports certain USB attached storage devices
367 Warning: Enabling this cripples the usb-storage driver.
372 tristate "RAM disk support"
374 Saying Y here will allow you to use a portion of your RAM memory as
375 a block device, so that you can make file systems on it, read and
376 write to it and do all the other things that you can do with normal
377 block devices (such as hard drives). It is usually used to load and
378 store a copy of a minimal root file system off of a floppy into RAM
379 during the initial install of Linux.
381 Note that the kernel command line option "ramdisk=XX" is now
382 obsolete. For details, read <file:Documentation/ramdisk.txt>.
384 To compile this driver as a module, choose M here: the
385 module will be called rd.
387 Most normal users won't need the RAM disk functionality, and can
390 config BLK_DEV_RAM_COUNT
391 int "Default number of RAM disks" if BLK_DEV_RAM
394 The default value is 16 RAM disks. Change this if you know what
395 are doing. If you boot from a filesystem that needs to be extracted
396 in memory, you will need at least one RAM disk (e.g. root on cramfs).
398 config BLK_DEV_RAM_SIZE
399 int "Default RAM disk size (kbytes)"
400 depends on BLK_DEV_RAM
403 The default value is 4096 kilobytes. Only change this if you know
404 what are you doing. If you are using IBM S/390, then set this to
407 config BLK_DEV_INITRD
408 bool "Initial RAM disk (initrd) support"
409 depends on BLK_DEV_RAM=y
411 The initial RAM disk is a RAM disk that is loaded by the boot loader
412 (loadlin or lilo) and that is mounted as root before the normal boot
413 procedure. It is typically used to load modules needed to mount the
414 "real" root file system, etc. See <file:Documentation/initrd.txt>
417 config INITRAMFS_SOURCE
418 string "Initramfs source file(s)"
421 This can be either a single cpio archive with a .cpio suffix or a
422 space-separated list of directories and files for building the
423 initramfs image. A cpio archive should contain a filesystem archive
424 to be used as an initramfs image. Directories should contain a
425 filesystem layout to be included in the initramfs image. Files
426 should contain entries according to the format described by the
427 "usr/gen_init_cpio" program in the kernel tree.
429 When multiple directories and files are specified then the
430 initramfs image will be the aggregate of all of them.
432 See <file:Documentation/early-userspace/README for more details.
434 If you are not sure, leave it blank.
436 config INITRAMFS_ROOT_UID
437 int "User ID to map to 0 (user root)"
438 depends on INITRAMFS_SOURCE!=""
441 This setting is only meaningful if the INITRAMFS_SOURCE is
442 contains a directory. Setting this user ID (UID) to something
443 other than "0" will cause all files owned by that UID to be
444 owned by user root in the initial ramdisk image.
446 If you are not sure, leave it set to "0".
448 config INITRAMFS_ROOT_GID
449 int "Group ID to map to 0 (group root)"
450 depends on INITRAMFS_SOURCE!=""
453 This setting is only meaningful if the INITRAMFS_SOURCE is
454 contains a directory. Setting this group ID (GID) to something
455 other than "0" will cause all files owned by that GID to be
456 owned by group root in the initial ramdisk image.
458 If you are not sure, leave it set to "0".
460 #XXX - it makes sense to enable this only for 32-bit subarch's, not for x86_64
463 bool "Support for Large Block Devices"
464 depends on X86 || MIPS32 || PPC32 || ARCH_S390_31 || SUPERH || USERMODE
466 Say Y here if you want to attach large (bigger than 2TB) discs to
467 your machine, or if you want to have a raid or loopback device
468 bigger than 2TB. Otherwise say N.
471 tristate "Packet writing on CD/DVD media"
474 If you have a CDROM drive that supports packet writing, say Y to
475 include preliminary support. It should work with any MMC/Mt Fuji
476 compliant ATAPI or SCSI drive, which is just about any newer CD
479 Currently only writing to CD-RW, DVD-RW and DVD+RW discs is possible.
480 DVD-RW disks must be in restricted overwrite mode.
482 To compile this driver as a module, choose M here: the
483 module will be called pktcdvd.
485 config CDROM_PKTCDVD_BUFFERS
486 int "Free buffers for data gathering"
487 depends on CDROM_PKTCDVD
490 This controls the maximum number of active concurrent packets. More
491 concurrent packets can increase write performance, but also require
492 more memory. Each concurrent packet will require approximately 64Kb
493 of non-swappable kernel memory, memory which will be allocated at
496 config CDROM_PKTCDVD_WCACHE
497 bool "Enable write caching"
498 depends on CDROM_PKTCDVD
500 If enabled, write caching will be set for the CD-R/W device. For now
501 this option is dangerous unless the CD-RW media is known good, as we
502 don't do deferred write error handling yet.
504 source "drivers/s390/block/Kconfig"
506 source "drivers/block/Kconfig.iosched"
509 tristate "ATA over Ethernet support"
512 This driver provides Support for ATA over Ethernet block
513 devices like the Coraid EtherDrive (R) Storage Blade.