Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473
  1. #
  2. # Block device driver configuration
  3. #
  4. menuconfig BLK_DEV
  5. bool "Block devices"
  6. depends on BLOCK
  7. default y
  8. ---help---
  9. Say Y here to get to see options for various different block device
  10. drivers. This option alone does not add any kernel code.
  11. If you say N, all options in this submenu will be skipped and disabled;
  12. only do this if you know what you are doing.
  13. if BLK_DEV
  14. config BLK_DEV_FD
  15. tristate "Normal floppy disk support"
  16. depends on ARCH_MAY_HAVE_PC_FDC
  17. ---help---
  18. If you want to use the floppy disk drive(s) of your PC under Linux,
  19. say Y. Information about this driver, especially important for IBM
  20. Thinkpad users, is contained in
  21. <file:Documentation/blockdev/floppy.txt>.
  22. That file also contains the location of the Floppy driver FAQ as
  23. well as location of the fdutils package used to configure additional
  24. parameters of the driver at run time.
  25. To compile this driver as a module, choose M here: the
  26. module will be called floppy.
  27. config AMIGA_FLOPPY
  28. tristate "Amiga floppy support"
  29. depends on AMIGA
  30. config ATARI_FLOPPY
  31. tristate "Atari floppy support"
  32. depends on ATARI
  33. config MAC_FLOPPY
  34. tristate "Support for PowerMac floppy"
  35. depends on PPC_PMAC && !PPC_PMAC64
  36. help
  37. If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
  38. floppy controller, say Y here. Most commonly found in PowerMacs.
  39. config BLK_DEV_SWIM
  40. tristate "Support for SWIM Macintosh floppy"
  41. depends on M68K && MAC
  42. help
  43. You should select this option if you want floppy support
  44. and you don't have a II, IIfx, Q900, Q950 or AV series.
  45. config AMIGA_Z2RAM
  46. tristate "Amiga Zorro II ramdisk support"
  47. depends on ZORRO
  48. help
  49. This enables support for using Chip RAM and Zorro II RAM as a
  50. ramdisk or as a swap partition. Say Y if you want to include this
  51. driver in the kernel.
  52. To compile this driver as a module, choose M here: the
  53. module will be called z2ram.
  54. config BLK_DEV_XD
  55. tristate "XT hard disk support"
  56. depends on ISA && ISA_DMA_API
  57. select CHECK_SIGNATURE
  58. help
  59. Very old 8 bit hard disk controllers used in the IBM XT computer
  60. will be supported if you say Y here.
  61. To compile this driver as a module, choose M here: the
  62. module will be called xd.
  63. It's pretty unlikely that you have one of these: say N.
  64. config PARIDE
  65. tristate "Parallel port IDE device support"
  66. depends on PARPORT_PC
  67. ---help---
  68. There are many external CD-ROM and disk devices that connect through
  69. your computer's parallel port. Most of them are actually IDE devices
  70. using a parallel port IDE adapter. This option enables the PARIDE
  71. subsystem which contains drivers for many of these external drives.
  72. Read <file:Documentation/blockdev/paride.txt> for more information.
  73. If you have said Y to the "Parallel-port support" configuration
  74. option, you may share a single port between your printer and other
  75. parallel port devices. Answer Y to build PARIDE support into your
  76. kernel, or M if you would like to build it as a loadable module. If
  77. your parallel port support is in a loadable module, you must build
  78. PARIDE as a module. If you built PARIDE support into your kernel,
  79. you may still build the individual protocol modules and high-level
  80. drivers as loadable modules. If you build this support as a module,
  81. it will be called paride.
  82. To use the PARIDE support, you must say Y or M here and also to at
  83. least one high-level driver (e.g. "Parallel port IDE disks",
  84. "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
  85. to at least one protocol driver (e.g. "ATEN EH-100 protocol",
  86. "MicroSolutions backpack protocol", "DataStor Commuter protocol"
  87. etc.).
  88. config GDROM
  89. tristate "SEGA Dreamcast GD-ROM drive"
  90. depends on SH_DREAMCAST
  91. help
  92. A standard SEGA Dreamcast comes with a modified CD ROM drive called a
  93. "GD-ROM" by SEGA to signify it is capable of reading special disks
  94. with up to 1 GB of data. This drive will also read standard CD ROM
  95. disks. Select this option to access any disks in your GD ROM drive.
  96. Most users will want to say "Y" here.
  97. You can also build this as a module which will be called gdrom.ko
  98. source "drivers/block/paride/Kconfig"
  99. config BLK_CPQ_DA
  100. tristate "Compaq SMART2 support"
  101. depends on PCI && VIRT_TO_BUS
  102. help
  103. This is the driver for Compaq Smart Array controllers. Everyone
  104. using these boards should say Y here. See the file
  105. <file:Documentation/blockdev/cpqarray.txt> for the current list of
  106. boards supported by this driver, and for further information on the
  107. use of this driver.
  108. config BLK_CPQ_CISS_DA
  109. tristate "Compaq Smart Array 5xxx support"
  110. depends on PCI
  111. help
  112. This is the driver for Compaq Smart Array 5xxx controllers.
  113. Everyone using these boards should say Y here.
  114. See <file:Documentation/blockdev/cciss.txt> for the current list of
  115. boards supported by this driver, and for further information
  116. on the use of this driver.
  117. config CISS_SCSI_TAPE
  118. bool "SCSI tape drive support for Smart Array 5xxx"
  119. depends on BLK_CPQ_CISS_DA && PROC_FS
  120. depends on SCSI=y || SCSI=BLK_CPQ_CISS_DA
  121. help
  122. When enabled (Y), this option allows SCSI tape drives and SCSI medium
  123. changers (tape robots) to be accessed via a Compaq 5xxx array
  124. controller. (See <file:Documentation/blockdev/cciss.txt> for more details.)
  125. "SCSI support" and "SCSI tape support" must also be enabled for this
  126. option to work.
  127. When this option is disabled (N), the SCSI portion of the driver
  128. is not compiled.
  129. config BLK_DEV_DAC960
  130. tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
  131. depends on PCI
  132. help
  133. This driver adds support for the Mylex DAC960, AcceleRAID, and
  134. eXtremeRAID PCI RAID controllers. See the file
  135. <file:Documentation/blockdev/README.DAC960> for further information
  136. about this driver.
  137. To compile this driver as a module, choose M here: the
  138. module will be called DAC960.
  139. config BLK_DEV_UMEM
  140. tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
  141. depends on PCI && EXPERIMENTAL
  142. ---help---
  143. Saying Y here will include support for the MM5415 family of
  144. battery backed (Non-volatile) RAM cards.
  145. <http://www.umem.com/>
  146. The cards appear as block devices that can be partitioned into
  147. as many as 15 partitions.
  148. To compile this driver as a module, choose M here: the
  149. module will be called umem.
  150. The umem driver has not yet been allocated a MAJOR number, so
  151. one is chosen dynamically.
  152. config BLK_DEV_UBD
  153. bool "Virtual block device"
  154. depends on UML
  155. ---help---
  156. The User-Mode Linux port includes a driver called UBD which will let
  157. you access arbitrary files on the host computer as block devices.
  158. Unless you know that you do not need such virtual block devices say
  159. Y here.
  160. config BLK_DEV_UBD_SYNC
  161. bool "Always do synchronous disk IO for UBD"
  162. depends on BLK_DEV_UBD
  163. ---help---
  164. Writes to the virtual block device are not immediately written to the
  165. host's disk; this may cause problems if, for example, the User-Mode
  166. Linux 'Virtual Machine' uses a journalling filesystem and the host
  167. computer crashes.
  168. Synchronous operation (i.e. always writing data to the host's disk
  169. immediately) is configurable on a per-UBD basis by using a special
  170. kernel command line option. Alternatively, you can say Y here to
  171. turn on synchronous operation by default for all block devices.
  172. If you're running a journalling file system (like reiserfs, for
  173. example) in your virtual machine, you will want to say Y here. If
  174. you care for the safety of the data in your virtual machine, Y is a
  175. wise choice too. In all other cases (for example, if you're just
  176. playing around with User-Mode Linux) you can choose N.
  177. config BLK_DEV_COW_COMMON
  178. bool
  179. default BLK_DEV_UBD
  180. config BLK_DEV_LOOP
  181. tristate "Loopback device support"
  182. ---help---
  183. Saying Y here will allow you to use a regular file as a block
  184. device; you can then create a file system on that block device and
  185. mount it just as you would mount other block devices such as hard
  186. drive partitions, CD-ROM drives or floppy drives. The loop devices
  187. are block special device files with major number 7 and typically
  188. called /dev/loop0, /dev/loop1 etc.
  189. This is useful if you want to check an ISO 9660 file system before
  190. burning the CD, or if you want to use floppy images without first
  191. writing them to floppy. Furthermore, some Linux distributions avoid
  192. the need for a dedicated Linux partition by keeping their complete
  193. root file system inside a DOS FAT file using this loop device
  194. driver.
  195. To use the loop device, you need the losetup utility, found in the
  196. util-linux package, see
  197. <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
  198. The loop device driver can also be used to "hide" a file system in
  199. a disk partition, floppy, or regular file, either using encryption
  200. (scrambling the data) or steganography (hiding the data in the low
  201. bits of, say, a sound file). This is also safe if the file resides
  202. on a remote file server.
  203. There are several ways of encrypting disks. Some of these require
  204. kernel patches. The vanilla kernel offers the cryptoloop option
  205. and a Device Mapper target (which is superior, as it supports all
  206. file systems). If you want to use the cryptoloop, say Y to both
  207. LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
  208. or later) version of util-linux. Additionally, be aware that
  209. the cryptoloop is not safe for storing journaled filesystems.
  210. Note that this loop device has nothing to do with the loopback
  211. device used for network connections from the machine to itself.
  212. To compile this driver as a module, choose M here: the
  213. module will be called loop.
  214. Most users will answer N here.
  215. config BLK_DEV_CRYPTOLOOP
  216. tristate "Cryptoloop Support"
  217. select CRYPTO
  218. select CRYPTO_CBC
  219. depends on BLK_DEV_LOOP
  220. ---help---
  221. Say Y here if you want to be able to use the ciphers that are
  222. provided by the CryptoAPI as loop transformation. This might be
  223. used as hard disk encryption.
  224. WARNING: This device is not safe for journaled file systems like
  225. ext3 or Reiserfs. Please use the Device Mapper crypto module
  226. instead, which can be configured to be on-disk compatible with the
  227. cryptoloop device.
  228. config BLK_DEV_NBD
  229. tristate "Network block device support"
  230. depends on NET
  231. ---help---
  232. Saying Y here will allow your computer to be a client for network
  233. block devices, i.e. it will be able to use block devices exported by
  234. servers (mount file systems on them etc.). Communication between
  235. client and server works over TCP/IP networking, but to the client
  236. program this is hidden: it looks like a regular local file access to
  237. a block device special file such as /dev/nd0.
  238. Network block devices also allows you to run a block-device in
  239. userland (making server and client physically the same computer,
  240. communicating using the loopback network device).
  241. Read <file:Documentation/blockdev/nbd.txt> for more information,
  242. especially about where to find the server code, which runs in user
  243. space and does not need special kernel support.
  244. Note that this has nothing to do with the network file systems NFS
  245. or Coda; you can say N here even if you intend to use NFS or Coda.
  246. To compile this driver as a module, choose M here: the
  247. module will be called nbd.
  248. If unsure, say N.
  249. config BLK_DEV_SX8
  250. tristate "Promise SATA SX8 support"
  251. depends on PCI
  252. ---help---
  253. Saying Y or M here will enable support for the
  254. Promise SATA SX8 controllers.
  255. Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
  256. config BLK_DEV_UB
  257. tristate "Low Performance USB Block driver"
  258. depends on USB
  259. help
  260. This driver supports certain USB attached storage devices
  261. such as flash keys.
  262. If you enable this driver, it is recommended to avoid conflicts
  263. with usb-storage by enabling USB_LIBUSUAL.
  264. If unsure, say N.
  265. config BLK_DEV_RAM
  266. tristate "RAM block device support"
  267. ---help---
  268. Saying Y here will allow you to use a portion of your RAM memory as
  269. a block device, so that you can make file systems on it, read and
  270. write to it and do all the other things that you can do with normal
  271. block devices (such as hard drives). It is usually used to load and
  272. store a copy of a minimal root file system off of a floppy into RAM
  273. during the initial install of Linux.
  274. Note that the kernel command line option "ramdisk=XX" is now obsolete.
  275. For details, read <file:Documentation/blockdev/ramdisk.txt>.
  276. To compile this driver as a module, choose M here: the
  277. module will be called rd.
  278. Most normal users won't need the RAM disk functionality, and can
  279. thus say N here.
  280. config BLK_DEV_RAM_COUNT
  281. int "Default number of RAM disks"
  282. default "16"
  283. depends on BLK_DEV_RAM
  284. help
  285. The default value is 16 RAM disks. Change this if you know what you
  286. are doing. If you boot from a filesystem that needs to be extracted
  287. in memory, you will need at least one RAM disk (e.g. root on cramfs).
  288. config BLK_DEV_RAM_SIZE
  289. int "Default RAM disk size (kbytes)"
  290. depends on BLK_DEV_RAM
  291. default "4096"
  292. help
  293. The default value is 4096 kilobytes. Only change this if you know
  294. what you are doing.
  295. config BLK_DEV_XIP
  296. bool "Support XIP filesystems on RAM block device"
  297. depends on BLK_DEV_RAM
  298. default n
  299. help
  300. Support XIP filesystems (such as ext2 with XIP support on) on
  301. top of block ram device. This will slightly enlarge the kernel, and
  302. will prevent RAM block device backing store memory from being
  303. allocated from highmem (only a problem for highmem systems).
  304. config CDROM_PKTCDVD
  305. tristate "Packet writing on CD/DVD media"
  306. depends on !UML
  307. help
  308. If you have a CDROM/DVD drive that supports packet writing, say
  309. Y to include support. It should work with any MMC/Mt Fuji
  310. compliant ATAPI or SCSI drive, which is just about any newer
  311. DVD/CD writer.
  312. Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
  313. is possible.
  314. DVD-RW disks must be in restricted overwrite mode.
  315. See the file <file:Documentation/cdrom/packet-writing.txt>
  316. for further information on the use of this driver.
  317. To compile this driver as a module, choose M here: the
  318. module will be called pktcdvd.
  319. config CDROM_PKTCDVD_BUFFERS
  320. int "Free buffers for data gathering"
  321. depends on CDROM_PKTCDVD
  322. default "8"
  323. help
  324. This controls the maximum number of active concurrent packets. More
  325. concurrent packets can increase write performance, but also require
  326. more memory. Each concurrent packet will require approximately 64Kb
  327. of non-swappable kernel memory, memory which will be allocated when
  328. a disc is opened for writing.
  329. config CDROM_PKTCDVD_WCACHE
  330. bool "Enable write caching (EXPERIMENTAL)"
  331. depends on CDROM_PKTCDVD && EXPERIMENTAL
  332. help
  333. If enabled, write caching will be set for the CD-R/W device. For now
  334. this option is dangerous unless the CD-RW media is known good, as we
  335. don't do deferred write error handling yet.
  336. config ATA_OVER_ETH
  337. tristate "ATA over Ethernet support"
  338. depends on NET
  339. help
  340. This driver provides Support for ATA over Ethernet block
  341. devices like the Coraid EtherDrive (R) Storage Blade.
  342. config MG_DISK
  343. tristate "mGine mflash, gflash support"
  344. depends on ARM && ATA && GPIOLIB
  345. help
  346. mGine mFlash(gFlash) block device driver
  347. config MG_DISK_RES
  348. int "Size of reserved area before MBR"
  349. depends on MG_DISK
  350. default 0
  351. help
  352. Define size of reserved area that usually used for boot. Unit is KB.
  353. All of the block device operation will be taken this value as start
  354. offset
  355. Examples:
  356. 1024 => 1 MB
  357. config SUNVDC
  358. tristate "Sun Virtual Disk Client support"
  359. depends on SUN_LDOMS
  360. help
  361. Support for virtual disk devices as a client under Sun
  362. Logical Domains.
  363. source "drivers/s390/block/Kconfig"
  364. config XILINX_SYSACE
  365. tristate "Xilinx SystemACE support"
  366. depends on 4xx
  367. help
  368. Include support for the Xilinx SystemACE CompactFlash interface
  369. config XEN_BLKDEV_FRONTEND
  370. tristate "Xen virtual block device support"
  371. depends on XEN
  372. default y
  373. help
  374. This driver implements the front-end of the Xen virtual
  375. block device driver. It communicates with a back-end driver
  376. in another domain which drives the actual block device.
  377. config VIRTIO_BLK
  378. tristate "Virtio block driver (EXPERIMENTAL)"
  379. depends on EXPERIMENTAL && VIRTIO
  380. ---help---
  381. This is the virtual block driver for virtio. It can be used with
  382. lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
  383. config BLK_DEV_HD
  384. bool "Very old hard disk (MFM/RLL/IDE) driver"
  385. depends on HAVE_IDE
  386. depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
  387. help
  388. This is a very old hard disk driver that lacks the enhanced
  389. functionality of the newer ones.
  390. It is required for systems with ancient MFM/RLL/ESDI drives.
  391. If unsure, say N.
  392. endif # BLK_DEV