Config.in.block 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444
  1. config ADK_KERNEL_MD
  2. boolean
  3. config ADK_KERNEL_LBD
  4. boolean
  5. config ADK_KERNEL_BLK_DEV_IO_TRACE
  6. boolean
  7. config ADK_KERNEL_LSF
  8. boolean
  9. config ADK_KERNEL_IOSCHED_AS
  10. boolean
  11. config ADK_KERNEL_IOSCHED_DEADLINE
  12. boolean
  13. config ADK_KERNEL_IOSCHED_CFQ
  14. boolean
  15. config ADK_KERNEL_SCSI
  16. boolean
  17. default y if ADK_TARGET_SYSTEM_IBM_X40
  18. config ADK_KERNEL_SCSI_DMA
  19. boolean
  20. config ADK_KERNEL_BLK_DEV_SD
  21. boolean
  22. config ADK_KERNEL_BLK_DEV_SR
  23. boolean
  24. config ADK_KERNEL_ISCSI_TCP
  25. boolean
  26. config ADK_KERNEL_DM_CRYPT
  27. boolean
  28. config ADK_KERNEL_BLK_DEV
  29. boolean
  30. config ADK_KERNEL_BLK_DEV_DM
  31. boolean
  32. select ADK_KERNEL_MD
  33. config ADK_KERNEL_ATA
  34. boolean
  35. config ADK_KERNEL_ATA_SFF
  36. boolean
  37. config ADK_KERNEL_ATA_BMDMA
  38. boolean
  39. config ADK_KERNEL_CONNECTOR
  40. boolean
  41. config ADK_KERNEL_MMC
  42. boolean
  43. config ADK_KERNEL_MMC_BLOCK
  44. boolean
  45. config ADK_KERNEL_MMC_SDHCI
  46. boolean
  47. config ADK_KERNEL_MMC_SDHCI_IO_ACCESSORS
  48. boolean
  49. config ADK_KERNEL_MMC_SDHCI_PLTFM
  50. boolean
  51. config ADK_KERNEL_MMC_SDHCI_BCM2708_DMA
  52. boolean
  53. config ADK_KERNEL_ATA_PIIX
  54. select ADK_KERNEL_SCSI
  55. select ADK_KERNEL_SCSI_DMA
  56. select ADK_KERNEL_ATA
  57. select ADK_KERNEL_ATA_SFF
  58. select ADK_KERNEL_ATA_BMDMA
  59. select ADK_KERNEL_BLK_DEV
  60. select ADK_KERNEL_BLK_DEV_SD
  61. boolean
  62. config ADK_KERNEL_SCSI_SYM53C8XX_2
  63. select ADK_KERNEL_SCSI
  64. select ADK_KERNEL_BLK_DEV
  65. select ADK_KERNEL_BLK_DEV_SD
  66. boolean
  67. config ADK_KERNEL_SCSI_IBMVSCSI
  68. select ADK_KERNEL_SCSI
  69. select ADK_KERNEL_BLK_DEV
  70. select ADK_KERNEL_BLK_DEV_SD
  71. boolean
  72. config ADK_KERNEL_SCSI_SUNESP
  73. select ADK_KERNEL_SCSI
  74. select ADK_KERNEL_BLK_DEV
  75. select ADK_KERNEL_BLK_DEV_SD
  76. boolean
  77. config ADK_KERNEL_PATA_MACIO
  78. select ADK_KERNEL_SCSI
  79. select ADK_KERNEL_ATA
  80. select ADK_KERNEL_ATA_SFF
  81. select ADK_KERNEL_ATA_BMDMA
  82. select ADK_KERNEL_BLK_DEV
  83. select ADK_KERNEL_BLK_DEV_SD
  84. boolean
  85. config ADK_KERNEL_PATA_PLATFORM
  86. select ADK_KERNEL_SCSI
  87. select ADK_KERNEL_ATA
  88. select ADK_KERNEL_ATA_SFF
  89. select ADK_KERNEL_ATA_BMDMA
  90. select ADK_KERNEL_BLK_DEV
  91. select ADK_KERNEL_BLK_DEV_SD
  92. boolean
  93. config ADK_KERNEL_PATA_PCMCIA
  94. boolean
  95. config ADK_KERNEL_PATA_PXA
  96. boolean
  97. select ADK_KERNEL_SCSI
  98. select ADK_KERNEL_ATA
  99. select ADK_KERNEL_ATA_SFF
  100. select ADK_KERNEL_ATA_BMDMA
  101. select ADK_KERNEL_BLK_DEV
  102. select ADK_KERNEL_BLK_DEV_SD
  103. select ADK_KERNEL_PATA_PCMCIA
  104. default y if ADK_TARGET_SYSTEM_SHARP_ZAURUS
  105. default n
  106. config ADK_KERNEL_MMC_AT91
  107. boolean
  108. select ADK_KERNEL_SCSI
  109. select ADK_KERNEL_MMC
  110. select ADK_KERNEL_MMC_BLOCK
  111. select ADK_KERNEL_BLK_DEV
  112. select ADK_KERNEL_BLK_DEV_SD
  113. default y if ADK_TARGET_SYSTEM_ACMESYSTEMS_FOXG20
  114. default n
  115. config ADK_KERNEL_MMC_SDHCI_BCM2708
  116. boolean
  117. select ADK_KERNEL_SCSI
  118. select ADK_KERNEL_MMC
  119. select ADK_KERNEL_MMC_BLOCK
  120. select ADK_KERNEL_BLK_DEV
  121. select ADK_KERNEL_BLK_DEV_SD
  122. select ADK_KERNEL_MMC_SDHCI
  123. select ADK_KERNEL_MMC_SDHCI_IO_ACCESSORS
  124. select ADK_KERNEL_MMC_SDHCI_PLTFM
  125. select ADK_KERNEL_MMC_SDHCI_BCM2708_DMA
  126. default y if ADK_TARGET_SYSTEM_RASPBERRY_PI
  127. default n
  128. config ADK_KERNEL_PATA_RB532
  129. boolean
  130. select ADK_KERNEL_SCSI
  131. select ADK_KERNEL_ATA
  132. select ADK_KERNEL_ATA_SFF
  133. select ADK_KERNEL_ATA_BMDMA
  134. select ADK_KERNEL_BLK_DEV
  135. select ADK_KERNEL_BLK_DEV_SD
  136. default y if ADK_TARGET_SYSTEM_MIKROTIK_RB532
  137. default n
  138. config ADK_KERNEL_PATA_AMD
  139. boolean
  140. select ADK_KERNEL_SCSI
  141. select ADK_KERNEL_ATA
  142. select ADK_KERNEL_ATA_SFF
  143. select ADK_KERNEL_ATA_BMDMA
  144. select ADK_KERNEL_BLK_DEV
  145. select ADK_KERNEL_BLK_DEV_SD
  146. default y if ADK_TARGET_SYSTEM_PCENGINES_ALIX2D2
  147. default y if ADK_TARGET_SYSTEM_PCENGINES_ALIX2D13
  148. default y if ADK_TARGET_SYSTEM_PCENGINES_ALIX1C
  149. default y if ADK_TARGET_SYSTEM_LEMOTE_YEELONG
  150. default n
  151. config ADK_KERNEL_PATA_SC1200
  152. boolean
  153. select ADK_KERNEL_SCSI
  154. select ADK_KERNEL_ATA
  155. select ADK_KERNEL_ATA_SFF
  156. select ADK_KERNEL_ATA_BMDMA
  157. select ADK_KERNEL_BLK_DEV
  158. select ADK_KERNEL_BLK_DEV_SD
  159. default y if ADK_TARGET_SYSTEM_PCENGINES_WRAP
  160. default n
  161. config ADK_KERNEL_PATA_JMICRON
  162. boolean
  163. select ADK_KERNEL_SCSI
  164. select ADK_KERNEL_ATA
  165. select ADK_KERNEL_ATA_SFF
  166. select ADK_KERNEL_ATA_BMDMA
  167. select ADK_KERNEL_BLK_DEV
  168. select ADK_KERNEL_BLK_DEV_SD
  169. default n
  170. config ADK_KERNEL_SATA_AHCI
  171. tristate
  172. select ADK_KERNEL_SCSI
  173. select ADK_KERNEL_ATA
  174. select ADK_KERNEL_BLK_DEV
  175. select ADK_KERNEL_BLK_DEV_SD
  176. depends on ADK_TARGET_WITH_SATA
  177. default y if ADK_TARGET_SYSTEM_VBOX_I686
  178. default n
  179. menu "Block devices support"
  180. config ADK_KPACKAGE_KMOD_SATA_AHCI
  181. prompt "kmod-sata-ahci.................... AHCI SATA driver"
  182. tristate
  183. select ADK_KERNEL_ATA
  184. select ADK_KERNEL_BLK_DEV_SD
  185. depends on !ADK_KERNEL_SATA_AHCI
  186. depends on ADK_TARGET_WITH_SATA
  187. default n
  188. help
  189. Enables support for AHCI Serial ATA.
  190. config ADK_KPACKAGE_KMOD_BLK_DEV_LOOP
  191. prompt "kmod-blk-dev-loop................. Loop mount support"
  192. tristate
  193. select ADK_KERNEL_BLK_DEV
  194. default n
  195. help
  196. Saying Y here will allow you to use a regular file as a block
  197. device; you can then create a file system on that block device and
  198. mount it just as you would mount other block devices such as hard
  199. drive partitions, CD-ROM drives or floppy drives. The loop devices
  200. are block special device files with major number 7 and typically
  201. called /dev/loop0, /dev/loop1 etc.
  202. This is useful if you want to check an ISO 9660 file system before
  203. burning the CD, or if you want to use floppy images without first
  204. writing them to floppy. Furthermore, some Linux distributions avoid
  205. the need for a dedicated Linux partition by keeping their complete
  206. root file system inside a DOS FAT file using this loop device
  207. driver.
  208. To use the loop device, you need the losetup utility, found in the
  209. util-linux package, see
  210. <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>.
  211. The loop device driver can also be used to "hide" a file system in
  212. a disk partition, floppy, or regular file, either using encryption
  213. (scrambling the data) or steganography (hiding the data in the low
  214. bits of, say, a sound file). This is also safe if the file resides
  215. on a remote file server.
  216. There are several ways of encrypting disks. Some of these require
  217. kernel patches. The vanilla kernel offers the cryptoloop option
  218. and a Device Mapper target (which is superior, as it supports all
  219. file systems). If you want to use the cryptoloop, say Y to both
  220. LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12
  221. or later) version of util-linux. Additionally, be aware that
  222. the cryptoloop is not safe for storing journaled filesystems.
  223. Note that this loop device has nothing to do with the loopback
  224. device used for network connections from the machine to itself.
  225. config ADK_KPACKAGE_KMOD_BLK_DEV_NBD
  226. prompt "kmod-blk-dev-nbd.................. Network Block Device"
  227. tristate
  228. default n
  229. help
  230. Saying Y here will allow your computer to be a client for network
  231. block devices, i.e. it will be able to use block devices exported by
  232. servers (mount file systems on them etc.). Communication between
  233. client and server works over TCP/IP networking, but to the client
  234. program this is hidden: it looks like a regular local file access to
  235. a block device special file such as /dev/nd0.
  236. Network block devices also allows you to run a block-device in
  237. userland (making server and client physically the same computer,
  238. communicating using the loopback network device).
  239. Read <file:Documentation/nbd.txt> for more information, especially
  240. about where to find the server code, which runs in user space and
  241. does not need special kernel support.
  242. Note that this has nothing to do with the network file systems NFS
  243. or Coda; you can say N here even if you intend to use NFS or Coda.
  244. config ADK_KPACKAGE_KMOD_SCSI
  245. prompt "kmod-scsi......................... SCSI support"
  246. select ADK_KERNEL_LBD
  247. select ADK_KERNEL_LSF
  248. select ADK_KERNEL_IOSCHED_AS
  249. depends on !ADK_KERNEL_SCSI
  250. tristate
  251. help
  252. If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
  253. any other SCSI device under Linux, say Y and make sure that you know
  254. the name of your SCSI host adapter (the card inside your computer
  255. that "speaks" the SCSI protocol, also called SCSI controller),
  256. because you will be asked for it.
  257. You also need to say Y here if you have a device which speaks
  258. the SCSI protocol. Examples of this include the parallel port
  259. version of the IOMEGA ZIP drive, USB storage devices, Fibre
  260. Channel, FireWire storage and the IDE-SCSI emulation driver.
  261. config ADK_KPACKAGE_KMOD_BLK_DEV_SD
  262. prompt "kmod-scsi-disk.................... SCSI disk support"
  263. select ADK_KPACKAGE_KMOD_SCSI if !ADK_KERNEL_SCSI
  264. depends on !ADK_KERNEL_BLK_DEV_SD
  265. tristate
  266. help
  267. If you want to use SCSI hard disks, Fibre Channel disks,
  268. USB storage or the SCSI or parallel port version of
  269. the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
  270. the Disk-HOWTO and the Multi-Disk-HOWTO, available from
  271. <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
  272. CD-ROMs.
  273. config ADK_KPACKAGE_KMOD_BLK_DEV_SR
  274. prompt "kmod-scsi-cdrom................... SCSI CDROM support"
  275. depends on !ADK_KERNEL_SCSI
  276. depends on !ADK_KERNEL_BLK_DEV_SR
  277. depends on ADK_KPACKAGE_KMOD_SCSI
  278. tristate
  279. help
  280. If you want to use a SCSI or FireWire CD-ROM under Linux,
  281. say Y and read the SCSI-HOWTO and the CDROM-HOWTO at
  282. <http://www.tldp.org/docs.html#howto>. Also make sure to say
  283. Y or M to "ISO 9660 CD-ROM file system support" later.
  284. config ADK_KERNEL_BLK_DEV_MD
  285. prompt "md support........................ RAID support (kernel)"
  286. tristate
  287. select ADK_KERNEL_MD
  288. default n
  289. config ADK_KPACKAGE_KMOD_BLK_DEV_MD
  290. prompt "kmod-blk-dev-md................... RAID support (module)"
  291. tristate
  292. depends on !ADK_KERNEL_BLK_DEV_MD
  293. select ADK_KERNEL_MD
  294. help
  295. config ADK_KERNEL_MD_RAID0
  296. prompt "raid0 support.................... RAID0 support (kernel)"
  297. tristate
  298. depends on ADK_KERNEL_BLK_DEV_MD
  299. help
  300. config ADK_KPACKAGE_KMOD_MD_RAID0
  301. prompt "kmod-md-raid0..................... RAID0 support (module)"
  302. tristate
  303. depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
  304. depends on !ADK_KERNEL_MD_RAID0
  305. help
  306. config ADK_KERNEL_MD_RAID1
  307. prompt "raid1 support.................... RAID1 support (kernel)"
  308. tristate
  309. depends on ADK_KERNEL_BLK_DEV_MD
  310. help
  311. config ADK_KPACKAGE_KMOD_MD_RAID1
  312. prompt "kmod-md-raid1..................... RAID1 support (module)"
  313. tristate
  314. depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
  315. help
  316. config ADK_KPACKAGE_KMOD_MD_RAID456
  317. prompt "kmod-md-raid456................... RAID456 support"
  318. tristate
  319. depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD
  320. help
  321. config ADK_KPACKAGE_KMOD_BLK_DEV_DM
  322. prompt "kmod-blk-dev-dm................... Device Mapper support"
  323. select ADK_KERNEL_MD
  324. depends on !ADK_KERNEL_BLK_DEV_DM
  325. tristate
  326. help
  327. Device-mapper is a low level volume manager. It works by allowing
  328. people to specify mappings for ranges of logical sectors. Various
  329. mapping types are available, in addition people may write their own
  330. modules containing custom mappings if they wish.
  331. Higher level volume managers such as LVM2 use this driver.
  332. config ADK_KPACKAGE_KMOD_DM_CRYPT
  333. prompt "kmod-dm-crypt..................... Crypt target support"
  334. depends on !ADK_KERNEL_DM_CRYPT
  335. depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM
  336. select ADK_KERNEL_MD
  337. select ADK_KERNEL_CRYPTO
  338. select ADK_KPACKAGE_KMOD_CRYPTO_CBC
  339. select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER
  340. tristate
  341. help
  342. This device-mapper target allows you to create a device that
  343. transparently encrypts the data on it. You'll need to activate
  344. the ciphers you're going to use in the cryptoapi configuration.
  345. Information on how to use dm-crypt can be found on
  346. <http://www.saout.de/misc/dm-crypt/>
  347. config ADK_KPACKAGE_KMOD_DM_SNAPSHOT
  348. prompt "kmod-dm-snapshot.................. Snapshot target"
  349. depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM
  350. tristate
  351. help
  352. Allow volume managers to take writable snapshots of a device.
  353. config ADK_KPACKAGE_KMOD_DM_MIRROR
  354. prompt "kmod-dm-mirror.................... Mirror target"
  355. depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM
  356. tristate
  357. help
  358. Allow volume managers to mirror logical volumes, also
  359. needed for live data migration tools such as 'pvmove'.
  360. config ADK_KPACKAGE_KMOD_BLK_DEV_DRBD
  361. prompt "kmod-blk-dev-drbd................. DRBD support (Network RAID 1)"
  362. tristate
  363. select ADK_KERNEL_BLK_DEV
  364. select ADK_KERNEL_CONNECTOR
  365. help
  366. DRBD - http://www.drbd.org
  367. config ADK_KERNEL_SWAP
  368. prompt "swap.............................. SWAP support"
  369. boolean
  370. help
  371. Kernel swap support.
  372. endmenu