Kconfig 20 KB

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