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