Kconfig 21 KB

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