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
45 config MTD_PHYSMAP_LEN
46 hex "Physical length of flash mapping"
47 depends on MTD_PHYSMAP_COMPAT
50 This is the total length of the mapping of the flash chips on
51 your particular board. If there is space, or aliases, in the
52 physical memory map between the chips, this could be larger
53 than the total amount of flash present. Refer to the memory
54 map which should hopefully be in the documentation for your
57 config MTD_PHYSMAP_BANKWIDTH
58 int "Bank width in octets"
59 depends on MTD_PHYSMAP_COMPAT
62 This is the total width of the data bus of the flash devices
63 in octets. For example, if you have a data bus width of 32
64 bits, you would set the bus width octet value to 4. This is
65 used internally by the CFI drivers.
68 tristate "Flash device in physical memory map based on OF description"
69 depends on OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
71 This provides a 'mapping' driver which allows the NOR Flash and
72 ROM driver code to communicate with chips which are mapped
73 physically into the CPU's memory. The mapping description here is
74 taken from OF device tree.
76 config MTD_PMC_MSP_EVM
77 tristate "CFI Flash device mapped on PMC-Sierra MSP"
78 depends on PMC_MSP && MTD_CFI
80 This provides a 'mapping' driver which supports the way
81 in which user-programmable flash chips are connected on the
82 PMC-Sierra MSP eval/demo boards.
85 prompt "Maximum mappable memory available for flash IO"
86 depends on MTD_PMC_MSP_EVM
87 default MSP_FLASH_MAP_LIMIT_32M
89 config MSP_FLASH_MAP_LIMIT_32M
94 config MSP_FLASH_MAP_LIMIT
97 depends on MSP_FLASH_MAP_LIMIT_32M
100 tristate "Sun Microsystems userflash support"
101 depends on SPARC && MTD_CFI && PCI
103 This provides a 'mapping' driver which supports the way in
104 which user-programmable flash chips are connected on various
105 Sun Microsystems boardsets. This driver will require CFI support
106 in the kernel, so if you did not enable CFI previously, do that now.
109 tristate "CFI Flash device mapped on AMD SC520 CDP"
110 depends on X86 && MTD_CFI
112 The SC520 CDP board has two banks of CFI-compliant chips and one
113 Dual-in-line JEDEC chip. This 'mapping' driver supports that
114 arrangement, implementing three MTD devices.
117 tristate "CFI Flash device mapped on AMD NetSc520"
118 depends on X86 && MTD_CFI
120 This enables access routines for the flash chips on the AMD NetSc520
121 demonstration board. If you have one of these boards and would like
122 to use the flash chips on it, say 'Y'.
125 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
127 select MTD_JEDECPROBE
128 select MTD_CFI_AMDSTD
130 This provides a driver for the on-board flash of the Technologic
131 System's TS-5500 board. The 2MB flash is split into 3 partitions
132 which are accessed as separate MTD devices.
134 mtd0 and mtd2 are the two BIOS drives, which use the resident
135 flash disk (RFD) flash translation layer.
137 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
139 Note that jumper 3 ("Write Enable Drive A") must be set
140 otherwise detection won't succeed.
143 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
144 depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS
146 This provides a driver for the on-board flash of Arcom Control
147 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
148 By default the flash is split into 3 partitions which are accessed
149 as separate MTD devices. This board utilizes Intel StrataFlash.
151 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
154 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
155 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
157 This provides a driver for the NOR flash attached to a PXA2xx chip.
160 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
161 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
163 This provides a 'mapping' driver which supports the way in which
164 the flash chips are connected in the Octagon-5066 Single Board
165 Computer. More information on the board is available at
166 <http://www.octagonsystems.com/products/5066.aspx>.
169 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
170 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
172 This provides a 'mapping' driver which supports the way in which
173 the flash chips are connected in the Tempustech VMAX SBC301 Single
174 Board Computer. More information on the board is available at
175 <http://www.tempustech.com/>.
177 config MTD_SCx200_DOCFLASH
178 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
179 depends on SCx200 && MTD_CFI
181 Enable support for a flash chip mapped using the DOCCS signal on a
182 National Semiconductor SCx200 processor.
184 If you don't know what to do here, say N.
186 If compiled as a module, it will be called scx200_docflash.
189 tristate "BIOS flash chip on AMD76x southbridge"
190 depends on X86 && MTD_JEDECPROBE
192 Support for treating the BIOS flash chip on AMD76x motherboards
193 as an MTD device - with this you can reprogram your BIOS.
198 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
199 depends on X86 && MTD_JEDECPROBE
201 Support for treating the BIOS flash chip on ICHX motherboards
202 as an MTD device - with this you can reprogram your BIOS.
207 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
208 depends on X86 && MTD_JEDECPROBE && PCI
210 Support for treating the BIOS flash chip on ESB2 motherboards
211 as an MTD device - with this you can reprogram your BIOS.
216 tristate "BIOS flash chip on Nvidia CK804"
217 depends on X86 && MTD_JEDECPROBE && PCI
219 Support for treating the BIOS flash chip on nvidia motherboards
220 as an MTD device - with this you can reprogram your BIOS.
224 config MTD_SCB2_FLASH
225 tristate "BIOS flash chip on Intel SCB2 boards"
226 depends on X86 && MTD_JEDECPROBE
228 Support for treating the BIOS flash chip on Intel SCB2 boards
229 as an MTD device - with this you can reprogram your BIOS.
234 tristate "Flash chips on Tsunami TIG bus"
235 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
237 Support for the flash chip on Tsunami TIG bus.
240 tristate "CFI flash device on SnapGear/SecureEdge"
241 depends on X86 && MTD_JEDECPROBE
243 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
246 tristate "Map driver for Broadcom BCM963xx boards"
248 select MTD_MAP_BANK_WIDTH_2
251 Support for parsing CFE image tag and creating MTD partitions on
252 Broadcom BCM63xx boards.
255 tristate "Lantiq SoC NOR support"
257 select MTD_PARTITIONS
259 Support for NOR flash attached to the Lantiq SoC's External Bus Unit.
262 tristate "CFI Flash device mapped on DIL/Net PC"
263 depends on X86 && MTD_CFI_INTELEXT && BROKEN
265 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
266 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
267 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
269 config MTD_DILNETPC_BOOTSIZE
270 hex "Size of DIL/Net PC flash boot partition"
271 depends on MTD_DILNETPC
274 The amount of space taken up by the kernel or Etherboot
275 on the DIL/Net PC flash chips.
278 tristate "BIOS flash chip on Intel L440GX boards"
279 depends on X86 && MTD_JEDECPROBE
281 Support for treating the BIOS flash chip on Intel L440GX motherboards
282 as an MTD device - with this you can reprogram your BIOS.
287 tristate "CFI Flash device mapped on TQM8XXL"
288 depends on MTD_CFI && TQM8xxL
290 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
291 chips, currently uses AMD one. This 'mapping' driver supports
292 that arrangement, allowing the CFI probe and command set driver
293 code to communicate with the chips on the TQM8xxL board. More at
294 <http://www.denx.de/wiki/PPCEmbedded/>.
297 tristate "CFI Flash device mapped on RPX Lite or CLLF"
298 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
300 The RPXLite PowerPC board has CFI-compliant chips mapped in
301 a strange sparse mapping. This 'mapping' driver supports that
302 arrangement, allowing the CFI probe and command set driver code
303 to communicate with the chips on the RPXLite board. More at
304 <http://www.embeddedplanet.com/>.
307 tristate "System flash on MBX860 board"
308 depends on MTD_CFI && MBX
310 This enables access routines for the flash chips on the Motorola
311 MBX860 board. If you have one of these boards and would like
312 to use the flash chips on it, say 'Y'.
315 tristate "CFI Flash device mapped on D-Box2"
316 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
318 This enables access routines for the flash chips on the Nokia/Sagem
319 D-Box 2 board. If you have one of these boards and would like to use
320 the flash chips on it, say 'Y'.
322 config MTD_CFI_FLAGADM
323 tristate "CFI Flash device mapping on FlagaDM"
324 depends on 8xx && MTD_CFI
326 Mapping for the Flaga digital module. If you don't have one, ignore
329 config MTD_SOLUTIONENGINE
330 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
331 depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
333 This enables access to the flash chips on the Hitachi SolutionEngine and
334 similar boards. Say 'Y' if you are building a kernel for such a board.
336 config MTD_ARM_INTEGRATOR
337 tristate "CFI Flash device mapped on ARM Integrator/P720T"
338 depends on ARM && MTD_CFI
341 tristate "Cirrus CDB89712 evaluation board mappings"
342 depends on MTD_CFI && ARCH_CDB89712
344 This enables access to the flash or ROM chips on the CDB89712 board.
345 If you have such a board, say 'Y'.
348 tristate "CFI Flash device mapped on StrongARM SA11x0"
349 depends on MTD_CFI && ARCH_SA1100
351 This enables access to the flash chips on most platforms based on
352 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
353 If you have such a board, say 'Y'.
356 tristate "CFI Flash device mapped on DC21285 Footbridge"
357 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
359 This provides a driver for the flash accessed using Intel's
360 21285 bridge used with Intel's StrongARM processors. More info at
361 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
364 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
365 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
367 This enables MTD access to flash devices on platforms based
368 on Intel's IXP4xx family of network processors such as the
369 IXDP425 and Coyote. If you have an IXP4xx based board and
370 would like to use the flash chips on it, say 'Y'.
373 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
374 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
376 This enables MTD access to flash devices on platforms based
377 on Intel's IXP2000 family of network processors. If you have an
378 IXP2000 based board and would like to use the flash chips on it,
382 tristate "CFI Flash device mapped on the FortuNet board"
383 depends on MTD_CFI && SA1100_FORTUNET
385 This enables access to the Flash on the FortuNet board. If you
386 have such a board, say 'Y'.
389 tristate "NV-RAM mapping AUTCPU12 board"
390 depends on ARCH_AUTCPU12
392 This enables access to the NV-RAM on autronix autcpu12 board.
393 If you have such a board, say 'Y'.
396 tristate "JEDEC Flash device mapped on impA7"
397 depends on ARM && MTD_JEDECPROBE
399 This enables access to the NOR Flash on the impA7 board of
400 implementa GmbH. If you have such a board, say 'Y' here.
403 tristate "Hynix evaluation board mappings"
404 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
406 This enables access to the flash chips on the Hynix evaluation boards.
407 If you have such a board, say 'Y'.
409 # This needs CFI or JEDEC, depending on the cards found.
411 tristate "PCI MTD driver"
412 depends on PCI && MTD_COMPLEX_MAPPINGS
414 Mapping for accessing flash devices on add-in cards like the Intel XScale
415 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
416 (please see the manual for the link settings).
418 If you are not sure, say N.
421 tristate "PCMCIA MTD driver"
422 depends on PCMCIA && MTD_COMPLEX_MAPPINGS
424 Map driver for accessing PCMCIA linear flash memory cards. These
425 cards are usually around 4-16MiB in size. This does not include
426 Compact Flash cards which are treated as IDE devices.
428 config MTD_PCMCIA_ANONYMOUS
429 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
430 depends on MTD_PCMCIA
432 If this option is enabled, PCMCIA cards which do not report
433 anything about themselves are assumed to be MTD cards.
437 config MTD_BFIN_ASYNC
438 tristate "Blackfin BF533-STAMP Flash Chip Support"
439 depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS
442 Map driver which allows for simultaneous utilization of
443 ethernet and CFI parallel flash.
445 If compiled as a module, it will be called bfin-async-flash.
448 tristate "GPIO-assisted Flash Chip Support"
449 depends on GENERIC_GPIO || GPIOLIB
450 depends on MTD_COMPLEX_MAPPINGS
452 Map driver which allows flashes to be partially physically addressed
453 and assisted by GPIOs.
455 If compiled as a module, it will be called gpio-addr-flash.
458 bool "Generic uClinux RAM/ROM filesystem support"
459 depends on MTD_RAM=y && !MMU
461 Map driver to support image based filesystems for uClinux.
464 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
465 depends on (SBC82xx || SBC8560)
466 select MTD_MAP_BANK_WIDTH_4
467 select MTD_MAP_BANK_WIDTH_1
471 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
472 all three flash regions on CS0, CS1 and CS6 if they are configured
473 correctly by the boot loader.
476 tristate "Map driver for Dy-4 SVME/DMV-182 board."
478 select MTD_MAP_BANK_WIDTH_32
480 select MTD_CFI_AMDSTD
482 Map driver for Dy-4 SVME/DMV-182 board.
484 config MTD_INTEL_VR_NOR
485 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
488 Map driver for a NOR flash bank located on the Expansion Bus of the
489 Intel Vermilion Range chipset.
492 tristate "Map driver for RBTX4939 board"
493 depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS
495 Map driver for NOR flash chips on RBTX4939 board.
498 tristate "Map driver for platform device RAM (mtd-ram)"
501 Map driver for RAM areas described via the platform device
504 This selection automatically selects the map_ram driver.
507 tristate "Map driver for Dreamcast VMU"
510 This driver enables access to the Dreamcast Visual Memory Unit (VMU).
512 Most Dreamcast users will want to say Y here.
514 To build this as a module select M here, the module will be called
518 tristate "MTD discovery driver for PISMO modules"
520 depends on ARCH_VERSATILE
522 This driver allows for discovery of PISMO modules - see
523 <http://www.pismoworld.org/>. These are small modules containing
524 up to five memory devices (eg, SRAM, flash, DOC) described by an
527 This driver does not create any MTD maps itself; instead it
528 creates MTD physmap and MTD SRAM platform devices. If you
529 enable this option, you should consider enabling MTD_PHYSMAP
530 and/or MTD_PLATRAM according to the devices on your module.
532 When built as a module, it will be called pismo.ko
534 config MTD_LATCH_ADDR
535 tristate "Latch-assisted Flash Chip Support"
536 depends on MTD_COMPLEX_MAPPINGS
538 Map driver which allows flashes to be partially physically addressed
539 and have the upper address lines set by a board specific code.
541 If compiled as a module, it will be called latch-addr-flash.