1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.59 2005/09/18 10:46:41 joern Exp $
4 menu "Mapping drivers for chip access"
7 config MTD_COMPLEX_MAPPINGS
8 bool "Support non-linear mappings of flash chips"
11 This causes the chip drivers to allow for complicated
12 paged mappings of flash chips.
15 tristate "CFI Flash device in physical memory map"
18 This provides a 'mapping' driver which allows the CFI probe and
19 command set driver code to communicate with flash chips which
20 are mapped physically into the CPU's memory. You will need to
21 configure the physical address and size of the flash chips on
22 your particular board as well as the bus width, either statically
23 with config options or at run-time.
25 config MTD_PHYSMAP_START
26 hex "Physical start address of flash mapping"
27 depends on MTD_PHYSMAP
30 This is the physical memory location at which the flash chips
31 are mapped on your particular target board. Refer to the
32 memory map which should hopefully be in the documentation for
34 Ignore this option if you use run-time physmap configuration
35 (i.e., run-time calling physmap_configure()).
37 config MTD_PHYSMAP_LEN
38 hex "Physical length of flash mapping"
39 depends on MTD_PHYSMAP
42 This is the total length of the mapping of the flash chips on
43 your particular board. If there is space, or aliases, in the
44 physical memory map between the chips, this could be larger
45 than the total amount of flash present. Refer to the memory
46 map which should hopefully be in the documentation for your
48 Ignore this option if you use run-time physmap configuration
49 (i.e., run-time calling physmap_configure()).
51 config MTD_PHYSMAP_BANKWIDTH
52 int "Bank width in octets"
53 depends on MTD_PHYSMAP
56 This is the total width of the data bus of the flash devices
57 in octets. For example, if you have a data bus width of 32
58 bits, you would set the bus width octect value to 4. This is
59 used internally by the CFI drivers.
60 Ignore this option if you use run-time physmap configuration
61 (i.e., run-time calling physmap_configure()).
64 tristate "Sun Microsystems userflash support"
65 depends on (SPARC32 || SPARC64) && MTD_CFI
67 This provides a 'mapping' driver which supports the way in
68 which user-programmable flash chips are connected on various
69 Sun Microsystems boardsets. This driver will require CFI support
70 in the kernel, so if you did not enable CFI previously, do that now.
73 tristate "CFI Flash device mapped on Photron PNC-2000"
74 depends on X86 && MTD_CFI && MTD_PARTITIONS
76 PNC-2000 is the name of Network Camera product from PHOTRON
77 Ltd. in Japan. It uses CFI-compliant flash.
80 tristate "CFI Flash device mapped on AMD SC520 CDP"
81 depends on X86 && MTD_CFI
83 The SC520 CDP board has two banks of CFI-compliant chips and one
84 Dual-in-line JEDEC chip. This 'mapping' driver supports that
85 arrangement, implementing three MTD devices.
88 tristate "CFI Flash device mapped on AMD NetSc520"
89 depends on X86 && MTD_CFI && MTD_PARTITIONS
91 This enables access routines for the flash chips on the AMD NetSc520
92 demonstration board. If you have one of these boards and would like
93 to use the flash chips on it, say 'Y'.
96 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
97 depends on X86 && MTD_JEDECPROBE && MTD_PARTITIONS
99 This provides a driver for the on-board flash of the Technologic
100 System's TS-5500 board. The 2MB flash is split into 3 partitions
101 which are accessed as separate MTD devices.
103 mtd0 and mtd2 are the two BIOS drives, which use the resident
104 flash disk (RFD) flash translation layer.
106 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
108 Note that jumper 3 ("Write Enable Drive A") must be set
109 otherwise detection won't succeeed.
112 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
113 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
115 This provides a driver for the on-board flash of Arcom Control
116 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
117 By default the flash is split into 3 partitions which are accessed
118 as separate MTD devices. This board utilizes Intel StrataFlash.
120 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
123 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
124 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
126 This provides a driver for the on-board flash of the Intel
127 'Lubbock' XScale evaluation board.
130 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
131 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
132 select MTD_PARTITIONS
134 This provides a driver for the on-board flash of the Intel
135 'Mainstone PXA27x evaluation board.
138 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
139 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
141 This provides a 'mapping' driver which supports the way in which
142 the flash chips are connected in the Octagon-5066 Single Board
143 Computer. More information on the board is available at
144 <http://www.octagonsystems.com/CPUpages/5066.html>.
147 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
148 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
150 This provides a 'mapping' driver which supports the way in which
151 the flash chips are connected in the Tempustech VMAX SBC301 Single
152 Board Computer. More information on the board is available at
153 <http://www.tempustech.com/>.
155 config MTD_SCx200_DOCFLASH
156 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
157 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
159 Enable support for a flash chip mapped using the DOCCS signal on a
160 National Semiconductor SCx200 processor.
162 If you don't know what to do here, say N.
164 If compiled as a module, it will be called scx200_docflash.
167 tristate "BIOS flash chip on AMD76x southbridge"
168 depends on X86 && MTD_JEDECPROBE
170 Support for treating the BIOS flash chip on AMD76x motherboards
171 as an MTD device - with this you can reprogram your BIOS.
176 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
177 depends on X86 && MTD_JEDECPROBE
179 Support for treating the BIOS flash chip on ICHX motherboards
180 as an MTD device - with this you can reprogram your BIOS.
184 config MTD_SCB2_FLASH
185 tristate "BIOS flash chip on Intel SCB2 boards"
186 depends on X86 && MTD_JEDECPROBE
188 Support for treating the BIOS flash chip on Intel SCB2 boards
189 as an MTD device - with this you can reprogram your BIOS.
194 tristate "Flash chips on Tsunami TIG bus"
195 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
197 Support for the flash chip on Tsunami TIG bus.
200 tristate "Flash chips on LASAT board"
203 Support for the flash chips on the Lasat 100 and 200 boards.
206 tristate "CFI flash device on SnapGear/SecureEdge"
207 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
209 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
212 tristate ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support'
213 depends on MIPS && SOC_AU1X00
215 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
218 tristate "4G Systems MTX-1 Flash device"
219 depends on MIPS && MIPS_MTX1
221 Flash memory access on 4G Systems MTX-1 Board. If you have one of
222 these boards and would like to use the flash chips on it, say 'Y'.
225 tristate "CFI Flash device mapped on DIL/Net PC"
226 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
228 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
229 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
230 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
232 config MTD_DILNETPC_BOOTSIZE
233 hex "Size of DIL/Net PC flash boot partition"
234 depends on MTD_DILNETPC
237 The amount of space taken up by the kernel or Etherboot
238 on the DIL/Net PC flash chips.
241 tristate "BIOS flash chip on Intel L440GX boards"
242 depends on X86 && MTD_JEDECPROBE
244 Support for treating the BIOS flash chip on Intel L440GX motherboards
245 as an MTD device - with this you can reprogram your BIOS.
250 tristate "Flash device on SBC8240"
251 depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260
253 Flash access on the SBC8240 board from Wind River. See
254 <http://www.windriver.com/products/sbc8240/>
257 tristate "CFI Flash device mapped on TQM8XXL"
258 depends on MTD_CFI && PPC32 && 8xx && TQM8xxL
260 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
261 chips, currently uses AMD one. This 'mapping' driver supports
262 that arrangement, allowing the CFI probe and command set driver
263 code to communicate with the chips on the TQM8xxL board. More at
264 <http://www.denx.de/embedded-ppc-en.html>.
267 tristate "CFI Flash device mapped on RPX Lite or CLLF"
268 depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)
270 The RPXLite PowerPC board has CFI-compliant chips mapped in
271 a strange sparse mapping. This 'mapping' driver supports that
272 arrangement, allowing the CFI probe and command set driver code
273 to communicate with the chips on the RPXLite board. More at
274 <http://www.embeddedplanet.com/>.
277 tristate "System flash on MBX860 board"
278 depends on MTD_CFI && PPC32 && 8xx && MBX
280 This enables access routines for the flash chips on the Motorola
281 MBX860 board. If you have one of these boards and would like
282 to use the flash chips on it, say 'Y'.
285 tristate "CFI Flash device mapped on D-Box2"
286 depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
288 This enables access routines for the flash chips on the Nokia/Sagem
289 D-Box 2 board. If you have one of these boards and would like to use
290 the flash chips on it, say 'Y'.
292 config MTD_CFI_FLAGADM
293 tristate "CFI Flash device mapping on FlagaDM"
294 depends on PPC32 && 8xx && MTD_CFI
296 Mapping for the Flaga digital module. If you don't have one, ignore
300 tristate "CFI Flash device mapped on IBM 405LP Beech"
301 depends on MTD_CFI && PPC32 && 40x && BEECH
303 This enables access routines for the flash chips on the IBM
304 405LP Beech 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 IBM 405LP Arctic"
309 depends on MTD_CFI && PPC32 && 40x && ARCTIC2
311 This enables access routines for the flash chips on the IBM 405LP
312 Arctic board. If you have one of these boards and would like to
313 use the flash chips on it, say 'Y'.
316 tristate "Flash device mapped on IBM 405GP Walnut"
317 depends on MTD_JEDECPROBE && PPC32 && 40x && WALNUT
319 This enables access routines for the flash chips on the IBM 405GP
320 Walnut board. If you have one of these boards and would like to
321 use the flash chips on it, say 'Y'.
324 tristate "Flash devices mapped on IBM 440GP Ebony"
325 depends on MTD_JEDECPROBE && PPC32 && 44x && EBONY
327 This enables access routines for the flash chips on the IBM 440GP
328 Ebony board. If you have one of these boards and would like to
329 use the flash chips on it, say 'Y'.
332 tristate "Flash devices mapped on IBM 440GX Ocotea"
333 depends on MTD_CFI && PPC32 && 44x && OCOTEA
335 This enables access routines for the flash chips on the IBM 440GX
336 Ocotea board. If you have one of these boards and would like to
337 use the flash chips on it, say 'Y'.
340 tristate "CFI Flash devices mapped on IBM Redwood"
341 depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
343 This enables access routines for the flash chips on the IBM
344 Redwood board. If you have one of these boards and would like to
345 use the flash chips on it, say 'Y'.
347 config MTD_CSTM_MIPS_IXX
348 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
349 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
351 This provides a mapping driver for the Integrated Technology
352 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
353 Reference Board. It provides the necessary addressing, length,
354 buswidth, vpp code and addition setup of the flash device for
355 these boards. In addition, this mapping driver can be used for
356 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
357 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
358 using one partition. The start address can be offset from the
359 beginning of flash and the len can be less than the total flash
360 device size to allow a window into the flash. Both CFI and JEDEC
363 config MTD_CSTM_MIPS_IXX_START
364 hex "Physical start address of flash mapping"
365 depends on MTD_CSTM_MIPS_IXX
368 This is the physical memory location that the MTD driver will
369 use for the flash chips on your particular target board.
370 Refer to the memory map which should hopefully be in the
371 documentation for your board.
373 config MTD_CSTM_MIPS_IXX_LEN
374 hex "Physical length of flash mapping"
375 depends on MTD_CSTM_MIPS_IXX
378 This is the total length that the MTD driver will use for the
379 flash chips on your particular board. Refer to the memory
380 map which should hopefully be in the documentation for your
383 config MTD_CSTM_MIPS_IXX_BUSWIDTH
384 int "Bus width in octets"
385 depends on MTD_CSTM_MIPS_IXX
388 This is the total bus width of the mapping of the flash chips
389 on your particular board.
392 tristate "Momenco Ocelot boot flash device"
393 depends on MIPS && MOMENCO_OCELOT
395 This enables access routines for the boot flash device and for the
396 NVRAM on the Momenco Ocelot board. If you have one of these boards
397 and would like access to either of these, say 'Y'.
399 config MTD_SOLUTIONENGINE
400 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
401 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
403 This enables access to the flash chips on the Hitachi SolutionEngine and
404 similar boards. Say 'Y' if you are building a kernel for such a board.
406 config MTD_ARM_INTEGRATOR
407 tristate "CFI Flash device mapped on ARM Integrator/P720T"
408 depends on ARM && MTD_CFI
411 tristate "Cirrus CDB89712 evaluation board mappings"
412 depends on ARM && MTD_CFI && ARCH_CDB89712
414 This enables access to the flash or ROM chips on the CDB89712 board.
415 If you have such a board, say 'Y'.
418 tristate "CFI Flash device mapped on StrongARM SA11x0"
419 depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
421 This enables access to the flash chips on most platforms based on
422 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
423 If you have such a board, say 'Y'.
426 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
427 depends on ARM && IPAQ_HANDHELD && MTD_CFI
429 This provides a driver for the on-board flash of the iPAQ.
432 tristate "CFI Flash device mapped on DC21285 Footbridge"
433 depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
435 This provides a driver for the flash accessed using Intel's
436 21285 bridge used with Intel's StrongARM processors. More info at
437 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
440 tristate "CFI Flash device mapped on the XScale IQ80310 board"
441 depends on ARM && MTD_CFI && ARCH_IQ80310
443 This enables access routines for the flash chips on the Intel XScale
444 IQ80310 evaluation board. If you have one of these boards and would
445 like to use the flash chips on it, say 'Y'.
448 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
449 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
451 This enables MTD access to flash devices on platforms based
452 on Intel's IXP4xx family of network processors such as the
453 IXDP425 and Coyote. If you have an IXP4xx based board and
454 would like to use the flash chips on it, say 'Y'.
457 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
458 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
460 This enables MTD access to flash devices on platforms based
461 on Intel's IXP2000 family of network processors such as the
462 IXDP425 and Coyote. If you have an IXP2000 based board and
463 would like to use the flash chips on it, say 'Y'.
466 tristate "CFI Flash device mapped on Epxa10db"
467 depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
469 This enables support for the flash devices on the Altera
470 Excalibur XA10 Development Board. If you are building a kernel
471 for on of these boards then you should say 'Y' otherwise say 'N'.
474 tristate "CFI Flash device mapped on the FortuNet board"
475 depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
477 This enables access to the Flash on the FortuNet board. If you
478 have such a board, say 'Y'.
481 tristate "NV-RAM mapping AUTCPU12 board"
482 depends on ARM && ARCH_AUTCPU12
484 This enables access to the NV-RAM on autronix autcpu12 board.
485 If you have such a board, say 'Y'.
488 tristate "CFI Flash device mapped on EDB7312"
489 depends on ARM && MTD_CFI
491 This enables access to the CFI Flash on the Cogent EDB7312 board.
492 If you have such a board, say 'Y' here.
495 tristate "JEDEC Flash device mapped on impA7"
496 depends on ARM && MTD_JEDECPROBE
498 This enables access to the NOR Flash on the impA7 board of
499 implementa GmbH. If you have such a board, say 'Y' here.
502 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
503 depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA
505 This enables access to the flash chips on the Ceiva/Polaroid
506 PhotoMax Digital Picture Frame.
507 If you have such a device, say 'Y'.
510 tristate "NOR Flash device on TOTO board"
511 depends on ARM && ARCH_OMAP && OMAP_TOTO
513 This enables access to the NOR flash on the Texas Instruments
517 tristate "Hynix evaluation board mappings"
518 depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
520 This enables access to the flash chips on the Hynix evaluation boards.
521 If you have such a board, say 'Y'.
524 tristate "CFI Flash device mapped on Interface MPC-1211"
525 depends on SUPERH && SH_MPC1211 && MTD_CFI
527 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
528 If you have such a board, say 'Y'.
531 tristate "JEDEC flash SIMM mapped on PQ2FADS and 8272ADS boards"
532 depends on (ADS8272 || PQ2FADS) && MTD_PARTITIONS && MTD_JEDECPROBE && MTD_PHYSMAP && MTD_CFI_GEOMETRY && MTD_CFI_INTELEXT
534 This enables access to flash SIMM on PQ2FADS-like boards
537 tristate "TI OMAP board mappings"
538 depends on MTD_CFI && ARCH_OMAP
540 This enables access to the NOR flash chips on TI OMAP-based
541 boards defining flash platform devices and flash platform data.
542 These boards include the Innovator, H2, H3, OSK, Perseus2, and
543 more. If you have such a board, say 'Y'.
545 # This needs CFI or JEDEC, depending on the cards found.
547 tristate "PCI MTD driver"
548 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
550 Mapping for accessing flash devices on add-in cards like the Intel XScale
551 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
552 (please see the manual for the link settings).
554 If you are not sure, say N.
557 tristate "PCMCIA MTD driver"
558 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
560 Map driver for accessing PCMCIA linear flash memory cards. These
561 cards are usually around 4-16MiB in size. This does not include
562 Compact Flash cards which are treated as IDE devices.
564 config MTD_PCMCIA_ANONYMOUS
565 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
566 depends on MTD_PCMCIA
569 If this option is enabled, PCMCIA cards which do not report
570 anything about themselves are assumed to be MTD cards.
575 tristate "Generic uClinux RAM/ROM filesystem support"
576 depends on MTD_PARTITIONS && !MMU
578 Map driver to support image based filesystems for uClinux.
581 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
582 depends on (SBC82xx || SBC8560)
583 select MTD_PARTITIONS
584 select MTD_MAP_BANK_WIDTH_4
585 select MTD_MAP_BANK_WIDTH_1
589 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
590 all three flash regions on CS0, CS1 and CS6 if they are configured
591 correctly by the boot loader.
594 tristate "Map driver for Dy-4 SVME/DMV-182 board."
596 select MTD_PARTITIONS
597 select MTD_MAP_BANK_WIDTH_32
599 select MTD_CFI_AMDSTD
601 Map driver for Dy-4 SVME/DMV-182 board.
604 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
605 depends on ARCH_BAST || MACH_VR1000
606 select MTD_PARTITIONS
607 select MTD_MAP_BANK_WIDTH_16
608 select MTD_JEDECPROBE
610 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
613 Note, this driver *cannot* over-ride the WP link on the
614 board, or currently detect the state of the link.
616 config MTD_BAST_MAXSIZE
617 int "Maximum size for BAST flash area (MiB)"
622 bool "ROM maped on Sharp SL Series"
623 depends on MTD && ARCH_PXA
625 This enables access to the flash chip on the Sharp SL Series of PDAs.
628 tristate "Map driver for platform device RAM (mtd-ram)"
632 Map driver for RAM areas described via the platform device
635 This selection automatically selects the map_ram driver.