Kconfig 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609
  1. # drivers/mtd/maps/Kconfig
  2. # $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner 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 || MTD_JEDECPROBE || MTD_ROM
  14. help
  15. This provides a 'mapping' driver which allows the NOR Flash and
  16. ROM driver code to communicate with chips which are mapped
  17. physically into the CPU's memory. You will need to configure
  18. the physical address and size of the flash chips on your
  19. 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 "0"
  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_PHYSMAP_OF
  57. tristate "Flash device in physical memory map based on OF descirption"
  58. depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
  59. help
  60. This provides a 'mapping' driver which allows the NOR Flash and
  61. ROM driver code to communicate with chips which are mapped
  62. physically into the CPU's memory. The mapping description here is
  63. taken from OF device tree.
  64. config MTD_SUN_UFLASH
  65. tristate "Sun Microsystems userflash support"
  66. depends on SPARC && MTD_CFI
  67. help
  68. This provides a 'mapping' driver which supports the way in
  69. which user-programmable flash chips are connected on various
  70. Sun Microsystems boardsets. This driver will require CFI support
  71. in the kernel, so if you did not enable CFI previously, do that now.
  72. config MTD_PNC2000
  73. tristate "CFI Flash device mapped on Photron PNC-2000"
  74. depends on X86 && MTD_CFI && MTD_PARTITIONS
  75. help
  76. PNC-2000 is the name of Network Camera product from PHOTRON
  77. Ltd. in Japan. It uses CFI-compliant flash.
  78. config MTD_SC520CDP
  79. tristate "CFI Flash device mapped on AMD SC520 CDP"
  80. depends on X86 && MTD_CFI && MTD_CONCAT
  81. help
  82. The SC520 CDP board has two banks of CFI-compliant chips and one
  83. Dual-in-line JEDEC chip. This 'mapping' driver supports that
  84. arrangement, implementing three MTD devices.
  85. config MTD_NETSC520
  86. tristate "CFI Flash device mapped on AMD NetSc520"
  87. depends on X86 && MTD_CFI && MTD_PARTITIONS
  88. help
  89. This enables access routines for the flash chips on the AMD NetSc520
  90. demonstration board. If you have one of these boards and would like
  91. to use the flash chips on it, say 'Y'.
  92. config MTD_TS5500
  93. tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
  94. depends on X86
  95. select MTD_PARTITIONS
  96. select MTD_JEDECPROBE
  97. select MTD_CFI_AMDSTD
  98. help
  99. This provides a driver for the on-board flash of the Technologic
  100. System's TS-5500 board. The 2MB flash is split into 3 partitions
  101. which are accessed as separate MTD devices.
  102. mtd0 and mtd2 are the two BIOS drives, which use the resident
  103. flash disk (RFD) flash translation layer.
  104. mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
  105. Note that jumper 3 ("Write Enable Drive A") must be set
  106. otherwise detection won't succeed.
  107. config MTD_SBC_GXX
  108. tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
  109. depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
  110. help
  111. This provides a driver for the on-board flash of Arcom Control
  112. Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
  113. By default the flash is split into 3 partitions which are accessed
  114. as separate MTD devices. This board utilizes Intel StrataFlash.
  115. More info at
  116. <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
  117. config MTD_LUBBOCK
  118. tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
  119. depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
  120. help
  121. This provides a driver for the on-board flash of the Intel
  122. 'Lubbock' XScale evaluation board.
  123. config MTD_MAINSTONE
  124. tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
  125. depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
  126. select MTD_PARTITIONS
  127. help
  128. This provides a driver for the on-board flash of the Intel
  129. 'Mainstone PXA27x evaluation board.
  130. config MTD_OCTAGON
  131. tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
  132. depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
  133. help
  134. This provides a 'mapping' driver which supports the way in which
  135. the flash chips are connected in the Octagon-5066 Single Board
  136. Computer. More information on the board is available at
  137. <http://www.octagonsystems.com/CPUpages/5066.html>.
  138. config MTD_VMAX
  139. tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
  140. depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
  141. help
  142. This provides a 'mapping' driver which supports the way in which
  143. the flash chips are connected in the Tempustech VMAX SBC301 Single
  144. Board Computer. More information on the board is available at
  145. <http://www.tempustech.com/>.
  146. config MTD_SCx200_DOCFLASH
  147. tristate "Flash device mapped with DOCCS on NatSemi SCx200"
  148. depends on SCx200 && MTD_CFI && MTD_PARTITIONS
  149. help
  150. Enable support for a flash chip mapped using the DOCCS signal on a
  151. National Semiconductor SCx200 processor.
  152. If you don't know what to do here, say N.
  153. If compiled as a module, it will be called scx200_docflash.
  154. config MTD_AMD76XROM
  155. tristate "BIOS flash chip on AMD76x southbridge"
  156. depends on X86 && MTD_JEDECPROBE
  157. help
  158. Support for treating the BIOS flash chip on AMD76x motherboards
  159. as an MTD device - with this you can reprogram your BIOS.
  160. BE VERY CAREFUL.
  161. config MTD_ICHXROM
  162. tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
  163. depends on X86 && MTD_JEDECPROBE
  164. help
  165. Support for treating the BIOS flash chip on ICHX motherboards
  166. as an MTD device - with this you can reprogram your BIOS.
  167. BE VERY CAREFUL.
  168. config MTD_ESB2ROM
  169. tristate "BIOS flash chip on Intel ESB Controller Hub 2"
  170. depends on X86 && MTD_JEDECPROBE && PCI
  171. help
  172. Support for treating the BIOS flash chip on ESB2 motherboards
  173. as an MTD device - with this you can reprogram your BIOS.
  174. BE VERY CAREFUL.
  175. config MTD_CK804XROM
  176. tristate "BIOS flash chip on Nvidia CK804"
  177. depends on X86 && MTD_JEDECPROBE
  178. help
  179. Support for treating the BIOS flash chip on nvidia motherboards
  180. as an MTD device - with this you can reprogram your BIOS.
  181. BE VERY CAREFUL.
  182. config MTD_SCB2_FLASH
  183. tristate "BIOS flash chip on Intel SCB2 boards"
  184. depends on X86 && MTD_JEDECPROBE
  185. help
  186. Support for treating the BIOS flash chip on Intel SCB2 boards
  187. as an MTD device - with this you can reprogram your BIOS.
  188. BE VERY CAREFUL.
  189. config MTD_TSUNAMI
  190. tristate "Flash chips on Tsunami TIG bus"
  191. depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
  192. help
  193. Support for the flash chip on Tsunami TIG bus.
  194. config MTD_LASAT
  195. tristate "LASAT flash device"
  196. depends on LASAT && MTD_CFI
  197. help
  198. Support for the flash chips on the Lasat 100 and 200 boards.
  199. config MTD_NETtel
  200. tristate "CFI flash device on SnapGear/SecureEdge"
  201. depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
  202. help
  203. Support for flash chips on NETtel/SecureEdge/SnapGear boards.
  204. config MTD_ALCHEMY
  205. tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
  206. depends on SOC_AU1X00
  207. help
  208. Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
  209. config MTD_MTX1
  210. tristate "4G Systems MTX-1 Flash device"
  211. depends on MIPS && MIPS_MTX1
  212. help
  213. Flash memory access on 4G Systems MTX-1 Board. If you have one of
  214. these boards and would like to use the flash chips on it, say 'Y'.
  215. config MTD_DILNETPC
  216. tristate "CFI Flash device mapped on DIL/Net PC"
  217. depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
  218. help
  219. MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
  220. For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
  221. and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
  222. config MTD_DILNETPC_BOOTSIZE
  223. hex "Size of DIL/Net PC flash boot partition"
  224. depends on MTD_DILNETPC
  225. default "0x80000"
  226. help
  227. The amount of space taken up by the kernel or Etherboot
  228. on the DIL/Net PC flash chips.
  229. config MTD_L440GX
  230. tristate "BIOS flash chip on Intel L440GX boards"
  231. depends on X86 && MTD_JEDECPROBE
  232. help
  233. Support for treating the BIOS flash chip on Intel L440GX motherboards
  234. as an MTD device - with this you can reprogram your BIOS.
  235. BE VERY CAREFUL.
  236. config MTD_SBC8240
  237. tristate "Flash device on SBC8240"
  238. depends on MTD_JEDECPROBE && 8260
  239. help
  240. Flash access on the SBC8240 board from Wind River. See
  241. <http://www.windriver.com/products/sbc8240/>
  242. config MTD_TQM8XXL
  243. tristate "CFI Flash device mapped on TQM8XXL"
  244. depends on MTD_CFI && TQM8xxL
  245. help
  246. The TQM8xxL PowerPC board has up to two banks of CFI-compliant
  247. chips, currently uses AMD one. This 'mapping' driver supports
  248. that arrangement, allowing the CFI probe and command set driver
  249. code to communicate with the chips on the TQM8xxL board. More at
  250. <http://www.denx.de/embedded-ppc-en.html>.
  251. config MTD_RPXLITE
  252. tristate "CFI Flash device mapped on RPX Lite or CLLF"
  253. depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
  254. help
  255. The RPXLite PowerPC board has CFI-compliant chips mapped in
  256. a strange sparse mapping. This 'mapping' driver supports that
  257. arrangement, allowing the CFI probe and command set driver code
  258. to communicate with the chips on the RPXLite board. More at
  259. <http://www.embeddedplanet.com/>.
  260. config MTD_MBX860
  261. tristate "System flash on MBX860 board"
  262. depends on MTD_CFI && MBX
  263. help
  264. This enables access routines for the flash chips on the Motorola
  265. MBX860 board. If you have one of these boards and would like
  266. to use the flash chips on it, say 'Y'.
  267. config MTD_DBOX2
  268. tristate "CFI Flash device mapped on D-Box2"
  269. depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
  270. help
  271. This enables access routines for the flash chips on the Nokia/Sagem
  272. D-Box 2 board. If you have one of these boards and would like to use
  273. the flash chips on it, say 'Y'.
  274. config MTD_CFI_FLAGADM
  275. tristate "CFI Flash device mapping on FlagaDM"
  276. depends on 8xx && MTD_CFI
  277. help
  278. Mapping for the Flaga digital module. If you don't have one, ignore
  279. this setting.
  280. config MTD_BEECH
  281. tristate "CFI Flash device mapped on IBM 405LP Beech"
  282. depends on MTD_CFI && BEECH
  283. help
  284. This enables access routines for the flash chips on the IBM
  285. 405LP Beech board. If you have one of these boards and would like
  286. to use the flash chips on it, say 'Y'.
  287. config MTD_ARCTIC
  288. tristate "CFI Flash device mapped on IBM 405LP Arctic"
  289. depends on MTD_CFI && ARCTIC2
  290. help
  291. This enables access routines for the flash chips on the IBM 405LP
  292. Arctic board. If you have one of these boards and would like to
  293. use the flash chips on it, say 'Y'.
  294. config MTD_WALNUT
  295. tristate "Flash device mapped on IBM 405GP Walnut"
  296. depends on MTD_JEDECPROBE && WALNUT
  297. help
  298. This enables access routines for the flash chips on the IBM 405GP
  299. Walnut board. If you have one of these boards and would like to
  300. use the flash chips on it, say 'Y'.
  301. config MTD_EBONY
  302. tristate "Flash devices mapped on IBM 440GP Ebony"
  303. depends on MTD_JEDECPROBE && EBONY
  304. help
  305. This enables access routines for the flash chips on the IBM 440GP
  306. Ebony board. If you have one of these boards and would like to
  307. use the flash chips on it, say 'Y'.
  308. config MTD_OCOTEA
  309. tristate "Flash devices mapped on IBM 440GX Ocotea"
  310. depends on MTD_CFI && OCOTEA
  311. help
  312. This enables access routines for the flash chips on the IBM 440GX
  313. Ocotea board. If you have one of these boards and would like to
  314. use the flash chips on it, say 'Y'.
  315. config MTD_REDWOOD
  316. tristate "CFI Flash devices mapped on IBM Redwood"
  317. depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
  318. help
  319. This enables access routines for the flash chips on the IBM
  320. Redwood board. If you have one of these boards and would like to
  321. use the flash chips on it, say 'Y'.
  322. config MTD_TQM834x
  323. tristate "Flash device mapped on TQ Components TQM834x Boards"
  324. depends on MTD_CFI && TQM834x
  325. help
  326. This enables access routines for the flash chips on the
  327. TQ Components TQM834x boards. If you have one of these boards
  328. and would like to use the flash chips on it, say 'Y'.
  329. config MTD_OCELOT
  330. tristate "Momenco Ocelot boot flash device"
  331. depends on MIPS && MOMENCO_OCELOT
  332. help
  333. This enables access routines for the boot flash device and for the
  334. NVRAM on the Momenco Ocelot board. If you have one of these boards
  335. and would like access to either of these, say 'Y'.
  336. config MTD_SOLUTIONENGINE
  337. tristate "CFI Flash device mapped on Hitachi SolutionEngine"
  338. depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
  339. help
  340. This enables access to the flash chips on the Hitachi SolutionEngine and
  341. similar boards. Say 'Y' if you are building a kernel for such a board.
  342. config MTD_ARM_INTEGRATOR
  343. tristate "CFI Flash device mapped on ARM Integrator/P720T"
  344. depends on ARM && MTD_CFI
  345. config MTD_CDB89712
  346. tristate "Cirrus CDB89712 evaluation board mappings"
  347. depends on MTD_CFI && ARCH_CDB89712
  348. help
  349. This enables access to the flash or ROM chips on the CDB89712 board.
  350. If you have such a board, say 'Y'.
  351. config MTD_SA1100
  352. tristate "CFI Flash device mapped on StrongARM SA11x0"
  353. depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
  354. help
  355. This enables access to the flash chips on most platforms based on
  356. the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
  357. If you have such a board, say 'Y'.
  358. config MTD_IPAQ
  359. tristate "CFI Flash device mapped on Compaq/HP iPAQ"
  360. depends on IPAQ_HANDHELD && MTD_CFI
  361. help
  362. This provides a driver for the on-board flash of the iPAQ.
  363. config MTD_DC21285
  364. tristate "CFI Flash device mapped on DC21285 Footbridge"
  365. depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
  366. help
  367. This provides a driver for the flash accessed using Intel's
  368. 21285 bridge used with Intel's StrongARM processors. More info at
  369. <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
  370. config MTD_IXP4XX
  371. tristate "CFI Flash device mapped on Intel IXP4xx based systems"
  372. depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
  373. help
  374. This enables MTD access to flash devices on platforms based
  375. on Intel's IXP4xx family of network processors such as the
  376. IXDP425 and Coyote. If you have an IXP4xx based board and
  377. would like to use the flash chips on it, say 'Y'.
  378. config MTD_IXP2000
  379. tristate "CFI Flash device mapped on Intel IXP2000 based systems"
  380. depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
  381. help
  382. This enables MTD access to flash devices on platforms based
  383. on Intel's IXP2000 family of network processors such as the
  384. IXDP425 and Coyote. If you have an IXP2000 based board and
  385. would like to use the flash chips on it, say 'Y'.
  386. config MTD_FORTUNET
  387. tristate "CFI Flash device mapped on the FortuNet board"
  388. depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
  389. help
  390. This enables access to the Flash on the FortuNet board. If you
  391. have such a board, say 'Y'.
  392. config MTD_AUTCPU12
  393. tristate "NV-RAM mapping AUTCPU12 board"
  394. depends on ARCH_AUTCPU12
  395. help
  396. This enables access to the NV-RAM on autronix autcpu12 board.
  397. If you have such a board, say 'Y'.
  398. config MTD_EDB7312
  399. tristate "CFI Flash device mapped on EDB7312"
  400. depends on ARCH_EDB7312 && MTD_CFI
  401. help
  402. This enables access to the CFI Flash on the Cogent EDB7312 board.
  403. If you have such a board, say 'Y' here.
  404. config MTD_IMPA7
  405. tristate "JEDEC Flash device mapped on impA7"
  406. depends on ARM && MTD_JEDECPROBE
  407. help
  408. This enables access to the NOR Flash on the impA7 board of
  409. implementa GmbH. If you have such a board, say 'Y' here.
  410. config MTD_CEIVA
  411. tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
  412. depends on MTD_JEDECPROBE && ARCH_CEIVA
  413. help
  414. This enables access to the flash chips on the Ceiva/Polaroid
  415. PhotoMax Digital Picture Frame.
  416. If you have such a device, say 'Y'.
  417. config MTD_NOR_TOTO
  418. tristate "NOR Flash device on TOTO board"
  419. depends on ARCH_OMAP && OMAP_TOTO
  420. help
  421. This enables access to the NOR flash on the Texas Instruments
  422. TOTO board.
  423. config MTD_H720X
  424. tristate "Hynix evaluation board mappings"
  425. depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
  426. help
  427. This enables access to the flash chips on the Hynix evaluation boards.
  428. If you have such a board, say 'Y'.
  429. config MTD_MPC1211
  430. tristate "CFI Flash device mapped on Interface MPC-1211"
  431. depends on SH_MPC1211 && MTD_CFI
  432. help
  433. This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
  434. If you have such a board, say 'Y'.
  435. config MTD_OMAP_NOR
  436. tristate "TI OMAP board mappings"
  437. depends on MTD_CFI && ARCH_OMAP
  438. help
  439. This enables access to the NOR flash chips on TI OMAP-based
  440. boards defining flash platform devices and flash platform data.
  441. These boards include the Innovator, H2, H3, OSK, Perseus2, and
  442. more. If you have such a board, say 'Y'.
  443. # This needs CFI or JEDEC, depending on the cards found.
  444. config MTD_PCI
  445. tristate "PCI MTD driver"
  446. depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
  447. help
  448. Mapping for accessing flash devices on add-in cards like the Intel XScale
  449. IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
  450. (please see the manual for the link settings).
  451. If you are not sure, say N.
  452. config MTD_PCMCIA
  453. tristate "PCMCIA MTD driver"
  454. depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
  455. help
  456. Map driver for accessing PCMCIA linear flash memory cards. These
  457. cards are usually around 4-16MiB in size. This does not include
  458. Compact Flash cards which are treated as IDE devices.
  459. config MTD_PCMCIA_ANONYMOUS
  460. bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
  461. depends on MTD_PCMCIA
  462. help
  463. If this option is enabled, PCMCIA cards which do not report
  464. anything about themselves are assumed to be MTD cards.
  465. If unsure, say N.
  466. config MTD_UCLINUX
  467. tristate "Generic uClinux RAM/ROM filesystem support"
  468. depends on MTD_PARTITIONS && !MMU
  469. help
  470. Map driver to support image based filesystems for uClinux.
  471. config MTD_WRSBC8260
  472. tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
  473. depends on (SBC82xx || SBC8560)
  474. select MTD_PARTITIONS
  475. select MTD_MAP_BANK_WIDTH_4
  476. select MTD_MAP_BANK_WIDTH_1
  477. select MTD_CFI_I1
  478. select MTD_CFI_I4
  479. help
  480. Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
  481. all three flash regions on CS0, CS1 and CS6 if they are configured
  482. correctly by the boot loader.
  483. config MTD_DMV182
  484. tristate "Map driver for Dy-4 SVME/DMV-182 board."
  485. depends on DMV182
  486. select MTD_PARTITIONS
  487. select MTD_MAP_BANK_WIDTH_32
  488. select MTD_CFI_I8
  489. select MTD_CFI_AMDSTD
  490. help
  491. Map driver for Dy-4 SVME/DMV-182 board.
  492. config MTD_BAST
  493. tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
  494. depends on ARCH_BAST || MACH_VR1000
  495. select MTD_PARTITIONS
  496. select MTD_MAP_BANK_WIDTH_16
  497. select MTD_JEDECPROBE
  498. help
  499. Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
  500. Thorcom VR1000
  501. Note, this driver *cannot* over-ride the WP link on the
  502. board, or currently detect the state of the link.
  503. config MTD_BAST_MAXSIZE
  504. int "Maximum size for BAST flash area (MiB)"
  505. depends on MTD_BAST
  506. default "4"
  507. config MTD_SHARP_SL
  508. bool "ROM mapped on Sharp SL Series"
  509. depends on MTD && ARCH_PXA
  510. help
  511. This enables access to the flash chip on the Sharp SL Series of PDAs.
  512. config MTD_PLATRAM
  513. tristate "Map driver for platform device RAM (mtd-ram)"
  514. depends on MTD
  515. select MTD_RAM
  516. help
  517. Map driver for RAM areas described via the platform device
  518. system.
  519. This selection automatically selects the map_ram driver.
  520. endmenu