Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # Block device driver configuration |
| 3 | # |
| 4 | |
Jan Engelhardt | fd11d17 | 2007-07-10 12:26:06 +0200 | [diff] [blame] | 5 | menuconfig BLK_DEV |
| 6 | bool "Block devices" |
| 7 | depends on BLOCK |
| 8 | default y |
Jan Engelhardt | 06bfb7e | 2007-08-18 12:56:21 +0200 | [diff] [blame] | 9 | ---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 Howells | 9361401 | 2006-09-30 20:45:40 +0200 | [diff] [blame] | 15 | |
Jan Engelhardt | fd11d17 | 2007-07-10 12:26:06 +0200 | [diff] [blame] | 16 | if BLK_DEV |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 17 | |
| 18 | config BLK_DEV_FD |
| 19 | tristate "Normal floppy disk support" |
viro@ZenIV.linux.org.uk | a08b6b7 | 2005-09-06 01:48:42 +0100 | [diff] [blame] | 20 | depends on ARCH_MAY_HAVE_PC_FDC |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 21 | ---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 Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 24 | Thinkpad users, is contained in |
| 25 | <file:Documentation/blockdev/floppy.txt>. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 26 | 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 | |
| 33 | config AMIGA_FLOPPY |
| 34 | tristate "Amiga floppy support" |
| 35 | depends on AMIGA |
| 36 | |
| 37 | config ATARI_FLOPPY |
| 38 | tristate "Atari floppy support" |
| 39 | depends on ATARI |
| 40 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 41 | config 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 Vivier | 8852ecd | 2008-11-15 16:10:10 +0100 | [diff] [blame] | 48 | config 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 Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 55 | config 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 Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 66 | config BLK_DEV_XD |
| 67 | tristate "XT hard disk support" |
Al Viro | a553260 | 2005-05-04 05:39:42 +0100 | [diff] [blame] | 68 | depends on ISA && ISA_DMA_API |
Geert Uytterhoeven | 928923c | 2007-08-22 14:01:36 -0700 | [diff] [blame] | 69 | select CHECK_SIGNATURE |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 70 | 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 | |
| 79 | config PARIDE |
| 80 | tristate "Parallel port IDE device support" |
Marko Kohtala | 6a19b41 | 2006-01-06 00:19:49 -0800 | [diff] [blame] | 81 | depends on PARPORT_PC |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 82 | ---help--- |
| 83 | There are many external CD-ROM and disk devices that connect through |
| 84 | your computer's parallel port. Most of them are actually IDE devices |
| 85 | using a parallel port IDE adapter. This option enables the PARIDE |
| 86 | subsystem which contains drivers for many of these external drives. |
Randy Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 87 | Read <file:Documentation/blockdev/paride.txt> for more information. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 88 | |
| 89 | If you have said Y to the "Parallel-port support" configuration |
| 90 | option, you may share a single port between your printer and other |
| 91 | parallel port devices. Answer Y to build PARIDE support into your |
| 92 | kernel, or M if you would like to build it as a loadable module. If |
| 93 | your parallel port support is in a loadable module, you must build |
| 94 | PARIDE as a module. If you built PARIDE support into your kernel, |
| 95 | you may still build the individual protocol modules and high-level |
| 96 | drivers as loadable modules. If you build this support as a module, |
| 97 | it will be called paride. |
| 98 | |
| 99 | To use the PARIDE support, you must say Y or M here and also to at |
| 100 | least one high-level driver (e.g. "Parallel port IDE disks", |
| 101 | "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and |
| 102 | to at least one protocol driver (e.g. "ATEN EH-100 protocol", |
| 103 | "MicroSolutions backpack protocol", "DataStor Commuter protocol" |
| 104 | etc.). |
| 105 | |
Adrian McMenamin | 74ee1a7 | 2008-01-21 18:52:48 +0900 | [diff] [blame] | 106 | config GDROM |
| 107 | tristate "SEGA Dreamcast GD-ROM drive" |
| 108 | depends on SH_DREAMCAST |
| 109 | help |
| 110 | A standard SEGA Dreamcast comes with a modified CD ROM drive called a |
| 111 | "GD-ROM" by SEGA to signify it is capable of reading special disks |
| 112 | with up to 1 GB of data. This drive will also read standard CD ROM |
| 113 | disks. Select this option to access any disks in your GD ROM drive. |
| 114 | Most users will want to say "Y" here. |
Pavel Machek | 4737f09 | 2009-06-05 00:44:53 +0200 | [diff] [blame] | 115 | You can also build this as a module which will be called gdrom. |
Adrian McMenamin | 74ee1a7 | 2008-01-21 18:52:48 +0900 | [diff] [blame] | 116 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 117 | source "drivers/block/paride/Kconfig" |
| 118 | |
| 119 | config BLK_CPQ_DA |
| 120 | tristate "Compaq SMART2 support" |
Stephen Rothwell | f057eac | 2007-07-15 23:40:05 -0700 | [diff] [blame] | 121 | depends on PCI && VIRT_TO_BUS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 122 | help |
| 123 | This is the driver for Compaq Smart Array controllers. Everyone |
| 124 | using these boards should say Y here. See the file |
Randy Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 125 | <file:Documentation/blockdev/cpqarray.txt> for the current list of |
| 126 | boards supported by this driver, and for further information on the |
| 127 | use of this driver. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 128 | |
| 129 | config BLK_CPQ_CISS_DA |
| 130 | tristate "Compaq Smart Array 5xxx support" |
| 131 | depends on PCI |
| 132 | help |
| 133 | This is the driver for Compaq Smart Array 5xxx controllers. |
| 134 | Everyone using these boards should say Y here. |
Randy Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 135 | See <file:Documentation/blockdev/cciss.txt> for the current list of |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 136 | boards supported by this driver, and for further information |
| 137 | on the use of this driver. |
| 138 | |
| 139 | config CISS_SCSI_TAPE |
| 140 | bool "SCSI tape drive support for Smart Array 5xxx" |
Randy Dunlap | 3e29fe8 | 2006-12-06 20:38:40 -0800 | [diff] [blame] | 141 | depends on BLK_CPQ_CISS_DA && PROC_FS |
| 142 | depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 143 | help |
| 144 | When enabled (Y), this option allows SCSI tape drives and SCSI medium |
| 145 | changers (tape robots) to be accessed via a Compaq 5xxx array |
Randy Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 146 | controller. (See <file:Documentation/blockdev/cciss.txt> for more details.) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 147 | |
| 148 | "SCSI support" and "SCSI tape support" must also be enabled for this |
| 149 | option to work. |
| 150 | |
| 151 | When this option is disabled (N), the SCSI portion of the driver |
| 152 | is not compiled. |
| 153 | |
| 154 | config BLK_DEV_DAC960 |
| 155 | tristate "Mylex DAC960/DAC1100 PCI RAID Controller support" |
| 156 | depends on PCI |
| 157 | help |
| 158 | This driver adds support for the Mylex DAC960, AcceleRAID, and |
| 159 | eXtremeRAID PCI RAID controllers. See the file |
Randy Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 160 | <file:Documentation/blockdev/README.DAC960> for further information |
| 161 | about this driver. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 162 | |
| 163 | To compile this driver as a module, choose M here: the |
| 164 | module will be called DAC960. |
| 165 | |
| 166 | config BLK_DEV_UMEM |
| 167 | tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)" |
| 168 | depends on PCI && EXPERIMENTAL |
| 169 | ---help--- |
| 170 | Saying Y here will include support for the MM5415 family of |
| 171 | battery backed (Non-volatile) RAM cards. |
| 172 | <http://www.umem.com/> |
| 173 | |
| 174 | The cards appear as block devices that can be partitioned into |
| 175 | as many as 15 partitions. |
| 176 | |
| 177 | To compile this driver as a module, choose M here: the |
| 178 | module will be called umem. |
| 179 | |
| 180 | The umem driver has not yet been allocated a MAJOR number, so |
Adrian Bunk | bf6ee0a | 2006-10-03 22:17:48 +0200 | [diff] [blame] | 181 | one is chosen dynamically. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 182 | |
| 183 | config BLK_DEV_UBD |
| 184 | bool "Virtual block device" |
| 185 | depends on UML |
| 186 | ---help--- |
| 187 | The User-Mode Linux port includes a driver called UBD which will let |
| 188 | you access arbitrary files on the host computer as block devices. |
| 189 | Unless you know that you do not need such virtual block devices say |
| 190 | Y here. |
| 191 | |
| 192 | config BLK_DEV_UBD_SYNC |
| 193 | bool "Always do synchronous disk IO for UBD" |
| 194 | depends on BLK_DEV_UBD |
| 195 | ---help--- |
| 196 | Writes to the virtual block device are not immediately written to the |
| 197 | host's disk; this may cause problems if, for example, the User-Mode |
| 198 | Linux 'Virtual Machine' uses a journalling filesystem and the host |
| 199 | computer crashes. |
| 200 | |
| 201 | Synchronous operation (i.e. always writing data to the host's disk |
| 202 | immediately) is configurable on a per-UBD basis by using a special |
| 203 | kernel command line option. Alternatively, you can say Y here to |
| 204 | turn on synchronous operation by default for all block devices. |
| 205 | |
| 206 | If you're running a journalling file system (like reiserfs, for |
| 207 | example) in your virtual machine, you will want to say Y here. If |
| 208 | you care for the safety of the data in your virtual machine, Y is a |
| 209 | wise choice too. In all other cases (for example, if you're just |
| 210 | playing around with User-Mode Linux) you can choose N. |
| 211 | |
| 212 | config BLK_DEV_COW_COMMON |
| 213 | bool |
| 214 | default BLK_DEV_UBD |
| 215 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 216 | config BLK_DEV_LOOP |
| 217 | tristate "Loopback device support" |
| 218 | ---help--- |
| 219 | Saying Y here will allow you to use a regular file as a block |
| 220 | device; you can then create a file system on that block device and |
| 221 | mount it just as you would mount other block devices such as hard |
| 222 | drive partitions, CD-ROM drives or floppy drives. The loop devices |
| 223 | are block special device files with major number 7 and typically |
| 224 | called /dev/loop0, /dev/loop1 etc. |
| 225 | |
| 226 | This is useful if you want to check an ISO 9660 file system before |
| 227 | burning the CD, or if you want to use floppy images without first |
| 228 | writing them to floppy. Furthermore, some Linux distributions avoid |
| 229 | the need for a dedicated Linux partition by keeping their complete |
| 230 | root file system inside a DOS FAT file using this loop device |
| 231 | driver. |
| 232 | |
| 233 | To use the loop device, you need the losetup utility, found in the |
| 234 | util-linux package, see |
| 235 | <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>. |
| 236 | |
| 237 | The loop device driver can also be used to "hide" a file system in |
| 238 | a disk partition, floppy, or regular file, either using encryption |
| 239 | (scrambling the data) or steganography (hiding the data in the low |
| 240 | bits of, say, a sound file). This is also safe if the file resides |
| 241 | on a remote file server. |
| 242 | |
| 243 | There are several ways of encrypting disks. Some of these require |
| 244 | kernel patches. The vanilla kernel offers the cryptoloop option |
| 245 | and a Device Mapper target (which is superior, as it supports all |
| 246 | file systems). If you want to use the cryptoloop, say Y to both |
| 247 | LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12 |
| 248 | or later) version of util-linux. Additionally, be aware that |
| 249 | the cryptoloop is not safe for storing journaled filesystems. |
| 250 | |
| 251 | Note that this loop device has nothing to do with the loopback |
| 252 | device used for network connections from the machine to itself. |
| 253 | |
| 254 | To compile this driver as a module, choose M here: the |
| 255 | module will be called loop. |
| 256 | |
| 257 | Most users will answer N here. |
| 258 | |
| 259 | config BLK_DEV_CRYPTOLOOP |
| 260 | tristate "Cryptoloop Support" |
| 261 | select CRYPTO |
Herbert Xu | 8df3b0a | 2006-12-02 14:36:03 +1100 | [diff] [blame] | 262 | select CRYPTO_CBC |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 263 | 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 | |
| 274 | config BLK_DEV_NBD |
| 275 | tristate "Network block device support" |
| 276 | depends on NET |
| 277 | ---help--- |
| 278 | Saying Y here will allow your computer to be a client for network |
| 279 | block devices, i.e. it will be able to use block devices exported by |
| 280 | servers (mount file systems on them etc.). Communication between |
| 281 | client and server works over TCP/IP networking, but to the client |
| 282 | program this is hidden: it looks like a regular local file access to |
| 283 | a block device special file such as /dev/nd0. |
| 284 | |
| 285 | Network block devices also allows you to run a block-device in |
| 286 | userland (making server and client physically the same computer, |
| 287 | communicating using the loopback network device). |
| 288 | |
Randy Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 289 | Read <file:Documentation/blockdev/nbd.txt> for more information, |
| 290 | especially about where to find the server code, which runs in user |
| 291 | space and does not need special kernel support. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 292 | |
| 293 | Note that this has nothing to do with the network file systems NFS |
| 294 | or Coda; you can say N here even if you intend to use NFS or Coda. |
| 295 | |
| 296 | To compile this driver as a module, choose M here: the |
| 297 | module will be called nbd. |
| 298 | |
| 299 | If unsure, say N. |
| 300 | |
Jeff Garzik | 2a13877 | 2009-04-10 07:50:45 -0400 | [diff] [blame^] | 301 | config BLK_DEV_OSD |
| 302 | tristate "OSD object-as-blkdev support" |
| 303 | depends on SCSI_OSD_ULD |
| 304 | ---help--- |
| 305 | Saying Y or M here will allow the exporting of a single SCSI |
| 306 | OSD (object-based storage) object as a Linux block device. |
| 307 | |
| 308 | For example, if you create a 2G object on an OSD device, |
| 309 | you can then use this module to present that 2G object as |
| 310 | a Linux block device. |
| 311 | |
| 312 | To compile this driver as a module, choose M here: the |
| 313 | module will be called osdblk. |
| 314 | |
| 315 | If unsure, say N. |
| 316 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 317 | config BLK_DEV_SX8 |
| 318 | tristate "Promise SATA SX8 support" |
| 319 | depends on PCI |
| 320 | ---help--- |
| 321 | Saying Y or M here will enable support for the |
| 322 | Promise SATA SX8 controllers. |
| 323 | |
| 324 | Use devices /dev/sx8/$N and /dev/sx8/$Np$M. |
| 325 | |
| 326 | config BLK_DEV_UB |
| 327 | tristate "Low Performance USB Block driver" |
| 328 | depends on USB |
| 329 | help |
| 330 | This driver supports certain USB attached storage devices |
| 331 | such as flash keys. |
| 332 | |
Pete Zaitcev | a00828e | 2005-10-22 20:15:09 -0700 | [diff] [blame] | 333 | If you enable this driver, it is recommended to avoid conflicts |
| 334 | with usb-storage by enabling USB_LIBUSUAL. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 335 | |
| 336 | If unsure, say N. |
| 337 | |
| 338 | config BLK_DEV_RAM |
Nick Piggin | 9db5579 | 2008-02-08 04:19:49 -0800 | [diff] [blame] | 339 | tristate "RAM block device support" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 340 | ---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 Dunlap | 31c00fc | 2008-11-13 21:33:24 +0000 | [diff] [blame] | 348 | Note that the kernel command line option "ramdisk=XX" is now obsolete. |
| 349 | For details, read <file:Documentation/blockdev/ramdisk.txt>. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 350 | |
| 351 | To compile this driver as a module, choose M here: the |
| 352 | module will be called rd. |
| 353 | |
| 354 | Most normal users won't need the RAM disk functionality, and can |
| 355 | thus say N here. |
| 356 | |
| 357 | config BLK_DEV_RAM_COUNT |
Adrian Bunk | a687fb1 | 2006-03-28 01:56:17 -0800 | [diff] [blame] | 358 | int "Default number of RAM disks" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 359 | default "16" |
Adrian Bunk | a687fb1 | 2006-03-28 01:56:17 -0800 | [diff] [blame] | 360 | depends on BLK_DEV_RAM |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 361 | help |
Patrick Ringl | 2e977c8 | 2007-10-19 23:05:02 +0200 | [diff] [blame] | 362 | The default value is 16 RAM disks. Change this if you know what you |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 363 | are doing. If you boot from a filesystem that needs to be extracted |
| 364 | in memory, you will need at least one RAM disk (e.g. root on cramfs). |
| 365 | |
| 366 | config BLK_DEV_RAM_SIZE |
| 367 | int "Default RAM disk size (kbytes)" |
| 368 | depends on BLK_DEV_RAM |
| 369 | default "4096" |
| 370 | help |
| 371 | The default value is 4096 kilobytes. Only change this if you know |
Patrick Ringl | 2e977c8 | 2007-10-19 23:05:02 +0200 | [diff] [blame] | 372 | what you are doing. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 373 | |
Nick Piggin | 75acb9c | 2008-02-08 04:19:50 -0800 | [diff] [blame] | 374 | config BLK_DEV_XIP |
| 375 | bool "Support XIP filesystems on RAM block device" |
| 376 | depends on BLK_DEV_RAM |
| 377 | default n |
| 378 | help |
| 379 | Support XIP filesystems (such as ext2 with XIP support on) on |
| 380 | top of block ram device. This will slightly enlarge the kernel, and |
| 381 | will prevent RAM block device backing store memory from being |
| 382 | allocated from highmem (only a problem for highmem systems). |
| 383 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 384 | config CDROM_PKTCDVD |
| 385 | tristate "Packet writing on CD/DVD media" |
| 386 | depends on !UML |
| 387 | help |
Thomas Maier | 2d4eeec5 | 2006-12-08 02:36:10 -0800 | [diff] [blame] | 388 | If you have a CDROM/DVD drive that supports packet writing, say |
| 389 | Y to include support. It should work with any MMC/Mt Fuji |
| 390 | compliant ATAPI or SCSI drive, which is just about any newer |
| 391 | DVD/CD writer. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 392 | |
Thomas Maier | 2d4eeec5 | 2006-12-08 02:36:10 -0800 | [diff] [blame] | 393 | Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs |
| 394 | is possible. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 395 | DVD-RW disks must be in restricted overwrite mode. |
| 396 | |
Thomas Maier | 2d4eeec5 | 2006-12-08 02:36:10 -0800 | [diff] [blame] | 397 | See the file <file:Documentation/cdrom/packet-writing.txt> |
| 398 | for further information on the use of this driver. |
| 399 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 400 | To compile this driver as a module, choose M here: the |
| 401 | module will be called pktcdvd. |
| 402 | |
| 403 | config CDROM_PKTCDVD_BUFFERS |
| 404 | int "Free buffers for data gathering" |
| 405 | depends on CDROM_PKTCDVD |
| 406 | default "8" |
| 407 | help |
| 408 | This controls the maximum number of active concurrent packets. More |
| 409 | concurrent packets can increase write performance, but also require |
| 410 | more memory. Each concurrent packet will require approximately 64Kb |
Peter Osterlund | e1bc89b | 2006-02-04 23:27:47 -0800 | [diff] [blame] | 411 | of non-swappable kernel memory, memory which will be allocated when |
| 412 | a disc is opened for writing. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 413 | |
| 414 | config CDROM_PKTCDVD_WCACHE |
Adrian Bunk | b566cce | 2006-02-04 23:27:45 -0800 | [diff] [blame] | 415 | bool "Enable write caching (EXPERIMENTAL)" |
| 416 | depends on CDROM_PKTCDVD && EXPERIMENTAL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 417 | help |
| 418 | If enabled, write caching will be set for the CD-R/W device. For now |
| 419 | this option is dangerous unless the CD-RW media is known good, as we |
| 420 | don't do deferred write error handling yet. |
| 421 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 422 | config ATA_OVER_ETH |
| 423 | tristate "ATA over Ethernet support" |
| 424 | depends on NET |
| 425 | help |
| 426 | This driver provides Support for ATA over Ethernet block |
| 427 | devices like the Coraid EtherDrive (R) Storage Blade. |
| 428 | |
unsik Kim | 3fbed4c | 2009-04-02 12:50:58 -0700 | [diff] [blame] | 429 | config MG_DISK |
| 430 | tristate "mGine mflash, gflash support" |
Bartlomiej Zolnierkiewicz | 8a11a78 | 2009-04-28 13:06:16 +0900 | [diff] [blame] | 431 | depends on ARM && GPIOLIB |
unsik Kim | 3fbed4c | 2009-04-02 12:50:58 -0700 | [diff] [blame] | 432 | help |
| 433 | mGine mFlash(gFlash) block device driver |
| 434 | |
| 435 | config MG_DISK_RES |
| 436 | int "Size of reserved area before MBR" |
| 437 | depends on MG_DISK |
| 438 | default 0 |
| 439 | help |
| 440 | Define size of reserved area that usually used for boot. Unit is KB. |
| 441 | All of the block device operation will be taken this value as start |
| 442 | offset |
| 443 | Examples: |
| 444 | 1024 => 1 MB |
| 445 | |
David S. Miller | 667ef3c | 2007-07-16 04:03:56 -0700 | [diff] [blame] | 446 | config SUNVDC |
| 447 | tristate "Sun Virtual Disk Client support" |
| 448 | depends on SUN_LDOMS |
| 449 | help |
| 450 | Support for virtual disk devices as a client under Sun |
| 451 | Logical Domains. |
| 452 | |
Martin Schwidefsky | 61d48c2 | 2007-05-10 15:46:00 +0200 | [diff] [blame] | 453 | source "drivers/s390/block/Kconfig" |
| 454 | |
Grant Likely | 74489a9 | 2007-07-17 04:03:39 -0700 | [diff] [blame] | 455 | config XILINX_SYSACE |
| 456 | tristate "Xilinx SystemACE support" |
Michal Simek | 6fa612b | 2009-05-11 15:49:12 +0200 | [diff] [blame] | 457 | depends on 4xx || MICROBLAZE |
Grant Likely | 74489a9 | 2007-07-17 04:03:39 -0700 | [diff] [blame] | 458 | help |
| 459 | Include support for the Xilinx SystemACE CompactFlash interface |
| 460 | |
Jeremy Fitzhardinge | 9f27ee5 | 2007-07-17 18:37:06 -0700 | [diff] [blame] | 461 | config XEN_BLKDEV_FRONTEND |
| 462 | tristate "Xen virtual block device support" |
| 463 | depends on XEN |
| 464 | default y |
| 465 | help |
| 466 | This driver implements the front-end of the Xen virtual |
| 467 | block device driver. It communicates with a back-end driver |
| 468 | in another domain which drives the actual block device. |
| 469 | |
Rusty Russell | e467cde | 2007-10-22 11:03:38 +1000 | [diff] [blame] | 470 | config VIRTIO_BLK |
| 471 | tristate "Virtio block driver (EXPERIMENTAL)" |
| 472 | depends on EXPERIMENTAL && VIRTIO |
| 473 | ---help--- |
Anthony Liguori | 0ad07ec | 2007-11-07 20:46:31 -0600 | [diff] [blame] | 474 | This is the virtual block driver for virtio. It can be used with |
| 475 | lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. |
Rusty Russell | e467cde | 2007-10-22 11:03:38 +1000 | [diff] [blame] | 476 | |
Adrian Bunk | 453ea3e | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 477 | config BLK_DEV_HD |
Adrian Bunk | f327c1c | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 478 | bool "Very old hard disk (MFM/RLL/IDE) driver" |
Adrian Bunk | 453ea3e | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 479 | depends on HAVE_IDE |
| 480 | depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN |
| 481 | help |
Adrian Bunk | f327c1c | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 482 | This is a very old hard disk driver that lacks the enhanced |
| 483 | functionality of the newer ones. |
Adrian Bunk | 453ea3e | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 484 | |
Adrian Bunk | f327c1c | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 485 | It is required for systems with ancient MFM/RLL/ESDI drives. |
Adrian Bunk | 453ea3e | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 486 | |
Adrian Bunk | f327c1c | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 487 | If unsure, say N. |
Adrian Bunk | 453ea3e | 2008-07-16 20:33:47 +0200 | [diff] [blame] | 488 | |
Jan Engelhardt | fd11d17 | 2007-07-10 12:26:06 +0200 | [diff] [blame] | 489 | endif # BLK_DEV |