blob: 39dd30b6ef86e8aac5db98a2db52c1f28a3787e3 [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_CISS_DA
114 tristate "Compaq Smart Array 5xxx support"
115 depends on PCI
Akinobu Mitab7010ed2012-09-09 12:47:47 +0200116 select CHECK_SIGNATURE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700117 help
118 This is the driver for Compaq Smart Array 5xxx controllers.
119 Everyone using these boards should say Y here.
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000120 See <file:Documentation/blockdev/cciss.txt> for the current list of
Linus Torvalds1da177e2005-04-16 15:20:36 -0700121 boards supported by this driver, and for further information
122 on the use of this driver.
123
124config CISS_SCSI_TAPE
125 bool "SCSI tape drive support for Smart Array 5xxx"
Randy Dunlap3e29fe82006-12-06 20:38:40 -0800126 depends on BLK_CPQ_CISS_DA && PROC_FS
127 depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700128 help
129 When enabled (Y), this option allows SCSI tape drives and SCSI medium
130 changers (tape robots) to be accessed via a Compaq 5xxx array
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000131 controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700132
133 "SCSI support" and "SCSI tape support" must also be enabled for this
134 option to work.
135
136 When this option is disabled (N), the SCSI portion of the driver
137 is not compiled.
138
139config BLK_DEV_DAC960
140 tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
141 depends on PCI
142 help
143 This driver adds support for the Mylex DAC960, AcceleRAID, and
144 eXtremeRAID PCI RAID controllers. See the file
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000145 <file:Documentation/blockdev/README.DAC960> for further information
146 about this driver.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700147
148 To compile this driver as a module, choose M here: the
149 module will be called DAC960.
150
151config BLK_DEV_UMEM
Kees Cookb8977282012-10-23 14:01:51 -0600152 tristate "Micro Memory MM5415 Battery Backed RAM support"
153 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700154 ---help---
155 Saying Y here will include support for the MM5415 family of
156 battery backed (Non-volatile) RAM cards.
157 <http://www.umem.com/>
158
159 The cards appear as block devices that can be partitioned into
160 as many as 15 partitions.
161
162 To compile this driver as a module, choose M here: the
163 module will be called umem.
164
165 The umem driver has not yet been allocated a MAJOR number, so
Adrian Bunkbf6ee0a2006-10-03 22:17:48 +0200166 one is chosen dynamically.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700167
168config BLK_DEV_UBD
169 bool "Virtual block device"
170 depends on UML
171 ---help---
172 The User-Mode Linux port includes a driver called UBD which will let
173 you access arbitrary files on the host computer as block devices.
174 Unless you know that you do not need such virtual block devices say
175 Y here.
176
177config BLK_DEV_UBD_SYNC
178 bool "Always do synchronous disk IO for UBD"
179 depends on BLK_DEV_UBD
180 ---help---
181 Writes to the virtual block device are not immediately written to the
182 host's disk; this may cause problems if, for example, the User-Mode
183 Linux 'Virtual Machine' uses a journalling filesystem and the host
184 computer crashes.
185
186 Synchronous operation (i.e. always writing data to the host's disk
187 immediately) is configurable on a per-UBD basis by using a special
188 kernel command line option. Alternatively, you can say Y here to
189 turn on synchronous operation by default for all block devices.
190
191 If you're running a journalling file system (like reiserfs, for
192 example) in your virtual machine, you will want to say Y here. If
193 you care for the safety of the data in your virtual machine, Y is a
194 wise choice too. In all other cases (for example, if you're just
195 playing around with User-Mode Linux) you can choose N.
196
197config BLK_DEV_COW_COMMON
198 bool
199 default BLK_DEV_UBD
200
Linus Torvalds1da177e2005-04-16 15:20:36 -0700201config BLK_DEV_LOOP
202 tristate "Loopback device support"
203 ---help---
204 Saying Y here will allow you to use a regular file as a block
205 device; you can then create a file system on that block device and
206 mount it just as you would mount other block devices such as hard
207 drive partitions, CD-ROM drives or floppy drives. The loop devices
208 are block special device files with major number 7 and typically
209 called /dev/loop0, /dev/loop1 etc.
210
211 This is useful if you want to check an ISO 9660 file system before
212 burning the CD, or if you want to use floppy images without first
213 writing them to floppy. Furthermore, some Linux distributions avoid
214 the need for a dedicated Linux partition by keeping their complete
215 root file system inside a DOS FAT file using this loop device
216 driver.
217
218 To use the loop device, you need the losetup utility, found in the
219 util-linux package, see
220 <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
221
222 The loop device driver can also be used to "hide" a file system in
223 a disk partition, floppy, or regular file, either using encryption
224 (scrambling the data) or steganography (hiding the data in the low
225 bits of, say, a sound file). This is also safe if the file resides
226 on a remote file server.
227
228 There are several ways of encrypting disks. Some of these require
229 kernel patches. The vanilla kernel offers the cryptoloop option
230 and a Device Mapper target (which is superior, as it supports all
231 file systems). If you want to use the cryptoloop, say Y to both
232 LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
233 or later) version of util-linux. Additionally, be aware that
234 the cryptoloop is not safe for storing journaled filesystems.
235
236 Note that this loop device has nothing to do with the loopback
237 device used for network connections from the machine to itself.
238
239 To compile this driver as a module, choose M here: the
240 module will be called loop.
241
242 Most users will answer N here.
243
Kay Sieversd134b002011-07-31 22:08:04 +0200244config BLK_DEV_LOOP_MIN_COUNT
245 int "Number of loop devices to pre-create at init time"
246 depends on BLK_DEV_LOOP
247 default 8
248 help
249 Static number of loop devices to be unconditionally pre-created
250 at init time.
251
252 This default value can be overwritten on the kernel command
253 line or with module-parameter loop.max_loop.
254
255 The historic default is 8. If a late 2011 version of losetup(8)
256 is used, it can be set to 0, since needed loop devices can be
257 dynamically allocated with the /dev/loop-control interface.
258
Linus Torvalds1da177e2005-04-16 15:20:36 -0700259config BLK_DEV_CRYPTOLOOP
260 tristate "Cryptoloop Support"
261 select CRYPTO
Herbert Xu8df3b0a2006-12-02 14:36:03 +1100262 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700263 depends on BLK_DEV_LOOP
264 ---help---
265 Say Y here if you want to be able to use the ciphers that are
266 provided by the CryptoAPI as loop transformation. This might be
267 used as hard disk encryption.
268
269 WARNING: This device is not safe for journaled file systems like
270 ext3 or Reiserfs. Please use the Device Mapper crypto module
271 instead, which can be configured to be on-disk compatible with the
272 cryptoloop device.
273
Philipp Reisnerb411b362009-09-25 16:07:19 -0700274source "drivers/block/drbd/Kconfig"
275
Linus Torvalds1da177e2005-04-16 15:20:36 -0700276config 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
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000291 Read <file:Documentation/blockdev/nbd.txt> for more information,
292 especially about where to find the server code, which runs in user
293 space and does not need special kernel support.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700294
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
Akhil Bhansalie67f86b2013-10-15 14:19:07 -0600303config BLK_DEV_SKD
304 tristate "STEC S1120 Block Driver"
305 depends on PCI
306 depends on 64BIT
307 ---help---
308 Saying Y or M here will enable support for the
309 STEC, Inc. S1120 PCIe SSD.
310
311 Use device /dev/skd$N amd /dev/skd$Np$M.
312
Jeff Garzik2a138772009-04-10 07:50:45 -0400313config BLK_DEV_OSD
314 tristate "OSD object-as-blkdev support"
315 depends on SCSI_OSD_ULD
316 ---help---
317 Saying Y or M here will allow the exporting of a single SCSI
318 OSD (object-based storage) object as a Linux block device.
319
320 For example, if you create a 2G object on an OSD device,
321 you can then use this module to present that 2G object as
322 a Linux block device.
323
324 To compile this driver as a module, choose M here: the
325 module will be called osdblk.
326
327 If unsure, say N.
328
Linus Torvalds1da177e2005-04-16 15:20:36 -0700329config BLK_DEV_SX8
330 tristate "Promise SATA SX8 support"
331 depends on PCI
332 ---help---
333 Saying Y or M here will enable support for the
334 Promise SATA SX8 controllers.
335
336 Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
337
Linus Torvalds1da177e2005-04-16 15:20:36 -0700338config BLK_DEV_RAM
Nick Piggin9db55792008-02-08 04:19:49 -0800339 tristate "RAM block device support"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700340 ---help---
341 Saying Y here will allow you to use a portion of your RAM memory as
342 a block device, so that you can make file systems on it, read and
343 write to it and do all the other things that you can do with normal
344 block devices (such as hard drives). It is usually used to load and
345 store a copy of a minimal root file system off of a floppy into RAM
346 during the initial install of Linux.
347
Randy Dunlap31c00fc2008-11-13 21:33:24 +0000348 Note that the kernel command line option "ramdisk=XX" is now obsolete.
349 For details, read <file:Documentation/blockdev/ramdisk.txt>.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700350
351 To compile this driver as a module, choose M here: the
Fabian Fredericka3b25d92014-01-23 15:53:46 -0800352 module will be called brd. An alias "rd" has been defined
353 for historical reasons.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700354
355 Most normal users won't need the RAM disk functionality, and can
356 thus say N here.
357
358config BLK_DEV_RAM_COUNT
Adrian Bunka687fb12006-03-28 01:56:17 -0800359 int "Default number of RAM disks"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700360 default "16"
Adrian Bunka687fb12006-03-28 01:56:17 -0800361 depends on BLK_DEV_RAM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700362 help
Patrick Ringl2e977c82007-10-19 23:05:02 +0200363 The default value is 16 RAM disks. Change this if you know what you
Linus Torvalds1da177e2005-04-16 15:20:36 -0700364 are doing. If you boot from a filesystem that needs to be extracted
365 in memory, you will need at least one RAM disk (e.g. root on cramfs).
366
367config BLK_DEV_RAM_SIZE
368 int "Default RAM disk size (kbytes)"
369 depends on BLK_DEV_RAM
370 default "4096"
371 help
372 The default value is 4096 kilobytes. Only change this if you know
Patrick Ringl2e977c82007-10-19 23:05:02 +0200373 what you are doing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700374
Matthew Wilcoxa7a97fc2015-02-16 15:59:41 -0800375config BLK_DEV_RAM_DAX
376 bool "Support Direct Access (DAX) to RAM block devices"
377 depends on BLK_DEV_RAM && FS_DAX
Nick Piggin75acb9c2008-02-08 04:19:50 -0800378 default n
379 help
Matthew Wilcoxa7a97fc2015-02-16 15:59:41 -0800380 Support filesystems using DAX to access RAM block devices. This
381 avoids double-buffering data in the page cache before copying it
382 to the block device. Answering Y will slightly enlarge the kernel,
383 and will prevent RAM block device backing store memory from being
Nick Piggin75acb9c2008-02-08 04:19:50 -0800384 allocated from highmem (only a problem for highmem systems).
385
Linus Torvalds1da177e2005-04-16 15:20:36 -0700386config CDROM_PKTCDVD
387 tristate "Packet writing on CD/DVD media"
388 depends on !UML
389 help
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800390 If you have a CDROM/DVD drive that supports packet writing, say
391 Y to include support. It should work with any MMC/Mt Fuji
392 compliant ATAPI or SCSI drive, which is just about any newer
393 DVD/CD writer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700394
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800395 Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
396 is possible.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700397 DVD-RW disks must be in restricted overwrite mode.
398
Thomas Maier2d4eeec52006-12-08 02:36:10 -0800399 See the file <file:Documentation/cdrom/packet-writing.txt>
400 for further information on the use of this driver.
401
Linus Torvalds1da177e2005-04-16 15:20:36 -0700402 To compile this driver as a module, choose M here: the
403 module will be called pktcdvd.
404
405config CDROM_PKTCDVD_BUFFERS
406 int "Free buffers for data gathering"
407 depends on CDROM_PKTCDVD
408 default "8"
409 help
410 This controls the maximum number of active concurrent packets. More
411 concurrent packets can increase write performance, but also require
412 more memory. Each concurrent packet will require approximately 64Kb
Peter Osterlunde1bc89b2006-02-04 23:27:47 -0800413 of non-swappable kernel memory, memory which will be allocated when
414 a disc is opened for writing.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700415
416config CDROM_PKTCDVD_WCACHE
Kees Cookb8977282012-10-23 14:01:51 -0600417 bool "Enable write caching"
418 depends on CDROM_PKTCDVD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700419 help
420 If enabled, write caching will be set for the CD-R/W device. For now
421 this option is dangerous unless the CD-RW media is known good, as we
422 don't do deferred write error handling yet.
423
Linus Torvalds1da177e2005-04-16 15:20:36 -0700424config ATA_OVER_ETH
425 tristate "ATA over Ethernet support"
426 depends on NET
427 help
428 This driver provides Support for ATA over Ethernet block
429 devices like the Coraid EtherDrive (R) Storage Blade.
430
unsik Kim3fbed4c2009-04-02 12:50:58 -0700431config MG_DISK
432 tristate "mGine mflash, gflash support"
Bartlomiej Zolnierkiewicz8a11a782009-04-28 13:06:16 +0900433 depends on ARM && GPIOLIB
unsik Kim3fbed4c2009-04-02 12:50:58 -0700434 help
435 mGine mFlash(gFlash) block device driver
436
437config MG_DISK_RES
438 int "Size of reserved area before MBR"
439 depends on MG_DISK
440 default 0
441 help
442 Define size of reserved area that usually used for boot. Unit is KB.
443 All of the block device operation will be taken this value as start
444 offset
445 Examples:
446 1024 => 1 MB
447
David S. Miller667ef3c2007-07-16 04:03:56 -0700448config SUNVDC
449 tristate "Sun Virtual Disk Client support"
450 depends on SUN_LDOMS
451 help
452 Support for virtual disk devices as a client under Sun
453 Logical Domains.
454
Martin Schwidefsky61d48c22007-05-10 15:46:00 +0200455source "drivers/s390/block/Kconfig"
456
Grant Likely74489a92007-07-17 04:03:39 -0700457config XILINX_SYSACE
458 tristate "Xilinx SystemACE support"
Michal Simek6fa612b2009-05-11 15:49:12 +0200459 depends on 4xx || MICROBLAZE
Grant Likely74489a92007-07-17 04:03:39 -0700460 help
461 Include support for the Xilinx SystemACE CompactFlash interface
462
Jeremy Fitzhardinge9f27ee52007-07-17 18:37:06 -0700463config XEN_BLKDEV_FRONTEND
464 tristate "Xen virtual block device support"
465 depends on XEN
466 default y
Ian Campbell2de06cc2009-02-09 12:05:51 -0800467 select XEN_XENBUS_FRONTEND
Jeremy Fitzhardinge9f27ee52007-07-17 18:37:06 -0700468 help
469 This driver implements the front-end of the Xen virtual
470 block device driver. It communicates with a back-end driver
471 in another domain which drives the actual block device.
472
Konrad Rzeszutek Wilkdfc07b12011-04-18 14:24:23 -0400473config XEN_BLKDEV_BACKEND
Konrad Rzeszutek Wilkea5e1162011-08-03 11:12:17 -0400474 tristate "Xen block-device backend driver"
Konrad Rzeszutek Wilkdfc07b12011-04-18 14:24:23 -0400475 depends on XEN_BACKEND
476 help
477 The block-device backend driver allows the kernel to export its
478 block devices to other guests via a high-performance shared-memory
479 interface.
480
Konrad Rzeszutek Wilka4c34852011-05-12 16:10:55 -0400481 The corresponding Linux frontend driver is enabled by the
482 CONFIG_XEN_BLKDEV_FRONTEND configuration option.
483
484 The backend driver attaches itself to a any block device specified
485 in the XenBus configuration. There are no limits to what the block
486 device as long as it has a major and minor.
487
488 If you are compiling a kernel to run in a Xen block backend driver
489 domain (often this is domain 0) you should say Y here. To
490 compile this driver as a module, chose M here: the module
491 will be called xen-blkback.
492
493
Rusty Russelle467cde2007-10-22 11:03:38 +1000494config VIRTIO_BLK
Kees Cookb8977282012-10-23 14:01:51 -0600495 tristate "Virtio block driver"
496 depends on VIRTIO
Rusty Russelle467cde2007-10-22 11:03:38 +1000497 ---help---
Anthony Liguori0ad07ec2007-11-07 20:46:31 -0600498 This is the virtual block driver for virtio. It can be used with
499 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
Rusty Russelle467cde2007-10-22 11:03:38 +1000500
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200501config BLK_DEV_HD
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200502 bool "Very old hard disk (MFM/RLL/IDE) driver"
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200503 depends on HAVE_IDE
Linus Walleij3c5710f62013-09-03 11:43:10 +0200504 depends on !ARM || ARCH_RPC || BROKEN
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200505 help
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200506 This is a very old hard disk driver that lacks the enhanced
507 functionality of the newer ones.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200508
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200509 It is required for systems with ancient MFM/RLL/ESDI drives.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200510
Adrian Bunkf327c1c2008-07-16 20:33:47 +0200511 If unsure, say N.
Adrian Bunk453ea3e2008-07-16 20:33:47 +0200512
Yehuda Sadeh602adf42010-08-12 16:11:25 -0700513config BLK_DEV_RBD
514 tristate "Rados block device (RBD)"
Kees Cookb8977282012-10-23 14:01:51 -0600515 depends on INET && BLOCK
Yehuda Sadeh602adf42010-08-12 16:11:25 -0700516 select CEPH_LIB
517 select LIBCRC32C
518 select CRYPTO_AES
519 select CRYPTO
520 default n
521 help
522 Say Y here if you want include the Rados block device, which stripes
523 a block device over objects stored in the Ceph distributed object
524 store.
525
526 More information at http://ceph.newdream.net/.
527
528 If unsure, say N.
529
josh.h.morris@us.ibm.com8722ff82013-02-05 14:15:02 +0100530config BLK_DEV_RSXX
Philip J Kelleherf730e3d2013-06-18 14:43:58 -0500531 tristate "IBM Flash Adapter 900GB Full Height PCIe Device Driver"
josh.h.morris@us.ibm.com8722ff82013-02-05 14:15:02 +0100532 depends on PCI
533 help
534 Device driver for IBM's high speed PCIe SSD
Philip J Kelleherf730e3d2013-06-18 14:43:58 -0500535 storage device: Flash Adapter 900GB Full Height.
josh.h.morris@us.ibm.com8722ff82013-02-05 14:15:02 +0100536
537 To compile this driver as a module, choose M here: the
538 module will be called rsxx.
539
Jan Engelhardtfd11d172007-07-10 12:26:06 +0200540endif # BLK_DEV