Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474
  1. #
  2. # Block device driver configuration
  3. #
  4. if BLOCK
  5. menu "Block devices"
  6. config BLK_DEV_FD
  7. tristate "Normal floppy disk support"
  8. depends on ARCH_MAY_HAVE_PC_FDC
  9. ---help---
  10. If you want to use the floppy disk drive(s) of your PC under Linux,
  11. say Y. Information about this driver, especially important for IBM
  12. Thinkpad users, is contained in <file:Documentation/floppy.txt>.
  13. That file also contains the location of the Floppy driver FAQ as
  14. well as location of the fdutils package used to configure additional
  15. parameters of the driver at run time.
  16. To compile this driver as a module, choose M here: the
  17. module will be called floppy.
  18. config AMIGA_FLOPPY
  19. tristate "Amiga floppy support"
  20. depends on AMIGA
  21. config ATARI_FLOPPY
  22. tristate "Atari floppy support"
  23. depends on ATARI
  24. config BLK_DEV_SWIM_IOP
  25. bool "Macintosh IIfx/Quadra 900/Quadra 950 floppy support (EXPERIMENTAL)"
  26. depends on MAC && EXPERIMENTAL && BROKEN
  27. help
  28. Say Y here to support the SWIM (Super Woz Integrated Machine) IOP
  29. floppy controller on the Macintosh IIfx and Quadra 900/950.
  30. config MAC_FLOPPY
  31. tristate "Support for PowerMac floppy"
  32. depends on PPC_PMAC && !PPC_PMAC64
  33. help
  34. If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
  35. floppy controller, say Y here. Most commonly found in PowerMacs.
  36. config BLK_DEV_PS2
  37. tristate "PS/2 ESDI hard disk support"
  38. depends on MCA && MCA_LEGACY && BROKEN
  39. help
  40. Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
  41. hard disk.
  42. To compile this driver as a module, choose M here: the
  43. module will be called ps2esdi.
  44. config AMIGA_Z2RAM
  45. tristate "Amiga Zorro II ramdisk support"
  46. depends on ZORRO
  47. help
  48. This enables support for using Chip RAM and Zorro II RAM as a
  49. ramdisk or as a swap partition. Say Y if you want to include this
  50. driver in the kernel.
  51. To compile this driver as a module, choose M here: the
  52. module will be called z2ram.
  53. config ATARI_ACSI
  54. tristate "Atari ACSI support"
  55. depends on ATARI && BROKEN
  56. ---help---
  57. This enables support for the Atari ACSI interface. The driver
  58. supports hard disks and CD-ROMs, which have 512-byte sectors, or can
  59. be switched to that mode. Due to the ACSI command format, only disks
  60. up to 1 GB are supported. Special support for certain ACSI to SCSI
  61. adapters, which could relax that, isn't included yet. The ACSI
  62. driver is also the basis for certain other drivers for devices
  63. attached to the ACSI bus: Atari SLM laser printer, BioNet-100
  64. Ethernet, and PAMsNet Ethernet. If you want to use one of these
  65. devices, you need ACSI support, too.
  66. To compile this driver as a module, choose M here: the
  67. module will be called acsi.
  68. comment "Some devices (e.g. CD jukebox) support multiple LUNs"
  69. depends on ATARI && ATARI_ACSI
  70. config ACSI_MULTI_LUN
  71. bool "Probe all LUNs on each ACSI device"
  72. depends on ATARI_ACSI
  73. help
  74. If you have a ACSI device that supports more than one LUN (Logical
  75. Unit Number), e.g. a CD jukebox, you should say Y here so that all
  76. will be found by the ACSI driver. An ACSI device with multiple LUNs
  77. acts logically like multiple ACSI devices. The vast majority of ACSI
  78. devices have only one LUN, and so most people can say N here and
  79. should in fact do so, because it is safer.
  80. config ATARI_SLM
  81. tristate "Atari SLM laser printer support"
  82. depends on ATARI && ATARI_ACSI!=n
  83. help
  84. If you have an Atari SLM laser printer, say Y to include support for
  85. it in the kernel. Otherwise, say N. This driver is also available as
  86. a module ( = code which can be inserted in and removed from the
  87. running kernel whenever you want). The module will be called
  88. acsi_slm. Be warned: the driver needs much ST-RAM and can cause
  89. problems due to that fact!
  90. config BLK_DEV_XD
  91. tristate "XT hard disk support"
  92. depends on ISA && ISA_DMA_API
  93. help
  94. Very old 8 bit hard disk controllers used in the IBM XT computer
  95. will be supported if you say Y here.
  96. To compile this driver as a module, choose M here: the
  97. module will be called xd.
  98. It's pretty unlikely that you have one of these: say N.
  99. config PARIDE
  100. tristate "Parallel port IDE device support"
  101. depends on PARPORT_PC
  102. ---help---
  103. There are many external CD-ROM and disk devices that connect through
  104. your computer's parallel port. Most of them are actually IDE devices
  105. using a parallel port IDE adapter. This option enables the PARIDE
  106. subsystem which contains drivers for many of these external drives.
  107. Read <file:Documentation/paride.txt> for more information.
  108. If you have said Y to the "Parallel-port support" configuration
  109. option, you may share a single port between your printer and other
  110. parallel port devices. Answer Y to build PARIDE support into your
  111. kernel, or M if you would like to build it as a loadable module. If
  112. your parallel port support is in a loadable module, you must build
  113. PARIDE as a module. If you built PARIDE support into your kernel,
  114. you may still build the individual protocol modules and high-level
  115. drivers as loadable modules. If you build this support as a module,
  116. it will be called paride.
  117. To use the PARIDE support, you must say Y or M here and also to at
  118. least one high-level driver (e.g. "Parallel port IDE disks",
  119. "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
  120. to at least one protocol driver (e.g. "ATEN EH-100 protocol",
  121. "MicroSolutions backpack protocol", "DataStor Commuter protocol"
  122. etc.).
  123. source "drivers/block/paride/Kconfig"
  124. config BLK_CPQ_DA
  125. tristate "Compaq SMART2 support"
  126. depends on PCI
  127. help
  128. This is the driver for Compaq Smart Array controllers. Everyone
  129. using these boards should say Y here. See the file
  130. <file:Documentation/cpqarray.txt> for the current list of boards
  131. supported by this driver, and for further information on the use of
  132. this driver.
  133. config BLK_CPQ_CISS_DA
  134. tristate "Compaq Smart Array 5xxx support"
  135. depends on PCI
  136. help
  137. This is the driver for Compaq Smart Array 5xxx controllers.
  138. Everyone using these boards should say Y here.
  139. See <file:Documentation/cciss.txt> for the current list of
  140. boards supported by this driver, and for further information
  141. on the use of this driver.
  142. config CISS_SCSI_TAPE
  143. bool "SCSI tape drive support for Smart Array 5xxx"
  144. depends on BLK_CPQ_CISS_DA && SCSI && PROC_FS
  145. help
  146. When enabled (Y), this option allows SCSI tape drives and SCSI medium
  147. changers (tape robots) to be accessed via a Compaq 5xxx array
  148. controller. (See <file:Documentation/cciss.txt> for more details.)
  149. "SCSI support" and "SCSI tape support" must also be enabled for this
  150. option to work.
  151. When this option is disabled (N), the SCSI portion of the driver
  152. is not compiled.
  153. config BLK_DEV_DAC960
  154. tristate "Mylex DAC960/DAC1100 PCI RAID Controller support"
  155. depends on PCI
  156. help
  157. This driver adds support for the Mylex DAC960, AcceleRAID, and
  158. eXtremeRAID PCI RAID controllers. See the file
  159. <file:Documentation/README.DAC960> for further information about
  160. this driver.
  161. To compile this driver as a module, choose M here: the
  162. module will be called DAC960.
  163. config BLK_DEV_UMEM
  164. tristate "Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)"
  165. depends on PCI && EXPERIMENTAL
  166. ---help---
  167. Saying Y here will include support for the MM5415 family of
  168. battery backed (Non-volatile) RAM cards.
  169. <http://www.umem.com/>
  170. The cards appear as block devices that can be partitioned into
  171. as many as 15 partitions.
  172. To compile this driver as a module, choose M here: the
  173. module will be called umem.
  174. The umem driver has not yet been allocated a MAJOR number, so
  175. one is chosen dynamically. Use "devfs" or look in /proc/devices
  176. for the device number
  177. config BLK_DEV_UBD
  178. bool "Virtual block device"
  179. depends on UML
  180. ---help---
  181. The User-Mode Linux port includes a driver called UBD which will let
  182. you access arbitrary files on the host computer as block devices.
  183. Unless you know that you do not need such virtual block devices say
  184. Y here.
  185. config BLK_DEV_UBD_SYNC
  186. bool "Always do synchronous disk IO for UBD"
  187. depends on BLK_DEV_UBD
  188. ---help---
  189. Writes to the virtual block device are not immediately written to the
  190. host's disk; this may cause problems if, for example, the User-Mode
  191. Linux 'Virtual Machine' uses a journalling filesystem and the host
  192. computer crashes.
  193. Synchronous operation (i.e. always writing data to the host's disk
  194. immediately) is configurable on a per-UBD basis by using a special
  195. kernel command line option. Alternatively, you can say Y here to
  196. turn on synchronous operation by default for all block devices.
  197. If you're running a journalling file system (like reiserfs, for
  198. example) in your virtual machine, you will want to say Y here. If
  199. you care for the safety of the data in your virtual machine, Y is a
  200. wise choice too. In all other cases (for example, if you're just
  201. playing around with User-Mode Linux) you can choose N.
  202. config BLK_DEV_COW_COMMON
  203. bool
  204. default BLK_DEV_UBD
  205. config MMAPPER
  206. tristate "Example IO memory driver (BROKEN)"
  207. depends on UML && BROKEN
  208. ---help---
  209. The User-Mode Linux port can provide support for IO Memory
  210. emulation with this option. This allows a host file to be
  211. specified as an I/O region on the kernel command line. That file
  212. will be mapped into UML's kernel address space where a driver can
  213. locate it and do whatever it wants with the memory, including
  214. providing an interface to it for UML processes to use.
  215. For more information, see
  216. <http://user-mode-linux.sourceforge.net/iomem.html>.
  217. If you'd like to be able to provide a simulated IO port space for
  218. User-Mode Linux processes, say Y. If unsure, say N.
  219. config BLK_DEV_LOOP
  220. tristate "Loopback device support"
  221. ---help---
  222. Saying Y here will allow you to use a regular file as a block
  223. device; you can then create a file system on that block device and
  224. mount it just as you would mount other block devices such as hard
  225. drive partitions, CD-ROM drives or floppy drives. The loop devices
  226. are block special device files with major number 7 and typically
  227. called /dev/loop0, /dev/loop1 etc.
  228. This is useful if you want to check an ISO 9660 file system before
  229. burning the CD, or if you want to use floppy images without first
  230. writing them to floppy. Furthermore, some Linux distributions avoid
  231. the need for a dedicated Linux partition by keeping their complete
  232. root file system inside a DOS FAT file using this loop device
  233. driver.
  234. To use the loop device, you need the losetup utility, found in the
  235. util-linux package, see
  236. <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
  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. There are several ways of encrypting disks. Some of these require
  243. kernel patches. The vanilla kernel offers the cryptoloop option
  244. and a Device Mapper target (which is superior, as it supports all
  245. file systems). If you want to use the cryptoloop, say Y to both
  246. LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
  247. or later) version of util-linux. Additionally, be aware that
  248. the cryptoloop is not safe for storing journaled filesystems.
  249. Note that this loop device has nothing to do with the loopback
  250. device used for network connections from the machine to itself.
  251. To compile this driver as a module, choose M here: the
  252. module will be called loop.
  253. Most users will answer N here.
  254. config BLK_DEV_CRYPTOLOOP
  255. tristate "Cryptoloop Support"
  256. select CRYPTO
  257. depends on BLK_DEV_LOOP
  258. ---help---
  259. Say Y here if you want to be able to use the ciphers that are
  260. provided by the CryptoAPI as loop transformation. This might be
  261. used as hard disk encryption.
  262. WARNING: This device is not safe for journaled file systems like
  263. ext3 or Reiserfs. Please use the Device Mapper crypto module
  264. instead, which can be configured to be on-disk compatible with the
  265. cryptoloop device.
  266. config BLK_DEV_NBD
  267. tristate "Network block device support"
  268. depends on NET
  269. ---help---
  270. Saying Y here will allow your computer to be a client for network
  271. block devices, i.e. it will be able to use block devices exported by
  272. servers (mount file systems on them etc.). Communication between
  273. client and server works over TCP/IP networking, but to the client
  274. program this is hidden: it looks like a regular local file access to
  275. a block device special file such as /dev/nd0.
  276. Network block devices also allows you to run a block-device in
  277. userland (making server and client physically the same computer,
  278. communicating using the loopback network device).
  279. Read <file:Documentation/nbd.txt> for more information, especially
  280. about where to find the server code, which runs in user space and
  281. does not need special kernel support.
  282. Note that this has nothing to do with the network file systems NFS
  283. or Coda; you can say N here even if you intend to use NFS or Coda.
  284. To compile this driver as a module, choose M here: the
  285. module will be called nbd.
  286. If unsure, say N.
  287. config BLK_DEV_SX8
  288. tristate "Promise SATA SX8 support"
  289. depends on PCI
  290. ---help---
  291. Saying Y or M here will enable support for the
  292. Promise SATA SX8 controllers.
  293. Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
  294. config BLK_DEV_UB
  295. tristate "Low Performance USB Block driver"
  296. depends on USB
  297. help
  298. This driver supports certain USB attached storage devices
  299. such as flash keys.
  300. If you enable this driver, it is recommended to avoid conflicts
  301. with usb-storage by enabling USB_LIBUSUAL.
  302. If unsure, say N.
  303. config BLK_DEV_RAM
  304. tristate "RAM disk support"
  305. ---help---
  306. Saying Y here will allow you to use a portion of your RAM memory as
  307. a block device, so that you can make file systems on it, read and
  308. write to it and do all the other things that you can do with normal
  309. block devices (such as hard drives). It is usually used to load and
  310. store a copy of a minimal root file system off of a floppy into RAM
  311. during the initial install of Linux.
  312. Note that the kernel command line option "ramdisk=XX" is now
  313. obsolete. For details, read <file:Documentation/ramdisk.txt>.
  314. To compile this driver as a module, choose M here: the
  315. module will be called rd.
  316. Most normal users won't need the RAM disk functionality, and can
  317. thus say N here.
  318. config BLK_DEV_RAM_COUNT
  319. int "Default number of RAM disks"
  320. default "16"
  321. depends on BLK_DEV_RAM
  322. help
  323. The default value is 16 RAM disks. Change this if you know what
  324. are doing. If you boot from a filesystem that needs to be extracted
  325. in memory, you will need at least one RAM disk (e.g. root on cramfs).
  326. config BLK_DEV_RAM_SIZE
  327. int "Default RAM disk size (kbytes)"
  328. depends on BLK_DEV_RAM
  329. default "4096"
  330. help
  331. The default value is 4096 kilobytes. Only change this if you know
  332. what are you doing. If you are using IBM S/390, then set this to
  333. 8192.
  334. config BLK_DEV_RAM_BLOCKSIZE
  335. int "Default RAM disk block size (bytes)"
  336. depends on BLK_DEV_RAM
  337. default "1024"
  338. help
  339. The default value is 1024 kilobytes. PAGE_SIZE is a much more
  340. efficient choice however. The default is kept to ensure initrd
  341. setups function - apparently needed by the rd_load_image routine
  342. that supposes the filesystem in the image uses a 1024 blocksize.
  343. config BLK_DEV_INITRD
  344. bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
  345. depends on BROKEN || !FRV
  346. help
  347. The initial RAM filesystem is a ramfs which is loaded by the
  348. boot loader (loadlin or lilo) and that is mounted as root
  349. before the normal boot procedure. It is typically used to
  350. load modules needed to mount the "real" root file system,
  351. etc. See <file:Documentation/initrd.txt> for details.
  352. If RAM disk support (BLK_DEV_RAM) is also included, this
  353. also enables initial RAM disk (initrd) support.
  354. config CDROM_PKTCDVD
  355. tristate "Packet writing on CD/DVD media"
  356. depends on !UML
  357. help
  358. If you have a CDROM drive that supports packet writing, say Y to
  359. include preliminary support. It should work with any MMC/Mt Fuji
  360. compliant ATAPI or SCSI drive, which is just about any newer CD
  361. writer.
  362. Currently only writing to CD-RW, DVD-RW and DVD+RW discs is possible.
  363. DVD-RW disks must be in restricted overwrite mode.
  364. To compile this driver as a module, choose M here: the
  365. module will be called pktcdvd.
  366. config CDROM_PKTCDVD_BUFFERS
  367. int "Free buffers for data gathering"
  368. depends on CDROM_PKTCDVD
  369. default "8"
  370. help
  371. This controls the maximum number of active concurrent packets. More
  372. concurrent packets can increase write performance, but also require
  373. more memory. Each concurrent packet will require approximately 64Kb
  374. of non-swappable kernel memory, memory which will be allocated when
  375. a disc is opened for writing.
  376. config CDROM_PKTCDVD_WCACHE
  377. bool "Enable write caching (EXPERIMENTAL)"
  378. depends on CDROM_PKTCDVD && EXPERIMENTAL
  379. help
  380. If enabled, write caching will be set for the CD-R/W device. For now
  381. this option is dangerous unless the CD-RW media is known good, as we
  382. don't do deferred write error handling yet.
  383. source "drivers/s390/block/Kconfig"
  384. config ATA_OVER_ETH
  385. tristate "ATA over Ethernet support"
  386. depends on NET
  387. help
  388. This driver provides Support for ATA over Ethernet block
  389. devices like the Coraid EtherDrive (R) Storage Blade.
  390. endmenu
  391. endif