blob: 4e4c8a4a5fd3fb4412a19fdbd3f62647b285fd6a [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
Randy Dunlap31c00fc2008-11-13 21:33:24 +000024 Thinkpad users, is contained in
25 <file:Documentation/blockdev/floppy.txt>.
Linus Torvalds1da177e2005-04-16 15:20:36 -070026 That file also contains the location of the Floppy driver FAQ as
27 well as location of the fdutils package used to configure additional
28 parameters of the driver at run time.
29
30 To compile this driver as a module, choose M here: the
31 module will be called floppy.
32
33config AMIGA_FLOPPY
34 tristate "Amiga floppy support"
35 depends on AMIGA
36
37config ATARI_FLOPPY
38 tristate "Atari floppy support"
39 depends on ATARI
40
Linus Torvalds1da177e2005-04-16 15:20:36 -070041config MAC_FLOPPY
42 tristate "Support for PowerMac floppy"
43 depends on PPC_PMAC && !PPC_PMAC64
44 help
45 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
46 floppy controller, say Y here. Most commonly found in PowerMacs.
47
Laurent Vivier8852ecd2008-11-15 16:10:10 +010048config BLK_DEV_SWIM
49 tristate "Support for SWIM Macintosh floppy"
50 depends on M68K && MAC
51 help
52 You should select this option if you want floppy support
53 and you don't have a II, IIfx, Q900, Q950 or AV series.
54
Linus Torvalds1da177e2005-04-16 15:20:36 -070055config AMIGA_Z2RAM
56 tristate "Amiga Zorro II ramdisk support"
57 depends on ZORRO
58 help
59 This enables support for using Chip RAM and Zorro II RAM as a
60 ramdisk or as a swap partition. Say Y if you want to include this
61 driver in the kernel.
62
63 To compile this driver as a module, choose M here: the
64 module will be called z2ram.
65
Linus Torvalds1da177e2005-04-16 15:20:36 -070066config BLK_DEV_XD
67 tristate "XT hard disk support"
Al Viroa5532602005-05-04 05:39:42 +010068 depends on ISA && ISA_DMA_API
Geert Uytterhoeven928923c2007-08-22 14:01:36 -070069 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -070070 help
71 Very old 8 bit hard disk controllers used in the IBM XT computer
72 will be supported if you say Y here.
73
74 To compile this driver as a module, choose M here: the
75 module will be called xd.
76
77 It's pretty unlikely that you have one of these: say N.
78
Randy Dunlap2395e462010-05-11 09:02:55 +020079config GDROM
80 tristate "SEGA Dreamcast GD-ROM drive"
81 depends on SH_DREAMCAST
82 help
83 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
84 "GD-ROM" by SEGA to signify it is capable of reading special disks
85 with up to 1 GB of data. This drive will also read standard CD ROM
86 disks. Select this option to access any disks in your GD ROM drive.
87 Most users will want to say "Y" here.
88 You can also build this as a module which will be called gdrom.
89
Linus Torvalds1da177e2005-04-16 15:20:36 -070090config PARIDE
91 tristate "Parallel port IDE device support"
Marko Kohtala6a19b412006-01-06 00:19:49 -080092 depends on PARPORT_PC
Linus Torvalds1da177e2005-04-16 15:20:36 -070093 ---help---
94 There are many external CD-ROM and disk devices that connect through
95 your computer's parallel port. Most of them are actually IDE devices
96 using a parallel port IDE adapter. This option enables the PARIDE
97 subsystem which contains drivers for many of these external drives.
Randy Dunlap31c00fc2008-11-13 21:33:24 +000098 Read <file:Documentation/blockdev/paride.txt> for more information.
Linus Torvalds1da177e2005-04-16 15:20:36 -070099
100 If you have said Y to the "Parallel-port support" configuration
101 option, you may share a single port between your printer and other
102 parallel port devices. Answer Y to build PARIDE support into your
103 kernel, or M if you would like to build it as a loadable module. If
104 your parallel port support is in a loadable module, you must build
105 PARIDE as a module. If you built PARIDE support into your kernel,
106 you may still build the individual protocol modules and high-level
107 drivers as loadable modules. If you build this support as a module,
108 it will be called paride.
109
110 To use the PARIDE support, you must say Y or M here and also to at
111 least one high-level driver (e.g. "Parallel port IDE disks",
112 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
113 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
114 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
115 etc.).
116
117source "drivers/block/paride/Kconfig"
118
Sam Bradshaw88523a62011-08-30 08:34:26 -0600119source "drivers/block/mtip32xx/Kconfig"
120
Linus Torvalds1da177e2005-04-16 15:20:36 -0700121config 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
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000127 <file:Documentation/blockdev/cpqarray.txt> for the current list of
128 boards supported by this driver, and for further information on the
129 use of this driver.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700130
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.
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000137 See <file:Documentation/blockdev/cciss.txt> for the current list of
Linus Torvalds1da177e2005-04-16 15:20:36 -0700138 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
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000148 controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700149
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
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000162 <file:Documentation/blockdev/README.DAC960> for further information
163 about this driver.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700164
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
Kay Sieversd134b002011-07-31 22:08:04 +0200261config BLK_DEV_LOOP_MIN_COUNT
262 int "Number of loop devices to pre-create at init time"
263 depends on BLK_DEV_LOOP
264 default 8
265 help
266 Static number of loop devices to be unconditionally pre-created
267 at init time.
268
269 This default value can be overwritten on the kernel command
270 line or with module-parameter loop.max_loop.
271
272 The historic default is 8. If a late 2011 version of losetup(8)
273 is used, it can be set to 0, since needed loop devices can be
274 dynamically allocated with the /dev/loop-control interface.
275
Linus Torvalds1da177e2005-04-16 15:20:36 -0700276config BLK_DEV_CRYPTOLOOP
277 tristate "Cryptoloop Support"
278 select CRYPTO
Herbert Xu8df3b0a2006-12-02 14:36:03 +1100279 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700280 depends on BLK_DEV_LOOP
281 ---help---
282 Say Y here if you want to be able to use the ciphers that are
283 provided by the CryptoAPI as loop transformation. This might be
284 used as hard disk encryption.
285
286 WARNING: This device is not safe for journaled file systems like
287 ext3 or Reiserfs. Please use the Device Mapper crypto module
288 instead, which can be configured to be on-disk compatible with the
289 cryptoloop device.
290
Philipp Reisnerb411b362009-09-25 16:07:19 -0700291source "drivers/block/drbd/Kconfig"
292
Linus Torvalds1da177e2005-04-16 15:20:36 -0700293config BLK_DEV_NBD
294 tristate "Network block device support"
295 depends on NET
296 ---help---
297 Saying Y here will allow your computer to be a client for network
298 block devices, i.e. it will be able to use block devices exported by
299 servers (mount file systems on them etc.). Communication between
300 client and server works over TCP/IP networking, but to the client
301 program this is hidden: it looks like a regular local file access to
302 a block device special file such as /dev/nd0.
303
304 Network block devices also allows you to run a block-device in
305 userland (making server and client physically the same computer,
306 communicating using the loopback network device).
307
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000308 Read <file:Documentation/blockdev/nbd.txt> for more information,
309 especially about where to find the server code, which runs in user
310 space and does not need special kernel support.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700311
312 Note that this has nothing to do with the network file systems NFS
313 or Coda; you can say N here even if you intend to use NFS or Coda.
314
315 To compile this driver as a module, choose M here: the
316 module will be called nbd.
317
318 If unsure, say N.
319
Matthew Wilcoxb60503b2011-01-20 12:50:14 -0500320config BLK_DEV_NVME
321 tristate "NVM Express block device"
322 depends on PCI
323 ---help---
324 The NVM Express driver is for solid state drives directly
325 connected to the PCI or PCI Express bus. If you know you
326 don't have one of these, it is safe to answer N.
327
328 To compile this driver as a module, choose M here: the
329 module will be called nvme.
330
Jeff Garzik2a138772009-04-10 07:50:45 -0400331config BLK_DEV_OSD
332 tristate "OSD object-as-blkdev support"
333 depends on SCSI_OSD_ULD
334 ---help---
335 Saying Y or M here will allow the exporting of a single SCSI
336 OSD (object-based storage) object as a Linux block device.
337
338 For example, if you create a 2G object on an OSD device,
339 you can then use this module to present that 2G object as
340 a Linux block device.
341
342 To compile this driver as a module, choose M here: the
343 module will be called osdblk.
344
345 If unsure, say N.
346
Linus Torvalds1da177e2005-04-16 15:20:36 -0700347config BLK_DEV_SX8
348 tristate "Promise SATA SX8 support"
349 depends on PCI
350 ---help---
351 Saying Y or M here will enable support for the
352 Promise SATA SX8 controllers.
353
354 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
355
356config BLK_DEV_UB
357 tristate "Low Performance USB Block driver"
358 depends on USB
359 help
360 This driver supports certain USB attached storage devices
361 such as flash keys.
362
Pete Zaitceva00828e2005-10-22 20:15:09 -0700363 If you enable this driver, it is recommended to avoid conflicts
364 with usb-storage by enabling USB_LIBUSUAL.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700365
366 If unsure, say N.
367
368config BLK_DEV_RAM
Nick Piggin9db55792008-02-08 04:19:49 -0800369 tristate "RAM block device support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700370 ---help---
371 Saying Y here will allow you to use a portion of your RAM memory as
372 a block device, so that you can make file systems on it, read and
373 write to it and do all the other things that you can do with normal
374 block devices (such as hard drives). It is usually used to load and
375 store a copy of a minimal root file system off of a floppy into RAM
376 during the initial install of Linux.
377
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000378 Note that the kernel command line option "ramdisk=XX" is now obsolete.
379 For details, read <file:Documentation/blockdev/ramdisk.txt>.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700380
381 To compile this driver as a module, choose M here: the
382 module will be called rd.
383
384 Most normal users won't need the RAM disk functionality, and can
385 thus say N here.
386
387config BLK_DEV_RAM_COUNT
Adrian Bunka687fb12006-03-28 01:56:17 -0800388 int "Default number of RAM disks"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700389 default "16"
Adrian Bunka687fb12006-03-28 01:56:17 -0800390 depends on BLK_DEV_RAM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700391 help
Patrick Ringl2e977c82007-10-19 23:05:02 +0200392 The default value is 16 RAM disks. Change this if you know what you
Linus Torvalds1da177e2005-04-16 15:20:36 -0700393 are doing. If you boot from a filesystem that needs to be extracted
394 in memory, you will need at least one RAM disk (e.g. root on cramfs).
395
396config BLK_DEV_RAM_SIZE
397 int "Default RAM disk size (kbytes)"
398 depends on BLK_DEV_RAM
399 default "4096"
400 help
401 The default value is 4096 kilobytes. Only change this if you know
Patrick Ringl2e977c82007-10-19 23:05:02 +0200402 what you are doing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700403
Nick Piggin75acb9c2008-02-08 04:19:50 -0800404config BLK_DEV_XIP
405 bool "Support XIP filesystems on RAM block device"
406 depends on BLK_DEV_RAM
407 default n
408 help
409 Support XIP filesystems (such as ext2 with XIP support on) on
410 top of block ram device. This will slightly enlarge the kernel, and
411 will prevent RAM block device backing store memory from being
412 allocated from highmem (only a problem for highmem systems).
413
Linus Torvalds1da177e2005-04-16 15:20:36 -0700414config CDROM_PKTCDVD
415 tristate "Packet writing on CD/DVD media"
416 depends on !UML
417 help
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800418 If you have a CDROM/DVD drive that supports packet writing, say
419 Y to include support. It should work with any MMC/Mt Fuji
420 compliant ATAPI or SCSI drive, which is just about any newer
421 DVD/CD writer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700422
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800423 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
424 is possible.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700425 DVD-RW disks must be in restricted overwrite mode.
426
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800427 See the file <file:Documentation/cdrom/packet-writing.txt>
428 for further information on the use of this driver.
429
Linus Torvalds1da177e2005-04-16 15:20:36 -0700430 To compile this driver as a module, choose M here: the
431 module will be called pktcdvd.
432
433config CDROM_PKTCDVD_BUFFERS
434 int "Free buffers for data gathering"
435 depends on CDROM_PKTCDVD
436 default "8"
437 help
438 This controls the maximum number of active concurrent packets. More
439 concurrent packets can increase write performance, but also require
440 more memory. Each concurrent packet will require approximately 64Kb
Peter Osterlunde1bc89b2006-02-04 23:27:47 -0800441 of non-swappable kernel memory, memory which will be allocated when
442 a disc is opened for writing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700443
444config CDROM_PKTCDVD_WCACHE
Adrian Bunkb566cce2006-02-04 23:27:45 -0800445 bool "Enable write caching (EXPERIMENTAL)"
446 depends on CDROM_PKTCDVD && EXPERIMENTAL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700447 help
448 If enabled, write caching will be set for the CD-R/W device. For now
449 this option is dangerous unless the CD-RW media is known good, as we
450 don't do deferred write error handling yet.
451
Linus Torvalds1da177e2005-04-16 15:20:36 -0700452config ATA_OVER_ETH
453 tristate "ATA over Ethernet support"
454 depends on NET
455 help
456 This driver provides Support for ATA over Ethernet block
457 devices like the Coraid EtherDrive (R) Storage Blade.
458
unsik Kim3fbed4c2009-04-02 12:50:58 -0700459config MG_DISK
460 tristate "mGine mflash, gflash support"
Bartlomiej Zolnierkiewicz8a11a782009-04-28 13:06:16 +0900461 depends on ARM && GPIOLIB
unsik Kim3fbed4c2009-04-02 12:50:58 -0700462 help
463 mGine mFlash(gFlash) block device driver
464
465config MG_DISK_RES
466 int "Size of reserved area before MBR"
467 depends on MG_DISK
468 default 0
469 help
470 Define size of reserved area that usually used for boot. Unit is KB.
471 All of the block device operation will be taken this value as start
472 offset
473 Examples:
474 1024 => 1 MB
475
David S. Miller667ef3c2007-07-16 04:03:56 -0700476config SUNVDC
477 tristate "Sun Virtual Disk Client support"
478 depends on SUN_LDOMS
479 help
480 Support for virtual disk devices as a client under Sun
481 Logical Domains.
482
Martin Schwidefsky61d48c22007-05-10 15:46:00 +0200483source "drivers/s390/block/Kconfig"
484
Grant Likely74489a92007-07-17 04:03:39 -0700485config XILINX_SYSACE
486 tristate "Xilinx SystemACE support"
Michal Simek6fa612b2009-05-11 15:49:12 +0200487 depends on 4xx || MICROBLAZE
Grant Likely74489a92007-07-17 04:03:39 -0700488 help
489 Include support for the Xilinx SystemACE CompactFlash interface
490
Jeremy Fitzhardinge9f27ee52007-07-17 18:37:06 -0700491config XEN_BLKDEV_FRONTEND
492 tristate "Xen virtual block device support"
493 depends on XEN
494 default y
Ian Campbell2de06cc2009-02-09 12:05:51 -0800495 select XEN_XENBUS_FRONTEND
Jeremy Fitzhardinge9f27ee52007-07-17 18:37:06 -0700496 help
497 This driver implements the front-end of the Xen virtual
498 block device driver. It communicates with a back-end driver
499 in another domain which drives the actual block device.
500
Konrad Rzeszutek Wilkdfc07b12011-04-18 14:24:23 -0400501config XEN_BLKDEV_BACKEND
Konrad Rzeszutek Wilkea5e1162011-08-03 11:12:17 -0400502 tristate "Xen block-device backend driver"
Konrad Rzeszutek Wilkdfc07b12011-04-18 14:24:23 -0400503 depends on XEN_BACKEND
504 help
505 The block-device backend driver allows the kernel to export its
506 block devices to other guests via a high-performance shared-memory
507 interface.
508
Konrad Rzeszutek Wilka4c34852011-05-12 16:10:55 -0400509 The corresponding Linux frontend driver is enabled by the
510 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
511
512 The backend driver attaches itself to a any block device specified
513 in the XenBus configuration. There are no limits to what the block
514 device as long as it has a major and minor.
515
516 If you are compiling a kernel to run in a Xen block backend driver
517 domain (often this is domain 0) you should say Y here. To
518 compile this driver as a module, chose M here: the module
519 will be called xen-blkback.
520
521
Rusty Russelle467cde2007-10-22 11:03:38 +1000522config VIRTIO_BLK
523 tristate "Virtio block driver (EXPERIMENTAL)"
524 depends on EXPERIMENTAL && VIRTIO
525 ---help---
Anthony Liguori0ad07ec2007-11-07 20:46:31 -0600526 This is the virtual block driver for virtio. It can be used with
527 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
Rusty Russelle467cde2007-10-22 11:03:38 +1000528
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200529config BLK_DEV_HD
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200530 bool "Very old hard disk (MFM/RLL/IDE) driver"
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200531 depends on HAVE_IDE
532 depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
533 help
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200534 This is a very old hard disk driver that lacks the enhanced
535 functionality of the newer ones.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200536
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200537 It is required for systems with ancient MFM/RLL/ESDI drives.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200538
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200539 If unsure, say N.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200540
Yehuda Sadeh602adf42010-08-12 16:11:25 -0700541config BLK_DEV_RBD
542 tristate "Rados block device (RBD)"
543 depends on INET && EXPERIMENTAL && BLOCK
544 select CEPH_LIB
545 select LIBCRC32C
546 select CRYPTO_AES
547 select CRYPTO
548 default n
549 help
550 Say Y here if you want include the Rados block device, which stripes
551 a block device over objects stored in the Ceph distributed object
552 store.
553
554 More information at http://ceph.newdream.net/.
555
556 If unsure, say N.
557
Jan Engelhardtfd11d172007-07-10 12:26:06 +0200558endif # BLK_DEV