blob: d6ad7b3ea0dc34dbdf820a0dc3df6875aae64a5f [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Block device driver configuration
3#
4
David Howells93614012006-09-30 20:45:40 +02005if BLOCK
6
Linus Torvalds1da177e2005-04-16 15:20:36 -07007menu "Block devices"
8
9config BLK_DEV_FD
10 tristate "Normal floppy disk support"
viro@ZenIV.linux.org.uka08b6b72005-09-06 01:48:42 +010011 depends on ARCH_MAY_HAVE_PC_FDC
Linus Torvalds1da177e2005-04-16 15:20:36 -070012 ---help---
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.
19
20 To compile this driver as a module, choose M here: the
21 module will be called floppy.
22
23config AMIGA_FLOPPY
24 tristate "Amiga floppy support"
25 depends on AMIGA
26
27config ATARI_FLOPPY
28 tristate "Atari floppy support"
29 depends on ATARI
30
Linus Torvalds1da177e2005-04-16 15:20:36 -070031config MAC_FLOPPY
32 tristate "Support for PowerMac floppy"
33 depends on PPC_PMAC && !PPC_PMAC64
34 help
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.
37
38config BLK_DEV_PS2
39 tristate "PS/2 ESDI hard disk support"
40 depends on MCA && MCA_LEGACY && BROKEN
41 help
42 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
43 hard disk.
44
45 To compile this driver as a module, choose M here: the
46 module will be called ps2esdi.
47
48config AMIGA_Z2RAM
49 tristate "Amiga Zorro II ramdisk support"
50 depends on ZORRO
51 help
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
54 driver in the kernel.
55
56 To compile this driver as a module, choose M here: the
57 module will be called z2ram.
58
Linus Torvalds1da177e2005-04-16 15:20:36 -070059config ATARI_SLM
60 tristate "Atari SLM laser printer support"
Jens Axboec2bcf3b2007-06-19 19:13:36 +020061 depends on ATARI
Linus Torvalds1da177e2005-04-16 15:20:36 -070062 help
63 If you have an Atari SLM laser printer, say Y to include support for
64 it in the kernel. Otherwise, say N. This driver is also available as
65 a module ( = code which can be inserted in and removed from the
66 running kernel whenever you want). The module will be called
67 acsi_slm. Be warned: the driver needs much ST-RAM and can cause
68 problems due to that fact!
69
70config BLK_DEV_XD
71 tristate "XT hard disk support"
Al Viroa5532602005-05-04 05:39:42 +010072 depends on ISA && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -070073 help
74 Very old 8 bit hard disk controllers used in the IBM XT computer
75 will be supported if you say Y here.
76
77 To compile this driver as a module, choose M here: the
78 module will be called xd.
79
80 It's pretty unlikely that you have one of these: say N.
81
82config PARIDE
83 tristate "Parallel port IDE device support"
Marko Kohtala6a19b412006-01-06 00:19:49 -080084 depends on PARPORT_PC
Linus Torvalds1da177e2005-04-16 15:20:36 -070085 ---help---
86 There are many external CD-ROM and disk devices that connect through
87 your computer's parallel port. Most of them are actually IDE devices
88 using a parallel port IDE adapter. This option enables the PARIDE
89 subsystem which contains drivers for many of these external drives.
90 Read <file:Documentation/paride.txt> for more information.
91
92 If you have said Y to the "Parallel-port support" configuration
93 option, you may share a single port between your printer and other
94 parallel port devices. Answer Y to build PARIDE support into your
95 kernel, or M if you would like to build it as a loadable module. If
96 your parallel port support is in a loadable module, you must build
97 PARIDE as a module. If you built PARIDE support into your kernel,
98 you may still build the individual protocol modules and high-level
99 drivers as loadable modules. If you build this support as a module,
100 it will be called paride.
101
102 To use the PARIDE support, you must say Y or M here and also to at
103 least one high-level driver (e.g. "Parallel port IDE disks",
104 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
105 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
106 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
107 etc.).
108
109source "drivers/block/paride/Kconfig"
110
111config BLK_CPQ_DA
112 tristate "Compaq SMART2 support"
113 depends on PCI
114 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
208config MMAPPER
209 tristate "Example IO memory driver (BROKEN)"
210 depends on UML && BROKEN
211 ---help---
212 The User-Mode Linux port can provide support for IO Memory
213 emulation with this option. This allows a host file to be
214 specified as an I/O region on the kernel command line. That file
215 will be mapped into UML's kernel address space where a driver can
216 locate it and do whatever it wants with the memory, including
217 providing an interface to it for UML processes to use.
218
219 For more information, see
220 <http://user-mode-linux.sourceforge.net/iomem.html>.
221
222 If you'd like to be able to provide a simulated IO port space for
223 User-Mode Linux processes, say Y. If unsure, say N.
224
225config BLK_DEV_LOOP
226 tristate "Loopback device support"
227 ---help---
228 Saying Y here will allow you to use a regular file as a block
229 device; you can then create a file system on that block device and
230 mount it just as you would mount other block devices such as hard
231 drive partitions, CD-ROM drives or floppy drives. The loop devices
232 are block special device files with major number 7 and typically
233 called /dev/loop0, /dev/loop1 etc.
234
235 This is useful if you want to check an ISO 9660 file system before
236 burning the CD, or if you want to use floppy images without first
237 writing them to floppy. Furthermore, some Linux distributions avoid
238 the need for a dedicated Linux partition by keeping their complete
239 root file system inside a DOS FAT file using this loop device
240 driver.
241
242 To use the loop device, you need the losetup utility, found in the
243 util-linux package, see
244 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
245
246 The loop device driver can also be used to "hide" a file system in
247 a disk partition, floppy, or regular file, either using encryption
248 (scrambling the data) or steganography (hiding the data in the low
249 bits of, say, a sound file). This is also safe if the file resides
250 on a remote file server.
251
252 There are several ways of encrypting disks. Some of these require
253 kernel patches. The vanilla kernel offers the cryptoloop option
254 and a Device Mapper target (which is superior, as it supports all
255 file systems). If you want to use the cryptoloop, say Y to both
256 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
257 or later) version of util-linux. Additionally, be aware that
258 the cryptoloop is not safe for storing journaled filesystems.
259
260 Note that this loop device has nothing to do with the loopback
261 device used for network connections from the machine to itself.
262
263 To compile this driver as a module, choose M here: the
264 module will be called loop.
265
266 Most users will answer N here.
267
268config BLK_DEV_CRYPTOLOOP
269 tristate "Cryptoloop Support"
270 select CRYPTO
Herbert Xu8df3b0a2006-12-02 14:36:03 +1100271 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700272 depends on BLK_DEV_LOOP
273 ---help---
274 Say Y here if you want to be able to use the ciphers that are
275 provided by the CryptoAPI as loop transformation. This might be
276 used as hard disk encryption.
277
278 WARNING: This device is not safe for journaled file systems like
279 ext3 or Reiserfs. Please use the Device Mapper crypto module
280 instead, which can be configured to be on-disk compatible with the
281 cryptoloop device.
282
283config BLK_DEV_NBD
284 tristate "Network block device support"
285 depends on NET
286 ---help---
287 Saying Y here will allow your computer to be a client for network
288 block devices, i.e. it will be able to use block devices exported by
289 servers (mount file systems on them etc.). Communication between
290 client and server works over TCP/IP networking, but to the client
291 program this is hidden: it looks like a regular local file access to
292 a block device special file such as /dev/nd0.
293
294 Network block devices also allows you to run a block-device in
295 userland (making server and client physically the same computer,
296 communicating using the loopback network device).
297
298 Read <file:Documentation/nbd.txt> for more information, especially
299 about where to find the server code, which runs in user space and
300 does not need special kernel support.
301
302 Note that this has nothing to do with the network file systems NFS
303 or Coda; you can say N here even if you intend to use NFS or Coda.
304
305 To compile this driver as a module, choose M here: the
306 module will be called nbd.
307
308 If unsure, say N.
309
310config BLK_DEV_SX8
311 tristate "Promise SATA SX8 support"
312 depends on PCI
313 ---help---
314 Saying Y or M here will enable support for the
315 Promise SATA SX8 controllers.
316
317 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
318
319config BLK_DEV_UB
320 tristate "Low Performance USB Block driver"
321 depends on USB
322 help
323 This driver supports certain USB attached storage devices
324 such as flash keys.
325
Pete Zaitceva00828e2005-10-22 20:15:09 -0700326 If you enable this driver, it is recommended to avoid conflicts
327 with usb-storage by enabling USB_LIBUSUAL.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700328
329 If unsure, say N.
330
331config BLK_DEV_RAM
332 tristate "RAM disk support"
333 ---help---
334 Saying Y here will allow you to use a portion of your RAM memory as
335 a block device, so that you can make file systems on it, read and
336 write to it and do all the other things that you can do with normal
337 block devices (such as hard drives). It is usually used to load and
338 store a copy of a minimal root file system off of a floppy into RAM
339 during the initial install of Linux.
340
341 Note that the kernel command line option "ramdisk=XX" is now
342 obsolete. For details, read <file:Documentation/ramdisk.txt>.
343
344 To compile this driver as a module, choose M here: the
345 module will be called rd.
346
347 Most normal users won't need the RAM disk functionality, and can
348 thus say N here.
349
350config BLK_DEV_RAM_COUNT
Adrian Bunka687fb12006-03-28 01:56:17 -0800351 int "Default number of RAM disks"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700352 default "16"
Adrian Bunka687fb12006-03-28 01:56:17 -0800353 depends on BLK_DEV_RAM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700354 help
355 The default value is 16 RAM disks. Change this if you know what
356 are doing. If you boot from a filesystem that needs to be extracted
357 in memory, you will need at least one RAM disk (e.g. root on cramfs).
358
359config BLK_DEV_RAM_SIZE
360 int "Default RAM disk size (kbytes)"
361 depends on BLK_DEV_RAM
362 default "4096"
363 help
364 The default value is 4096 kilobytes. Only change this if you know
365 what are you doing. If you are using IBM S/390, then set this to
366 8192.
367
Nathan Scottbef317e2006-07-14 00:24:10 -0700368config BLK_DEV_RAM_BLOCKSIZE
369 int "Default RAM disk block size (bytes)"
370 depends on BLK_DEV_RAM
371 default "1024"
372 help
Christian Borntraeger73cf9632006-10-03 23:40:34 +0200373 The default value is 1024 bytes. PAGE_SIZE is a much more
Nathan Scottbef317e2006-07-14 00:24:10 -0700374 efficient choice however. The default is kept to ensure initrd
375 setups function - apparently needed by the rd_load_image routine
376 that supposes the filesystem in the image uses a 1024 blocksize.
377
Linus Torvalds1da177e2005-04-16 15:20:36 -0700378config CDROM_PKTCDVD
379 tristate "Packet writing on CD/DVD media"
380 depends on !UML
381 help
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800382 If you have a CDROM/DVD drive that supports packet writing, say
383 Y to include support. It should work with any MMC/Mt Fuji
384 compliant ATAPI or SCSI drive, which is just about any newer
385 DVD/CD writer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700386
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800387 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
388 is possible.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700389 DVD-RW disks must be in restricted overwrite mode.
390
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800391 See the file <file:Documentation/cdrom/packet-writing.txt>
392 for further information on the use of this driver.
393
Linus Torvalds1da177e2005-04-16 15:20:36 -0700394 To compile this driver as a module, choose M here: the
395 module will be called pktcdvd.
396
397config CDROM_PKTCDVD_BUFFERS
398 int "Free buffers for data gathering"
399 depends on CDROM_PKTCDVD
400 default "8"
401 help
402 This controls the maximum number of active concurrent packets. More
403 concurrent packets can increase write performance, but also require
404 more memory. Each concurrent packet will require approximately 64Kb
Peter Osterlunde1bc89b2006-02-04 23:27:47 -0800405 of non-swappable kernel memory, memory which will be allocated when
406 a disc is opened for writing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700407
408config CDROM_PKTCDVD_WCACHE
Adrian Bunkb566cce2006-02-04 23:27:45 -0800409 bool "Enable write caching (EXPERIMENTAL)"
410 depends on CDROM_PKTCDVD && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700411 help
412 If enabled, write caching will be set for the CD-R/W device. For now
413 this option is dangerous unless the CD-RW media is known good, as we
414 don't do deferred write error handling yet.
415
Linus Torvalds1da177e2005-04-16 15:20:36 -0700416config ATA_OVER_ETH
417 tristate "ATA over Ethernet support"
418 depends on NET
419 help
420 This driver provides Support for ATA over Ethernet block
421 devices like the Coraid EtherDrive (R) Storage Blade.
422
Martin Schwidefsky61d48c22007-05-10 15:46:00 +0200423source "drivers/s390/block/Kconfig"
424
Linus Torvalds1da177e2005-04-16 15:20:36 -0700425endmenu
David Howells93614012006-09-30 20:45:40 +0200426
427endif