Kconfig 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552
  1. menu "Mapping drivers for chip access"
  2. depends on MTD!=n
  3. config MTD_COMPLEX_MAPPINGS
  4. bool "Support non-linear mappings of flash chips"
  5. help
  6. This causes the chip drivers to allow for complicated
  7. paged mappings of flash chips.
  8. config MTD_PHYSMAP
  9. tristate "Flash device in physical memory map"
  10. depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR
  11. help
  12. This provides a 'mapping' driver which allows the NOR Flash and
  13. ROM driver code to communicate with chips which are mapped
  14. physically into the CPU's memory. You will need to configure
  15. the physical address and size of the flash chips on your
  16. particular board as well as the bus width, either statically
  17. with config options or at run-time.
  18. To compile this driver as a module, choose M here: the
  19. module will be called physmap.
  20. config MTD_PHYSMAP_COMPAT
  21. bool "Physmap compat support"
  22. depends on MTD_PHYSMAP
  23. default n
  24. help
  25. Setup a simple mapping via the Kconfig options. Normally the
  26. physmap configuration options are done via your board's
  27. resource file.
  28. If unsure, say N here.
  29. config MTD_PHYSMAP_START
  30. hex "Physical start address of flash mapping"
  31. depends on MTD_PHYSMAP_COMPAT
  32. default "0x8000000"
  33. help
  34. This is the physical memory location at which the flash chips
  35. are mapped on your particular target board. Refer to the
  36. memory map which should hopefully be in the documentation for
  37. your board.
  38. Ignore this option if you use run-time physmap configuration
  39. (i.e., run-time calling physmap_configure()).
  40. config MTD_PHYSMAP_LEN
  41. hex "Physical length of flash mapping"
  42. depends on MTD_PHYSMAP_COMPAT
  43. default "0"
  44. help
  45. This is the total length of the mapping of the flash chips on
  46. your particular board. If there is space, or aliases, in the
  47. physical memory map between the chips, this could be larger
  48. than the total amount of flash present. Refer to the memory
  49. map which should hopefully be in the documentation for your
  50. board.
  51. Ignore this option if you use run-time physmap configuration
  52. (i.e., run-time calling physmap_configure()).
  53. config MTD_PHYSMAP_BANKWIDTH
  54. int "Bank width in octets"
  55. depends on MTD_PHYSMAP_COMPAT
  56. default "2"
  57. help
  58. This is the total width of the data bus of the flash devices
  59. in octets. For example, if you have a data bus width of 32
  60. bits, you would set the bus width octet value to 4. This is
  61. used internally by the CFI drivers.
  62. Ignore this option if you use run-time physmap configuration
  63. (i.e., run-time calling physmap_configure()).
  64. config MTD_PHYSMAP_OF
  65. tristate "Flash device in physical memory map based on OF description"
  66. depends on (MICROBLAZE || PPC_OF) && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
  67. help
  68. This provides a 'mapping' driver which allows the NOR Flash and
  69. ROM driver code to communicate with chips which are mapped
  70. physically into the CPU's memory. The mapping description here is
  71. taken from OF device tree.
  72. config MTD_PMC_MSP_EVM
  73. tristate "CFI Flash device mapped on PMC-Sierra MSP"
  74. depends on PMC_MSP && MTD_CFI
  75. select MTD_PARTITIONS
  76. help
  77. This provides a 'mapping' driver which supports the way
  78. in which user-programmable flash chips are connected on the
  79. PMC-Sierra MSP eval/demo boards.
  80. choice
  81. prompt "Maximum mappable memory available for flash IO"
  82. depends on MTD_PMC_MSP_EVM
  83. default MSP_FLASH_MAP_LIMIT_32M
  84. config MSP_FLASH_MAP_LIMIT_32M
  85. bool "32M"
  86. endchoice
  87. config MSP_FLASH_MAP_LIMIT
  88. hex
  89. default "0x02000000"
  90. depends on MSP_FLASH_MAP_LIMIT_32M
  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 && BROKEN
  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_TQM8XXL
  240. tristate "CFI Flash device mapped on TQM8XXL"
  241. depends on MTD_CFI && TQM8xxL
  242. help
  243. The TQM8xxL PowerPC board has up to two banks of CFI-compliant
  244. chips, currently uses AMD one. This 'mapping' driver supports
  245. that arrangement, allowing the CFI probe and command set driver
  246. code to communicate with the chips on the TQM8xxL board. More at
  247. <http://www.denx.de/embedded-ppc-en.html>.
  248. config MTD_RPXLITE
  249. tristate "CFI Flash device mapped on RPX Lite or CLLF"
  250. depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
  251. help
  252. The RPXLite PowerPC board has CFI-compliant chips mapped in
  253. a strange sparse mapping. This 'mapping' driver supports that
  254. arrangement, allowing the CFI probe and command set driver code
  255. to communicate with the chips on the RPXLite board. More at
  256. <http://www.embeddedplanet.com/>.
  257. config MTD_MBX860
  258. tristate "System flash on MBX860 board"
  259. depends on MTD_CFI && MBX
  260. help
  261. This enables access routines for the flash chips on the Motorola
  262. MBX860 board. If you have one of these boards and would like
  263. to use the flash chips on it, say 'Y'.
  264. config MTD_DBOX2
  265. tristate "CFI Flash device mapped on D-Box2"
  266. depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
  267. help
  268. This enables access routines for the flash chips on the Nokia/Sagem
  269. D-Box 2 board. If you have one of these boards and would like to use
  270. the flash chips on it, say 'Y'.
  271. config MTD_CFI_FLAGADM
  272. tristate "CFI Flash device mapping on FlagaDM"
  273. depends on 8xx && MTD_CFI
  274. help
  275. Mapping for the Flaga digital module. If you don't have one, ignore
  276. this setting.
  277. config MTD_REDWOOD
  278. tristate "CFI Flash devices mapped on IBM Redwood"
  279. depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
  280. help
  281. This enables access routines for the flash chips on the IBM
  282. Redwood board. If you have one of these boards and would like to
  283. use the flash chips on it, say 'Y'.
  284. config MTD_SOLUTIONENGINE
  285. tristate "CFI Flash device mapped on Hitachi SolutionEngine"
  286. depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
  287. help
  288. This enables access to the flash chips on the Hitachi SolutionEngine and
  289. similar boards. Say 'Y' if you are building a kernel for such a board.
  290. config MTD_ARM_INTEGRATOR
  291. tristate "CFI Flash device mapped on ARM Integrator/P720T"
  292. depends on ARM && MTD_CFI
  293. config MTD_CDB89712
  294. tristate "Cirrus CDB89712 evaluation board mappings"
  295. depends on MTD_CFI && ARCH_CDB89712
  296. help
  297. This enables access to the flash or ROM chips on the CDB89712 board.
  298. If you have such a board, say 'Y'.
  299. config MTD_SA1100
  300. tristate "CFI Flash device mapped on StrongARM SA11x0"
  301. depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
  302. help
  303. This enables access to the flash chips on most platforms based on
  304. the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
  305. If you have such a board, say 'Y'.
  306. config MTD_DC21285
  307. tristate "CFI Flash device mapped on DC21285 Footbridge"
  308. depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
  309. help
  310. This provides a driver for the flash accessed using Intel's
  311. 21285 bridge used with Intel's StrongARM processors. More info at
  312. <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
  313. config MTD_IXP4XX
  314. tristate "CFI Flash device mapped on Intel IXP4xx based systems"
  315. depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
  316. help
  317. This enables MTD access to flash devices on platforms based
  318. on Intel's IXP4xx family of network processors such as the
  319. IXDP425 and Coyote. If you have an IXP4xx based board and
  320. would like to use the flash chips on it, say 'Y'.
  321. config MTD_IXP2000
  322. tristate "CFI Flash device mapped on Intel IXP2000 based systems"
  323. depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
  324. help
  325. This enables MTD access to flash devices on platforms based
  326. on Intel's IXP2000 family of network processors. If you have an
  327. IXP2000 based board and would like to use the flash chips on it,
  328. say 'Y'.
  329. config MTD_FORTUNET
  330. tristate "CFI Flash device mapped on the FortuNet board"
  331. depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
  332. help
  333. This enables access to the Flash on the FortuNet board. If you
  334. have such a board, say 'Y'.
  335. config MTD_AUTCPU12
  336. tristate "NV-RAM mapping AUTCPU12 board"
  337. depends on ARCH_AUTCPU12
  338. help
  339. This enables access to the NV-RAM on autronix autcpu12 board.
  340. If you have such a board, say 'Y'.
  341. config MTD_EDB7312
  342. tristate "CFI Flash device mapped on EDB7312"
  343. depends on ARCH_EDB7312 && MTD_CFI
  344. help
  345. This enables access to the CFI Flash on the Cogent EDB7312 board.
  346. If you have such a board, say 'Y' here.
  347. config MTD_IMPA7
  348. tristate "JEDEC Flash device mapped on impA7"
  349. depends on ARM && MTD_JEDECPROBE
  350. help
  351. This enables access to the NOR Flash on the impA7 board of
  352. implementa GmbH. If you have such a board, say 'Y' here.
  353. config MTD_CEIVA
  354. tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
  355. depends on MTD_JEDECPROBE && ARCH_CEIVA
  356. help
  357. This enables access to the flash chips on the Ceiva/Polaroid
  358. PhotoMax Digital Picture Frame.
  359. If you have such a device, say 'Y'.
  360. config MTD_H720X
  361. tristate "Hynix evaluation board mappings"
  362. depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
  363. help
  364. This enables access to the flash chips on the Hynix evaluation boards.
  365. If you have such a board, say 'Y'.
  366. config MTD_OMAP_NOR
  367. tristate "TI OMAP board mappings"
  368. depends on MTD_CFI && ARCH_OMAP
  369. help
  370. This enables access to the NOR flash chips on TI OMAP-based
  371. boards defining flash platform devices and flash platform data.
  372. These boards include the Innovator, H2, H3, OSK, Perseus2, and
  373. more. If you have such a board, say 'Y'.
  374. # This needs CFI or JEDEC, depending on the cards found.
  375. config MTD_PCI
  376. tristate "PCI MTD driver"
  377. depends on PCI && MTD_COMPLEX_MAPPINGS
  378. help
  379. Mapping for accessing flash devices on add-in cards like the Intel XScale
  380. IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
  381. (please see the manual for the link settings).
  382. If you are not sure, say N.
  383. config MTD_PCMCIA
  384. tristate "PCMCIA MTD driver"
  385. depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
  386. help
  387. Map driver for accessing PCMCIA linear flash memory cards. These
  388. cards are usually around 4-16MiB in size. This does not include
  389. Compact Flash cards which are treated as IDE devices.
  390. config MTD_PCMCIA_ANONYMOUS
  391. bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
  392. depends on MTD_PCMCIA
  393. help
  394. If this option is enabled, PCMCIA cards which do not report
  395. anything about themselves are assumed to be MTD cards.
  396. If unsure, say N.
  397. config MTD_BFIN_ASYNC
  398. tristate "Blackfin BF533-STAMP Flash Chip Support"
  399. depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS
  400. select MTD_PARTITIONS
  401. default y
  402. help
  403. Map driver which allows for simultaneous utilization of
  404. ethernet and CFI parallel flash.
  405. If compiled as a module, it will be called bfin-async-flash.
  406. config MTD_GPIO_ADDR
  407. tristate "GPIO-assisted Flash Chip Support"
  408. depends on GENERIC_GPIO || GPIOLIB
  409. depends on MTD_COMPLEX_MAPPINGS
  410. select MTD_PARTITIONS
  411. help
  412. Map driver which allows flashes to be partially physically addressed
  413. and assisted by GPIOs.
  414. If compiled as a module, it will be called gpio-addr-flash.
  415. config MTD_UCLINUX
  416. bool "Generic uClinux RAM/ROM filesystem support"
  417. depends on MTD_PARTITIONS && MTD_RAM=y && !MMU
  418. help
  419. Map driver to support image based filesystems for uClinux.
  420. config MTD_WRSBC8260
  421. tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
  422. depends on (SBC82xx || SBC8560)
  423. select MTD_PARTITIONS
  424. select MTD_MAP_BANK_WIDTH_4
  425. select MTD_MAP_BANK_WIDTH_1
  426. select MTD_CFI_I1
  427. select MTD_CFI_I4
  428. help
  429. Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
  430. all three flash regions on CS0, CS1 and CS6 if they are configured
  431. correctly by the boot loader.
  432. config MTD_DMV182
  433. tristate "Map driver for Dy-4 SVME/DMV-182 board."
  434. depends on DMV182
  435. select MTD_PARTITIONS
  436. select MTD_MAP_BANK_WIDTH_32
  437. select MTD_CFI_I8
  438. select MTD_CFI_AMDSTD
  439. help
  440. Map driver for Dy-4 SVME/DMV-182 board.
  441. config MTD_INTEL_VR_NOR
  442. tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
  443. depends on PCI
  444. help
  445. Map driver for a NOR flash bank located on the Expansion Bus of the
  446. Intel Vermilion Range chipset.
  447. config MTD_RBTX4939
  448. tristate "Map driver for RBTX4939 board"
  449. depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS
  450. help
  451. Map driver for NOR flash chips on RBTX4939 board.
  452. config MTD_PLATRAM
  453. tristate "Map driver for platform device RAM (mtd-ram)"
  454. select MTD_RAM
  455. help
  456. Map driver for RAM areas described via the platform device
  457. system.
  458. This selection automatically selects the map_ram driver.
  459. config MTD_VMU
  460. tristate "Map driver for Dreamcast VMU"
  461. depends on MAPLE
  462. help
  463. This driver enables access to the Dreamcast Visual Memory Unit (VMU).
  464. Most Dreamcast users will want to say Y here.
  465. To build this as a module select M here, the module will be called
  466. vmu-flash.
  467. endmenu