blob: 1b8094d4d7af70f38e38bd9d3f5736a55f31dd82 [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
Jens Axboef2298c02013-10-25 11:52:25 +010018config BLK_DEV_NULL_BLK
19 tristate "Null test block driver"
20
Linus Torvalds1da177e2005-04-16 15:20:36 -070021config BLK_DEV_FD
22 tristate "Normal floppy disk support"
viro@ZenIV.linux.org.uka08b6b72005-09-06 01:48:42 +010023 depends on ARCH_MAY_HAVE_PC_FDC
Linus Torvalds1da177e2005-04-16 15:20:36 -070024 ---help---
25 If you want to use the floppy disk drive(s) of your PC under Linux,
26 say Y. Information about this driver, especially important for IBM
Randy Dunlap31c00fc2008-11-13 21:33:24 +000027 Thinkpad users, is contained in
28 <file:Documentation/blockdev/floppy.txt>.
Linus Torvalds1da177e2005-04-16 15:20:36 -070029 That file also contains the location of the Floppy driver FAQ as
30 well as location of the fdutils package used to configure additional
31 parameters of the driver at run time.
32
33 To compile this driver as a module, choose M here: the
34 module will be called floppy.
35
36config AMIGA_FLOPPY
37 tristate "Amiga floppy support"
38 depends on AMIGA
39
40config ATARI_FLOPPY
41 tristate "Atari floppy support"
42 depends on ATARI
43
Linus Torvalds1da177e2005-04-16 15:20:36 -070044config MAC_FLOPPY
45 tristate "Support for PowerMac floppy"
46 depends on PPC_PMAC && !PPC_PMAC64
47 help
48 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
49 floppy controller, say Y here. Most commonly found in PowerMacs.
50
Laurent Vivier8852ecd2008-11-15 16:10:10 +010051config BLK_DEV_SWIM
52 tristate "Support for SWIM Macintosh floppy"
53 depends on M68K && MAC
54 help
55 You should select this option if you want floppy support
56 and you don't have a II, IIfx, Q900, Q950 or AV series.
57
Linus Torvalds1da177e2005-04-16 15:20:36 -070058config AMIGA_Z2RAM
59 tristate "Amiga Zorro II ramdisk support"
60 depends on ZORRO
61 help
62 This enables support for using Chip RAM and Zorro II RAM as a
63 ramdisk or as a swap partition. Say Y if you want to include this
64 driver in the kernel.
65
66 To compile this driver as a module, choose M here: the
67 module will be called z2ram.
68
Randy Dunlap2395e462010-05-11 09:02:55 +020069config GDROM
70 tristate "SEGA Dreamcast GD-ROM drive"
71 depends on SH_DREAMCAST
72 help
73 A standard SEGA Dreamcast comes with a modified CD ROM drive called a
74 "GD-ROM" by SEGA to signify it is capable of reading special disks
75 with up to 1 GB of data. This drive will also read standard CD ROM
76 disks. Select this option to access any disks in your GD ROM drive.
77 Most users will want to say "Y" here.
78 You can also build this as a module which will be called gdrom.
79
Linus Torvalds1da177e2005-04-16 15:20:36 -070080config PARIDE
81 tristate "Parallel port IDE device support"
Marko Kohtala6a19b412006-01-06 00:19:49 -080082 depends on PARPORT_PC
Linus Torvalds1da177e2005-04-16 15:20:36 -070083 ---help---
84 There are many external CD-ROM and disk devices that connect through
85 your computer's parallel port. Most of them are actually IDE devices
86 using a parallel port IDE adapter. This option enables the PARIDE
87 subsystem which contains drivers for many of these external drives.
Randy Dunlap31c00fc2008-11-13 21:33:24 +000088 Read <file:Documentation/blockdev/paride.txt> for more information.
Linus Torvalds1da177e2005-04-16 15:20:36 -070089
90 If you have said Y to the "Parallel-port support" configuration
91 option, you may share a single port between your printer and other
92 parallel port devices. Answer Y to build PARIDE support into your
93 kernel, or M if you would like to build it as a loadable module. If
94 your parallel port support is in a loadable module, you must build
95 PARIDE as a module. If you built PARIDE support into your kernel,
96 you may still build the individual protocol modules and high-level
97 drivers as loadable modules. If you build this support as a module,
98 it will be called paride.
99
100 To use the PARIDE support, you must say Y or M here and also to at
101 least one high-level driver (e.g. "Parallel port IDE disks",
102 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
103 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
104 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
105 etc.).
106
107source "drivers/block/paride/Kconfig"
108
Sam Bradshaw88523a62011-08-30 08:34:26 -0600109source "drivers/block/mtip32xx/Kconfig"
110
Minchan Kimcd67e102014-01-30 15:45:52 -0800111source "drivers/block/zram/Kconfig"
112
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113config BLK_CPQ_DA
114 tristate "Compaq SMART2 support"
Jens Axboe7badfb12013-10-17 16:38:30 -0600115 depends on PCI && VIRT_TO_BUS && 0
Linus Torvalds1da177e2005-04-16 15:20:36 -0700116 help
117 This is the driver for Compaq Smart Array controllers. Everyone
118 using these boards should say Y here. See the file
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000119 <file:Documentation/blockdev/cpqarray.txt> for the current list of
120 boards supported by this driver, and for further information on the
121 use of this driver.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700122
123config BLK_CPQ_CISS_DA
124 tristate "Compaq Smart Array 5xxx support"
125 depends on PCI
Akinobu Mitab7010ed2012-09-09 12:47:47 +0200126 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700127 help
128 This is the driver for Compaq Smart Array 5xxx controllers.
129 Everyone using these boards should say Y here.
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000130 See <file:Documentation/blockdev/cciss.txt> for the current list of
Linus Torvalds1da177e2005-04-16 15:20:36 -0700131 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
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000141 controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700142
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
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000155 <file:Documentation/blockdev/README.DAC960> for further information
156 about this driver.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700157
158 To compile this driver as a module, choose M here: the
159 module will be called DAC960.
160
161config BLK_DEV_UMEM
Kees Cookb8977282012-10-23 14:01:51 -0600162 tristate "Micro Memory MM5415 Battery Backed RAM support"
163 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700164 ---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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700211config BLK_DEV_LOOP
212 tristate "Loopback device support"
213 ---help---
214 Saying Y here will allow you to use a regular file as a block
215 device; you can then create a file system on that block device and
216 mount it just as you would mount other block devices such as hard
217 drive partitions, CD-ROM drives or floppy drives. The loop devices
218 are block special device files with major number 7 and typically
219 called /dev/loop0, /dev/loop1 etc.
220
221 This is useful if you want to check an ISO 9660 file system before
222 burning the CD, or if you want to use floppy images without first
223 writing them to floppy. Furthermore, some Linux distributions avoid
224 the need for a dedicated Linux partition by keeping their complete
225 root file system inside a DOS FAT file using this loop device
226 driver.
227
228 To use the loop device, you need the losetup utility, found in the
229 util-linux package, see
230 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
231
232 The loop device driver can also be used to "hide" a file system in
233 a disk partition, floppy, or regular file, either using encryption
234 (scrambling the data) or steganography (hiding the data in the low
235 bits of, say, a sound file). This is also safe if the file resides
236 on a remote file server.
237
238 There are several ways of encrypting disks. Some of these require
239 kernel patches. The vanilla kernel offers the cryptoloop option
240 and a Device Mapper target (which is superior, as it supports all
241 file systems). If you want to use the cryptoloop, say Y to both
242 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
243 or later) version of util-linux. Additionally, be aware that
244 the cryptoloop is not safe for storing journaled filesystems.
245
246 Note that this loop device has nothing to do with the loopback
247 device used for network connections from the machine to itself.
248
249 To compile this driver as a module, choose M here: the
250 module will be called loop.
251
252 Most users will answer N here.
253
Kay Sieversd134b002011-07-31 22:08:04 +0200254config BLK_DEV_LOOP_MIN_COUNT
255 int "Number of loop devices to pre-create at init time"
256 depends on BLK_DEV_LOOP
257 default 8
258 help
259 Static number of loop devices to be unconditionally pre-created
260 at init time.
261
262 This default value can be overwritten on the kernel command
263 line or with module-parameter loop.max_loop.
264
265 The historic default is 8. If a late 2011 version of losetup(8)
266 is used, it can be set to 0, since needed loop devices can be
267 dynamically allocated with the /dev/loop-control interface.
268
Linus Torvalds1da177e2005-04-16 15:20:36 -0700269config BLK_DEV_CRYPTOLOOP
270 tristate "Cryptoloop Support"
271 select CRYPTO
Herbert Xu8df3b0a2006-12-02 14:36:03 +1100272 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700273 depends on BLK_DEV_LOOP
274 ---help---
275 Say Y here if you want to be able to use the ciphers that are
276 provided by the CryptoAPI as loop transformation. This might be
277 used as hard disk encryption.
278
279 WARNING: This device is not safe for journaled file systems like
280 ext3 or Reiserfs. Please use the Device Mapper crypto module
281 instead, which can be configured to be on-disk compatible with the
282 cryptoloop device.
283
Philipp Reisnerb411b362009-09-25 16:07:19 -0700284source "drivers/block/drbd/Kconfig"
285
Linus Torvalds1da177e2005-04-16 15:20:36 -0700286config 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
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000301 Read <file:Documentation/blockdev/nbd.txt> for more information,
302 especially about where to find the server code, which runs in user
303 space and does not need special kernel support.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700304
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
Matthew Wilcoxb60503b2011-01-20 12:50:14 -0500313config BLK_DEV_NVME
314 tristate "NVM Express block device"
315 depends on PCI
316 ---help---
317 The NVM Express driver is for solid state drives directly
318 connected to the PCI or PCI Express bus. If you know you
319 don't have one of these, it is safe to answer N.
320
321 To compile this driver as a module, choose M here: the
322 module will be called nvme.
323
Akhil Bhansalie67f86b2013-10-15 14:19:07 -0600324config BLK_DEV_SKD
325 tristate "STEC S1120 Block Driver"
326 depends on PCI
327 depends on 64BIT
328 ---help---
329 Saying Y or M here will enable support for the
330 STEC, Inc. S1120 PCIe SSD.
331
332 Use device /dev/skd$N amd /dev/skd$Np$M.
333
Jeff Garzik2a138772009-04-10 07:50:45 -0400334config BLK_DEV_OSD
335 tristate "OSD object-as-blkdev support"
336 depends on SCSI_OSD_ULD
337 ---help---
338 Saying Y or M here will allow the exporting of a single SCSI
339 OSD (object-based storage) object as a Linux block device.
340
341 For example, if you create a 2G object on an OSD device,
342 you can then use this module to present that 2G object as
343 a Linux block device.
344
345 To compile this driver as a module, choose M here: the
346 module will be called osdblk.
347
348 If unsure, say N.
349
Linus Torvalds1da177e2005-04-16 15:20:36 -0700350config BLK_DEV_SX8
351 tristate "Promise SATA SX8 support"
352 depends on PCI
353 ---help---
354 Saying Y or M here will enable support for the
355 Promise SATA SX8 controllers.
356
357 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
358
Linus Torvalds1da177e2005-04-16 15:20:36 -0700359config BLK_DEV_RAM
Nick Piggin9db55792008-02-08 04:19:49 -0800360 tristate "RAM block device support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700361 ---help---
362 Saying Y here will allow you to use a portion of your RAM memory as
363 a block device, so that you can make file systems on it, read and
364 write to it and do all the other things that you can do with normal
365 block devices (such as hard drives). It is usually used to load and
366 store a copy of a minimal root file system off of a floppy into RAM
367 during the initial install of Linux.
368
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000369 Note that the kernel command line option "ramdisk=XX" is now obsolete.
370 For details, read <file:Documentation/blockdev/ramdisk.txt>.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700371
372 To compile this driver as a module, choose M here: the
Fabian Fredericka3b25d92014-01-23 15:53:46 -0800373 module will be called brd. An alias "rd" has been defined
374 for historical reasons.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700375
376 Most normal users won't need the RAM disk functionality, and can
377 thus say N here.
378
379config BLK_DEV_RAM_COUNT
Adrian Bunka687fb12006-03-28 01:56:17 -0800380 int "Default number of RAM disks"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700381 default "16"
Adrian Bunka687fb12006-03-28 01:56:17 -0800382 depends on BLK_DEV_RAM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700383 help
Patrick Ringl2e977c82007-10-19 23:05:02 +0200384 The default value is 16 RAM disks. Change this if you know what you
Linus Torvalds1da177e2005-04-16 15:20:36 -0700385 are doing. If you boot from a filesystem that needs to be extracted
386 in memory, you will need at least one RAM disk (e.g. root on cramfs).
387
388config BLK_DEV_RAM_SIZE
389 int "Default RAM disk size (kbytes)"
390 depends on BLK_DEV_RAM
391 default "4096"
392 help
393 The default value is 4096 kilobytes. Only change this if you know
Patrick Ringl2e977c82007-10-19 23:05:02 +0200394 what you are doing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700395
Matthew Wilcoxa7a97fc2015-02-16 15:59:41 -0800396config BLK_DEV_RAM_DAX
397 bool "Support Direct Access (DAX) to RAM block devices"
398 depends on BLK_DEV_RAM && FS_DAX
Nick Piggin75acb9c2008-02-08 04:19:50 -0800399 default n
400 help
Matthew Wilcoxa7a97fc2015-02-16 15:59:41 -0800401 Support filesystems using DAX to access RAM block devices. This
402 avoids double-buffering data in the page cache before copying it
403 to the block device. Answering Y will slightly enlarge the kernel,
404 and will prevent RAM block device backing store memory from being
Nick Piggin75acb9c2008-02-08 04:19:50 -0800405 allocated from highmem (only a problem for highmem systems).
406
Linus Torvalds1da177e2005-04-16 15:20:36 -0700407config CDROM_PKTCDVD
408 tristate "Packet writing on CD/DVD media"
409 depends on !UML
410 help
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800411 If you have a CDROM/DVD drive that supports packet writing, say
412 Y to include support. It should work with any MMC/Mt Fuji
413 compliant ATAPI or SCSI drive, which is just about any newer
414 DVD/CD writer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700415
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800416 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
417 is possible.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700418 DVD-RW disks must be in restricted overwrite mode.
419
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800420 See the file <file:Documentation/cdrom/packet-writing.txt>
421 for further information on the use of this driver.
422
Linus Torvalds1da177e2005-04-16 15:20:36 -0700423 To compile this driver as a module, choose M here: the
424 module will be called pktcdvd.
425
426config CDROM_PKTCDVD_BUFFERS
427 int "Free buffers for data gathering"
428 depends on CDROM_PKTCDVD
429 default "8"
430 help
431 This controls the maximum number of active concurrent packets. More
432 concurrent packets can increase write performance, but also require
433 more memory. Each concurrent packet will require approximately 64Kb
Peter Osterlunde1bc89b2006-02-04 23:27:47 -0800434 of non-swappable kernel memory, memory which will be allocated when
435 a disc is opened for writing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700436
437config CDROM_PKTCDVD_WCACHE
Kees Cookb8977282012-10-23 14:01:51 -0600438 bool "Enable write caching"
439 depends on CDROM_PKTCDVD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700440 help
441 If enabled, write caching will be set for the CD-R/W device. For now
442 this option is dangerous unless the CD-RW media is known good, as we
443 don't do deferred write error handling yet.
444
Linus Torvalds1da177e2005-04-16 15:20:36 -0700445config ATA_OVER_ETH
446 tristate "ATA over Ethernet support"
447 depends on NET
448 help
449 This driver provides Support for ATA over Ethernet block
450 devices like the Coraid EtherDrive (R) Storage Blade.
451
unsik Kim3fbed4c2009-04-02 12:50:58 -0700452config MG_DISK
453 tristate "mGine mflash, gflash support"
Bartlomiej Zolnierkiewicz8a11a782009-04-28 13:06:16 +0900454 depends on ARM && GPIOLIB
unsik Kim3fbed4c2009-04-02 12:50:58 -0700455 help
456 mGine mFlash(gFlash) block device driver
457
458config MG_DISK_RES
459 int "Size of reserved area before MBR"
460 depends on MG_DISK
461 default 0
462 help
463 Define size of reserved area that usually used for boot. Unit is KB.
464 All of the block device operation will be taken this value as start
465 offset
466 Examples:
467 1024 => 1 MB
468
David S. Miller667ef3c2007-07-16 04:03:56 -0700469config SUNVDC
470 tristate "Sun Virtual Disk Client support"
471 depends on SUN_LDOMS
472 help
473 Support for virtual disk devices as a client under Sun
474 Logical Domains.
475
Martin Schwidefsky61d48c22007-05-10 15:46:00 +0200476source "drivers/s390/block/Kconfig"
477
Grant Likely74489a92007-07-17 04:03:39 -0700478config XILINX_SYSACE
479 tristate "Xilinx SystemACE support"
Michal Simek6fa612b2009-05-11 15:49:12 +0200480 depends on 4xx || MICROBLAZE
Grant Likely74489a92007-07-17 04:03:39 -0700481 help
482 Include support for the Xilinx SystemACE CompactFlash interface
483
Jeremy Fitzhardinge9f27ee52007-07-17 18:37:06 -0700484config XEN_BLKDEV_FRONTEND
485 tristate "Xen virtual block device support"
486 depends on XEN
487 default y
Ian Campbell2de06cc2009-02-09 12:05:51 -0800488 select XEN_XENBUS_FRONTEND
Jeremy Fitzhardinge9f27ee52007-07-17 18:37:06 -0700489 help
490 This driver implements the front-end of the Xen virtual
491 block device driver. It communicates with a back-end driver
492 in another domain which drives the actual block device.
493
Konrad Rzeszutek Wilkdfc07b12011-04-18 14:24:23 -0400494config XEN_BLKDEV_BACKEND
Konrad Rzeszutek Wilkea5e1162011-08-03 11:12:17 -0400495 tristate "Xen block-device backend driver"
Konrad Rzeszutek Wilkdfc07b12011-04-18 14:24:23 -0400496 depends on XEN_BACKEND
497 help
498 The block-device backend driver allows the kernel to export its
499 block devices to other guests via a high-performance shared-memory
500 interface.
501
Konrad Rzeszutek Wilka4c34852011-05-12 16:10:55 -0400502 The corresponding Linux frontend driver is enabled by the
503 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
504
505 The backend driver attaches itself to a any block device specified
506 in the XenBus configuration. There are no limits to what the block
507 device as long as it has a major and minor.
508
509 If you are compiling a kernel to run in a Xen block backend driver
510 domain (often this is domain 0) you should say Y here. To
511 compile this driver as a module, chose M here: the module
512 will be called xen-blkback.
513
514
Rusty Russelle467cde2007-10-22 11:03:38 +1000515config VIRTIO_BLK
Kees Cookb8977282012-10-23 14:01:51 -0600516 tristate "Virtio block driver"
517 depends on VIRTIO
Rusty Russelle467cde2007-10-22 11:03:38 +1000518 ---help---
Anthony Liguori0ad07ec2007-11-07 20:46:31 -0600519 This is the virtual block driver for virtio. It can be used with
520 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
Rusty Russelle467cde2007-10-22 11:03:38 +1000521
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200522config BLK_DEV_HD
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200523 bool "Very old hard disk (MFM/RLL/IDE) driver"
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200524 depends on HAVE_IDE
Linus Walleij3c5710f62013-09-03 11:43:10 +0200525 depends on !ARM || ARCH_RPC || BROKEN
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200526 help
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200527 This is a very old hard disk driver that lacks the enhanced
528 functionality of the newer ones.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200529
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200530 It is required for systems with ancient MFM/RLL/ESDI drives.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200531
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200532 If unsure, say N.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200533
Yehuda Sadeh602adf42010-08-12 16:11:25 -0700534config BLK_DEV_RBD
535 tristate "Rados block device (RBD)"
Kees Cookb8977282012-10-23 14:01:51 -0600536 depends on INET && BLOCK
Yehuda Sadeh602adf42010-08-12 16:11:25 -0700537 select CEPH_LIB
538 select LIBCRC32C
539 select CRYPTO_AES
540 select CRYPTO
541 default n
542 help
543 Say Y here if you want include the Rados block device, which stripes
544 a block device over objects stored in the Ceph distributed object
545 store.
546
547 More information at http://ceph.newdream.net/.
548
549 If unsure, say N.
550
josh.h.morris@us.ibm.com8722ff82013-02-05 14:15:02 +0100551config BLK_DEV_RSXX
Philip J Kelleherf730e3d2013-06-18 14:43:58 -0500552 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
josh.h.morris@us.ibm.com8722ff82013-02-05 14:15:02 +0100553 depends on PCI
554 help
555 Device driver for IBM's high speed PCIe SSD
Philip J Kelleherf730e3d2013-06-18 14:43:58 -0500556 storage device: Flash Adapter 900GB Full Height.
josh.h.morris@us.ibm.com8722ff82013-02-05 14:15:02 +0100557
558 To compile this driver as a module, choose M here: the
559 module will be called rsxx.
560
Jan Engelhardtfd11d172007-07-10 12:26:06 +0200561endif # BLK_DEV