blob: f2122855d4ec5d714ae0260708aa66562af17db1 [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
Jan Engelhardt06bfb7e2007-08-18 12:56:21 +02009 ---help---
10 Say Y here to get to see options for various different block device
11 drivers. This option alone does not add any kernel code.
12
13 If you say N, all options in this submenu will be skipped and disabled;
14 only do this if you know what you are doing.
David Howells93614012006-09-30 20:45:40 +020015
Jan Engelhardtfd11d172007-07-10 12:26:06 +020016if BLK_DEV
Linus Torvalds1da177e2005-04-16 15:20:36 -070017
18config BLK_DEV_FD
19 tristate "Normal floppy disk support"
viro@ZenIV.linux.org.uka08b6b72005-09-06 01:48:42 +010020 depends on ARCH_MAY_HAVE_PC_FDC
Linus Torvalds1da177e2005-04-16 15:20:36 -070021 ---help---
22 If you want to use the floppy disk drive(s) of your PC under Linux,
23 say Y. Information about this driver, especially important for IBM
24 Thinkpad users, is contained in <file:Documentation/floppy.txt>.
25 That file also contains the location of the Floppy driver FAQ as
26 well as location of the fdutils package used to configure additional
27 parameters of the driver at run time.
28
29 To compile this driver as a module, choose M here: the
30 module will be called floppy.
31
32config AMIGA_FLOPPY
33 tristate "Amiga floppy support"
34 depends on AMIGA
35
36config ATARI_FLOPPY
37 tristate "Atari floppy support"
38 depends on ATARI
39
Linus Torvalds1da177e2005-04-16 15:20:36 -070040config MAC_FLOPPY
41 tristate "Support for PowerMac floppy"
42 depends on PPC_PMAC && !PPC_PMAC64
43 help
44 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
45 floppy controller, say Y here. Most commonly found in PowerMacs.
46
47config BLK_DEV_PS2
48 tristate "PS/2 ESDI hard disk support"
49 depends on MCA && MCA_LEGACY && BROKEN
50 help
51 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
52 hard disk.
53
54 To compile this driver as a module, choose M here: the
55 module will be called ps2esdi.
56
57config AMIGA_Z2RAM
58 tristate "Amiga Zorro II ramdisk support"
59 depends on ZORRO
60 help
61 This enables support for using Chip RAM and Zorro II RAM as a
62 ramdisk or as a swap partition. Say Y if you want to include this
63 driver in the kernel.
64
65 To compile this driver as a module, choose M here: the
66 module will be called z2ram.
67
Linus Torvalds1da177e2005-04-16 15:20:36 -070068config BLK_DEV_XD
69 tristate "XT hard disk support"
Al Viroa5532602005-05-04 05:39:42 +010070 depends on ISA && ISA_DMA_API
Geert Uytterhoeven928923c2007-08-22 14:01:36 -070071 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -070072 help
73 Very old 8 bit hard disk controllers used in the IBM XT computer
74 will be supported if you say Y here.
75
76 To compile this driver as a module, choose M here: the
77 module will be called xd.
78
79 It's pretty unlikely that you have one of these: say N.
80
81config PARIDE
82 tristate "Parallel port IDE device support"
Marko Kohtala6a19b412006-01-06 00:19:49 -080083 depends on PARPORT_PC
Linus Torvalds1da177e2005-04-16 15:20:36 -070084 ---help---
85 There are many external CD-ROM and disk devices that connect through
86 your computer's parallel port. Most of them are actually IDE devices
87 using a parallel port IDE adapter. This option enables the PARIDE
88 subsystem which contains drivers for many of these external drives.
89 Read <file:Documentation/paride.txt> for more information.
90
91 If you have said Y to the "Parallel-port support" configuration
92 option, you may share a single port between your printer and other
93 parallel port devices. Answer Y to build PARIDE support into your
94 kernel, or M if you would like to build it as a loadable module. If
95 your parallel port support is in a loadable module, you must build
96 PARIDE as a module. If you built PARIDE support into your kernel,
97 you may still build the individual protocol modules and high-level
98 drivers as loadable modules. If you build this support as a module,
99 it will be called paride.
100
101 To use the PARIDE support, you must say Y or M here and also to at
102 least one high-level driver (e.g. "Parallel port IDE disks",
103 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
104 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
105 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
106 etc.).
107
Adrian McMenamin74ee1a72008-01-21 18:52:48 +0900108config GDROM
109 tristate "SEGA Dreamcast GD-ROM drive"
110 depends on SH_DREAMCAST
111 help
112 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
113 "GD-ROM" by SEGA to signify it is capable of reading special disks
114 with up to 1 GB of data. This drive will also read standard CD ROM
115 disks. Select this option to access any disks in your GD ROM drive.
116 Most users will want to say "Y" here.
117 You can also build this as a module which will be called gdrom.ko
118
Linus Torvalds1da177e2005-04-16 15:20:36 -0700119source "drivers/block/paride/Kconfig"
120
121config BLK_CPQ_DA
122 tristate "Compaq SMART2 support"
Stephen Rothwellf057eac2007-07-15 23:40:05 -0700123 depends on PCI && VIRT_TO_BUS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700124 help
125 This is the driver for Compaq Smart Array controllers. Everyone
126 using these boards should say Y here. See the file
127 <file:Documentation/cpqarray.txt> for the current list of boards
128 supported by this driver, and for further information on the use of
129 this driver.
130
131config BLK_CPQ_CISS_DA
132 tristate "Compaq Smart Array 5xxx support"
133 depends on PCI
134 help
135 This is the driver for Compaq Smart Array 5xxx controllers.
136 Everyone using these boards should say Y here.
137 See <file:Documentation/cciss.txt> for the current list of
138 boards supported by this driver, and for further information
139 on the use of this driver.
140
141config CISS_SCSI_TAPE
142 bool "SCSI tape drive support for Smart Array 5xxx"
Randy Dunlap3e29fe82006-12-06 20:38:40 -0800143 depends on BLK_CPQ_CISS_DA && PROC_FS
144 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700145 help
146 When enabled (Y), this option allows SCSI tape drives and SCSI medium
147 changers (tape robots) to be accessed via a Compaq 5xxx array
148 controller. (See <file:Documentation/cciss.txt> for more details.)
149
150 "SCSI support" and "SCSI tape support" must also be enabled for this
151 option to work.
152
153 When this option is disabled (N), the SCSI portion of the driver
154 is not compiled.
155
156config BLK_DEV_DAC960
157 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
158 depends on PCI
159 help
160 This driver adds support for the Mylex DAC960, AcceleRAID, and
161 eXtremeRAID PCI RAID controllers. See the file
162 <file:Documentation/README.DAC960> for further information about
163 this driver.
164
165 To compile this driver as a module, choose M here: the
166 module will be called DAC960.
167
168config BLK_DEV_UMEM
169 tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
170 depends on PCI && EXPERIMENTAL
171 ---help---
172 Saying Y here will include support for the MM5415 family of
173 battery backed (Non-volatile) RAM cards.
174 <http://www.umem.com/>
175
176 The cards appear as block devices that can be partitioned into
177 as many as 15 partitions.
178
179 To compile this driver as a module, choose M here: the
180 module will be called umem.
181
182 The umem driver has not yet been allocated a MAJOR number, so
Adrian Bunkbf6ee0a2006-10-03 22:17:48 +0200183 one is chosen dynamically.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700184
185config BLK_DEV_UBD
186 bool "Virtual block device"
187 depends on UML
188 ---help---
189 The User-Mode Linux port includes a driver called UBD which will let
190 you access arbitrary files on the host computer as block devices.
191 Unless you know that you do not need such virtual block devices say
192 Y here.
193
194config BLK_DEV_UBD_SYNC
195 bool "Always do synchronous disk IO for UBD"
196 depends on BLK_DEV_UBD
197 ---help---
198 Writes to the virtual block device are not immediately written to the
199 host's disk; this may cause problems if, for example, the User-Mode
200 Linux 'Virtual Machine' uses a journalling filesystem and the host
201 computer crashes.
202
203 Synchronous operation (i.e. always writing data to the host's disk
204 immediately) is configurable on a per-UBD basis by using a special
205 kernel command line option. Alternatively, you can say Y here to
206 turn on synchronous operation by default for all block devices.
207
208 If you're running a journalling file system (like reiserfs, for
209 example) in your virtual machine, you will want to say Y here. If
210 you care for the safety of the data in your virtual machine, Y is a
211 wise choice too. In all other cases (for example, if you're just
212 playing around with User-Mode Linux) you can choose N.
213
214config BLK_DEV_COW_COMMON
215 bool
216 default BLK_DEV_UBD
217
Linus Torvalds1da177e2005-04-16 15:20:36 -0700218config BLK_DEV_LOOP
219 tristate "Loopback device support"
220 ---help---
221 Saying Y here will allow you to use a regular file as a block
222 device; you can then create a file system on that block device and
223 mount it just as you would mount other block devices such as hard
224 drive partitions, CD-ROM drives or floppy drives. The loop devices
225 are block special device files with major number 7 and typically
226 called /dev/loop0, /dev/loop1 etc.
227
228 This is useful if you want to check an ISO 9660 file system before
229 burning the CD, or if you want to use floppy images without first
230 writing them to floppy. Furthermore, some Linux distributions avoid
231 the need for a dedicated Linux partition by keeping their complete
232 root file system inside a DOS FAT file using this loop device
233 driver.
234
235 To use the loop device, you need the losetup utility, found in the
236 util-linux package, see
237 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
238
239 The loop device driver can also be used to "hide" a file system in
240 a disk partition, floppy, or regular file, either using encryption
241 (scrambling the data) or steganography (hiding the data in the low
242 bits of, say, a sound file). This is also safe if the file resides
243 on a remote file server.
244
245 There are several ways of encrypting disks. Some of these require
246 kernel patches. The vanilla kernel offers the cryptoloop option
247 and a Device Mapper target (which is superior, as it supports all
248 file systems). If you want to use the cryptoloop, say Y to both
249 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
250 or later) version of util-linux. Additionally, be aware that
251 the cryptoloop is not safe for storing journaled filesystems.
252
253 Note that this loop device has nothing to do with the loopback
254 device used for network connections from the machine to itself.
255
256 To compile this driver as a module, choose M here: the
257 module will be called loop.
258
259 Most users will answer N here.
260
261config BLK_DEV_CRYPTOLOOP
262 tristate "Cryptoloop Support"
263 select CRYPTO
Herbert Xu8df3b0a2006-12-02 14:36:03 +1100264 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700265 depends on BLK_DEV_LOOP
266 ---help---
267 Say Y here if you want to be able to use the ciphers that are
268 provided by the CryptoAPI as loop transformation. This might be
269 used as hard disk encryption.
270
271 WARNING: This device is not safe for journaled file systems like
272 ext3 or Reiserfs. Please use the Device Mapper crypto module
273 instead, which can be configured to be on-disk compatible with the
274 cryptoloop device.
275
276config BLK_DEV_NBD
277 tristate "Network block device support"
278 depends on NET
279 ---help---
280 Saying Y here will allow your computer to be a client for network
281 block devices, i.e. it will be able to use block devices exported by
282 servers (mount file systems on them etc.). Communication between
283 client and server works over TCP/IP networking, but to the client
284 program this is hidden: it looks like a regular local file access to
285 a block device special file such as /dev/nd0.
286
287 Network block devices also allows you to run a block-device in
288 userland (making server and client physically the same computer,
289 communicating using the loopback network device).
290
291 Read <file:Documentation/nbd.txt> for more information, especially
292 about where to find the server code, which runs in user space and
293 does not need special kernel support.
294
295 Note that this has nothing to do with the network file systems NFS
296 or Coda; you can say N here even if you intend to use NFS or Coda.
297
298 To compile this driver as a module, choose M here: the
299 module will be called nbd.
300
301 If unsure, say N.
302
303config BLK_DEV_SX8
304 tristate "Promise SATA SX8 support"
305 depends on PCI
306 ---help---
307 Saying Y or M here will enable support for the
308 Promise SATA SX8 controllers.
309
310 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
311
312config BLK_DEV_UB
313 tristate "Low Performance USB Block driver"
314 depends on USB
315 help
316 This driver supports certain USB attached storage devices
317 such as flash keys.
318
Pete Zaitceva00828e2005-10-22 20:15:09 -0700319 If you enable this driver, it is recommended to avoid conflicts
320 with usb-storage by enabling USB_LIBUSUAL.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700321
322 If unsure, say N.
323
324config BLK_DEV_RAM
325 tristate "RAM disk support"
326 ---help---
327 Saying Y here will allow you to use a portion of your RAM memory as
328 a block device, so that you can make file systems on it, read and
329 write to it and do all the other things that you can do with normal
330 block devices (such as hard drives). It is usually used to load and
331 store a copy of a minimal root file system off of a floppy into RAM
332 during the initial install of Linux.
333
334 Note that the kernel command line option "ramdisk=XX" is now
335 obsolete. For details, read <file:Documentation/ramdisk.txt>.
336
337 To compile this driver as a module, choose M here: the
338 module will be called rd.
339
340 Most normal users won't need the RAM disk functionality, and can
341 thus say N here.
342
343config BLK_DEV_RAM_COUNT
Adrian Bunka687fb12006-03-28 01:56:17 -0800344 int "Default number of RAM disks"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700345 default "16"
Adrian Bunka687fb12006-03-28 01:56:17 -0800346 depends on BLK_DEV_RAM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700347 help
Patrick Ringl2e977c82007-10-19 23:05:02 +0200348 The default value is 16 RAM disks. Change this if you know what you
Linus Torvalds1da177e2005-04-16 15:20:36 -0700349 are doing. If you boot from a filesystem that needs to be extracted
350 in memory, you will need at least one RAM disk (e.g. root on cramfs).
351
352config BLK_DEV_RAM_SIZE
353 int "Default RAM disk size (kbytes)"
354 depends on BLK_DEV_RAM
355 default "4096"
356 help
357 The default value is 4096 kilobytes. Only change this if you know
Patrick Ringl2e977c82007-10-19 23:05:02 +0200358 what you are doing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700359
Nathan Scottbef317e2006-07-14 00:24:10 -0700360config BLK_DEV_RAM_BLOCKSIZE
361 int "Default RAM disk block size (bytes)"
362 depends on BLK_DEV_RAM
363 default "1024"
364 help
Christian Borntraeger73cf9632006-10-03 23:40:34 +0200365 The default value is 1024 bytes. PAGE_SIZE is a much more
Nathan Scottbef317e2006-07-14 00:24:10 -0700366 efficient choice however. The default is kept to ensure initrd
367 setups function - apparently needed by the rd_load_image routine
368 that supposes the filesystem in the image uses a 1024 blocksize.
369
Linus Torvalds1da177e2005-04-16 15:20:36 -0700370config CDROM_PKTCDVD
371 tristate "Packet writing on CD/DVD media"
372 depends on !UML
373 help
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800374 If you have a CDROM/DVD drive that supports packet writing, say
375 Y to include support. It should work with any MMC/Mt Fuji
376 compliant ATAPI or SCSI drive, which is just about any newer
377 DVD/CD writer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700378
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800379 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
380 is possible.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700381 DVD-RW disks must be in restricted overwrite mode.
382
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800383 See the file <file:Documentation/cdrom/packet-writing.txt>
384 for further information on the use of this driver.
385
Linus Torvalds1da177e2005-04-16 15:20:36 -0700386 To compile this driver as a module, choose M here: the
387 module will be called pktcdvd.
388
389config CDROM_PKTCDVD_BUFFERS
390 int "Free buffers for data gathering"
391 depends on CDROM_PKTCDVD
392 default "8"
393 help
394 This controls the maximum number of active concurrent packets. More
395 concurrent packets can increase write performance, but also require
396 more memory. Each concurrent packet will require approximately 64Kb
Peter Osterlunde1bc89b2006-02-04 23:27:47 -0800397 of non-swappable kernel memory, memory which will be allocated when
398 a disc is opened for writing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700399
400config CDROM_PKTCDVD_WCACHE
Adrian Bunkb566cce2006-02-04 23:27:45 -0800401 bool "Enable write caching (EXPERIMENTAL)"
402 depends on CDROM_PKTCDVD && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700403 help
404 If enabled, write caching will be set for the CD-R/W device. For now
405 this option is dangerous unless the CD-RW media is known good, as we
406 don't do deferred write error handling yet.
407
Linus Torvalds1da177e2005-04-16 15:20:36 -0700408config ATA_OVER_ETH
409 tristate "ATA over Ethernet support"
410 depends on NET
411 help
412 This driver provides Support for ATA over Ethernet block
413 devices like the Coraid EtherDrive (R) Storage Blade.
414
David S. Miller667ef3c2007-07-16 04:03:56 -0700415config SUNVDC
416 tristate "Sun Virtual Disk Client support"
417 depends on SUN_LDOMS
418 help
419 Support for virtual disk devices as a client under Sun
420 Logical Domains.
421
Martin Schwidefsky61d48c22007-05-10 15:46:00 +0200422source "drivers/s390/block/Kconfig"
423
Grant Likely74489a92007-07-17 04:03:39 -0700424config XILINX_SYSACE
425 tristate "Xilinx SystemACE support"
426 depends on 4xx
427 help
428 Include support for the Xilinx SystemACE CompactFlash interface
429
Jeremy Fitzhardinge9f27ee52007-07-17 18:37:06 -0700430config XEN_BLKDEV_FRONTEND
431 tristate "Xen virtual block device support"
432 depends on XEN
433 default y
434 help
435 This driver implements the front-end of the Xen virtual
436 block device driver. It communicates with a back-end driver
437 in another domain which drives the actual block device.
438
Rusty Russelle467cde2007-10-22 11:03:38 +1000439config VIRTIO_BLK
440 tristate "Virtio block driver (EXPERIMENTAL)"
441 depends on EXPERIMENTAL && VIRTIO
442 ---help---
443 This is the virtual block driver for lguest. Say Y or M.
444
Jan Engelhardtfd11d172007-07-10 12:26:06 +0200445endif # BLK_DEV