1
0

Config.in.block 8.8 KB

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