2 # Block device driver configuration
10 tristate "Normal floppy disk support"
11 depends on ARCH_MAY_HAVE_PC_FDC
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.
20 To compile this driver as a module, choose M here: the
21 module will be called floppy.
24 tristate "Amiga floppy support"
28 tristate "Atari floppy support"
32 tristate "Support for PowerMac floppy"
33 depends on PPC_PMAC && !PPC_PMAC64
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.
39 tristate "PS/2 ESDI hard disk support"
40 depends on MCA && MCA_LEGACY && BROKEN
42 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
45 To compile this driver as a module, choose M here: the
46 module will be called ps2esdi.
49 tristate "Amiga Zorro II ramdisk support"
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
56 To compile this driver as a module, choose M here: the
57 module will be called z2ram.
60 tristate "Atari ACSI support"
61 depends on ATARI && BROKEN
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.
73 To compile this driver as a module, choose M here: the
74 module will be called acsi.
76 comment "Some devices (e.g. CD jukebox) support multiple LUNs"
77 depends on ATARI && ATARI_ACSI
80 bool "Probe all LUNs on each ACSI device"
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.
91 tristate "Atari SLM laser printer support"
92 depends on ATARI && ATARI_ACSI!=n
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!
102 tristate "XT hard disk support"
103 depends on ISA && ISA_DMA_API
105 Very old 8 bit hard disk controllers used in the IBM XT computer
106 will be supported if you say Y here.
108 To compile this driver as a module, choose M here: the
109 module will be called xd.
111 It's pretty unlikely that you have one of these: say N.
114 tristate "Parallel port IDE device support"
115 depends on PARPORT_PC
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.
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.
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"
140 source "drivers/block/paride/Kconfig"
143 tristate "Compaq SMART2 support"
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
152 config BLK_CPQ_CISS_DA
153 tristate "Compaq Smart Array 5xxx support"
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.
162 config 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
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.)
171 "SCSI support" and "SCSI tape support" must also be enabled for this
174 When this option is disabled (N), the SCSI portion of the driver
177 config BLK_DEV_DAC960
178 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
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
186 To compile this driver as a module, choose M here: the
187 module will be called DAC960.
190 tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
191 depends on PCI && EXPERIMENTAL
193 Saying Y here will include support for the MM5415 family of
194 battery backed (Non-volatile) RAM cards.
195 <http://www.umem.com/>
197 The cards appear as block devices that can be partitioned into
198 as many as 15 partitions.
200 To compile this driver as a module, choose M here: the
201 module will be called umem.
203 The umem driver has not yet been allocated a MAJOR number, so
204 one is chosen dynamically.
207 bool "Virtual block device"
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
215 config BLK_DEV_UBD_SYNC
216 bool "Always do synchronous disk IO for UBD"
217 depends on BLK_DEV_UBD
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
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.
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.
235 config BLK_DEV_COW_COMMON
240 tristate "Example IO memory driver (BROKEN)"
241 depends on UML && BROKEN
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.
250 For more information, see
251 <http://user-mode-linux.sourceforge.net/iomem.html>.
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.
257 tristate "Loopback device support"
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.
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
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/>.
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.
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.
291 Note that this loop device has nothing to do with the loopback
292 device used for network connections from the machine to itself.
294 To compile this driver as a module, choose M here: the
295 module will be called loop.
297 Most users will answer N here.
299 config BLK_DEV_CRYPTOLOOP
300 tristate "Cryptoloop Support"
303 depends on BLK_DEV_LOOP
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.
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
315 tristate "Virtual Root device support"
318 Saying Y here will allow you to use quota/fs ioctls on a shared
319 partition within a virtual server without compromising security.
322 tristate "Network block device support"
325 Saying Y here will allow your computer to be a client for network
326 block devices, i.e. it will be able to use block devices exported by
327 servers (mount file systems on them etc.). Communication between
328 client and server works over TCP/IP networking, but to the client
329 program this is hidden: it looks like a regular local file access to
330 a block device special file such as /dev/nd0.
332 Network block devices also allows you to run a block-device in
333 userland (making server and client physically the same computer,
334 communicating using the loopback network device).
336 Read <file:Documentation/nbd.txt> for more information, especially
337 about where to find the server code, which runs in user space and
338 does not need special kernel support.
340 Note that this has nothing to do with the network file systems NFS
341 or Coda; you can say N here even if you intend to use NFS or Coda.
343 To compile this driver as a module, choose M here: the
344 module will be called nbd.
349 tristate "Promise SATA SX8 support"
352 Saying Y or M here will enable support for the
353 Promise SATA SX8 controllers.
355 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
358 tristate "Low Performance USB Block driver"
361 This driver supports certain USB attached storage devices
364 If you enable this driver, it is recommended to avoid conflicts
365 with usb-storage by enabling USB_LIBUSUAL.
370 tristate "RAM disk support"
372 Saying Y here will allow you to use a portion of your RAM memory as
373 a block device, so that you can make file systems on it, read and
374 write to it and do all the other things that you can do with normal
375 block devices (such as hard drives). It is usually used to load and
376 store a copy of a minimal root file system off of a floppy into RAM
377 during the initial install of Linux.
379 Note that the kernel command line option "ramdisk=XX" is now
380 obsolete. For details, read <file:Documentation/ramdisk.txt>.
382 To compile this driver as a module, choose M here: the
383 module will be called rd.
385 Most normal users won't need the RAM disk functionality, and can
388 config BLK_DEV_RAM_COUNT
389 int "Default number of RAM disks"
391 depends on BLK_DEV_RAM
393 The default value is 16 RAM disks. Change this if you know what
394 are doing. If you boot from a filesystem that needs to be extracted
395 in memory, you will need at least one RAM disk (e.g. root on cramfs).
397 config BLK_DEV_RAM_SIZE
398 int "Default RAM disk size (kbytes)"
399 depends on BLK_DEV_RAM
402 The default value is 4096 kilobytes. Only change this if you know
403 what are you doing. If you are using IBM S/390, then set this to
406 config BLK_DEV_RAM_BLOCKSIZE
407 int "Default RAM disk block size (bytes)"
408 depends on BLK_DEV_RAM
411 The default value is 1024 bytes. PAGE_SIZE is a much more
412 efficient choice however. The default is kept to ensure initrd
413 setups function - apparently needed by the rd_load_image routine
414 that supposes the filesystem in the image uses a 1024 blocksize.
416 config BLK_DEV_INITRD
417 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
418 depends on BROKEN || !FRV
420 The initial RAM filesystem is a ramfs which is loaded by the
421 boot loader (loadlin or lilo) and that is mounted as root
422 before the normal boot procedure. It is typically used to
423 load modules needed to mount the "real" root file system,
424 etc. See <file:Documentation/initrd.txt> for details.
426 If RAM disk support (BLK_DEV_RAM) is also included, this
427 also enables initial RAM disk (initrd) support.
431 tristate "Packet writing on CD/DVD media"
434 If you have a CDROM/DVD drive that supports packet writing, say
435 Y to include support. It should work with any MMC/Mt Fuji
436 compliant ATAPI or SCSI drive, which is just about any newer
439 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
441 DVD-RW disks must be in restricted overwrite mode.
443 See the file <file:Documentation/cdrom/packet-writing.txt>
444 for further information on the use of this driver.
446 To compile this driver as a module, choose M here: the
447 module will be called pktcdvd.
449 config CDROM_PKTCDVD_BUFFERS
450 int "Free buffers for data gathering"
451 depends on CDROM_PKTCDVD
454 This controls the maximum number of active concurrent packets. More
455 concurrent packets can increase write performance, but also require
456 more memory. Each concurrent packet will require approximately 64Kb
457 of non-swappable kernel memory, memory which will be allocated when
458 a disc is opened for writing.
460 config CDROM_PKTCDVD_WCACHE
461 bool "Enable write caching (EXPERIMENTAL)"
462 depends on CDROM_PKTCDVD && EXPERIMENTAL
464 If enabled, write caching will be set for the CD-R/W device. For now
465 this option is dangerous unless the CD-RW media is known good, as we
466 don't do deferred write error handling yet.
468 source "drivers/s390/block/Kconfig"
471 tristate "ATA over Ethernet support"
474 This driver provides Support for ATA over Ethernet block
475 devices like the Coraid EtherDrive (R) Storage Blade.