blob: 61ad8d639ba39830ee96687d2ef18d3fcba8cad4 [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
Linus Torvalds1da177e2005-04-16 15:20:36 -070047config AMIGA_Z2RAM
48 tristate "Amiga Zorro II ramdisk support"
49 depends on ZORRO
50 help
51 This enables support for using Chip RAM and Zorro II RAM as a
52 ramdisk or as a swap partition. Say Y if you want to include this
53 driver in the kernel.
54
55 To compile this driver as a module, choose M here: the
56 module will be called z2ram.
57
Linus Torvalds1da177e2005-04-16 15:20:36 -070058config BLK_DEV_XD
59 tristate "XT hard disk support"
Al Viroa5532602005-05-04 05:39:42 +010060 depends on ISA && ISA_DMA_API
Geert Uytterhoeven928923c2007-08-22 14:01:36 -070061 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -070062 help
63 Very old 8 bit hard disk controllers used in the IBM XT computer
64 will be supported if you say Y here.
65
66 To compile this driver as a module, choose M here: the
67 module will be called xd.
68
69 It's pretty unlikely that you have one of these: say N.
70
71config PARIDE
72 tristate "Parallel port IDE device support"
Marko Kohtala6a19b412006-01-06 00:19:49 -080073 depends on PARPORT_PC
Linus Torvalds1da177e2005-04-16 15:20:36 -070074 ---help---
75 There are many external CD-ROM and disk devices that connect through
76 your computer's parallel port. Most of them are actually IDE devices
77 using a parallel port IDE adapter. This option enables the PARIDE
78 subsystem which contains drivers for many of these external drives.
79 Read <file:Documentation/paride.txt> for more information.
80
81 If you have said Y to the "Parallel-port support" configuration
82 option, you may share a single port between your printer and other
83 parallel port devices. Answer Y to build PARIDE support into your
84 kernel, or M if you would like to build it as a loadable module. If
85 your parallel port support is in a loadable module, you must build
86 PARIDE as a module. If you built PARIDE support into your kernel,
87 you may still build the individual protocol modules and high-level
88 drivers as loadable modules. If you build this support as a module,
89 it will be called paride.
90
91 To use the PARIDE support, you must say Y or M here and also to at
92 least one high-level driver (e.g. "Parallel port IDE disks",
93 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
94 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
95 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
96 etc.).
97
Adrian McMenamin74ee1a72008-01-21 18:52:48 +090098config GDROM
99 tristate "SEGA Dreamcast GD-ROM drive"
100 depends on SH_DREAMCAST
101 help
102 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
103 "GD-ROM" by SEGA to signify it is capable of reading special disks
104 with up to 1 GB of data. This drive will also read standard CD ROM
105 disks. Select this option to access any disks in your GD ROM drive.
106 Most users will want to say "Y" here.
107 You can also build this as a module which will be called gdrom.ko
108
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109source "drivers/block/paride/Kconfig"
110
111config BLK_CPQ_DA
112 tristate "Compaq SMART2 support"
Stephen Rothwellf057eac2007-07-15 23:40:05 -0700113 depends on PCI && VIRT_TO_BUS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700114 help
115 This is the driver for Compaq Smart Array controllers. Everyone
116 using these boards should say Y here. See the file
117 <file:Documentation/cpqarray.txt> for the current list of boards
118 supported by this driver, and for further information on the use of
119 this driver.
120
121config BLK_CPQ_CISS_DA
122 tristate "Compaq Smart Array 5xxx support"
123 depends on PCI
124 help
125 This is the driver for Compaq Smart Array 5xxx controllers.
126 Everyone using these boards should say Y here.
127 See <file:Documentation/cciss.txt> for the current list of
128 boards supported by this driver, and for further information
129 on the use of this driver.
130
131config CISS_SCSI_TAPE
132 bool "SCSI tape drive support for Smart Array 5xxx"
Randy Dunlap3e29fe82006-12-06 20:38:40 -0800133 depends on BLK_CPQ_CISS_DA && PROC_FS
134 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700135 help
136 When enabled (Y), this option allows SCSI tape drives and SCSI medium
137 changers (tape robots) to be accessed via a Compaq 5xxx array
138 controller. (See <file:Documentation/cciss.txt> for more details.)
139
140 "SCSI support" and "SCSI tape support" must also be enabled for this
141 option to work.
142
143 When this option is disabled (N), the SCSI portion of the driver
144 is not compiled.
145
146config BLK_DEV_DAC960
147 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
148 depends on PCI
149 help
150 This driver adds support for the Mylex DAC960, AcceleRAID, and
151 eXtremeRAID PCI RAID controllers. See the file
152 <file:Documentation/README.DAC960> for further information about
153 this driver.
154
155 To compile this driver as a module, choose M here: the
156 module will be called DAC960.
157
158config BLK_DEV_UMEM
159 tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
160 depends on PCI && EXPERIMENTAL
161 ---help---
162 Saying Y here will include support for the MM5415 family of
163 battery backed (Non-volatile) RAM cards.
164 <http://www.umem.com/>
165
166 The cards appear as block devices that can be partitioned into
167 as many as 15 partitions.
168
169 To compile this driver as a module, choose M here: the
170 module will be called umem.
171
172 The umem driver has not yet been allocated a MAJOR number, so
Adrian Bunkbf6ee0a2006-10-03 22:17:48 +0200173 one is chosen dynamically.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700174
175config BLK_DEV_UBD
176 bool "Virtual block device"
177 depends on UML
178 ---help---
179 The User-Mode Linux port includes a driver called UBD which will let
180 you access arbitrary files on the host computer as block devices.
181 Unless you know that you do not need such virtual block devices say
182 Y here.
183
184config BLK_DEV_UBD_SYNC
185 bool "Always do synchronous disk IO for UBD"
186 depends on BLK_DEV_UBD
187 ---help---
188 Writes to the virtual block device are not immediately written to the
189 host's disk; this may cause problems if, for example, the User-Mode
190 Linux 'Virtual Machine' uses a journalling filesystem and the host
191 computer crashes.
192
193 Synchronous operation (i.e. always writing data to the host's disk
194 immediately) is configurable on a per-UBD basis by using a special
195 kernel command line option. Alternatively, you can say Y here to
196 turn on synchronous operation by default for all block devices.
197
198 If you're running a journalling file system (like reiserfs, for
199 example) in your virtual machine, you will want to say Y here. If
200 you care for the safety of the data in your virtual machine, Y is a
201 wise choice too. In all other cases (for example, if you're just
202 playing around with User-Mode Linux) you can choose N.
203
204config BLK_DEV_COW_COMMON
205 bool
206 default BLK_DEV_UBD
207
Linus Torvalds1da177e2005-04-16 15:20:36 -0700208config BLK_DEV_LOOP
209 tristate "Loopback device support"
210 ---help---
211 Saying Y here will allow you to use a regular file as a block
212 device; you can then create a file system on that block device and
213 mount it just as you would mount other block devices such as hard
214 drive partitions, CD-ROM drives or floppy drives. The loop devices
215 are block special device files with major number 7 and typically
216 called /dev/loop0, /dev/loop1 etc.
217
218 This is useful if you want to check an ISO 9660 file system before
219 burning the CD, or if you want to use floppy images without first
220 writing them to floppy. Furthermore, some Linux distributions avoid
221 the need for a dedicated Linux partition by keeping their complete
222 root file system inside a DOS FAT file using this loop device
223 driver.
224
225 To use the loop device, you need the losetup utility, found in the
226 util-linux package, see
227 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
228
229 The loop device driver can also be used to "hide" a file system in
230 a disk partition, floppy, or regular file, either using encryption
231 (scrambling the data) or steganography (hiding the data in the low
232 bits of, say, a sound file). This is also safe if the file resides
233 on a remote file server.
234
235 There are several ways of encrypting disks. Some of these require
236 kernel patches. The vanilla kernel offers the cryptoloop option
237 and a Device Mapper target (which is superior, as it supports all
238 file systems). If you want to use the cryptoloop, say Y to both
239 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
240 or later) version of util-linux. Additionally, be aware that
241 the cryptoloop is not safe for storing journaled filesystems.
242
243 Note that this loop device has nothing to do with the loopback
244 device used for network connections from the machine to itself.
245
246 To compile this driver as a module, choose M here: the
247 module will be called loop.
248
249 Most users will answer N here.
250
251config BLK_DEV_CRYPTOLOOP
252 tristate "Cryptoloop Support"
253 select CRYPTO
Herbert Xu8df3b0a2006-12-02 14:36:03 +1100254 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700255 depends on BLK_DEV_LOOP
256 ---help---
257 Say Y here if you want to be able to use the ciphers that are
258 provided by the CryptoAPI as loop transformation. This might be
259 used as hard disk encryption.
260
261 WARNING: This device is not safe for journaled file systems like
262 ext3 or Reiserfs. Please use the Device Mapper crypto module
263 instead, which can be configured to be on-disk compatible with the
264 cryptoloop device.
265
266config BLK_DEV_NBD
267 tristate "Network block device support"
268 depends on NET
269 ---help---
270 Saying Y here will allow your computer to be a client for network
271 block devices, i.e. it will be able to use block devices exported by
272 servers (mount file systems on them etc.). Communication between
273 client and server works over TCP/IP networking, but to the client
274 program this is hidden: it looks like a regular local file access to
275 a block device special file such as /dev/nd0.
276
277 Network block devices also allows you to run a block-device in
278 userland (making server and client physically the same computer,
279 communicating using the loopback network device).
280
281 Read <file:Documentation/nbd.txt> for more information, especially
282 about where to find the server code, which runs in user space and
283 does not need special kernel support.
284
285 Note that this has nothing to do with the network file systems NFS
286 or Coda; you can say N here even if you intend to use NFS or Coda.
287
288 To compile this driver as a module, choose M here: the
289 module will be called nbd.
290
291 If unsure, say N.
292
293config BLK_DEV_SX8
294 tristate "Promise SATA SX8 support"
295 depends on PCI
296 ---help---
297 Saying Y or M here will enable support for the
298 Promise SATA SX8 controllers.
299
300 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
301
302config BLK_DEV_UB
303 tristate "Low Performance USB Block driver"
304 depends on USB
305 help
306 This driver supports certain USB attached storage devices
307 such as flash keys.
308
Pete Zaitceva00828e2005-10-22 20:15:09 -0700309 If you enable this driver, it is recommended to avoid conflicts
310 with usb-storage by enabling USB_LIBUSUAL.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700311
312 If unsure, say N.
313
314config BLK_DEV_RAM
Nick Piggin9db55792008-02-08 04:19:49 -0800315 tristate "RAM block device support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700316 ---help---
317 Saying Y here will allow you to use a portion of your RAM memory as
318 a block device, so that you can make file systems on it, read and
319 write to it and do all the other things that you can do with normal
320 block devices (such as hard drives). It is usually used to load and
321 store a copy of a minimal root file system off of a floppy into RAM
322 during the initial install of Linux.
323
324 Note that the kernel command line option "ramdisk=XX" is now
325 obsolete. For details, read <file:Documentation/ramdisk.txt>.
326
327 To compile this driver as a module, choose M here: the
328 module will be called rd.
329
330 Most normal users won't need the RAM disk functionality, and can
331 thus say N here.
332
333config BLK_DEV_RAM_COUNT
Adrian Bunka687fb12006-03-28 01:56:17 -0800334 int "Default number of RAM disks"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700335 default "16"
Adrian Bunka687fb12006-03-28 01:56:17 -0800336 depends on BLK_DEV_RAM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700337 help
Patrick Ringl2e977c82007-10-19 23:05:02 +0200338 The default value is 16 RAM disks. Change this if you know what you
Linus Torvalds1da177e2005-04-16 15:20:36 -0700339 are doing. If you boot from a filesystem that needs to be extracted
340 in memory, you will need at least one RAM disk (e.g. root on cramfs).
341
342config BLK_DEV_RAM_SIZE
343 int "Default RAM disk size (kbytes)"
344 depends on BLK_DEV_RAM
345 default "4096"
346 help
347 The default value is 4096 kilobytes. Only change this if you know
Patrick Ringl2e977c82007-10-19 23:05:02 +0200348 what you are doing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700349
Nick Piggin75acb9c2008-02-08 04:19:50 -0800350config BLK_DEV_XIP
351 bool "Support XIP filesystems on RAM block device"
352 depends on BLK_DEV_RAM
353 default n
354 help
355 Support XIP filesystems (such as ext2 with XIP support on) on
356 top of block ram device. This will slightly enlarge the kernel, and
357 will prevent RAM block device backing store memory from being
358 allocated from highmem (only a problem for highmem systems).
359
Linus Torvalds1da177e2005-04-16 15:20:36 -0700360config CDROM_PKTCDVD
361 tristate "Packet writing on CD/DVD media"
362 depends on !UML
363 help
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800364 If you have a CDROM/DVD drive that supports packet writing, say
365 Y to include support. It should work with any MMC/Mt Fuji
366 compliant ATAPI or SCSI drive, which is just about any newer
367 DVD/CD writer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700368
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800369 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
370 is possible.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700371 DVD-RW disks must be in restricted overwrite mode.
372
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800373 See the file <file:Documentation/cdrom/packet-writing.txt>
374 for further information on the use of this driver.
375
Linus Torvalds1da177e2005-04-16 15:20:36 -0700376 To compile this driver as a module, choose M here: the
377 module will be called pktcdvd.
378
379config CDROM_PKTCDVD_BUFFERS
380 int "Free buffers for data gathering"
381 depends on CDROM_PKTCDVD
382 default "8"
383 help
384 This controls the maximum number of active concurrent packets. More
385 concurrent packets can increase write performance, but also require
386 more memory. Each concurrent packet will require approximately 64Kb
Peter Osterlunde1bc89b2006-02-04 23:27:47 -0800387 of non-swappable kernel memory, memory which will be allocated when
388 a disc is opened for writing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700389
390config CDROM_PKTCDVD_WCACHE
Adrian Bunkb566cce2006-02-04 23:27:45 -0800391 bool "Enable write caching (EXPERIMENTAL)"
392 depends on CDROM_PKTCDVD && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700393 help
394 If enabled, write caching will be set for the CD-R/W device. For now
395 this option is dangerous unless the CD-RW media is known good, as we
396 don't do deferred write error handling yet.
397
Linus Torvalds1da177e2005-04-16 15:20:36 -0700398config ATA_OVER_ETH
399 tristate "ATA over Ethernet support"
400 depends on NET
401 help
402 This driver provides Support for ATA over Ethernet block
403 devices like the Coraid EtherDrive (R) Storage Blade.
404
David S. Miller667ef3c2007-07-16 04:03:56 -0700405config SUNVDC
406 tristate "Sun Virtual Disk Client support"
407 depends on SUN_LDOMS
408 help
409 Support for virtual disk devices as a client under Sun
410 Logical Domains.
411
Martin Schwidefsky61d48c22007-05-10 15:46:00 +0200412source "drivers/s390/block/Kconfig"
413
Grant Likely74489a92007-07-17 04:03:39 -0700414config XILINX_SYSACE
415 tristate "Xilinx SystemACE support"
416 depends on 4xx
417 help
418 Include support for the Xilinx SystemACE CompactFlash interface
419
Jeremy Fitzhardinge9f27ee52007-07-17 18:37:06 -0700420config XEN_BLKDEV_FRONTEND
421 tristate "Xen virtual block device support"
422 depends on XEN
423 default y
424 help
425 This driver implements the front-end of the Xen virtual
426 block device driver. It communicates with a back-end driver
427 in another domain which drives the actual block device.
428
Rusty Russelle467cde2007-10-22 11:03:38 +1000429config VIRTIO_BLK
430 tristate "Virtio block driver (EXPERIMENTAL)"
431 depends on EXPERIMENTAL && VIRTIO
432 ---help---
Anthony Liguori0ad07ec2007-11-07 20:46:31 -0600433 This is the virtual block driver for virtio. It can be used with
434 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
Rusty Russelle467cde2007-10-22 11:03:38 +1000435
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200436config BLK_DEV_HD
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200437 bool "Very old hard disk (MFM/RLL/IDE) driver"
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200438 depends on HAVE_IDE
439 depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
440 help
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200441 This is a very old hard disk driver that lacks the enhanced
442 functionality of the newer ones.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200443
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200444 It is required for systems with ancient MFM/RLL/ESDI drives.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200445
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200446 If unsure, say N.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200447
Jan Engelhardtfd11d172007-07-10 12:26:06 +0200448endif # BLK_DEV