1 menu "Mapping drivers for chip access"
4 config MTD_COMPLEX_MAPPINGS
5 bool "Support non-linear mappings of flash chips"
7 This causes the chip drivers to allow for complicated
8 paged mappings of flash chips.
11 tristate "Flash device in physical memory map"
12 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR
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.
21 To compile this driver as a module, choose M here: the
22 module will be called physmap.
24 config MTD_PHYSMAP_COMPAT
25 bool "Physmap compat support"
26 depends on MTD_PHYSMAP
29 Setup a simple mapping via the Kconfig options. Normally the
30 physmap configuration options are done via your board's
33 If unsure, say N here.
35 config MTD_PHYSMAP_START
36 hex "Physical start address of flash mapping"
37 depends on MTD_PHYSMAP_COMPAT
40 This is the physical memory location at which the flash chips
41 are mapped on your particular target board. Refer to the
42 memory map which should hopefully be in the documentation for
44 Ignore this option if you use run-time physmap configuration
45 (i.e., run-time calling physmap_configure()).
47 config MTD_PHYSMAP_LEN
48 hex "Physical length of flash mapping"
49 depends on MTD_PHYSMAP_COMPAT
52 This is the total length of the mapping of the flash chips on
53 your particular board. If there is space, or aliases, in the
54 physical memory map between the chips, this could be larger
55 than the total amount of flash present. Refer to the memory
56 map which should hopefully be in the documentation for your
58 Ignore this option if you use run-time physmap configuration
59 (i.e., run-time calling physmap_configure()).
61 config MTD_PHYSMAP_BANKWIDTH
62 int "Bank width in octets"
63 depends on MTD_PHYSMAP_COMPAT
66 This is the total width of the data bus of the flash devices
67 in octets. For example, if you have a data bus width of 32
68 bits, you would set the bus width octet value to 4. This is
69 used internally by the CFI drivers.
70 Ignore this option if you use run-time physmap configuration
71 (i.e., run-time calling physmap_configure()).
74 tristate "Flash device in physical memory map based on OF description"
75 depends on OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
77 This provides a 'mapping' driver which allows the NOR Flash and
78 ROM driver code to communicate with chips which are mapped
79 physically into the CPU's memory. The mapping description here is
80 taken from OF device tree.
82 config MTD_PMC_MSP_EVM
83 tristate "CFI Flash device mapped on PMC-Sierra MSP"
84 depends on PMC_MSP && MTD_CFI
86 This provides a 'mapping' driver which supports the way
87 in which user-programmable flash chips are connected on the
88 PMC-Sierra MSP eval/demo boards.
91 prompt "Maximum mappable memory available for flash IO"
92 depends on MTD_PMC_MSP_EVM
93 default MSP_FLASH_MAP_LIMIT_32M
95 config MSP_FLASH_MAP_LIMIT_32M
100 config MSP_FLASH_MAP_LIMIT
103 depends on MSP_FLASH_MAP_LIMIT_32M
105 config MTD_SUN_UFLASH
106 tristate "Sun Microsystems userflash support"
107 depends on SPARC && MTD_CFI && PCI
109 This provides a 'mapping' driver which supports the way in
110 which user-programmable flash chips are connected on various
111 Sun Microsystems boardsets. This driver will require CFI support
112 in the kernel, so if you did not enable CFI previously, do that now.
115 tristate "CFI Flash device mapped on AMD SC520 CDP"
116 depends on X86 && MTD_CFI
118 The SC520 CDP board has two banks of CFI-compliant chips and one
119 Dual-in-line JEDEC chip. This 'mapping' driver supports that
120 arrangement, implementing three MTD devices.
123 tristate "CFI Flash device mapped on AMD NetSc520"
124 depends on X86 && MTD_CFI
126 This enables access routines for the flash chips on the AMD NetSc520
127 demonstration board. If you have one of these boards and would like
128 to use the flash chips on it, say 'Y'.
131 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
133 select MTD_JEDECPROBE
134 select MTD_CFI_AMDSTD
136 This provides a driver for the on-board flash of the Technologic
137 System's TS-5500 board. The 2MB flash is split into 3 partitions
138 which are accessed as separate MTD devices.
140 mtd0 and mtd2 are the two BIOS drives, which use the resident
141 flash disk (RFD) flash translation layer.
143 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
145 Note that jumper 3 ("Write Enable Drive A") must be set
146 otherwise detection won't succeed.
149 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
150 depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS
152 This provides a driver for the on-board flash of Arcom Control
153 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
154 By default the flash is split into 3 partitions which are accessed
155 as separate MTD devices. This board utilizes Intel StrataFlash.
157 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
160 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
161 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
163 This provides a driver for the NOR flash attached to a PXA2xx chip.
165 config MTD_IMX6X_WEIMNOR
166 tristate "CFI Flash device mapped on iMX6x based boards"
167 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR
169 This provides a driver for the WEIM (Parallel) NOR flash attached to
170 an iMX6x chip. This driver provides a cached read to take advantage
171 of paged reads by using memcopy. If you have a board such as the
172 SabreAI select 'Y' to use the NOR flash chips on it.
175 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
176 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
178 This provides a 'mapping' driver which supports the way in which
179 the flash chips are connected in the Octagon-5066 Single Board
180 Computer. More information on the board is available at
181 <http://www.octagonsystems.com/products/5066.aspx>.
184 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
185 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
187 This provides a 'mapping' driver which supports the way in which
188 the flash chips are connected in the Tempustech VMAX SBC301 Single
189 Board Computer. More information on the board is available at
190 <http://www.tempustech.com/>.
192 config MTD_SCx200_DOCFLASH
193 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
194 depends on SCx200 && MTD_CFI
196 Enable support for a flash chip mapped using the DOCCS signal on a
197 National Semiconductor SCx200 processor.
199 If you don't know what to do here, say N.
201 If compiled as a module, it will be called scx200_docflash.
204 tristate "BIOS flash chip on AMD76x southbridge"
205 depends on X86 && MTD_JEDECPROBE
207 Support for treating the BIOS flash chip on AMD76x motherboards
208 as an MTD device - with this you can reprogram your BIOS.
213 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
214 depends on X86 && MTD_JEDECPROBE
216 Support for treating the BIOS flash chip on ICHX motherboards
217 as an MTD device - with this you can reprogram your BIOS.
222 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
223 depends on X86 && MTD_JEDECPROBE && PCI
225 Support for treating the BIOS flash chip on ESB2 motherboards
226 as an MTD device - with this you can reprogram your BIOS.
231 tristate "BIOS flash chip on Nvidia CK804"
232 depends on X86 && MTD_JEDECPROBE && PCI
234 Support for treating the BIOS flash chip on nvidia motherboards
235 as an MTD device - with this you can reprogram your BIOS.
239 config MTD_SCB2_FLASH
240 tristate "BIOS flash chip on Intel SCB2 boards"
241 depends on X86 && MTD_JEDECPROBE
243 Support for treating the BIOS flash chip on Intel SCB2 boards
244 as an MTD device - with this you can reprogram your BIOS.
249 tristate "Flash chips on Tsunami TIG bus"
250 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
252 Support for the flash chip on Tsunami TIG bus.
255 tristate "CFI flash device on SnapGear/SecureEdge"
256 depends on X86 && MTD_JEDECPROBE
258 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
261 tristate "Map driver for Broadcom BCM963xx boards"
263 select MTD_MAP_BANK_WIDTH_2
266 Support for parsing CFE image tag and creating MTD partitions on
267 Broadcom BCM63xx boards.
270 tristate "Lantiq SoC NOR support"
272 select MTD_PARTITIONS
274 Support for NOR flash attached to the Lantiq SoC's External Bus Unit.
277 tristate "CFI Flash device mapped on DIL/Net PC"
278 depends on X86 && MTD_CFI_INTELEXT && BROKEN
280 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
281 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
282 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
284 config MTD_DILNETPC_BOOTSIZE
285 hex "Size of DIL/Net PC flash boot partition"
286 depends on MTD_DILNETPC
289 The amount of space taken up by the kernel or Etherboot
290 on the DIL/Net PC flash chips.
293 tristate "BIOS flash chip on Intel L440GX boards"
294 depends on X86 && MTD_JEDECPROBE
296 Support for treating the BIOS flash chip on Intel L440GX motherboards
297 as an MTD device - with this you can reprogram your BIOS.
302 tristate "CFI Flash device mapped on TQM8XXL"
303 depends on MTD_CFI && TQM8xxL
305 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
306 chips, currently uses AMD one. This 'mapping' driver supports
307 that arrangement, allowing the CFI probe and command set driver
308 code to communicate with the chips on the TQM8xxL board. More at
309 <http://www.denx.de/wiki/PPCEmbedded/>.
312 tristate "CFI Flash device mapped on RPX Lite or CLLF"
313 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
315 The RPXLite PowerPC board has CFI-compliant chips mapped in
316 a strange sparse mapping. This 'mapping' driver supports that
317 arrangement, allowing the CFI probe and command set driver code
318 to communicate with the chips on the RPXLite board. More at
319 <http://www.embeddedplanet.com/>.
322 tristate "System flash on MBX860 board"
323 depends on MTD_CFI && MBX
325 This enables access routines for the flash chips on the Motorola
326 MBX860 board. If you have one of these boards and would like
327 to use the flash chips on it, say 'Y'.
330 tristate "CFI Flash device mapped on D-Box2"
331 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
333 This enables access routines for the flash chips on the Nokia/Sagem
334 D-Box 2 board. If you have one of these boards and would like to use
335 the flash chips on it, say 'Y'.
337 config MTD_CFI_FLAGADM
338 tristate "CFI Flash device mapping on FlagaDM"
339 depends on 8xx && MTD_CFI
341 Mapping for the Flaga digital module. If you don't have one, ignore
344 config MTD_SOLUTIONENGINE
345 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
346 depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
348 This enables access to the flash chips on the Hitachi SolutionEngine and
349 similar boards. Say 'Y' if you are building a kernel for such a board.
351 config MTD_ARM_INTEGRATOR
352 tristate "CFI Flash device mapped on ARM Integrator/P720T"
353 depends on ARM && MTD_CFI
356 tristate "Cirrus CDB89712 evaluation board mappings"
357 depends on MTD_CFI && ARCH_CDB89712
359 This enables access to the flash or ROM chips on the CDB89712 board.
360 If you have such a board, say 'Y'.
363 tristate "CFI Flash device mapped on StrongARM SA11x0"
364 depends on MTD_CFI && ARCH_SA1100
366 This enables access to the flash chips on most platforms based on
367 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
368 If you have such a board, say 'Y'.
371 tristate "CFI Flash device mapped on DC21285 Footbridge"
372 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
374 This provides a driver for the flash accessed using Intel's
375 21285 bridge used with Intel's StrongARM processors. More info at
376 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
379 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
380 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
382 This enables MTD access to flash devices on platforms based
383 on Intel's IXP4xx family of network processors such as the
384 IXDP425 and Coyote. If you have an IXP4xx based board and
385 would like to use the flash chips on it, say 'Y'.
388 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
389 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
391 This enables MTD access to flash devices on platforms based
392 on Intel's IXP2000 family of network processors. If you have an
393 IXP2000 based board and would like to use the flash chips on it,
397 tristate "CFI Flash device mapped on the FortuNet board"
398 depends on MTD_CFI && SA1100_FORTUNET
400 This enables access to the Flash on the FortuNet board. If you
401 have such a board, say 'Y'.
404 tristate "NV-RAM mapping AUTCPU12 board"
405 depends on ARCH_AUTCPU12
407 This enables access to the NV-RAM on autronix autcpu12 board.
408 If you have such a board, say 'Y'.
411 tristate "CFI Flash device mapped on EDB7312"
412 depends on ARCH_EDB7312 && MTD_CFI
414 This enables access to the CFI Flash on the Cogent EDB7312 board.
415 If you have such a board, say 'Y' here.
418 tristate "JEDEC Flash device mapped on impA7"
419 depends on ARM && MTD_JEDECPROBE
421 This enables access to the NOR Flash on the impA7 board of
422 implementa GmbH. If you have such a board, say 'Y' here.
425 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
426 depends on MTD_JEDECPROBE && ARCH_CEIVA
428 This enables access to the flash chips on the Ceiva/Polaroid
429 PhotoMax Digital Picture Frame.
430 If you have such a device, say 'Y'.
433 tristate "Hynix evaluation board mappings"
434 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
436 This enables access to the flash chips on the Hynix evaluation boards.
437 If you have such a board, say 'Y'.
439 # This needs CFI or JEDEC, depending on the cards found.
441 tristate "PCI MTD driver"
442 depends on PCI && MTD_COMPLEX_MAPPINGS
444 Mapping for accessing flash devices on add-in cards like the Intel XScale
445 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
446 (please see the manual for the link settings).
448 If you are not sure, say N.
451 tristate "PCMCIA MTD driver"
452 depends on PCMCIA && MTD_COMPLEX_MAPPINGS
454 Map driver for accessing PCMCIA linear flash memory cards. These
455 cards are usually around 4-16MiB in size. This does not include
456 Compact Flash cards which are treated as IDE devices.
458 config MTD_PCMCIA_ANONYMOUS
459 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
460 depends on MTD_PCMCIA
462 If this option is enabled, PCMCIA cards which do not report
463 anything about themselves are assumed to be MTD cards.
467 config MTD_BFIN_ASYNC
468 tristate "Blackfin BF533-STAMP Flash Chip Support"
469 depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS
472 Map driver which allows for simultaneous utilization of
473 ethernet and CFI parallel flash.
475 If compiled as a module, it will be called bfin-async-flash.
478 tristate "GPIO-assisted Flash Chip Support"
479 depends on GENERIC_GPIO || GPIOLIB
480 depends on MTD_COMPLEX_MAPPINGS
482 Map driver which allows flashes to be partially physically addressed
483 and assisted by GPIOs.
485 If compiled as a module, it will be called gpio-addr-flash.
488 bool "Generic uClinux RAM/ROM filesystem support"
489 depends on MTD_RAM=y && !MMU
491 Map driver to support image based filesystems for uClinux.
494 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
495 depends on (SBC82xx || SBC8560)
496 select MTD_MAP_BANK_WIDTH_4
497 select MTD_MAP_BANK_WIDTH_1
501 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
502 all three flash regions on CS0, CS1 and CS6 if they are configured
503 correctly by the boot loader.
506 tristate "Map driver for Dy-4 SVME/DMV-182 board."
508 select MTD_MAP_BANK_WIDTH_32
510 select MTD_CFI_AMDSTD
512 Map driver for Dy-4 SVME/DMV-182 board.
514 config MTD_INTEL_VR_NOR
515 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
518 Map driver for a NOR flash bank located on the Expansion Bus of the
519 Intel Vermilion Range chipset.
522 tristate "Map driver for RBTX4939 board"
523 depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS
525 Map driver for NOR flash chips on RBTX4939 board.
528 tristate "Map driver for platform device RAM (mtd-ram)"
531 Map driver for RAM areas described via the platform device
534 This selection automatically selects the map_ram driver.
537 tristate "Map driver for Dreamcast VMU"
540 This driver enables access to the Dreamcast Visual Memory Unit (VMU).
542 Most Dreamcast users will want to say Y here.
544 To build this as a module select M here, the module will be called
548 tristate "MTD discovery driver for PISMO modules"
550 depends on ARCH_VERSATILE
552 This driver allows for discovery of PISMO modules - see
553 <http://www.pismoworld.org/>. These are small modules containing
554 up to five memory devices (eg, SRAM, flash, DOC) described by an
557 This driver does not create any MTD maps itself; instead it
558 creates MTD physmap and MTD SRAM platform devices. If you
559 enable this option, you should consider enabling MTD_PHYSMAP
560 and/or MTD_PLATRAM according to the devices on your module.
562 When built as a module, it will be called pismo.ko
564 config MTD_LATCH_ADDR
565 tristate "Latch-assisted Flash Chip Support"
566 depends on MTD_COMPLEX_MAPPINGS
568 Map driver which allows flashes to be partially physically addressed
569 and have the upper address lines set by a board specific code.
571 If compiled as a module, it will be called latch-addr-flash.