2 # Block device driver configuration
8 tristate "Normal floppy disk support"
9 depends on (!ARCH_S390 && !M68K && !IA64) || 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 "PS/2 ESDI hard disk support"
38 depends on MCA && MCA_LEGACY
40 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
43 To compile this driver as a module, choose M here: the
44 module will be called ps2esdi.
47 tristate "Amiga Zorro II ramdisk support"
50 This enables support for using Chip RAM and Zorro II RAM as a
51 ramdisk or as a swap partition. Say Y if you want to include this
54 To compile this driver as a module, choose M here: the
55 module will be called z2ram.
58 tristate "Atari ACSI support"
59 depends on ATARI && BROKEN
61 This enables support for the Atari ACSI interface. The driver
62 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
63 be switched to that mode. Due to the ACSI command format, only disks
64 up to 1 GB are supported. Special support for certain ACSI to SCSI
65 adapters, which could relax that, isn't included yet. The ACSI
66 driver is also the basis for certain other drivers for devices
67 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
68 Ethernet, and PAMsNet Ethernet. If you want to use one of these
69 devices, you need ACSI support, too.
71 To compile this driver as a module, choose M here: the
72 module will be called acsi.
74 comment "Some devices (e.g. CD jukebox) support multiple LUNs"
75 depends on ATARI && ATARI_ACSI
78 bool "Probe all LUNs on each ACSI device"
81 If you have a ACSI device that supports more than one LUN (Logical
82 Unit Number), e.g. a CD jukebox, you should say Y here so that all
83 will be found by the ACSI driver. An ACSI device with multiple LUNs
84 acts logically like multiple ACSI devices. The vast majority of ACSI
85 devices have only one LUN, and so most people can say N here and
86 should in fact do so, because it is safer.
89 tristate "Atari SLM laser printer support"
90 depends on ATARI && ATARI_ACSI!=n
92 If you have an Atari SLM laser printer, say Y to include support for
93 it in the kernel. Otherwise, say N. This driver is also available as
94 a module ( = code which can be inserted in and removed from the
95 running kernel whenever you want). The module will be called
96 acsi_slm. Be warned: the driver needs much ST-RAM and can cause
97 problems due to that fact!
100 tristate "XT hard disk support"
103 Very old 8 bit hard disk controllers used in the IBM XT computer
104 will be supported if you say Y here.
106 To compile this driver as a module, choose M here: the
107 module will be called xd.
109 It's pretty unlikely that you have one of these: say N.
112 tristate "Parallel port IDE device support"
115 There are many external CD-ROM and disk devices that connect through
116 your computer's parallel port. Most of them are actually IDE devices
117 using a parallel port IDE adapter. This option enables the PARIDE
118 subsystem which contains drivers for many of these external drives.
119 Read <file:Documentation/paride.txt> for more information.
121 If you have said Y to the "Parallel-port support" configuration
122 option, you may share a single port between your printer and other
123 parallel port devices. Answer Y to build PARIDE support into your
124 kernel, or M if you would like to build it as a loadable module. If
125 your parallel port support is in a loadable module, you must build
126 PARIDE as a module. If you built PARIDE support into your kernel,
127 you may still build the individual protocol modules and high-level
128 drivers as loadable modules. If you build this support as a module,
129 it will be called paride.
131 To use the PARIDE support, you must say Y or M here and also to at
132 least one high-level driver (e.g. "Parallel port IDE disks",
133 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
134 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
135 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
138 source "drivers/block/paride/Kconfig"
141 tristate "Compaq SMART2 support"
144 This is the driver for Compaq Smart Array controllers. Everyone
145 using these boards should say Y here. See the file
146 <file:Documentation/cpqarray.txt> for the current list of boards
147 supported by this driver, and for further information on the use of
150 config BLK_CPQ_CISS_DA
151 tristate "Compaq Smart Array 5xxx support"
154 This is the driver for Compaq Smart Array 5xxx controllers.
155 Everyone using these boards should say Y here.
156 See <file:Documentation/cciss.txt> for the current list of
157 boards supported by this driver, and for further information
158 on the use of this driver.
160 config CISS_SCSI_TAPE
161 bool "SCSI tape drive support for Smart Array 5xxx"
162 depends on BLK_CPQ_CISS_DA && SCSI
164 When enabled (Y), this option allows SCSI tape drives and SCSI medium
165 changers (tape robots) to be accessed via a Compaq 5xxx array
166 controller. (See Documentation/cciss.txt for more details.)
168 "SCSI support" and "SCSI tape support" must also be enabled for this
171 When this option is disabled (N), the SCSI portion of the driver
174 config BLK_DEV_DAC960
175 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
178 This driver adds support for the Mylex DAC960, AcceleRAID, and
179 eXtremeRAID PCI RAID controllers. See the file
180 <file:Documentation/README.DAC960> for further information about
183 To compile this driver as a module, choose M here: the
184 module will be called DAC960.
187 tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
188 depends on PCI && EXPERIMENTAL
190 Saying Y here will include support for the MM5415 family of
191 battery backed (Non-volatile) RAM cards.
194 The cards appear as block devices that can be partitioned into
195 as many as 15 partitions.
197 To compile this driver as a module, choose M here: the
198 module will be called umem.
200 The umem driver has not yet been allocated a MAJOR number, so
201 one is chosen dynamically. Use "devfs" or look in /proc/devices
202 for the device number
205 tristate "Loopback device support"
207 Saying Y here will allow you to use a regular file as a block
208 device; you can then create a file system on that block device and
209 mount it just as you would mount other block devices such as hard
210 drive partitions, CD-ROM drives or floppy drives. The loop devices
211 are block special device files with major number 7 and typically
212 called /dev/loop0, /dev/loop1 etc.
214 This is useful if you want to check an ISO 9660 file system before
215 burning the CD, or if you want to use floppy images without first
216 writing them to floppy. Furthermore, some Linux distributions avoid
217 the need for a dedicated Linux partition by keeping their complete
218 root file system inside a DOS FAT file using this loop device
221 To use the loop device, you need the losetup utility, found in the
222 util-linux package, see
223 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
225 The loop device driver can also be used to "hide" a file system in
226 a disk partition, floppy, or regular file, either using encryption
227 (scrambling the data) or steganography (hiding the data in the low
228 bits of, say, a sound file). This is also safe if the file resides
229 on a remote file server.
231 There are several ways of encrypting disks. Some of these require
232 kernel patches. The vanilla kernel offers the cryptoloop option
233 and a Device Mapper target (which is superior, as it supports all
234 file systems). If you want to use the cryptoloop, say Y to both
235 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
236 or later) version of util-linux. Additionally, be aware that
237 the cryptoloop is not safe for storing journaled filesystems.
239 Note that this loop device has nothing to do with the loopback
240 device used for network connections from the machine to itself.
242 To compile this driver as a module, choose M here: the
243 module will be called loop.
245 Most users will answer N here.
247 config BLK_DEV_CRYPTOLOOP
248 tristate "Cryptoloop Support"
250 depends on BLK_DEV_LOOP
252 Say Y here if you want to be able to use the ciphers that are
253 provided by the CryptoAPI as loop transformation. This might be
254 used as hard disk encryption.
256 WARNING: This device is not safe for journaled file systems like
257 ext3 or Reiserfs. Please use the Device Mapper crypto module
258 instead, which can be configured to be on-disk compatible with the
262 tristate "Network block device support"
265 Saying Y here will allow your computer to be a client for network
266 block devices, i.e. it will be able to use block devices exported by
267 servers (mount file systems on them etc.). Communication between
268 client and server works over TCP/IP networking, but to the client
269 program this is hidden: it looks like a regular local file access to
270 a block device special file such as /dev/nd0.
272 Network block devices also allows you to run a block-device in
273 userland (making server and client physically the same computer,
274 communicating using the loopback network device).
276 Read <file:Documentation/nbd.txt> for more information, especially
277 about where to find the server code, which runs in user space and
278 does not need special kernel support.
280 Note that this has nothing to do with the network file systems NFS
281 or Coda; you can say N here even if you intend to use NFS or Coda.
283 To compile this driver as a module, choose M here: the
284 module will be called nbd.
289 tristate "Promise SATA SX8 support"
292 Saying Y or M here will enable support for the
293 Promise SATA SX8 controllers.
295 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
298 tristate "RAM disk support"
300 Saying Y here will allow you to use a portion of your RAM memory as
301 a block device, so that you can make file systems on it, read and
302 write to it and do all the other things that you can do with normal
303 block devices (such as hard drives). It is usually used to load and
304 store a copy of a minimal root file system off of a floppy into RAM
305 during the initial install of Linux.
307 Note that the kernel command line option "ramdisk=XX" is now
308 obsolete. For details, read <file:Documentation/ramdisk.txt>.
310 To compile this driver as a module, choose M here: the
311 module will be called rd.
313 Most normal users won't need the RAM disk functionality, and can
316 config BLK_DEV_RAM_SIZE
317 int "Default RAM disk size (kbytes)"
318 depends on BLK_DEV_RAM
321 The default value is 4096 kilobytes. Only change this if you know
322 what are you doing. If you are using IBM S/390, then set this to
325 config BLK_DEV_INITRD
326 bool "Initial RAM disk (initrd) support"
327 depends on BLK_DEV_RAM=y
329 The initial RAM disk is a RAM disk that is loaded by the boot loader
330 (loadlin or lilo) and that is mounted as root before the normal boot
331 procedure. It is typically used to load modules needed to mount the
332 "real" root file system, etc. See <file:Documentation/initrd.txt>
336 bool "Support for Large Block Devices"
337 depends on X86 || MIPS32 || PPC32 || ARCH_S390_31 || SUPERH
339 Say Y here if you want to attach large (bigger than 2TB) discs to
340 your machine, or if you want to have a raid or loopback device
341 bigger than 2TB. Otherwise say N.
343 source "drivers/s390/block/Kconfig"