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 config MTD_PHYSMAP_START
25 hex "Physical start address of flash mapping"
26 depends on MTD_PHYSMAP
29 This is the physical memory location at which the flash chips
30 are mapped on your particular target board. Refer to the
31 memory map which should hopefully be in the documentation for
33 Ignore this option if you use run-time physmap configuration
34 (i.e., run-time calling physmap_configure()).
36 config MTD_PHYSMAP_LEN
37 hex "Physical length of flash mapping"
38 depends on MTD_PHYSMAP
41 This is the total length of the mapping of the flash chips on
42 your particular board. If there is space, or aliases, in the
43 physical memory map between the chips, this could be larger
44 than the total amount of flash present. Refer to the memory
45 map which should hopefully be in the documentation for your
47 Ignore this option if you use run-time physmap configuration
48 (i.e., run-time calling physmap_configure()).
50 config MTD_PHYSMAP_BANKWIDTH
51 int "Bank width in octets"
52 depends on MTD_PHYSMAP
55 This is the total width of the data bus of the flash devices
56 in octets. For example, if you have a data bus width of 32
57 bits, you would set the bus width octect value to 4. This is
58 used internally by the CFI drivers.
59 Ignore this option if you use run-time physmap configuration
60 (i.e., run-time calling physmap_configure()).
63 tristate "Flash device in physical memory map based on OF description"
64 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
66 This provides a 'mapping' driver which allows the NOR Flash and
67 ROM driver code to communicate with chips which are mapped
68 physically into the CPU's memory. The mapping description here is
69 taken from OF device tree.
71 config MTD_PMC_MSP_EVM
72 tristate "CFI Flash device mapped on PMC-Sierra MSP"
73 depends on PMC_MSP && MTD_CFI
76 This provides a 'mapping' driver which support the way
77 in which user-programmable flash chips are connected on the
78 PMC-Sierra MSP eval/demo boards
81 prompt "Maximum mappable memory avialable for flash IO"
82 depends on MTD_PMC_MSP_EVM
83 default MSP_FLASH_MAP_LIMIT_32M
85 config MSP_FLASH_MAP_LIMIT_32M
90 config MSP_FLASH_MAP_LIMIT
93 depends on MSP_FLASH_MAP_LIMIT_32M
95 config MTD_PMC_MSP_RAMROOT
96 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
97 depends on PMC_MSP_EMBEDDED_ROOTFS && \
98 (MTD_BLOCK || MTD_BLOCK_RO) && \
101 This provides support for the embedded root file system
102 on PMC MSP devices. This memory is mapped as a MTD block device.
104 config MTD_SUN_UFLASH
105 tristate "Sun Microsystems userflash support"
106 depends on SPARC && MTD_CFI
108 This provides a 'mapping' driver which supports the way in
109 which user-programmable flash chips are connected on various
110 Sun Microsystems boardsets. This driver will require CFI support
111 in the kernel, so if you did not enable CFI previously, do that now.
114 tristate "CFI Flash device mapped on Photron PNC-2000"
115 depends on X86 && MTD_CFI && MTD_PARTITIONS
117 PNC-2000 is the name of Network Camera product from PHOTRON
118 Ltd. in Japan. It uses CFI-compliant flash.
121 tristate "CFI Flash device mapped on AMD SC520 CDP"
122 depends on X86 && MTD_CFI && MTD_CONCAT
124 The SC520 CDP board has two banks of CFI-compliant chips and one
125 Dual-in-line JEDEC chip. This 'mapping' driver supports that
126 arrangement, implementing three MTD devices.
129 tristate "CFI Flash device mapped on AMD NetSc520"
130 depends on X86 && MTD_CFI && MTD_PARTITIONS
132 This enables access routines for the flash chips on the AMD NetSc520
133 demonstration board. If you have one of these boards and would like
134 to use the flash chips on it, say 'Y'.
137 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
139 select MTD_PARTITIONS
140 select MTD_JEDECPROBE
141 select MTD_CFI_AMDSTD
143 This provides a driver for the on-board flash of the Technologic
144 System's TS-5500 board. The 2MB flash is split into 3 partitions
145 which are accessed as separate MTD devices.
147 mtd0 and mtd2 are the two BIOS drives, which use the resident
148 flash disk (RFD) flash translation layer.
150 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
152 Note that jumper 3 ("Write Enable Drive A") must be set
153 otherwise detection won't succeed.
156 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
157 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
159 This provides a driver for the on-board flash of Arcom Control
160 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
161 By default the flash is split into 3 partitions which are accessed
162 as separate MTD devices. This board utilizes Intel StrataFlash.
164 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
167 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
168 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
170 This provides a driver for the on-board flash of the Intel
171 'Lubbock' XScale evaluation board.
174 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
175 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
176 select MTD_PARTITIONS
178 This provides a driver for the on-board flash of the Intel
179 'Mainstone PXA27x evaluation board.
182 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
183 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
185 This provides a 'mapping' driver which supports the way in which
186 the flash chips are connected in the Octagon-5066 Single Board
187 Computer. More information on the board is available at
188 <http://www.octagonsystems.com/CPUpages/5066.html>.
191 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
192 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
194 This provides a 'mapping' driver which supports the way in which
195 the flash chips are connected in the Tempustech VMAX SBC301 Single
196 Board Computer. More information on the board is available at
197 <http://www.tempustech.com/>.
199 config MTD_SCx200_DOCFLASH
200 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
201 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
203 Enable support for a flash chip mapped using the DOCCS signal on a
204 National Semiconductor SCx200 processor.
206 If you don't know what to do here, say N.
208 If compiled as a module, it will be called scx200_docflash.
211 tristate "BIOS flash chip on AMD76x southbridge"
212 depends on X86 && MTD_JEDECPROBE
214 Support for treating the BIOS flash chip on AMD76x motherboards
215 as an MTD device - with this you can reprogram your BIOS.
220 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
221 depends on X86 && MTD_JEDECPROBE
223 Support for treating the BIOS flash chip on ICHX motherboards
224 as an MTD device - with this you can reprogram your BIOS.
229 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
230 depends on X86 && MTD_JEDECPROBE && PCI
232 Support for treating the BIOS flash chip on ESB2 motherboards
233 as an MTD device - with this you can reprogram your BIOS.
238 tristate "BIOS flash chip on Nvidia CK804"
239 depends on X86 && MTD_JEDECPROBE && PCI
241 Support for treating the BIOS flash chip on nvidia motherboards
242 as an MTD device - with this you can reprogram your BIOS.
246 config MTD_SCB2_FLASH
247 tristate "BIOS flash chip on Intel SCB2 boards"
248 depends on X86 && MTD_JEDECPROBE
250 Support for treating the BIOS flash chip on Intel SCB2 boards
251 as an MTD device - with this you can reprogram your BIOS.
256 tristate "Flash chips on Tsunami TIG bus"
257 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
259 Support for the flash chip on Tsunami TIG bus.
262 tristate "CFI flash device on SnapGear/SecureEdge"
263 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
265 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
268 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
269 depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
271 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
274 tristate "4G Systems MTX-1 Flash device"
275 depends on MIPS_MTX1 && MTD_CFI
277 Flash memory access on 4G Systems MTX-1 Board. If you have one of
278 these boards and would like to use the flash chips on it, say 'Y'.
281 tristate "CFI Flash device mapped on DIL/Net PC"
282 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
284 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
285 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
286 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
288 config MTD_DILNETPC_BOOTSIZE
289 hex "Size of DIL/Net PC flash boot partition"
290 depends on MTD_DILNETPC
293 The amount of space taken up by the kernel or Etherboot
294 on the DIL/Net PC flash chips.
297 tristate "BIOS flash chip on Intel L440GX boards"
298 depends on X86 && MTD_JEDECPROBE
300 Support for treating the BIOS flash chip on Intel L440GX motherboards
301 as an MTD device - with this you can reprogram your BIOS.
306 tristate "Flash device on SBC8240"
307 depends on MTD_JEDECPROBE && 8260
309 Flash access on the SBC8240 board from Wind River. See
310 <http://www.windriver.com/products/sbc8240/>
313 tristate "CFI Flash device mapped on TQM8XXL"
314 depends on MTD_CFI && TQM8xxL
316 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
317 chips, currently uses AMD one. This 'mapping' driver supports
318 that arrangement, allowing the CFI probe and command set driver
319 code to communicate with the chips on the TQM8xxL board. More at
320 <http://www.denx.de/embedded-ppc-en.html>.
323 tristate "CFI Flash device mapped on RPX Lite or CLLF"
324 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
326 The RPXLite PowerPC board has CFI-compliant chips mapped in
327 a strange sparse mapping. This 'mapping' driver supports that
328 arrangement, allowing the CFI probe and command set driver code
329 to communicate with the chips on the RPXLite board. More at
330 <http://www.embeddedplanet.com/>.
333 tristate "System flash on MBX860 board"
334 depends on MTD_CFI && MBX
336 This enables access routines for the flash chips on the Motorola
337 MBX860 board. If you have one of these boards and would like
338 to use the flash chips on it, say 'Y'.
341 tristate "CFI Flash device mapped on D-Box2"
342 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
344 This enables access routines for the flash chips on the Nokia/Sagem
345 D-Box 2 board. If you have one of these boards and would like to use
346 the flash chips on it, say 'Y'.
348 config MTD_CFI_FLAGADM
349 tristate "CFI Flash device mapping on FlagaDM"
350 depends on 8xx && MTD_CFI
352 Mapping for the Flaga digital module. If you don't have one, ignore
356 tristate "Flash device mapped on IBM 405GP Walnut"
357 depends on MTD_JEDECPROBE && WALNUT
359 This enables access routines for the flash chips on the IBM 405GP
360 Walnut board. If you have one of these boards and would like to
361 use the flash chips on it, say 'Y'.
364 tristate "Flash devices mapped on IBM 440GP Ebony"
365 depends on MTD_JEDECPROBE && EBONY
367 This enables access routines for the flash chips on the IBM 440GP
368 Ebony board. If you have one of these boards and would like to
369 use the flash chips on it, say 'Y'.
372 tristate "Flash devices mapped on IBM 440GX Ocotea"
373 depends on MTD_CFI && OCOTEA
375 This enables access routines for the flash chips on the IBM 440GX
376 Ocotea board. If you have one of these boards and would like to
377 use the flash chips on it, say 'Y'.
380 tristate "CFI Flash devices mapped on IBM Redwood"
381 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
383 This enables access routines for the flash chips on the IBM
384 Redwood board. If you have one of these boards and would like to
385 use the flash chips on it, say 'Y'.
388 tristate "Flash device mapped on TQ Components TQM834x Boards"
389 depends on MTD_CFI && TQM834x
391 This enables access routines for the flash chips on the
392 TQ Components TQM834x boards. If you have one of these boards
393 and would like to use the flash chips on it, say 'Y'.
396 tristate "Momenco Ocelot boot flash device"
397 depends on MOMENCO_OCELOT
399 This enables access routines for the boot flash device and for the
400 NVRAM on the Momenco Ocelot board. If you have one of these boards
401 and would like access to either of these, say 'Y'.
403 config MTD_SOLUTIONENGINE
404 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
405 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
407 This enables access to the flash chips on the Hitachi SolutionEngine and
408 similar boards. Say 'Y' if you are building a kernel for such a board.
410 config MTD_ARM_INTEGRATOR
411 tristate "CFI Flash device mapped on ARM Integrator/P720T"
412 depends on ARM && MTD_CFI
415 tristate "Cirrus CDB89712 evaluation board mappings"
416 depends on MTD_CFI && ARCH_CDB89712
418 This enables access to the flash or ROM chips on the CDB89712 board.
419 If you have such a board, say 'Y'.
422 tristate "CFI Flash device mapped on StrongARM SA11x0"
423 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
425 This enables access to the flash chips on most platforms based on
426 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
427 If you have such a board, say 'Y'.
430 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
431 depends on IPAQ_HANDHELD && MTD_CFI
433 This provides a driver for the on-board flash of the iPAQ.
436 tristate "CFI Flash device mapped on DC21285 Footbridge"
437 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
439 This provides a driver for the flash accessed using Intel's
440 21285 bridge used with Intel's StrongARM processors. More info at
441 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
444 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
445 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
447 This enables MTD access to flash devices on platforms based
448 on Intel's IXP4xx family of network processors such as the
449 IXDP425 and Coyote. If you have an IXP4xx based board and
450 would like to use the flash chips on it, say 'Y'.
453 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
454 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
456 This enables MTD access to flash devices on platforms based
457 on Intel's IXP2000 family of network processors such as the
458 IXDP425 and Coyote. If you have an IXP2000 based board and
459 would like to use the flash chips on it, say 'Y'.
462 tristate "CFI Flash device mapped on the FortuNet board"
463 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
465 This enables access to the Flash on the FortuNet board. If you
466 have such a board, say 'Y'.
469 tristate "NV-RAM mapping AUTCPU12 board"
470 depends on ARCH_AUTCPU12
472 This enables access to the NV-RAM on autronix autcpu12 board.
473 If you have such a board, say 'Y'.
476 tristate "CFI Flash device mapped on EDB7312"
477 depends on ARCH_EDB7312 && MTD_CFI
479 This enables access to the CFI Flash on the Cogent EDB7312 board.
480 If you have such a board, say 'Y' here.
483 tristate "JEDEC Flash device mapped on impA7"
484 depends on ARM && MTD_JEDECPROBE
486 This enables access to the NOR Flash on the impA7 board of
487 implementa GmbH. If you have such a board, say 'Y' here.
490 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
491 depends on MTD_JEDECPROBE && ARCH_CEIVA
493 This enables access to the flash chips on the Ceiva/Polaroid
494 PhotoMax Digital Picture Frame.
495 If you have such a device, say 'Y'.
498 tristate "NOR Flash device on TOTO board"
499 depends on ARCH_OMAP && OMAP_TOTO
501 This enables access to the NOR flash on the Texas Instruments
505 tristate "Hynix evaluation board mappings"
506 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
508 This enables access to the flash chips on the Hynix evaluation boards.
509 If you have such a board, say 'Y'.
512 tristate "CFI Flash device mapped on Interface MPC-1211"
513 depends on SH_MPC1211 && MTD_CFI
515 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
516 If you have such a board, say 'Y'.
519 tristate "TI OMAP board mappings"
520 depends on MTD_CFI && ARCH_OMAP
522 This enables access to the NOR flash chips on TI OMAP-based
523 boards defining flash platform devices and flash platform data.
524 These boards include the Innovator, H2, H3, OSK, Perseus2, and
525 more. If you have such a board, say 'Y'.
527 # This needs CFI or JEDEC, depending on the cards found.
529 tristate "PCI MTD driver"
530 depends on PCI && MTD_COMPLEX_MAPPINGS
532 Mapping for accessing flash devices on add-in cards like the Intel XScale
533 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
534 (please see the manual for the link settings).
536 If you are not sure, say N.
539 tristate "PCMCIA MTD driver"
540 depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
542 Map driver for accessing PCMCIA linear flash memory cards. These
543 cards are usually around 4-16MiB in size. This does not include
544 Compact Flash cards which are treated as IDE devices.
546 config MTD_PCMCIA_ANONYMOUS
547 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
548 depends on MTD_PCMCIA
550 If this option is enabled, PCMCIA cards which do not report
551 anything about themselves are assumed to be MTD cards.
556 tristate "Generic uClinux RAM/ROM filesystem support"
557 depends on MTD_PARTITIONS && !MMU
559 Map driver to support image based filesystems for uClinux.
562 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
563 depends on (SBC82xx || SBC8560)
564 select MTD_PARTITIONS
565 select MTD_MAP_BANK_WIDTH_4
566 select MTD_MAP_BANK_WIDTH_1
570 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
571 all three flash regions on CS0, CS1 and CS6 if they are configured
572 correctly by the boot loader.
575 tristate "Map driver for Dy-4 SVME/DMV-182 board."
577 select MTD_PARTITIONS
578 select MTD_MAP_BANK_WIDTH_32
580 select MTD_CFI_AMDSTD
582 Map driver for Dy-4 SVME/DMV-182 board.
585 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
586 depends on ARCH_BAST || MACH_VR1000
587 select MTD_PARTITIONS
588 select MTD_MAP_BANK_WIDTH_16
589 select MTD_JEDECPROBE
591 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
594 Note, this driver *cannot* over-ride the WP link on the
595 board, or currently detect the state of the link.
597 config MTD_BAST_MAXSIZE
598 int "Maximum size for BAST flash area (MiB)"
603 bool "ROM mapped on Sharp SL Series"
606 This enables access to the flash chip on the Sharp SL Series of PDAs.
609 tristate "Map driver for platform device RAM (mtd-ram)"
612 Map driver for RAM areas described via the platform device
615 This selection automatically selects the map_ram driver.