Kconfig 22 KB

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