Kconfig 19 KB

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