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"
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"
16 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
18 This provides a 'mapping' driver which allows the NOR Flash and
19 ROM driver code to communicate with chips which are mapped
20 physically into the CPU's memory. You will need to configure
21 the physical address and size of the flash chips on your
22 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 "Flash device in physical memory map based on OF descirption"
65 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
67 This provides a 'mapping' driver which allows the NOR Flash and
68 ROM driver code to communicate with chips which are mapped
69 physically into the CPU's memory. The mapping description here is
70 taken from OF device tree.
72 config MTD_PMC_MSP_EVM
73 tristate "CFI Flash device mapped on PMC-Sierra MSP"
74 depends on PMC_MSP && MTD_CFI
77 This provides a 'mapping' driver which support the way
78 in which user-programmable flash chips are connected on the
79 PMC-Sierra MSP eval/demo boards
82 prompt "Maximum mappable memory avialable for flash IO"
83 depends on MTD_PMC_MSP_EVM
84 default MSP_FLASH_MAP_LIMIT_32M
86 config MSP_FLASH_MAP_LIMIT_32M
91 config MSP_FLASH_MAP_LIMIT
94 depends on MSP_FLASH_MAP_LIMIT_32M
96 config MTD_PMC_MSP_RAMROOT
97 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
98 depends on PMC_MSP_EMBEDDED_ROOTFS && \
99 (MTD_BLOCK || MTD_BLOCK_RO) && \
102 This provides support for the embedded root file system
103 on PMC MSP devices. This memory is mapped as a MTD block device.
105 config MTD_SUN_UFLASH
106 tristate "Sun Microsystems userflash support"
107 depends on SPARC && MTD_CFI
109 This provides a 'mapping' driver which supports the way in
110 which user-programmable flash chips are connected on various
111 Sun Microsystems boardsets. This driver will require CFI support
112 in the kernel, so if you did not enable CFI previously, do that now.
115 tristate "CFI Flash device mapped on Photron PNC-2000"
116 depends on X86 && MTD_CFI && MTD_PARTITIONS
118 PNC-2000 is the name of Network Camera product from PHOTRON
119 Ltd. in Japan. It uses CFI-compliant flash.
122 tristate "CFI Flash device mapped on AMD SC520 CDP"
123 depends on X86 && MTD_CFI && MTD_CONCAT
125 The SC520 CDP board has two banks of CFI-compliant chips and one
126 Dual-in-line JEDEC chip. This 'mapping' driver supports that
127 arrangement, implementing three MTD devices.
130 tristate "CFI Flash device mapped on AMD NetSc520"
131 depends on X86 && MTD_CFI && MTD_PARTITIONS
133 This enables access routines for the flash chips on the AMD NetSc520
134 demonstration board. If you have one of these boards and would like
135 to use the flash chips on it, say 'Y'.
138 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
140 select MTD_PARTITIONS
141 select MTD_JEDECPROBE
142 select MTD_CFI_AMDSTD
144 This provides a driver for the on-board flash of the Technologic
145 System's TS-5500 board. The 2MB flash is split into 3 partitions
146 which are accessed as separate MTD devices.
148 mtd0 and mtd2 are the two BIOS drives, which use the resident
149 flash disk (RFD) flash translation layer.
151 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
153 Note that jumper 3 ("Write Enable Drive A") must be set
154 otherwise detection won't succeed.
157 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
158 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
160 This provides a driver for the on-board flash of Arcom Control
161 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
162 By default the flash is split into 3 partitions which are accessed
163 as separate MTD devices. This board utilizes Intel StrataFlash.
165 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
168 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
169 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
171 This provides a driver for the on-board flash of the Intel
172 'Lubbock' XScale evaluation board.
175 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
176 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
177 select MTD_PARTITIONS
179 This provides a driver for the on-board flash of the Intel
180 'Mainstone PXA27x evaluation board.
183 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
184 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
186 This provides a 'mapping' driver which supports the way in which
187 the flash chips are connected in the Octagon-5066 Single Board
188 Computer. More information on the board is available at
189 <http://www.octagonsystems.com/CPUpages/5066.html>.
192 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
193 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
195 This provides a 'mapping' driver which supports the way in which
196 the flash chips are connected in the Tempustech VMAX SBC301 Single
197 Board Computer. More information on the board is available at
198 <http://www.tempustech.com/>.
200 config MTD_SCx200_DOCFLASH
201 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
202 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
204 Enable support for a flash chip mapped using the DOCCS signal on a
205 National Semiconductor SCx200 processor.
207 If you don't know what to do here, say N.
209 If compiled as a module, it will be called scx200_docflash.
212 tristate "BIOS flash chip on AMD76x southbridge"
213 depends on X86 && MTD_JEDECPROBE
215 Support for treating the BIOS flash chip on AMD76x motherboards
216 as an MTD device - with this you can reprogram your BIOS.
221 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
222 depends on X86 && MTD_JEDECPROBE
224 Support for treating the BIOS flash chip on ICHX motherboards
225 as an MTD device - with this you can reprogram your BIOS.
230 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
231 depends on X86 && MTD_JEDECPROBE && PCI
233 Support for treating the BIOS flash chip on ESB2 motherboards
234 as an MTD device - with this you can reprogram your BIOS.
239 tristate "BIOS flash chip on Nvidia CK804"
240 depends on X86 && MTD_JEDECPROBE && PCI
242 Support for treating the BIOS flash chip on nvidia motherboards
243 as an MTD device - with this you can reprogram your BIOS.
247 config MTD_SCB2_FLASH
248 tristate "BIOS flash chip on Intel SCB2 boards"
249 depends on X86 && MTD_JEDECPROBE
251 Support for treating the BIOS flash chip on Intel SCB2 boards
252 as an MTD device - with this you can reprogram your BIOS.
257 tristate "Flash chips on Tsunami TIG bus"
258 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
260 Support for the flash chip on Tsunami TIG bus.
263 tristate "LASAT flash device"
264 depends on LASAT && MTD_CFI
266 Support for the flash chips on the Lasat 100 and 200 boards.
269 tristate "CFI flash device on SnapGear/SecureEdge"
270 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
272 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
275 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
276 depends on SOC_AU1X00
278 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
281 tristate "4G Systems MTX-1 Flash device"
282 depends on MIPS && MIPS_MTX1
284 Flash memory access on 4G Systems MTX-1 Board. If you have one of
285 these boards and would like to use the flash chips on it, say 'Y'.
288 tristate "CFI Flash device mapped on DIL/Net PC"
289 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
291 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
292 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
293 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
295 config MTD_DILNETPC_BOOTSIZE
296 hex "Size of DIL/Net PC flash boot partition"
297 depends on MTD_DILNETPC
300 The amount of space taken up by the kernel or Etherboot
301 on the DIL/Net PC flash chips.
304 tristate "BIOS flash chip on Intel L440GX boards"
305 depends on X86 && MTD_JEDECPROBE
307 Support for treating the BIOS flash chip on Intel L440GX motherboards
308 as an MTD device - with this you can reprogram your BIOS.
313 tristate "Flash device on SBC8240"
314 depends on MTD_JEDECPROBE && 8260
316 Flash access on the SBC8240 board from Wind River. See
317 <http://www.windriver.com/products/sbc8240/>
320 tristate "CFI Flash device mapped on TQM8XXL"
321 depends on MTD_CFI && TQM8xxL
323 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
324 chips, currently uses AMD one. This 'mapping' driver supports
325 that arrangement, allowing the CFI probe and command set driver
326 code to communicate with the chips on the TQM8xxL board. More at
327 <http://www.denx.de/embedded-ppc-en.html>.
330 tristate "CFI Flash device mapped on RPX Lite or CLLF"
331 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
333 The RPXLite PowerPC board has CFI-compliant chips mapped in
334 a strange sparse mapping. This 'mapping' driver supports that
335 arrangement, allowing the CFI probe and command set driver code
336 to communicate with the chips on the RPXLite board. More at
337 <http://www.embeddedplanet.com/>.
340 tristate "System flash on MBX860 board"
341 depends on MTD_CFI && MBX
343 This enables access routines for the flash chips on the Motorola
344 MBX860 board. If you have one of these boards and would like
345 to use the flash chips on it, say 'Y'.
348 tristate "CFI Flash device mapped on D-Box2"
349 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
351 This enables access routines for the flash chips on the Nokia/Sagem
352 D-Box 2 board. If you have one of these boards and would like to use
353 the flash chips on it, say 'Y'.
355 config MTD_CFI_FLAGADM
356 tristate "CFI Flash device mapping on FlagaDM"
357 depends on 8xx && MTD_CFI
359 Mapping for the Flaga digital module. If you don't have one, ignore
363 tristate "CFI Flash device mapped on IBM 405LP Beech"
364 depends on MTD_CFI && BEECH
366 This enables access routines for the flash chips on the IBM
367 405LP Beech board. If you have one of these boards and would like
368 to use the flash chips on it, say 'Y'.
371 tristate "CFI Flash device mapped on IBM 405LP Arctic"
372 depends on MTD_CFI && ARCTIC2
374 This enables access routines for the flash chips on the IBM 405LP
375 Arctic board. If you have one of these boards and would like to
376 use the flash chips on it, say 'Y'.
379 tristate "Flash device mapped on IBM 405GP Walnut"
380 depends on MTD_JEDECPROBE && WALNUT
382 This enables access routines for the flash chips on the IBM 405GP
383 Walnut board. If you have one of these boards and would like to
384 use the flash chips on it, say 'Y'.
387 tristate "Flash devices mapped on IBM 440GP Ebony"
388 depends on MTD_JEDECPROBE && EBONY
390 This enables access routines for the flash chips on the IBM 440GP
391 Ebony board. If you have one of these boards and would like to
392 use the flash chips on it, say 'Y'.
395 tristate "Flash devices mapped on IBM 440GX Ocotea"
396 depends on MTD_CFI && OCOTEA
398 This enables access routines for the flash chips on the IBM 440GX
399 Ocotea board. If you have one of these boards and would like to
400 use the flash chips on it, say 'Y'.
403 tristate "CFI Flash devices mapped on IBM Redwood"
404 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
406 This enables access routines for the flash chips on the IBM
407 Redwood board. If you have one of these boards and would like to
408 use the flash chips on it, say 'Y'.
411 tristate "Flash device mapped on TQ Components TQM834x Boards"
412 depends on MTD_CFI && TQM834x
414 This enables access routines for the flash chips on the
415 TQ Components TQM834x boards. If you have one of these boards
416 and would like to use the flash chips on it, say 'Y'.
419 tristate "Momenco Ocelot boot flash device"
420 depends on MIPS && MOMENCO_OCELOT
422 This enables access routines for the boot flash device and for the
423 NVRAM on the Momenco Ocelot board. If you have one of these boards
424 and would like access to either of these, say 'Y'.
426 config MTD_SOLUTIONENGINE
427 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
428 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
430 This enables access to the flash chips on the Hitachi SolutionEngine and
431 similar boards. Say 'Y' if you are building a kernel for such a board.
433 config MTD_ARM_INTEGRATOR
434 tristate "CFI Flash device mapped on ARM Integrator/P720T"
435 depends on ARM && MTD_CFI
438 tristate "Cirrus CDB89712 evaluation board mappings"
439 depends on MTD_CFI && ARCH_CDB89712
441 This enables access to the flash or ROM chips on the CDB89712 board.
442 If you have such a board, say 'Y'.
445 tristate "CFI Flash device mapped on StrongARM SA11x0"
446 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
448 This enables access to the flash chips on most platforms based on
449 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
450 If you have such a board, say 'Y'.
453 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
454 depends on IPAQ_HANDHELD && MTD_CFI
456 This provides a driver for the on-board flash of the iPAQ.
459 tristate "CFI Flash device mapped on DC21285 Footbridge"
460 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
462 This provides a driver for the flash accessed using Intel's
463 21285 bridge used with Intel's StrongARM processors. More info at
464 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
467 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
468 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
470 This enables MTD access to flash devices on platforms based
471 on Intel's IXP4xx family of network processors such as the
472 IXDP425 and Coyote. If you have an IXP4xx based board and
473 would like to use the flash chips on it, say 'Y'.
476 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
477 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
479 This enables MTD access to flash devices on platforms based
480 on Intel's IXP2000 family of network processors such as the
481 IXDP425 and Coyote. If you have an IXP2000 based board and
482 would like to use the flash chips on it, say 'Y'.
485 tristate "CFI Flash device mapped on the FortuNet board"
486 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
488 This enables access to the Flash on the FortuNet board. If you
489 have such a board, say 'Y'.
492 tristate "NV-RAM mapping AUTCPU12 board"
493 depends on ARCH_AUTCPU12
495 This enables access to the NV-RAM on autronix autcpu12 board.
496 If you have such a board, say 'Y'.
499 tristate "CFI Flash device mapped on EDB7312"
500 depends on ARCH_EDB7312 && MTD_CFI
502 This enables access to the CFI Flash on the Cogent EDB7312 board.
503 If you have such a board, say 'Y' here.
506 tristate "JEDEC Flash device mapped on impA7"
507 depends on ARM && MTD_JEDECPROBE
509 This enables access to the NOR Flash on the impA7 board of
510 implementa GmbH. If you have such a board, say 'Y' here.
513 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
514 depends on MTD_JEDECPROBE && ARCH_CEIVA
516 This enables access to the flash chips on the Ceiva/Polaroid
517 PhotoMax Digital Picture Frame.
518 If you have such a device, say 'Y'.
521 tristate "NOR Flash device on TOTO board"
522 depends on ARCH_OMAP && OMAP_TOTO
524 This enables access to the NOR flash on the Texas Instruments
528 tristate "Hynix evaluation board mappings"
529 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
531 This enables access to the flash chips on the Hynix evaluation boards.
532 If you have such a board, say 'Y'.
535 tristate "CFI Flash device mapped on Interface MPC-1211"
536 depends on SH_MPC1211 && MTD_CFI
538 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
539 If you have such a board, say 'Y'.
542 tristate "TI OMAP board mappings"
543 depends on MTD_CFI && ARCH_OMAP
545 This enables access to the NOR flash chips on TI OMAP-based
546 boards defining flash platform devices and flash platform data.
547 These boards include the Innovator, H2, H3, OSK, Perseus2, and
548 more. If you have such a board, say 'Y'.
550 # This needs CFI or JEDEC, depending on the cards found.
552 tristate "PCI MTD driver"
553 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
555 Mapping for accessing flash devices on add-in cards like the Intel XScale
556 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
557 (please see the manual for the link settings).
559 If you are not sure, say N.
562 tristate "PCMCIA MTD driver"
563 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
565 Map driver for accessing PCMCIA linear flash memory cards. These
566 cards are usually around 4-16MiB in size. This does not include
567 Compact Flash cards which are treated as IDE devices.
569 config MTD_PCMCIA_ANONYMOUS
570 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
571 depends on MTD_PCMCIA
573 If this option is enabled, PCMCIA cards which do not report
574 anything about themselves are assumed to be MTD cards.
579 tristate "Generic uClinux RAM/ROM filesystem support"
580 depends on MTD_PARTITIONS && !MMU
582 Map driver to support image based filesystems for uClinux.
585 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
586 depends on (SBC82xx || SBC8560)
587 select MTD_PARTITIONS
588 select MTD_MAP_BANK_WIDTH_4
589 select MTD_MAP_BANK_WIDTH_1
593 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
594 all three flash regions on CS0, CS1 and CS6 if they are configured
595 correctly by the boot loader.
598 tristate "Map driver for Dy-4 SVME/DMV-182 board."
600 select MTD_PARTITIONS
601 select MTD_MAP_BANK_WIDTH_32
603 select MTD_CFI_AMDSTD
605 Map driver for Dy-4 SVME/DMV-182 board.
608 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
609 depends on ARCH_BAST || MACH_VR1000
610 select MTD_PARTITIONS
611 select MTD_MAP_BANK_WIDTH_16
612 select MTD_JEDECPROBE
614 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
617 Note, this driver *cannot* over-ride the WP link on the
618 board, or currently detect the state of the link.
620 config MTD_BAST_MAXSIZE
621 int "Maximum size for BAST flash area (MiB)"
626 bool "ROM mapped on Sharp SL Series"
627 depends on MTD && ARCH_PXA
629 This enables access to the flash chip on the Sharp SL Series of PDAs.
632 tristate "Map driver for platform device RAM (mtd-ram)"
636 Map driver for RAM areas described via the platform device
639 This selection automatically selects the map_ram driver.