Config.in.block 9.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305
  1. menu "Block devices support"
  2. config ADK_KERNEL_MD
  3. boolean
  4. default n
  5. config ADK_KERNEL_SWAP
  6. boolean
  7. default n
  8. config ADK_KERNEL_LBD
  9. boolean
  10. default n
  11. config ADK_KERNEL_BLK_DEV_IO_TRACE
  12. boolean
  13. default n
  14. config ADK_KERNEL_LSF
  15. boolean
  16. default n
  17. config ADK_KERNEL_IOSCHED_AS
  18. boolean
  19. default n
  20. config ADK_KERNEL_IOSCHED_DEADLINE
  21. boolean
  22. default n
  23. config ADK_KERNEL_IOSCHED_CFQ
  24. boolean
  25. default n
  26. config ADK_KERNEL_SCSI
  27. boolean
  28. default n
  29. config ADK_KERNEL_BLK_DEV_SD
  30. boolean
  31. default n
  32. config ADK_KERNEL_DM_CRYPT
  33. boolean
  34. default n
  35. config ADK_KERNEL_BLK_DEV_DM
  36. select ADK_KERNEL_MD
  37. depends on !ADK_LINUX_CRIS_FOXBOARD
  38. boolean
  39. default n
  40. config ADK_KERNEL_ATA
  41. boolean
  42. default n
  43. config ADK_KERNEL_SATA_AHCI
  44. tristate
  45. select ADK_KERNEL_BLOCK
  46. select ADK_KERNEL_ATA
  47. select ADK_KERNEL_BLK_DEV_SD
  48. default n
  49. config ADK_KPACKAGE_KMOD_SATA_AHCI
  50. prompt "kmod-sata-ahci.................... AHCI SATA driver"
  51. tristate
  52. select ADK_KERNEL_BLOCK
  53. select ADK_KERNEL_ATA
  54. select ADK_KERNEL_BLK_DEV_SD
  55. depends on !ADK_KERNEL_SATA_AHCI
  56. depends on !(ADK_LINUX_CRIS_FOXBOARD || ADK_LINUX_MIPS_AG241)
  57. default n
  58. help
  59. Enables support for AHCI Serial ATA.
  60. #config ADK_KERNEL_IDE
  61. # boolean
  62. # default n
  63. #
  64. #config ADK_KPACKAGE_KMOD_BLK_DEV_IDE
  65. # prompt "kmod-ide.......................... IDE support"
  66. # tristate
  67. # select ADK_KERNEL_BLOCK
  68. # select ADK_KERNEL_IDE
  69. # default n
  70. # help
  71. # If you say Y here, you will use the full-featured IDE driver to
  72. # control up to ten ATA/IDE interfaces, each being able to serve a
  73. # "master" and a "slave" device, for a total of up to twenty ATA/IDE
  74. # disk/cdrom/tape/floppy drives.
  75. #
  76. # Useful information about large (>540 MB) IDE disks, multiple
  77. # interfaces, what to do if ATA/IDE devices are not automatically
  78. # detected, sound card ATA/IDE ports, module support, and other
  79. # topics, is contained in <file:Documentation/ide.txt>. For detailed
  80. # information about hard drives, consult the Disk-HOWTO and the
  81. # Multi-Disk-HOWTO, available from
  82. # <http://www.tldp.org/docs.html#howto>.
  83. #
  84. # To fine-tune ATA/IDE drive/interface parameters for improved
  85. # performance, look for the hdparm package at
  86. # <ftp://ibiblio.org/pub/Linux/system/hardware/>.
  87. #
  88. # To compile this driver as a module, choose M here and read
  89. # <file:Documentation/ide.txt>. The module will be called ide-mod.
  90. # Do not compile this driver as a module if your root file system (the
  91. # one containing the directory /) is located on an IDE device.
  92. config ADK_KPACKAGE_KMOD_BLK_DEV_LOOP
  93. prompt "kmod-loop......................... Loop mount support"
  94. tristate
  95. default n
  96. help
  97. Saying Y here will allow you to use a regular file as a block
  98. device; you can then create a file system on that block device and
  99. mount it just as you would mount other block devices such as hard
  100. drive partitions, CD-ROM drives or floppy drives. The loop devices
  101. are block special device files with major number 7 and typically
  102. called /dev/loop0, /dev/loop1 etc.
  103. This is useful if you want to check an ISO 9660 file system before
  104. burning the CD, or if you want to use floppy images without first
  105. writing them to floppy. Furthermore, some Linux distributions avoid
  106. the need for a dedicated Linux partition by keeping their complete
  107. root file system inside a DOS FAT file using this loop device
  108. driver.
  109. To use the loop device, you need the losetup utility, found in the
  110. util-linux package, see
  111. <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
  112. The loop device driver can also be used to "hide" a file system in
  113. a disk partition, floppy, or regular file, either using encryption
  114. (scrambling the data) or steganography (hiding the data in the low
  115. bits of, say, a sound file). This is also safe if the file resides
  116. on a remote file server.
  117. There are several ways of encrypting disks. Some of these require
  118. kernel patches. The vanilla kernel offers the cryptoloop option
  119. and a Device Mapper target (which is superior, as it supports all
  120. file systems). If you want to use the cryptoloop, say Y to both
  121. LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
  122. or later) version of util-linux. Additionally, be aware that
  123. the cryptoloop is not safe for storing journaled filesystems.
  124. Note that this loop device has nothing to do with the loopback
  125. device used for network connections from the machine to itself.
  126. config ADK_KPACKAGE_KMOD_BLK_DEV_NBD
  127. prompt "kmod-nbd.......................... Network Block Device"
  128. tristate
  129. default n
  130. help
  131. Saying Y here will allow your computer to be a client for network
  132. block devices, i.e. it will be able to use block devices exported by
  133. servers (mount file systems on them etc.). Communication between
  134. client and server works over TCP/IP networking, but to the client
  135. program this is hidden: it looks like a regular local file access to
  136. a block device special file such as /dev/nd0.
  137. Network block devices also allows you to run a block-device in
  138. userland (making server and client physically the same computer,
  139. communicating using the loopback network device).
  140. Read <file:Documentation/nbd.txt> for more information, especially
  141. about where to find the server code, which runs in user space and
  142. does not need special kernel support.
  143. Note that this has nothing to do with the network file systems NFS
  144. or Coda; you can say N here even if you intend to use NFS or Coda.
  145. config ADK_KPACKAGE_KMOD_SCSI
  146. prompt "kmod-scsi......................... SCSI support"
  147. select ADK_KERNEL_LBD
  148. select ADK_KERNEL_LSF
  149. select ADK_KERNEL_IOSCHED_AS
  150. depends on !ADK_KERNEL_SCSI
  151. tristate
  152. help
  153. If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
  154. any other SCSI device under Linux, say Y and make sure that you know
  155. the name of your SCSI host adapter (the card inside your computer
  156. that "speaks" the SCSI protocol, also called SCSI controller),
  157. because you will be asked for it.
  158. You also need to say Y here if you have a device which speaks
  159. the SCSI protocol. Examples of this include the parallel port
  160. version of the IOMEGA ZIP drive, USB storage devices, Fibre
  161. Channel, FireWire storage and the IDE-SCSI emulation driver.
  162. config ADK_KPACKAGE_KMOD_BLK_DEV_SD
  163. prompt "kmod-scsi-disk.................... SCSI disk support"
  164. depends on !ADK_KERNEL_BLK_DEV_SD
  165. depends on ADK_KPACKAGE_KMOD_SCSI
  166. tristate
  167. help
  168. If you want to use SCSI hard disks, Fibre Channel disks,
  169. USB storage or the SCSI or parallel port version of
  170. the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
  171. the Disk-HOWTO and the Multi-Disk-HOWTO, available from
  172. <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
  173. CD-ROMs.
  174. config ADK_KPACKAGE_KMOD_BLK_DEV_SR
  175. prompt "kmod-scsi-cdrom................... SCSI CDROM support"
  176. depends on !ADK_KERNEL_SCSI
  177. depends on ADK_KPACKAGE_KMOD_SCSI
  178. tristate
  179. help
  180. If you want to use a SCSI or FireWire CD-ROM under Linux,
  181. say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
  182. <http://www.tldp.org/docs.html#howto>. Also make sure to say
  183. Y or M to "ISO 9660 CD-ROM file system support" later.
  184. config ADK_KERNEL_BLK_DEV_MD
  185. tristate
  186. select ADK_KERNEL_MD
  187. depends on !ADK_LINUX_CRIS_FOXBOARD
  188. default n
  189. config ADK_KPACKAGE_KMOD_BLK_DEV_MD
  190. prompt "kmod-md........................... RAID support"
  191. tristate
  192. depends on !ADK_KERNEL_BLK_DEV_MD
  193. depends on !ADK_LINUX_CRIS_FOXBOARD
  194. select ADK_KERNEL_MD
  195. help
  196. config ADK_KERNEL_MD_RAID0
  197. tristate
  198. depends on ADK_KERNEL_BLK_DEV_MD
  199. help
  200. config ADK_KPACKAGE_KMOD_MD_RAID0
  201. prompt "kmod-md-raid0..................... RAID0 support"
  202. tristate
  203. depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
  204. help
  205. config ADK_KERNEL_MD_RAID1
  206. tristate
  207. depends on ADK_KERNEL_BLK_DEV_MD
  208. help
  209. config ADK_KPACKAGE_KMOD_MD_RAID1
  210. prompt "kmod-md-raid1..................... RAID1 support"
  211. tristate
  212. depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
  213. help
  214. config ADK_KPACKAGE_KMOD_MD_RAID456
  215. prompt "kmod-md-raid456................... RAID456 support"
  216. tristate
  217. depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
  218. help
  219. config ADK_KPACKAGE_KMOD_BLK_DEV_DM
  220. prompt "kmod-dm........................... Device Mapper support"
  221. select ADK_KERNEL_MD
  222. depends on !(ADK_KERNEL_BLK_DEV_DM || ADK_LINUX_CRIS_FOXBOARD)
  223. tristate
  224. help
  225. Device-mapper is a low level volume manager. It works by allowing
  226. people to specify mappings for ranges of logical sectors. Various
  227. mapping types are available, in addition people may write their own
  228. modules containing custom mappings if they wish.
  229. Higher level volume managers such as LVM2 use this driver.
  230. config ADK_KPACKAGE_KMOD_DM_CRYPT
  231. prompt "kmod-dm-crypt................... Crypt target support"
  232. depends on !(ADK_KERNEL_DM_CRYPT || ADK_LINUX_CRIS_FOXBOARD)
  233. select ADK_KPACKAGE_KMOD_BLK_DEV_DM
  234. select ADK_KERNEL_MD
  235. select ADK_KERNEL_CRYPTO
  236. select ADK_KPACKAGE_KMOD_CRYPTO_CBC
  237. select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
  238. tristate
  239. help
  240. This device-mapper target allows you to create a device that
  241. transparently encrypts the data on it. You'll need to activate
  242. the ciphers you're going to use in the cryptoapi configuration.
  243. Information on how to use dm-crypt can be found on
  244. <http://www.saout.de/misc/dm-crypt/>
  245. config ADK_KPACKAGE_KMOD_DM_SNAPSHOT
  246. prompt "kmod-dm-snapshot................ Snapshot target"
  247. select ADK_KPACKAGE_KMOD_BLK_DEV_DM
  248. depends on !ADK_LINUX_CRIS_FOXBOARD
  249. tristate
  250. help
  251. Allow volume managers to take writable snapshots of a device.
  252. config ADK_KPACKAGE_KMOD_DM_MIRROR
  253. prompt "kmod-dm-mirror.................. Mirror target"
  254. select ADK_KPACKAGE_KMOD_BLK_DEV_DM
  255. depends on !ADK_LINUX_CRIS_FOXBOARD
  256. tristate
  257. help
  258. Allow volume managers to mirror logical volumes, also
  259. needed for live data migration tools such as 'pvmove'.
  260. endmenu