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 (MICROBLAZE || PPC_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 && MTD_CONCAT
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
164 select MTD_PARTITIONS
166 This provides a driver for the NOR flash attached to a PXA2xx chip.
169 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
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 Octagon-5066 Single Board
174 Computer. More information on the board is available at
175 <http://www.octagonsystems.com/CPUpages/5066.html>.
178 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
179 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
181 This provides a 'mapping' driver which supports the way in which
182 the flash chips are connected in the Tempustech VMAX SBC301 Single
183 Board Computer. More information on the board is available at
184 <http://www.tempustech.com/>.
186 config MTD_SCx200_DOCFLASH
187 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
188 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
190 Enable support for a flash chip mapped using the DOCCS signal on a
191 National Semiconductor SCx200 processor.
193 If you don't know what to do here, say N.
195 If compiled as a module, it will be called scx200_docflash.
198 tristate "BIOS flash chip on AMD76x southbridge"
199 depends on X86 && MTD_JEDECPROBE
201 Support for treating the BIOS flash chip on AMD76x motherboards
202 as an MTD device - with this you can reprogram your BIOS.
207 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
208 depends on X86 && MTD_JEDECPROBE
210 Support for treating the BIOS flash chip on ICHX motherboards
211 as an MTD device - with this you can reprogram your BIOS.
216 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
217 depends on X86 && MTD_JEDECPROBE && PCI
219 Support for treating the BIOS flash chip on ESB2 motherboards
220 as an MTD device - with this you can reprogram your BIOS.
225 tristate "BIOS flash chip on Nvidia CK804"
226 depends on X86 && MTD_JEDECPROBE && PCI
228 Support for treating the BIOS flash chip on nvidia motherboards
229 as an MTD device - with this you can reprogram your BIOS.
233 config MTD_SCB2_FLASH
234 tristate "BIOS flash chip on Intel SCB2 boards"
235 depends on X86 && MTD_JEDECPROBE
237 Support for treating the BIOS flash chip on Intel SCB2 boards
238 as an MTD device - with this you can reprogram your BIOS.
243 tristate "Flash chips on Tsunami TIG bus"
244 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
246 Support for the flash chip on Tsunami TIG bus.
249 tristate "CFI flash device on SnapGear/SecureEdge"
250 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
252 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
255 tristate "CFI Flash device mapped on DIL/Net PC"
256 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT && BROKEN
258 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
259 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
260 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
262 config MTD_DILNETPC_BOOTSIZE
263 hex "Size of DIL/Net PC flash boot partition"
264 depends on MTD_DILNETPC
267 The amount of space taken up by the kernel or Etherboot
268 on the DIL/Net PC flash chips.
271 tristate "BIOS flash chip on Intel L440GX boards"
272 depends on X86 && MTD_JEDECPROBE
274 Support for treating the BIOS flash chip on Intel L440GX motherboards
275 as an MTD device - with this you can reprogram your BIOS.
280 tristate "CFI Flash device mapped on TQM8XXL"
281 depends on MTD_CFI && TQM8xxL
283 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
284 chips, currently uses AMD one. This 'mapping' driver supports
285 that arrangement, allowing the CFI probe and command set driver
286 code to communicate with the chips on the TQM8xxL board. More at
287 <http://www.denx.de/embedded-ppc-en.html>.
290 tristate "CFI Flash device mapped on RPX Lite or CLLF"
291 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
293 The RPXLite PowerPC board has CFI-compliant chips mapped in
294 a strange sparse mapping. This 'mapping' driver supports that
295 arrangement, allowing the CFI probe and command set driver code
296 to communicate with the chips on the RPXLite board. More at
297 <http://www.embeddedplanet.com/>.
300 tristate "System flash on MBX860 board"
301 depends on MTD_CFI && MBX
303 This enables access routines for the flash chips on the Motorola
304 MBX860 board. If you have one of these boards and would like
305 to use the flash chips on it, say 'Y'.
308 tristate "CFI Flash device mapped on D-Box2"
309 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
311 This enables access routines for the flash chips on the Nokia/Sagem
312 D-Box 2 board. If you have one of these boards and would like to use
313 the flash chips on it, say 'Y'.
315 config MTD_CFI_FLAGADM
316 tristate "CFI Flash device mapping on FlagaDM"
317 depends on 8xx && MTD_CFI
319 Mapping for the Flaga digital module. If you don't have one, ignore
322 config MTD_SOLUTIONENGINE
323 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
324 depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
326 This enables access to the flash chips on the Hitachi SolutionEngine and
327 similar boards. Say 'Y' if you are building a kernel for such a board.
329 config MTD_ARM_INTEGRATOR
330 tristate "CFI Flash device mapped on ARM Integrator/P720T"
331 depends on ARM && MTD_CFI
334 tristate "Cirrus CDB89712 evaluation board mappings"
335 depends on MTD_CFI && ARCH_CDB89712
337 This enables access to the flash or ROM chips on the CDB89712 board.
338 If you have such a board, say 'Y'.
341 tristate "CFI Flash device mapped on StrongARM SA11x0"
342 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
344 This enables access to the flash chips on most platforms based on
345 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
346 If you have such a board, say 'Y'.
349 tristate "CFI Flash device mapped on DC21285 Footbridge"
350 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
352 This provides a driver for the flash accessed using Intel's
353 21285 bridge used with Intel's StrongARM processors. More info at
354 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
357 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
358 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
360 This enables MTD access to flash devices on platforms based
361 on Intel's IXP4xx family of network processors such as the
362 IXDP425 and Coyote. If you have an IXP4xx based board and
363 would like to use the flash chips on it, say 'Y'.
366 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
367 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
369 This enables MTD access to flash devices on platforms based
370 on Intel's IXP2000 family of network processors. If you have an
371 IXP2000 based board and would like to use the flash chips on it,
375 tristate "CFI Flash device mapped on the FortuNet board"
376 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
378 This enables access to the Flash on the FortuNet board. If you
379 have such a board, say 'Y'.
382 tristate "NV-RAM mapping AUTCPU12 board"
383 depends on ARCH_AUTCPU12
385 This enables access to the NV-RAM on autronix autcpu12 board.
386 If you have such a board, say 'Y'.
389 tristate "CFI Flash device mapped on EDB7312"
390 depends on ARCH_EDB7312 && MTD_CFI
392 This enables access to the CFI Flash on the Cogent EDB7312 board.
393 If you have such a board, say 'Y' here.
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 "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
404 depends on MTD_JEDECPROBE && ARCH_CEIVA
406 This enables access to the flash chips on the Ceiva/Polaroid
407 PhotoMax Digital Picture Frame.
408 If you have such a device, say 'Y'.
411 tristate "Hynix evaluation board mappings"
412 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
414 This enables access to the flash chips on the Hynix evaluation boards.
415 If you have such a board, say 'Y'.
417 # This needs CFI or JEDEC, depending on the cards found.
419 tristate "PCI MTD driver"
420 depends on PCI && MTD_COMPLEX_MAPPINGS
422 Mapping for accessing flash devices on add-in cards like the Intel XScale
423 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
424 (please see the manual for the link settings).
426 If you are not sure, say N.
429 tristate "PCMCIA MTD driver"
430 depends on PCMCIA && MTD_COMPLEX_MAPPINGS
432 Map driver for accessing PCMCIA linear flash memory cards. These
433 cards are usually around 4-16MiB in size. This does not include
434 Compact Flash cards which are treated as IDE devices.
436 config MTD_PCMCIA_ANONYMOUS
437 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
438 depends on MTD_PCMCIA
440 If this option is enabled, PCMCIA cards which do not report
441 anything about themselves are assumed to be MTD cards.
445 config MTD_BFIN_ASYNC
446 tristate "Blackfin BF533-STAMP Flash Chip Support"
447 depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS
448 select MTD_PARTITIONS
451 Map driver which allows for simultaneous utilization of
452 ethernet and CFI parallel flash.
454 If compiled as a module, it will be called bfin-async-flash.
457 tristate "GPIO-assisted Flash Chip Support"
458 depends on GENERIC_GPIO || GPIOLIB
459 depends on MTD_COMPLEX_MAPPINGS
460 select MTD_PARTITIONS
462 Map driver which allows flashes to be partially physically addressed
463 and assisted by GPIOs.
465 If compiled as a module, it will be called gpio-addr-flash.
468 bool "Generic uClinux RAM/ROM filesystem support"
469 depends on MTD_PARTITIONS && MTD_RAM=y && !MMU
471 Map driver to support image based filesystems for uClinux.
474 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
475 depends on (SBC82xx || SBC8560)
476 select MTD_PARTITIONS
477 select MTD_MAP_BANK_WIDTH_4
478 select MTD_MAP_BANK_WIDTH_1
482 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
483 all three flash regions on CS0, CS1 and CS6 if they are configured
484 correctly by the boot loader.
487 tristate "Map driver for Dy-4 SVME/DMV-182 board."
489 select MTD_PARTITIONS
490 select MTD_MAP_BANK_WIDTH_32
492 select MTD_CFI_AMDSTD
494 Map driver for Dy-4 SVME/DMV-182 board.
496 config MTD_INTEL_VR_NOR
497 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
500 Map driver for a NOR flash bank located on the Expansion Bus of the
501 Intel Vermilion Range chipset.
504 tristate "Map driver for RBTX4939 board"
505 depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS
507 Map driver for NOR flash chips on RBTX4939 board.
510 tristate "Map driver for platform device RAM (mtd-ram)"
513 Map driver for RAM areas described via the platform device
516 This selection automatically selects the map_ram driver.
519 tristate "Map driver for Dreamcast VMU"
522 This driver enables access to the Dreamcast Visual Memory Unit (VMU).
524 Most Dreamcast users will want to say Y here.
526 To build this as a module select M here, the module will be called
530 tristate "MTD discovery driver for PISMO modules"
532 depends on ARCH_VERSATILE
534 This driver allows for discovery of PISMO modules - see
535 <http://www.pismoworld.org/>. These are small modules containing
536 up to five memory devices (eg, SRAM, flash, DOC) described by an
539 This driver does not create any MTD maps itself; instead it
540 creates MTD physmap and MTD SRAM platform devices. If you
541 enable this option, you should consider enabling MTD_PHYSMAP
542 and/or MTD_PLATRAM according to the devices on your module.
544 When built as a module, it will be called pismo.ko