Kconfig 19 KB

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