1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner Exp $
4 menu "Mapping drivers for chip access"
7 config MTD_COMPLEX_MAPPINGS
8 bool "Support non-linear mappings of flash chips"
10 This causes the chip drivers to allow for complicated
11 paged mappings of flash chips.
14 tristate "CFI Flash device in physical memory map"
15 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
17 This provides a 'mapping' driver which allows the NOR Flash and
18 ROM driver code to communicate with chips which are mapped
19 physically into the CPU's memory. You will need to configure
20 the physical address and size of the flash chips on your
21 particular board as well as the bus width, either statically
22 with config options or at run-time.
24 To compile this driver as a module, choose M here: the
25 module will be called physmap.
27 config MTD_PHYSMAP_START
28 hex "Physical start address of flash mapping"
29 depends on MTD_PHYSMAP
32 This is the physical memory location at which the flash chips
33 are mapped on your particular target board. Refer to the
34 memory map which should hopefully be in the documentation for
36 Ignore this option if you use run-time physmap configuration
37 (i.e., run-time calling physmap_configure()).
39 config MTD_PHYSMAP_LEN
40 hex "Physical length of flash mapping"
41 depends on MTD_PHYSMAP
44 This is the total length of the mapping of the flash chips on
45 your particular board. If there is space, or aliases, in the
46 physical memory map between the chips, this could be larger
47 than the total amount of flash present. Refer to the memory
48 map which should hopefully be in the documentation for your
50 Ignore this option if you use run-time physmap configuration
51 (i.e., run-time calling physmap_configure()).
53 config MTD_PHYSMAP_BANKWIDTH
54 int "Bank width in octets"
55 depends on MTD_PHYSMAP
58 This is the total width of the data bus of the flash devices
59 in octets. For example, if you have a data bus width of 32
60 bits, you would set the bus width octet value to 4. This is
61 used internally by the CFI drivers.
62 Ignore this option if you use run-time physmap configuration
63 (i.e., run-time calling physmap_configure()).
66 tristate "Flash device in physical memory map based on OF description"
67 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
69 This provides a 'mapping' driver which allows the NOR Flash and
70 ROM driver code to communicate with chips which are mapped
71 physically into the CPU's memory. The mapping description here is
72 taken from OF device tree.
74 config MTD_PMC_MSP_EVM
75 tristate "CFI Flash device mapped on PMC-Sierra MSP"
76 depends on PMC_MSP && MTD_CFI
79 This provides a 'mapping' driver which supports the way
80 in which user-programmable flash chips are connected on the
81 PMC-Sierra MSP eval/demo boards.
84 prompt "Maximum mappable memory available for flash IO"
85 depends on MTD_PMC_MSP_EVM
86 default MSP_FLASH_MAP_LIMIT_32M
88 config MSP_FLASH_MAP_LIMIT_32M
93 config MSP_FLASH_MAP_LIMIT
96 depends on MSP_FLASH_MAP_LIMIT_32M
98 config MTD_PMC_MSP_RAMROOT
99 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
100 depends on PMC_MSP_EMBEDDED_ROOTFS && \
101 (MTD_BLOCK || MTD_BLOCK_RO) && \
104 This provides support for the embedded root file system
105 on PMC MSP devices. This memory is mapped as a MTD block device.
107 config MTD_XILINX_OPB
108 bool "OPB CFI Flash device mapped on Xilinx boards"
109 depends on MTD_CFI_INTELEXT && SP3E && HAVE_XILINX_EMC
111 OPB Flash mapping support for Xilinx boards
113 config MTD_SUN_UFLASH
114 tristate "Sun Microsystems userflash support"
115 depends on SPARC && MTD_CFI && PCI
117 This provides a 'mapping' driver which supports the way in
118 which user-programmable flash chips are connected on various
119 Sun Microsystems boardsets. This driver will require CFI support
120 in the kernel, so if you did not enable CFI previously, do that now.
123 tristate "CFI Flash device mapped on AMD SC520 CDP"
124 depends on X86 && MTD_CFI && MTD_CONCAT
126 The SC520 CDP board has two banks of CFI-compliant chips and one
127 Dual-in-line JEDEC chip. This 'mapping' driver supports that
128 arrangement, implementing three MTD devices.
131 tristate "CFI Flash device mapped on AMD NetSc520"
132 depends on X86 && MTD_CFI && MTD_PARTITIONS
134 This enables access routines for the flash chips on the AMD NetSc520
135 demonstration board. If you have one of these boards and would like
136 to use the flash chips on it, say 'Y'.
139 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
141 select MTD_PARTITIONS
142 select MTD_JEDECPROBE
143 select MTD_CFI_AMDSTD
145 This provides a driver for the on-board flash of the Technologic
146 System's TS-5500 board. The 2MB flash is split into 3 partitions
147 which are accessed as separate MTD devices.
149 mtd0 and mtd2 are the two BIOS drives, which use the resident
150 flash disk (RFD) flash translation layer.
152 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
154 Note that jumper 3 ("Write Enable Drive A") must be set
155 otherwise detection won't succeed.
158 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
159 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
161 This provides a driver for the on-board flash of Arcom Control
162 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
163 By default the flash is split into 3 partitions which are accessed
164 as separate MTD devices. This board utilizes Intel StrataFlash.
166 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
169 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
170 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
171 select MTD_PARTITIONS
173 This provides a driver for the NOR flash attached to a PXA2xx chip.
176 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
177 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
179 This provides a 'mapping' driver which supports the way in which
180 the flash chips are connected in the Octagon-5066 Single Board
181 Computer. More information on the board is available at
182 <http://www.octagonsystems.com/CPUpages/5066.html>.
185 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
186 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
188 This provides a 'mapping' driver which supports the way in which
189 the flash chips are connected in the Tempustech VMAX SBC301 Single
190 Board Computer. More information on the board is available at
191 <http://www.tempustech.com/>.
193 config MTD_SCx200_DOCFLASH
194 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
195 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
197 Enable support for a flash chip mapped using the DOCCS signal on a
198 National Semiconductor SCx200 processor.
200 If you don't know what to do here, say N.
202 If compiled as a module, it will be called scx200_docflash.
205 tristate "BIOS flash chip on AMD76x southbridge"
206 depends on X86 && MTD_JEDECPROBE
208 Support for treating the BIOS flash chip on AMD76x motherboards
209 as an MTD device - with this you can reprogram your BIOS.
214 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
215 depends on X86 && MTD_JEDECPROBE
217 Support for treating the BIOS flash chip on ICHX motherboards
218 as an MTD device - with this you can reprogram your BIOS.
223 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
224 depends on X86 && MTD_JEDECPROBE && PCI
226 Support for treating the BIOS flash chip on ESB2 motherboards
227 as an MTD device - with this you can reprogram your BIOS.
232 tristate "BIOS flash chip on Nvidia CK804"
233 depends on X86 && MTD_JEDECPROBE && PCI
235 Support for treating the BIOS flash chip on nvidia motherboards
236 as an MTD device - with this you can reprogram your BIOS.
240 config MTD_SCB2_FLASH
241 tristate "BIOS flash chip on Intel SCB2 boards"
242 depends on X86 && MTD_JEDECPROBE
244 Support for treating the BIOS flash chip on Intel SCB2 boards
245 as an MTD device - with this you can reprogram your BIOS.
250 tristate "Flash chips on Tsunami TIG bus"
251 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
253 Support for the flash chip on Tsunami TIG bus.
256 tristate "CFI flash device on SnapGear/SecureEdge"
257 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
259 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
262 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
263 depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
265 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
268 tristate "4G Systems MTX-1 Flash device"
269 depends on MIPS_MTX1 && MTD_CFI
271 Flash memory access on 4G Systems MTX-1 Board. If you have one of
272 these boards and would like to use the flash chips on it, say 'Y'.
275 tristate "CFI Flash device mapped on DIL/Net PC"
276 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
278 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
279 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
280 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
282 config MTD_DILNETPC_BOOTSIZE
283 hex "Size of DIL/Net PC flash boot partition"
284 depends on MTD_DILNETPC
287 The amount of space taken up by the kernel or Etherboot
288 on the DIL/Net PC flash chips.
291 tristate "BIOS flash chip on Intel L440GX boards"
292 depends on X86 && MTD_JEDECPROBE
294 Support for treating the BIOS flash chip on Intel L440GX motherboards
295 as an MTD device - with this you can reprogram your BIOS.
300 tristate "Flash device on SBC8240"
301 depends on MTD_JEDECPROBE && 8260
303 Flash access on the SBC8240 board from Wind River. See
304 <http://www.windriver.com/products/sbc8240/>
307 tristate "CFI Flash device mapped on TQM8XXL"
308 depends on MTD_CFI && TQM8xxL
310 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
311 chips, currently uses AMD one. This 'mapping' driver supports
312 that arrangement, allowing the CFI probe and command set driver
313 code to communicate with the chips on the TQM8xxL board. More at
314 <http://www.denx.de/embedded-ppc-en.html>.
317 tristate "CFI Flash device mapped on RPX Lite or CLLF"
318 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
320 The RPXLite PowerPC board has CFI-compliant chips mapped in
321 a strange sparse mapping. This 'mapping' driver supports that
322 arrangement, allowing the CFI probe and command set driver code
323 to communicate with the chips on the RPXLite board. More at
324 <http://www.embeddedplanet.com/>.
327 tristate "System flash on MBX860 board"
328 depends on MTD_CFI && MBX
330 This enables access routines for the flash chips on the Motorola
331 MBX860 board. If you have one of these boards and would like
332 to use the flash chips on it, say 'Y'.
335 tristate "CFI Flash device mapped on D-Box2"
336 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
338 This enables access routines for the flash chips on the Nokia/Sagem
339 D-Box 2 board. If you have one of these boards and would like to use
340 the flash chips on it, say 'Y'.
342 config MTD_CFI_FLAGADM
343 tristate "CFI Flash device mapping on FlagaDM"
344 depends on 8xx && MTD_CFI
346 Mapping for the Flaga digital module. If you don't have one, ignore
350 tristate "Flash device mapped on IBM 405GP Walnut"
351 depends on MTD_JEDECPROBE && WALNUT && !PPC_MERGE
353 This enables access routines for the flash chips on the IBM 405GP
354 Walnut board. If you have one of these boards and would like to
355 use the flash chips on it, say 'Y'.
358 tristate "Flash devices mapped on IBM 440GP Ebony"
359 depends on MTD_JEDECPROBE && EBONY && !PPC_MERGE
361 This enables access routines for the flash chips on the IBM 440GP
362 Ebony board. If you have one of these boards and would like to
363 use the flash chips on it, say 'Y'.
366 tristate "Flash devices mapped on IBM 440GX Ocotea"
367 depends on MTD_CFI && OCOTEA && !PPC_MERGE
369 This enables access routines for the flash chips on the IBM 440GX
370 Ocotea board. If you have one of these boards and would like to
371 use the flash chips on it, say 'Y'.
374 tristate "CFI Flash devices mapped on IBM Redwood"
375 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
377 This enables access routines for the flash chips on the IBM
378 Redwood board. If you have one of these boards and would like to
379 use the flash chips on it, say 'Y'.
381 config MTD_SOLUTIONENGINE
382 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
383 depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
385 This enables access to the flash chips on the Hitachi SolutionEngine and
386 similar boards. Say 'Y' if you are building a kernel for such a board.
388 config MTD_ARM_INTEGRATOR
389 tristate "CFI Flash device mapped on ARM Integrator/P720T"
390 depends on ARM && MTD_CFI
393 tristate "Cirrus CDB89712 evaluation board mappings"
394 depends on MTD_CFI && ARCH_CDB89712
396 This enables access to the flash or ROM chips on the CDB89712 board.
397 If you have such a board, say 'Y'.
400 tristate "CFI Flash device mapped on StrongARM SA11x0"
401 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
403 This enables access to the flash chips on most platforms based on
404 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
405 If you have such a board, say 'Y'.
408 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
409 depends on IPAQ_HANDHELD && MTD_CFI
411 This provides a driver for the on-board flash of the iPAQ.
414 tristate "CFI Flash device mapped on DC21285 Footbridge"
415 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
417 This provides a driver for the flash accessed using Intel's
418 21285 bridge used with Intel's StrongARM processors. More info at
419 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
422 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
423 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
425 This enables MTD access to flash devices on platforms based
426 on Intel's IXP4xx family of network processors such as the
427 IXDP425 and Coyote. If you have an IXP4xx based board and
428 would like to use the flash chips on it, say 'Y'.
431 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
432 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
434 This enables MTD access to flash devices on platforms based
435 on Intel's IXP2000 family of network processors such as the
436 IXDP425 and Coyote. If you have an IXP2000 based board and
437 would like to use the flash chips on it, say 'Y'.
440 tristate "CFI Flash device mapped on the FortuNet board"
441 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
443 This enables access to the Flash on the FortuNet board. If you
444 have such a board, say 'Y'.
447 tristate "NV-RAM mapping AUTCPU12 board"
448 depends on ARCH_AUTCPU12
450 This enables access to the NV-RAM on autronix autcpu12 board.
451 If you have such a board, say 'Y'.
454 tristate "CFI Flash device mapped on EDB7312"
455 depends on ARCH_EDB7312 && MTD_CFI
457 This enables access to the CFI Flash on the Cogent EDB7312 board.
458 If you have such a board, say 'Y' here.
461 tristate "JEDEC Flash device mapped on impA7"
462 depends on ARM && MTD_JEDECPROBE
464 This enables access to the NOR Flash on the impA7 board of
465 implementa GmbH. If you have such a board, say 'Y' here.
468 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
469 depends on MTD_JEDECPROBE && ARCH_CEIVA
471 This enables access to the flash chips on the Ceiva/Polaroid
472 PhotoMax Digital Picture Frame.
473 If you have such a device, say 'Y'.
476 tristate "NOR Flash device on TOTO board"
477 depends on ARCH_OMAP && OMAP_TOTO
479 This enables access to the NOR flash on the Texas Instruments
483 tristate "Hynix evaluation board mappings"
484 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
486 This enables access to the flash chips on the Hynix evaluation boards.
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.
527 tristate "Generic uClinux RAM/ROM filesystem support"
528 depends on MTD_PARTITIONS && !MMU
530 Map driver to support image based filesystems for uClinux.
533 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
534 depends on (SBC82xx || SBC8560)
535 select MTD_PARTITIONS
536 select MTD_MAP_BANK_WIDTH_4
537 select MTD_MAP_BANK_WIDTH_1
541 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
542 all three flash regions on CS0, CS1 and CS6 if they are configured
543 correctly by the boot loader.
546 tristate "Map driver for Dy-4 SVME/DMV-182 board."
548 select MTD_PARTITIONS
549 select MTD_MAP_BANK_WIDTH_32
551 select MTD_CFI_AMDSTD
553 Map driver for Dy-4 SVME/DMV-182 board.
556 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
557 depends on ARCH_BAST || MACH_VR1000
558 select MTD_PARTITIONS
559 select MTD_MAP_BANK_WIDTH_16
560 select MTD_JEDECPROBE
562 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
565 Note, this driver *cannot* over-ride the WP link on the
566 board, or currently detect the state of the link.
568 config MTD_BAST_MAXSIZE
569 int "Maximum size for BAST flash area (MiB)"
574 tristate "ROM mapped on Sharp SL Series"
577 This enables access to the flash chip on the Sharp SL Series of PDAs.
579 config MTD_INTEL_VR_NOR
580 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
583 Map driver for a NOR flash bank located on the Expansion Bus of the
584 Intel Vermilion Range chipset.
587 tristate "Map driver for platform device RAM (mtd-ram)"
590 Map driver for RAM areas described via the platform device
593 This selection automatically selects the map_ram driver.