Kconfig 23 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673
  1. # drivers/mtd/maps/Kconfig
  2. # $Id: Kconfig,v 1.42 2005/01/05 16:59:50 dwmw2 Exp $
  3. menu "Mapping drivers for chip access"
  4. depends on MTD!=n
  5. config MTD_COMPLEX_MAPPINGS
  6. bool "Support non-linear mappings of flash chips"
  7. depends on MTD
  8. help
  9. This causes the chip drivers to allow for complicated
  10. paged mappings of flash chips.
  11. config MTD_PHYSMAP
  12. tristate "CFI Flash device in physical memory map"
  13. depends on MTD_CFI
  14. help
  15. This provides a 'mapping' driver which allows the CFI probe and
  16. command set driver code to communicate with flash chips which
  17. are mapped physically into the CPU's memory. You will need to
  18. configure the physical address and size of the flash chips on
  19. your particular board as well as the bus width, either statically
  20. with config options or at run-time.
  21. config MTD_PHYSMAP_START
  22. hex "Physical start address of flash mapping"
  23. depends on MTD_PHYSMAP
  24. default "0x8000000"
  25. help
  26. This is the physical memory location at which the flash chips
  27. are mapped on your particular target board. Refer to the
  28. memory map which should hopefully be in the documentation for
  29. your board.
  30. Ignore this option if you use run-time physmap configuration
  31. (i.e., run-time calling physmap_configure()).
  32. config MTD_PHYSMAP_LEN
  33. hex "Physical length of flash mapping"
  34. depends on MTD_PHYSMAP
  35. default "0x4000000"
  36. help
  37. This is the total length of the mapping of the flash chips on
  38. your particular board. If there is space, or aliases, in the
  39. physical memory map between the chips, this could be larger
  40. than the total amount of flash present. Refer to the memory
  41. map which should hopefully be in the documentation for your
  42. board.
  43. Ignore this option if you use run-time physmap configuration
  44. (i.e., run-time calling physmap_configure()).
  45. config MTD_PHYSMAP_BANKWIDTH
  46. int "Bank width in octets"
  47. depends on MTD_PHYSMAP
  48. default "2"
  49. help
  50. This is the total width of the data bus of the flash devices
  51. in octets. For example, if you have a data bus width of 32
  52. bits, you would set the bus width octect value to 4. This is
  53. used internally by the CFI drivers.
  54. Ignore this option if you use run-time physmap configuration
  55. (i.e., run-time calling physmap_configure()).
  56. config MTD_SUN_UFLASH
  57. tristate "Sun Microsystems userflash support"
  58. depends on (SPARC32 || SPARC64) && MTD_CFI
  59. help
  60. This provides a 'mapping' driver which supports the way in
  61. which user-programmable flash chips are connected on various
  62. Sun Microsystems boardsets. This driver will require CFI support
  63. in the kernel, so if you did not enable CFI previously, do that now.
  64. config MTD_PNC2000
  65. tristate "CFI Flash device mapped on Photron PNC-2000"
  66. depends on X86 && MTD_CFI && MTD_PARTITIONS
  67. help
  68. PNC-2000 is the name of Network Camera product from PHOTRON
  69. Ltd. in Japan. It uses CFI-compliant flash.
  70. config MTD_SC520CDP
  71. tristate "CFI Flash device mapped on AMD SC520 CDP"
  72. depends on X86 && MTD_CFI
  73. help
  74. The SC520 CDP board has two banks of CFI-compliant chips and one
  75. Dual-in-line JEDEC chip. This 'mapping' driver supports that
  76. arrangement, implementing three MTD devices.
  77. config MTD_NETSC520
  78. tristate "CFI Flash device mapped on AMD NetSc520"
  79. depends on X86 && MTD_CFI && MTD_PARTITIONS
  80. help
  81. This enables access routines for the flash chips on the AMD NetSc520
  82. demonstration board. If you have one of these boards and would like
  83. to use the flash chips on it, say 'Y'.
  84. config MTD_TS5500
  85. tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
  86. depends on X86 && MTD_JEDECPROBE && MTD_PARTITIONS
  87. help
  88. This provides a driver for the on-board flash of the Technologic
  89. System's TS-5500 board. The flash is split into 3 partitions
  90. which are accessed as separate MTD devices.
  91. mtd0 and mtd2 are the two BIOS drives. Unfortunately the BIOS
  92. uses a proprietary flash translation layer from General Software,
  93. which is not supported (the drives cannot be mounted). You can
  94. create your own file system (jffs for example), but the BIOS
  95. won't be able to boot from it.
  96. mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
  97. Note that jumper 3 ("Write Enable Drive A") must be set
  98. otherwise detection won't succeeed.
  99. config MTD_SBC_GXX
  100. tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
  101. depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
  102. help
  103. This provides a driver for the on-board flash of Arcom Control
  104. Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
  105. By default the flash is split into 3 partitions which are accessed
  106. as separate MTD devices. This board utilizes Intel StrataFlash.
  107. More info at
  108. <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
  109. config MTD_ELAN_104NC
  110. tristate "CFI Flash device mapped on Arcom ELAN-104NC"
  111. depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
  112. help
  113. This provides a driver for the on-board flash of the Arcom Control
  114. System's ELAN-104NC development board. By default the flash
  115. is split into 3 partitions which are accessed as separate MTD
  116. devices. This board utilizes Intel StrataFlash. More info at
  117. <http://www.arcomcontrols.com/products/icp/pc104/processors/ELAN104NC.htm>.
  118. config MTD_LUBBOCK
  119. tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
  120. depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
  121. help
  122. This provides a driver for the on-board flash of the Intel
  123. 'Lubbock' XScale evaluation board.
  124. config MTD_OCTAGON
  125. tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
  126. depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
  127. help
  128. This provides a 'mapping' driver which supports the way in which
  129. the flash chips are connected in the Octagon-5066 Single Board
  130. Computer. More information on the board is available at
  131. <http://www.octagonsystems.com/CPUpages/5066.html>.
  132. config MTD_VMAX
  133. tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
  134. depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
  135. help
  136. This provides a 'mapping' driver which supports the way in which
  137. the flash chips are connected in the Tempustech VMAX SBC301 Single
  138. Board Computer. More information on the board is available at
  139. <http://www.tempustech.com/>.
  140. config MTD_SCx200_DOCFLASH
  141. tristate "Flash device mapped with DOCCS on NatSemi SCx200"
  142. depends on SCx200 && MTD_CFI && MTD_PARTITIONS
  143. help
  144. Enable support for a flash chip mapped using the DOCCS signal on a
  145. National Semiconductor SCx200 processor.
  146. If you don't know what to do here, say N.
  147. If compiled as a module, it will be called scx200_docflash.
  148. config MTD_AMD76XROM
  149. tristate "BIOS flash chip on AMD76x southbridge"
  150. depends on X86 && MTD_JEDECPROBE
  151. help
  152. Support for treating the BIOS flash chip on AMD76x motherboards
  153. as an MTD device - with this you can reprogram your BIOS.
  154. BE VERY CAREFUL.
  155. config MTD_ICHXROM
  156. tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
  157. depends on X86 && MTD_JEDECPROBE
  158. help
  159. Support for treating the BIOS flash chip on ICHX motherboards
  160. as an MTD device - with this you can reprogram your BIOS.
  161. BE VERY CAREFUL.
  162. config MTD_SCB2_FLASH
  163. tristate "BIOS flash chip on Intel SCB2 boards"
  164. depends on X86 && MTD_JEDECPROBE
  165. help
  166. Support for treating the BIOS flash chip on Intel SCB2 boards
  167. as an MTD device - with this you can reprogram your BIOS.
  168. BE VERY CAREFUL.
  169. config MTD_TSUNAMI
  170. tristate "Flash chips on Tsunami TIG bus"
  171. depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
  172. help
  173. Support for the flash chip on Tsunami TIG bus.
  174. config MTD_LASAT
  175. tristate "Flash chips on LASAT board"
  176. depends on LASAT
  177. help
  178. Support for the flash chips on the Lasat 100 and 200 boards.
  179. config MTD_NETtel
  180. tristate "CFI flash device on SnapGear/SecureEdge"
  181. depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
  182. help
  183. Support for flash chips on NETtel/SecureEdge/SnapGear boards.
  184. config MTD_PB1XXX
  185. tristate "Flash devices on Alchemy PB1xxx boards"
  186. depends on MIPS && ( MIPS_PB1000 || MIPS_PB1100 || MIPS_PB1500 )
  187. help
  188. Flash memory access on Alchemy Pb1000/Pb1100/Pb1500 boards
  189. config MTD_PB1XXX_BOOT
  190. bool "PB1x00 boot flash device"
  191. depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 )
  192. help
  193. Use the first of the two 32MiB flash banks on Pb1100/Pb1500 board.
  194. You can say 'Y' to both this and 'MTD_PB1XXX_USER' below, to use
  195. both banks.
  196. config MTD_PB1XXX_USER
  197. bool "PB1x00 user flash device"
  198. depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 )
  199. default y if MTD_PB1XX_BOOT = n
  200. help
  201. Use the second of the two 32MiB flash banks on Pb1100/Pb1500 board.
  202. You can say 'Y' to both this and 'MTD_PB1XXX_BOOT' above, to use
  203. both banks.
  204. config MTD_PB1550
  205. tristate "Flash devices on Alchemy PB1550 board"
  206. depends on MIPS && MIPS_PB1550
  207. help
  208. Flash memory access on Alchemy Pb1550 board
  209. config MTD_PB1550_BOOT
  210. bool "PB1550 boot flash device"
  211. depends on MTD_PB1550
  212. help
  213. Use the first of the two 64MiB flash banks on Pb1550 board.
  214. You can say 'Y' to both this and 'MTD_PB1550_USER' below, to use
  215. both banks.
  216. config MTD_PB1550_USER
  217. bool "PB1550 user flash device"
  218. depends on MTD_PB1550
  219. default y if MTD_PB1550_BOOT = n
  220. help
  221. Use the second of the two 64MiB flash banks on Pb1550 board.
  222. You can say 'Y' to both this and 'MTD_PB1550_BOOT' above, to use
  223. both banks.
  224. config MTD_DB1550
  225. tristate "Flash devices on Alchemy DB1550 board"
  226. depends on MIPS && MIPS_DB1550
  227. help
  228. Flash memory access on Alchemy Db1550 board
  229. config MTD_DB1550_BOOT
  230. bool "DB1550 boot flash device"
  231. depends on MTD_DB1550
  232. help
  233. Use the first of the two 64MiB flash banks on Db1550 board.
  234. You can say 'Y' to both this and 'MTD_DB1550_USER' below, to use
  235. both banks.
  236. config MTD_DB1550_USER
  237. bool "DB1550 user flash device"
  238. depends on MTD_DB1550
  239. default y if MTD_DB1550_BOOT = n
  240. help
  241. Use the second of the two 64MiB flash banks on Db1550 board.
  242. You can say 'Y' to both this and 'MTD_DB1550_BOOT' above, to use
  243. both banks.
  244. config MTD_DILNETPC
  245. tristate "CFI Flash device mapped on DIL/Net PC"
  246. depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
  247. help
  248. MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
  249. For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
  250. and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
  251. config MTD_DILNETPC_BOOTSIZE
  252. hex "Size of DIL/Net PC flash boot partition"
  253. depends on MTD_DILNETPC
  254. default "0x80000"
  255. help
  256. The amount of space taken up by the kernel or Etherboot
  257. on the DIL/Net PC flash chips.
  258. config MTD_L440GX
  259. tristate "BIOS flash chip on Intel L440GX boards"
  260. depends on X86 && MTD_JEDECPROBE
  261. help
  262. Support for treating the BIOS flash chip on Intel L440GX motherboards
  263. as an MTD device - with this you can reprogram your BIOS.
  264. BE VERY CAREFUL.
  265. config MTD_SBC8240
  266. tristate "Flash device on SBC8240"
  267. depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260
  268. help
  269. Flash access on the SBC8240 board from Wind River. See
  270. <http://www.windriver.com/products/sbc8240/>
  271. config MTD_TQM8XXL
  272. tristate "CFI Flash device mapped on TQM8XXL"
  273. depends on MTD_CFI && PPC32 && 8xx && TQM8xxL
  274. help
  275. The TQM8xxL PowerPC board has up to two banks of CFI-compliant
  276. chips, currently uses AMD one. This 'mapping' driver supports
  277. that arrangement, allowing the CFI probe and command set driver
  278. code to communicate with the chips on the TQM8xxL board. More at
  279. <http://www.denx.de/embedded-ppc-en.html>.
  280. config MTD_RPXLITE
  281. tristate "CFI Flash device mapped on RPX Lite or CLLF"
  282. depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)
  283. help
  284. The RPXLite PowerPC board has CFI-compliant chips mapped in
  285. a strange sparse mapping. This 'mapping' driver supports that
  286. arrangement, allowing the CFI probe and command set driver code
  287. to communicate with the chips on the RPXLite board. More at
  288. <http://www.embeddedplanet.com/>.
  289. config MTD_MBX860
  290. tristate "System flash on MBX860 board"
  291. depends on MTD_CFI && PPC32 && 8xx && MBX
  292. help
  293. This enables access routines for the flash chips on the Motorola
  294. MBX860 board. If you have one of these boards and would like
  295. to use the flash chips on it, say 'Y'.
  296. config MTD_DBOX2
  297. tristate "CFI Flash device mapped on D-Box2"
  298. depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
  299. help
  300. This enables access routines for the flash chips on the Nokia/Sagem
  301. D-Box 2 board. If you have one of these boards and would like to use
  302. the flash chips on it, say 'Y'.
  303. config MTD_CFI_FLAGADM
  304. tristate "CFI Flash device mapping on FlagaDM"
  305. depends on PPC32 && 8xx && MTD_CFI
  306. help
  307. Mapping for the Flaga digital module. If you don't have one, ignore
  308. this setting.
  309. config MTD_BEECH
  310. tristate "CFI Flash device mapped on IBM 405LP Beech"
  311. depends on MTD_CFI && PPC32 && 40x && BEECH
  312. help
  313. This enables access routines for the flash chips on the IBM
  314. 405LP Beech board. If you have one of these boards and would like
  315. to use the flash chips on it, say 'Y'.
  316. config MTD_ARCTIC
  317. tristate "CFI Flash device mapped on IBM 405LP Arctic"
  318. depends on MTD_CFI && PPC32 && 40x && ARCTIC2
  319. help
  320. This enables access routines for the flash chips on the IBM 405LP
  321. Arctic board. If you have one of these boards and would like to
  322. use the flash chips on it, say 'Y'.
  323. config MTD_WALNUT
  324. tristate "Flash device mapped on IBM 405GP Walnut"
  325. depends on MTD_JEDECPROBE && PPC32 && 40x && WALNUT
  326. help
  327. This enables access routines for the flash chips on the IBM 405GP
  328. Walnut board. If you have one of these boards and would like to
  329. use the flash chips on it, say 'Y'.
  330. config MTD_EBONY
  331. tristate "Flash devices mapped on IBM 440GP Ebony"
  332. depends on MTD_JEDECPROBE && PPC32 && 44x && EBONY
  333. help
  334. This enables access routines for the flash chips on the IBM 440GP
  335. Ebony board. If you have one of these boards and would like to
  336. use the flash chips on it, say 'Y'.
  337. config MTD_OCOTEA
  338. tristate "Flash devices mapped on IBM 440GX Ocotea"
  339. depends on MTD_CFI && PPC32 && 44x && OCOTEA
  340. help
  341. This enables access routines for the flash chips on the IBM 440GX
  342. Ocotea board. If you have one of these boards and would like to
  343. use the flash chips on it, say 'Y'.
  344. config MTD_REDWOOD
  345. tristate "CFI Flash devices mapped on IBM Redwood"
  346. depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
  347. help
  348. This enables access routines for the flash chips on the IBM
  349. Redwood board. If you have one of these boards and would like to
  350. use the flash chips on it, say 'Y'.
  351. config MTD_CSTM_MIPS_IXX
  352. tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
  353. depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
  354. help
  355. This provides a mapping driver for the Integrated Technology
  356. Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
  357. Reference Board. It provides the necessary addressing, length,
  358. buswidth, vpp code and addition setup of the flash device for
  359. these boards. In addition, this mapping driver can be used for
  360. other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
  361. LEN/BUSWIDTH parameters. This mapping will provide one mtd device
  362. using one partition. The start address can be offset from the
  363. beginning of flash and the len can be less than the total flash
  364. device size to allow a window into the flash. Both CFI and JEDEC
  365. probes are called.
  366. config MTD_CSTM_MIPS_IXX_START
  367. hex "Physical start address of flash mapping"
  368. depends on MTD_CSTM_MIPS_IXX
  369. default "0x8000000"
  370. help
  371. This is the physical memory location that the MTD driver will
  372. use for the flash chips on your particular target board.
  373. Refer to the memory map which should hopefully be in the
  374. documentation for your board.
  375. config MTD_CSTM_MIPS_IXX_LEN
  376. hex "Physical length of flash mapping"
  377. depends on MTD_CSTM_MIPS_IXX
  378. default "0x4000000"
  379. help
  380. This is the total length that the MTD driver will use for the
  381. flash chips on your particular board. Refer to the memory
  382. map which should hopefully be in the documentation for your
  383. board.
  384. config MTD_CSTM_MIPS_IXX_BUSWIDTH
  385. int "Bus width in octets"
  386. depends on MTD_CSTM_MIPS_IXX
  387. default "2"
  388. help
  389. This is the total bus width of the mapping of the flash chips
  390. on your particular board.
  391. config MTD_OCELOT
  392. tristate "Momenco Ocelot boot flash device"
  393. depends on MIPS && MOMENCO_OCELOT
  394. help
  395. This enables access routines for the boot flash device and for the
  396. NVRAM on the Momenco Ocelot board. If you have one of these boards
  397. and would like access to either of these, say 'Y'.
  398. config MTD_SOLUTIONENGINE
  399. tristate "CFI Flash device mapped on Hitachi SolutionEngine"
  400. depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
  401. help
  402. This enables access to the flash chips on the Hitachi SolutionEngine and
  403. similar boards. Say 'Y' if you are building a kernel for such a board.
  404. config MTD_ARM_INTEGRATOR
  405. tristate "CFI Flash device mapped on ARM Integrator/P720T"
  406. depends on ARM && MTD_CFI
  407. config MTD_CDB89712
  408. tristate "Cirrus CDB89712 evaluation board mappings"
  409. depends on ARM && MTD_CFI && ARCH_CDB89712
  410. help
  411. This enables access to the flash or ROM chips on the CDB89712 board.
  412. If you have such a board, say 'Y'.
  413. config MTD_SA1100
  414. tristate "CFI Flash device mapped on StrongARM SA11x0"
  415. depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
  416. help
  417. This enables access to the flash chips on most platforms based on
  418. the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
  419. If you have such a board, say 'Y'.
  420. config MTD_IPAQ
  421. tristate "CFI Flash device mapped on Compaq/HP iPAQ"
  422. depends on ARM && IPAQ_HANDHELD && MTD_CFI
  423. help
  424. This provides a driver for the on-board flash of the iPAQ.
  425. config MTD_DC21285
  426. tristate "CFI Flash device mapped on DC21285 Footbridge"
  427. depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
  428. help
  429. This provides a driver for the flash accessed using Intel's
  430. 21285 bridge used with Intel's StrongARM processors. More info at
  431. <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
  432. config MTD_IQ80310
  433. tristate "CFI Flash device mapped on the XScale IQ80310 board"
  434. depends on ARM && MTD_CFI && ARCH_IQ80310
  435. help
  436. This enables access routines for the flash chips on the Intel XScale
  437. IQ80310 evaluation board. If you have one of these boards and would
  438. like to use the flash chips on it, say 'Y'.
  439. config MTD_IXP4XX
  440. tristate "CFI Flash device mapped on Intel IXP4xx based systems"
  441. depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
  442. help
  443. This enables MTD access to flash devices on platforms based
  444. on Intel's IXP4xx family of network processors such as the
  445. IXDP425 and Coyote. If you have an IXP4xx based board and
  446. would like to use the flash chips on it, say 'Y'.
  447. config MTD_IXP2000
  448. tristate "CFI Flash device mapped on Intel IXP2000 based systems"
  449. depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
  450. help
  451. This enables MTD access to flash devices on platforms based
  452. on Intel's IXP2000 family of network processors such as the
  453. IXDP425 and Coyote. If you have an IXP2000 based board and
  454. would like to use the flash chips on it, say 'Y'.
  455. config MTD_EPXA10DB
  456. tristate "CFI Flash device mapped on Epxa10db"
  457. depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
  458. help
  459. This enables support for the flash devices on the Altera
  460. Excalibur XA10 Development Board. If you are building a kernel
  461. for on of these boards then you should say 'Y' otherwise say 'N'.
  462. config MTD_FORTUNET
  463. tristate "CFI Flash device mapped on the FortuNet board"
  464. depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
  465. help
  466. This enables access to the Flash on the FortuNet board. If you
  467. have such a board, say 'Y'.
  468. config MTD_AUTCPU12
  469. tristate "NV-RAM mapping AUTCPU12 board"
  470. depends on ARM && ARCH_AUTCPU12
  471. help
  472. This enables access to the NV-RAM on autronix autcpu12 board.
  473. If you have such a board, say 'Y'.
  474. config MTD_EDB7312
  475. tristate "CFI Flash device mapped on EDB7312"
  476. depends on ARM && MTD_CFI
  477. help
  478. This enables access to the CFI Flash on the Cogent EDB7312 board.
  479. If you have such a board, say 'Y' here.
  480. config MTD_IMPA7
  481. tristate "JEDEC Flash device mapped on impA7"
  482. depends on ARM && MTD_JEDECPROBE
  483. help
  484. This enables access to the NOR Flash on the impA7 board of
  485. implementa GmbH. If you have such a board, say 'Y' here.
  486. config MTD_CEIVA
  487. tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
  488. depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA
  489. help
  490. This enables access to the flash chips on the Ceiva/Polaroid
  491. PhotoMax Digital Picture Frame.
  492. If you have such a device, say 'Y'.
  493. config MTD_NOR_TOTO
  494. tristate "NOR Flash device on TOTO board"
  495. depends on ARM && ARCH_OMAP && OMAP_TOTO
  496. help
  497. This enables access to the NOR flash on the Texas Instruments
  498. TOTO board.
  499. config MTD_H720X
  500. tristate "Hynix evaluation board mappings"
  501. depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
  502. help
  503. This enables access to the flash chips on the Hynix evaluation boards.
  504. If you have such a board, say 'Y'.
  505. config MTD_MPC1211
  506. tristate "CFI Flash device mapped on Interface MPC-1211"
  507. depends on SUPERH && SH_MPC1211 && MTD_CFI
  508. help
  509. This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
  510. If you have such a board, say 'Y'.
  511. # This needs CFI or JEDEC, depending on the cards found.
  512. config MTD_PCI
  513. tristate "PCI MTD driver"
  514. depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
  515. help
  516. Mapping for accessing flash devices on add-in cards like the Intel XScale
  517. IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
  518. (please see the manual for the link settings).
  519. If you are not sure, say N.
  520. config MTD_PCMCIA
  521. tristate "PCMCIA MTD driver"
  522. depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
  523. help
  524. Map driver for accessing PCMCIA linear flash memory cards. These
  525. cards are usually around 4-16MiB in size. This does not include
  526. Compact Flash cards which are treated as IDE devices.
  527. config MTD_PCMCIA_ANONYMOUS
  528. bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
  529. depends on MTD_PCMCIA
  530. default N
  531. help
  532. If this option is enabled, PCMCIA cards which do not report
  533. anything about themselves are assumed to be MTD cards.
  534. If unsure, say N.
  535. config MTD_UCLINUX
  536. tristate "Generic uClinux RAM/ROM filesystem support"
  537. depends on MTD_PARTITIONS && !MMU
  538. help
  539. Map driver to support image based filesystems for uClinux.
  540. config MTD_WRSBC8260
  541. tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
  542. depends on (SBC82xx || SBC8560)
  543. select MTD_PARTITIONS
  544. select MTD_MAP_BANK_WIDTH_4
  545. select MTD_MAP_BANK_WIDTH_1
  546. select MTD_CFI_I1
  547. select MTD_CFI_I4
  548. help
  549. Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
  550. all three flash regions on CS0, CS1 and CS6 if they are configured
  551. correctly by the boot loader.
  552. config MTD_DMV182
  553. tristate "Map driver for Dy-4 SVME/DMV-182 board."
  554. depends on DMV182
  555. select MTD_PARTITIONS
  556. select MTD_MAP_BANK_WIDTH_32
  557. select MTD_CFI_I8
  558. select MTD_CFI_AMDSTD
  559. help
  560. Map driver for Dy-4 SVME/DMV-182 board.
  561. config MTD_BAST
  562. tristate "Map driver for Simtec BAST (EB2410ITX)"
  563. depends on ARCH_BAST
  564. select MTD_PARTITIONS
  565. select MTD_MAP_BANK_WIDTH_16
  566. select MTD_JEDECPROBE
  567. help
  568. Map driver for NOR flash on the Simtec BAST (EB2410ITX).
  569. Note, this driver *cannot* over-ride the WP link on the
  570. board, or currently detect the state of the link.
  571. config MTD_BAST_MAXSIZE
  572. int "Maximum size for BAST flash area (MiB)"
  573. depends on MTD_BAST
  574. default "4"
  575. config MTD_SHARP_SL
  576. bool "ROM maped on Sharp SL Series"
  577. depends on MTD && ARCH_PXA
  578. help
  579. This enables access to the flash chip on the Sharp SL Series of PDAs.
  580. endmenu