1 # drivers/mtd/maps/Kconfig
3 menu "Mapping drivers for chip access"
6 config MTD_COMPLEX_MAPPINGS
7 bool "Support non-linear mappings of flash chips"
9 This causes the chip drivers to allow for complicated
10 paged mappings of flash chips.
13 tristate "CFI Flash device in physical memory map"
14 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
16 This provides a 'mapping' driver which allows the NOR Flash and
17 ROM driver code to communicate with chips which are mapped
18 physically into the CPU's memory. You will need to configure
19 the physical address and size of the flash chips on your
20 particular board as well as the bus width, either statically
21 with config options or at run-time.
23 To compile this driver as a module, choose M here: the
24 module will be called physmap.
26 config MTD_PHYSMAP_START
27 hex "Physical start address of flash mapping"
28 depends on MTD_PHYSMAP
31 This is the physical memory location at which the flash chips
32 are mapped on your particular target board. Refer to the
33 memory map which should hopefully be in the documentation for
35 Ignore this option if you use run-time physmap configuration
36 (i.e., run-time calling physmap_configure()).
38 config MTD_PHYSMAP_LEN
39 hex "Physical length of flash mapping"
40 depends on MTD_PHYSMAP
43 This is the total length of the mapping of the flash chips on
44 your particular board. If there is space, or aliases, in the
45 physical memory map between the chips, this could be larger
46 than the total amount of flash present. Refer to the memory
47 map which should hopefully be in the documentation for your
49 Ignore this option if you use run-time physmap configuration
50 (i.e., run-time calling physmap_configure()).
52 config MTD_PHYSMAP_BANKWIDTH
53 int "Bank width in octets"
54 depends on MTD_PHYSMAP
57 This is the total width of the data bus of the flash devices
58 in octets. For example, if you have a data bus width of 32
59 bits, you would set the bus width octet value to 4. This is
60 used internally by the CFI drivers.
61 Ignore this option if you use run-time physmap configuration
62 (i.e., run-time calling physmap_configure()).
65 tristate "Flash device in physical memory map based on OF description"
66 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
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.
73 config MTD_PMC_MSP_EVM
74 tristate "CFI Flash device mapped on PMC-Sierra MSP"
75 depends on PMC_MSP && MTD_CFI
78 This provides a 'mapping' driver which supports the way
79 in which user-programmable flash chips are connected on the
80 PMC-Sierra MSP eval/demo boards.
83 prompt "Maximum mappable memory available for flash IO"
84 depends on MTD_PMC_MSP_EVM
85 default MSP_FLASH_MAP_LIMIT_32M
87 config MSP_FLASH_MAP_LIMIT_32M
92 config MSP_FLASH_MAP_LIMIT
95 depends on MSP_FLASH_MAP_LIMIT_32M
97 config MTD_PMC_MSP_RAMROOT
98 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
99 depends on PMC_MSP_EMBEDDED_ROOTFS && \
100 (MTD_BLOCK || MTD_BLOCK_RO) && \
103 This provides support for the embedded root file system
104 on PMC MSP devices. This memory is mapped as a MTD block device.
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 "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
256 depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
258 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
261 tristate "4G Systems MTX-1 Flash device"
262 depends on MIPS_MTX1 && MTD_CFI
264 Flash memory access on 4G Systems MTX-1 Board. If you have one of
265 these boards and would like to use the flash chips on it, say 'Y'.
268 tristate "CFI Flash device mapped on DIL/Net PC"
269 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
271 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
272 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
273 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
275 config MTD_DILNETPC_BOOTSIZE
276 hex "Size of DIL/Net PC flash boot partition"
277 depends on MTD_DILNETPC
280 The amount of space taken up by the kernel or Etherboot
281 on the DIL/Net PC flash chips.
284 tristate "BIOS flash chip on Intel L440GX boards"
285 depends on X86 && MTD_JEDECPROBE
287 Support for treating the BIOS flash chip on Intel L440GX motherboards
288 as an MTD device - with this you can reprogram your BIOS.
293 tristate "Flash device on SBC8240"
294 depends on MTD_JEDECPROBE && 8260
296 Flash access on the SBC8240 board from Wind River. See
297 <http://www.windriver.com/products/sbc8240/>
300 tristate "CFI Flash device mapped on TQM8XXL"
301 depends on MTD_CFI && TQM8xxL
303 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
304 chips, currently uses AMD one. This 'mapping' driver supports
305 that arrangement, allowing the CFI probe and command set driver
306 code to communicate with the chips on the TQM8xxL board. More at
307 <http://www.denx.de/embedded-ppc-en.html>.
310 tristate "CFI Flash device mapped on RPX Lite or CLLF"
311 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
313 The RPXLite PowerPC board has CFI-compliant chips mapped in
314 a strange sparse mapping. This 'mapping' driver supports that
315 arrangement, allowing the CFI probe and command set driver code
316 to communicate with the chips on the RPXLite board. More at
317 <http://www.embeddedplanet.com/>.
320 tristate "System flash on MBX860 board"
321 depends on MTD_CFI && MBX
323 This enables access routines for the flash chips on the Motorola
324 MBX860 board. If you have one of these boards and would like
325 to use the flash chips on it, say 'Y'.
328 tristate "CFI Flash device mapped on D-Box2"
329 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
331 This enables access routines for the flash chips on the Nokia/Sagem
332 D-Box 2 board. If you have one of these boards and would like to use
333 the flash chips on it, say 'Y'.
335 config MTD_CFI_FLAGADM
336 tristate "CFI Flash device mapping on FlagaDM"
337 depends on 8xx && MTD_CFI
339 Mapping for the Flaga digital module. If you don't have one, ignore
343 tristate "Flash device mapped on IBM 405GP Walnut"
344 depends on MTD_JEDECPROBE && WALNUT && !PPC_MERGE
346 This enables access routines for the flash chips on the IBM 405GP
347 Walnut board. If you have one of these boards and would like to
348 use the flash chips on it, say 'Y'.
351 tristate "Flash devices mapped on IBM 440GP Ebony"
352 depends on MTD_JEDECPROBE && EBONY && !PPC_MERGE
354 This enables access routines for the flash chips on the IBM 440GP
355 Ebony board. If you have one of these boards and would like to
356 use the flash chips on it, say 'Y'.
359 tristate "Flash devices mapped on IBM 440GX Ocotea"
360 depends on MTD_CFI && OCOTEA && !PPC_MERGE
362 This enables access routines for the flash chips on the IBM 440GX
363 Ocotea board. If you have one of these boards and would like to
364 use the flash chips on it, say 'Y'.
367 tristate "CFI Flash devices mapped on IBM Redwood"
368 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
370 This enables access routines for the flash chips on the IBM
371 Redwood board. If you have one of these boards and would like to
372 use the flash chips on it, say 'Y'.
374 config MTD_SOLUTIONENGINE
375 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
376 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
378 This enables access to the flash chips on the Hitachi SolutionEngine and
379 similar boards. Say 'Y' if you are building a kernel for such a board.
381 config MTD_ARM_INTEGRATOR
382 tristate "CFI Flash device mapped on ARM Integrator/P720T"
383 depends on ARM && MTD_CFI
386 tristate "Cirrus CDB89712 evaluation board mappings"
387 depends on MTD_CFI && ARCH_CDB89712
389 This enables access to the flash or ROM chips on the CDB89712 board.
390 If you have such a board, say 'Y'.
393 tristate "CFI Flash device mapped on StrongARM SA11x0"
394 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
396 This enables access to the flash chips on most platforms based on
397 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
398 If you have such a board, say 'Y'.
401 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
402 depends on IPAQ_HANDHELD && MTD_CFI
404 This provides a driver for the on-board flash of the iPAQ.
407 tristate "CFI Flash device mapped on DC21285 Footbridge"
408 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
410 This provides a driver for the flash accessed using Intel's
411 21285 bridge used with Intel's StrongARM processors. More info at
412 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
415 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
416 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
418 This enables MTD access to flash devices on platforms based
419 on Intel's IXP4xx family of network processors such as the
420 IXDP425 and Coyote. If you have an IXP4xx based board and
421 would like to use the flash chips on it, say 'Y'.
424 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
425 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
427 This enables MTD access to flash devices on platforms based
428 on Intel's IXP2000 family of network processors such as the
429 IXDP425 and Coyote. If you have an IXP2000 based board and
430 would like to use the flash chips on it, say 'Y'.
433 tristate "CFI Flash device mapped on the FortuNet board"
434 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
436 This enables access to the Flash on the FortuNet board. If you
437 have such a board, say 'Y'.
440 tristate "NV-RAM mapping AUTCPU12 board"
441 depends on ARCH_AUTCPU12
443 This enables access to the NV-RAM on autronix autcpu12 board.
444 If you have such a board, say 'Y'.
447 tristate "CFI Flash device mapped on EDB7312"
448 depends on ARCH_EDB7312 && MTD_CFI
450 This enables access to the CFI Flash on the Cogent EDB7312 board.
451 If you have such a board, say 'Y' here.
454 tristate "JEDEC Flash device mapped on impA7"
455 depends on ARM && MTD_JEDECPROBE
457 This enables access to the NOR Flash on the impA7 board of
458 implementa GmbH. If you have such a board, say 'Y' here.
461 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
462 depends on MTD_JEDECPROBE && ARCH_CEIVA
464 This enables access to the flash chips on the Ceiva/Polaroid
465 PhotoMax Digital Picture Frame.
466 If you have such a device, say 'Y'.
469 tristate "NOR Flash device on TOTO board"
470 depends on ARCH_OMAP && OMAP_TOTO
472 This enables access to the NOR flash on the Texas Instruments
476 tristate "Hynix evaluation board mappings"
477 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
479 This enables access to the flash chips on the Hynix evaluation boards.
480 If you have such a board, say 'Y'.
483 tristate "CFI Flash device mapped on Interface MPC-1211"
484 depends on SH_MPC1211 && MTD_CFI
486 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
487 If you have such a board, say 'Y'.
490 tristate "TI OMAP board mappings"
491 depends on MTD_CFI && ARCH_OMAP
493 This enables access to the NOR flash chips on TI OMAP-based
494 boards defining flash platform devices and flash platform data.
495 These boards include the Innovator, H2, H3, OSK, Perseus2, and
496 more. If you have such a board, say 'Y'.
498 # This needs CFI or JEDEC, depending on the cards found.
500 tristate "PCI MTD driver"
501 depends on PCI && MTD_COMPLEX_MAPPINGS
503 Mapping for accessing flash devices on add-in cards like the Intel XScale
504 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
505 (please see the manual for the link settings).
507 If you are not sure, say N.
510 tristate "PCMCIA MTD driver"
511 depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
513 Map driver for accessing PCMCIA linear flash memory cards. These
514 cards are usually around 4-16MiB in size. This does not include
515 Compact Flash cards which are treated as IDE devices.
517 config MTD_PCMCIA_ANONYMOUS
518 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
519 depends on MTD_PCMCIA
521 If this option is enabled, PCMCIA cards which do not report
522 anything about themselves are assumed to be MTD cards.
526 config MTD_BFIN_ASYNC
527 tristate "Blackfin BF533-STAMP Flash Chip Support"
528 depends on BFIN533_STAMP && MTD_CFI
529 select MTD_PARTITIONS
532 Map driver which allows for simultaneous utilization of
533 ethernet and CFI parallel flash.
535 If compiled as a module, it will be called bfin-async-flash.
538 tristate "Generic uClinux RAM/ROM filesystem support"
539 depends on MTD_PARTITIONS && !MMU
541 Map driver to support image based filesystems for uClinux.
544 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
545 depends on (SBC82xx || SBC8560)
546 select MTD_PARTITIONS
547 select MTD_MAP_BANK_WIDTH_4
548 select MTD_MAP_BANK_WIDTH_1
552 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
553 all three flash regions on CS0, CS1 and CS6 if they are configured
554 correctly by the boot loader.
557 tristate "Map driver for Dy-4 SVME/DMV-182 board."
559 select MTD_PARTITIONS
560 select MTD_MAP_BANK_WIDTH_32
562 select MTD_CFI_AMDSTD
564 Map driver for Dy-4 SVME/DMV-182 board.
567 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
568 depends on ARCH_BAST || MACH_VR1000
569 select MTD_PARTITIONS
570 select MTD_MAP_BANK_WIDTH_16
571 select MTD_JEDECPROBE
573 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
576 Note, this driver *cannot* over-ride the WP link on the
577 board, or currently detect the state of the link.
579 config MTD_BAST_MAXSIZE
580 int "Maximum size for BAST flash area (MiB)"
585 tristate "ROM mapped on Sharp SL Series"
588 This enables access to the flash chip on the Sharp SL Series of PDAs.
590 config MTD_INTEL_VR_NOR
591 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
594 Map driver for a NOR flash bank located on the Expansion Bus of the
595 Intel Vermilion Range chipset.
598 tristate "Map driver for platform device RAM (mtd-ram)"
601 Map driver for RAM areas described via the platform device
604 This selection automatically selects the map_ram driver.