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
87 This provides a 'mapping' driver which supports the way
88 in which user-programmable flash chips are connected on the
89 PMC-Sierra MSP eval/demo boards.
92 prompt "Maximum mappable memory available for flash IO"
93 depends on MTD_PMC_MSP_EVM
94 default MSP_FLASH_MAP_LIMIT_32M
96 config MSP_FLASH_MAP_LIMIT_32M
101 config MSP_FLASH_MAP_LIMIT
104 depends on MSP_FLASH_MAP_LIMIT_32M
106 config MTD_SUN_UFLASH
107 tristate "Sun Microsystems userflash support"
108 depends on SPARC && MTD_CFI && PCI
110 This provides a 'mapping' driver which supports the way in
111 which user-programmable flash chips are connected on various
112 Sun Microsystems boardsets. This driver will require CFI support
113 in the kernel, so if you did not enable CFI previously, do that now.
116 tristate "CFI Flash device mapped on AMD SC520 CDP"
117 depends on X86 && MTD_CFI
119 The SC520 CDP board has two banks of CFI-compliant chips and one
120 Dual-in-line JEDEC chip. This 'mapping' driver supports that
121 arrangement, implementing three MTD devices.
124 tristate "CFI Flash device mapped on AMD NetSc520"
125 depends on X86 && MTD_CFI && MTD_PARTITIONS
127 This enables access routines for the flash chips on the AMD NetSc520
128 demonstration board. If you have one of these boards and would like
129 to use the flash chips on it, say 'Y'.
132 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
134 select MTD_PARTITIONS
135 select MTD_JEDECPROBE
136 select MTD_CFI_AMDSTD
138 This provides a driver for the on-board flash of the Technologic
139 System's TS-5500 board. The 2MB flash is split into 3 partitions
140 which are accessed as separate MTD devices.
142 mtd0 and mtd2 are the two BIOS drives, which use the resident
143 flash disk (RFD) flash translation layer.
145 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
147 Note that jumper 3 ("Write Enable Drive A") must be set
148 otherwise detection won't succeed.
151 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
152 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
154 This provides a driver for the on-board flash of Arcom Control
155 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
156 By default the flash is split into 3 partitions which are accessed
157 as separate MTD devices. This board utilizes Intel StrataFlash.
159 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
162 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
163 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
165 This provides a driver for the NOR flash attached to a PXA2xx chip.
168 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
169 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
171 This provides a 'mapping' driver which supports the way in which
172 the flash chips are connected in the Octagon-5066 Single Board
173 Computer. More information on the board is available at
174 <http://www.octagonsystems.com/products/5066.aspx>.
177 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
178 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
180 This provides a 'mapping' driver which supports the way in which
181 the flash chips are connected in the Tempustech VMAX SBC301 Single
182 Board Computer. More information on the board is available at
183 <http://www.tempustech.com/>.
185 config MTD_SCx200_DOCFLASH
186 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
187 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
189 Enable support for a flash chip mapped using the DOCCS signal on a
190 National Semiconductor SCx200 processor.
192 If you don't know what to do here, say N.
194 If compiled as a module, it will be called scx200_docflash.
197 tristate "BIOS flash chip on AMD76x southbridge"
198 depends on X86 && MTD_JEDECPROBE
200 Support for treating the BIOS flash chip on AMD76x motherboards
201 as an MTD device - with this you can reprogram your BIOS.
206 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
207 depends on X86 && MTD_JEDECPROBE
209 Support for treating the BIOS flash chip on ICHX motherboards
210 as an MTD device - with this you can reprogram your BIOS.
215 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
216 depends on X86 && MTD_JEDECPROBE && PCI
218 Support for treating the BIOS flash chip on ESB2 motherboards
219 as an MTD device - with this you can reprogram your BIOS.
224 tristate "BIOS flash chip on Nvidia CK804"
225 depends on X86 && MTD_JEDECPROBE && PCI
227 Support for treating the BIOS flash chip on nvidia motherboards
228 as an MTD device - with this you can reprogram your BIOS.
232 config MTD_SCB2_FLASH
233 tristate "BIOS flash chip on Intel SCB2 boards"
234 depends on X86 && MTD_JEDECPROBE
236 Support for treating the BIOS flash chip on Intel SCB2 boards
237 as an MTD device - with this you can reprogram your BIOS.
242 tristate "Flash chips on Tsunami TIG bus"
243 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
245 Support for the flash chip on Tsunami TIG bus.
248 tristate "CFI flash device on SnapGear/SecureEdge"
249 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
251 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
254 tristate "Map driver for Broadcom BCM963xx boards"
256 select MTD_MAP_BANK_WIDTH_2
259 Support for parsing CFE image tag and creating MTD partitions on
260 Broadcom BCM63xx boards.
263 tristate "CFI Flash device mapped on DIL/Net PC"
264 depends on X86 && MTD_PARTITIONS && MTD_CFI_INTELEXT && BROKEN
266 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
267 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
268 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
270 config MTD_DILNETPC_BOOTSIZE
271 hex "Size of DIL/Net PC flash boot partition"
272 depends on MTD_DILNETPC
275 The amount of space taken up by the kernel or Etherboot
276 on the DIL/Net PC flash chips.
279 tristate "BIOS flash chip on Intel L440GX boards"
280 depends on X86 && MTD_JEDECPROBE
282 Support for treating the BIOS flash chip on Intel L440GX motherboards
283 as an MTD device - with this you can reprogram your BIOS.
288 tristate "CFI Flash device mapped on TQM8XXL"
289 depends on MTD_CFI && TQM8xxL
291 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
292 chips, currently uses AMD one. This 'mapping' driver supports
293 that arrangement, allowing the CFI probe and command set driver
294 code to communicate with the chips on the TQM8xxL board. More at
295 <http://www.denx.de/wiki/PPCEmbedded/>.
298 tristate "CFI Flash device mapped on RPX Lite or CLLF"
299 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
301 The RPXLite PowerPC board has CFI-compliant chips mapped in
302 a strange sparse mapping. This 'mapping' driver supports that
303 arrangement, allowing the CFI probe and command set driver code
304 to communicate with the chips on the RPXLite board. More at
305 <http://www.embeddedplanet.com/>.
308 tristate "System flash on MBX860 board"
309 depends on MTD_CFI && MBX
311 This enables access routines for the flash chips on the Motorola
312 MBX860 board. If you have one of these boards and would like
313 to use the flash chips on it, say 'Y'.
316 tristate "CFI Flash device mapped on D-Box2"
317 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
319 This enables access routines for the flash chips on the Nokia/Sagem
320 D-Box 2 board. If you have one of these boards and would like to use
321 the flash chips on it, say 'Y'.
323 config MTD_CFI_FLAGADM
324 tristate "CFI Flash device mapping on FlagaDM"
325 depends on 8xx && MTD_CFI
327 Mapping for the Flaga digital module. If you don't have one, ignore
330 config MTD_SOLUTIONENGINE
331 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
332 depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
334 This enables access to the flash chips on the Hitachi SolutionEngine and
335 similar boards. Say 'Y' if you are building a kernel for such a board.
337 config MTD_ARM_INTEGRATOR
338 tristate "CFI Flash device mapped on ARM Integrator/P720T"
339 depends on ARM && MTD_CFI
342 tristate "Cirrus CDB89712 evaluation board mappings"
343 depends on MTD_CFI && ARCH_CDB89712
345 This enables access to the flash or ROM chips on the CDB89712 board.
346 If you have such a board, say 'Y'.
349 tristate "CFI Flash device mapped on StrongARM SA11x0"
350 depends on MTD_CFI && ARCH_SA1100
352 This enables access to the flash chips on most platforms based on
353 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
354 If you have such a board, say 'Y'.
357 tristate "CFI Flash device mapped on DC21285 Footbridge"
358 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
360 This provides a driver for the flash accessed using Intel's
361 21285 bridge used with Intel's StrongARM processors. More info at
362 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
365 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
366 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
368 This enables MTD access to flash devices on platforms based
369 on Intel's IXP4xx family of network processors such as the
370 IXDP425 and Coyote. If you have an IXP4xx based board and
371 would like to use the flash chips on it, say 'Y'.
374 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
375 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
377 This enables MTD access to flash devices on platforms based
378 on Intel's IXP2000 family of network processors. If you have an
379 IXP2000 based board and would like to use the flash chips on it,
383 tristate "CFI Flash device mapped on the FortuNet board"
384 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
386 This enables access to the Flash on the FortuNet board. If you
387 have such a board, say 'Y'.
390 tristate "NV-RAM mapping AUTCPU12 board"
391 depends on ARCH_AUTCPU12
393 This enables access to the NV-RAM on autronix autcpu12 board.
394 If you have such a board, say 'Y'.
397 tristate "CFI Flash device mapped on EDB7312"
398 depends on ARCH_EDB7312 && MTD_CFI
400 This enables access to the CFI Flash on the Cogent EDB7312 board.
401 If you have such a board, say 'Y' here.
404 tristate "JEDEC Flash device mapped on impA7"
405 depends on ARM && MTD_JEDECPROBE
407 This enables access to the NOR Flash on the impA7 board of
408 implementa GmbH. If you have such a board, say 'Y' here.
411 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
412 depends on MTD_JEDECPROBE && ARCH_CEIVA
414 This enables access to the flash chips on the Ceiva/Polaroid
415 PhotoMax Digital Picture Frame.
416 If you have such a device, say 'Y'.
419 tristate "Hynix evaluation board mappings"
420 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
422 This enables access to the flash chips on the Hynix evaluation boards.
423 If you have such a board, say 'Y'.
425 # This needs CFI or JEDEC, depending on the cards found.
427 tristate "PCI MTD driver"
428 depends on PCI && MTD_COMPLEX_MAPPINGS
430 Mapping for accessing flash devices on add-in cards like the Intel XScale
431 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
432 (please see the manual for the link settings).
434 If you are not sure, say N.
437 tristate "PCMCIA MTD driver"
438 depends on PCMCIA && MTD_COMPLEX_MAPPINGS
440 Map driver for accessing PCMCIA linear flash memory cards. These
441 cards are usually around 4-16MiB in size. This does not include
442 Compact Flash cards which are treated as IDE devices.
444 config MTD_PCMCIA_ANONYMOUS
445 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
446 depends on MTD_PCMCIA
448 If this option is enabled, PCMCIA cards which do not report
449 anything about themselves are assumed to be MTD cards.
453 config MTD_BFIN_ASYNC
454 tristate "Blackfin BF533-STAMP Flash Chip Support"
455 depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS
458 Map driver which allows for simultaneous utilization of
459 ethernet and CFI parallel flash.
461 If compiled as a module, it will be called bfin-async-flash.
464 tristate "GPIO-assisted Flash Chip Support"
465 depends on GENERIC_GPIO || GPIOLIB
466 depends on MTD_COMPLEX_MAPPINGS
468 Map driver which allows flashes to be partially physically addressed
469 and assisted by GPIOs.
471 If compiled as a module, it will be called gpio-addr-flash.
474 bool "Generic uClinux RAM/ROM filesystem support"
475 depends on MTD_PARTITIONS && MTD_RAM=y && !MMU
477 Map driver to support image based filesystems for uClinux.
480 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
481 depends on (SBC82xx || SBC8560)
482 select MTD_PARTITIONS
483 select MTD_MAP_BANK_WIDTH_4
484 select MTD_MAP_BANK_WIDTH_1
488 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
489 all three flash regions on CS0, CS1 and CS6 if they are configured
490 correctly by the boot loader.
493 tristate "Map driver for Dy-4 SVME/DMV-182 board."
495 select MTD_PARTITIONS
496 select MTD_MAP_BANK_WIDTH_32
498 select MTD_CFI_AMDSTD
500 Map driver for Dy-4 SVME/DMV-182 board.
502 config MTD_INTEL_VR_NOR
503 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
506 Map driver for a NOR flash bank located on the Expansion Bus of the
507 Intel Vermilion Range chipset.
510 tristate "Map driver for RBTX4939 board"
511 depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS
513 Map driver for NOR flash chips on RBTX4939 board.
516 tristate "Map driver for platform device RAM (mtd-ram)"
519 Map driver for RAM areas described via the platform device
522 This selection automatically selects the map_ram driver.
525 tristate "Map driver for Dreamcast VMU"
528 This driver enables access to the Dreamcast Visual Memory Unit (VMU).
530 Most Dreamcast users will want to say Y here.
532 To build this as a module select M here, the module will be called
536 tristate "MTD discovery driver for PISMO modules"
538 depends on ARCH_VERSATILE
540 This driver allows for discovery of PISMO modules - see
541 <http://www.pismoworld.org/>. These are small modules containing
542 up to five memory devices (eg, SRAM, flash, DOC) described by an
545 This driver does not create any MTD maps itself; instead it
546 creates MTD physmap and MTD SRAM platform devices. If you
547 enable this option, you should consider enabling MTD_PHYSMAP
548 and/or MTD_PLATRAM according to the devices on your module.
550 When built as a module, it will be called pismo.ko
552 config MTD_LATCH_ADDR
553 tristate "Latch-assisted Flash Chip Support"
554 depends on MTD_COMPLEX_MAPPINGS
556 Map driver which allows flashes to be partially physically addressed
557 and have the upper address lines set by a board specific code.
559 If compiled as a module, it will be called latch-addr-flash.