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 "Sun Microsystems userflash support"
65 depends on SPARC && 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 && MTD_CONCAT
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"
100 select MTD_CFI_AMDSTD
102 This provides a driver for the on-board flash of the Technologic
103 System's TS-5500 board. The 2MB flash is split into 3 partitions
104 which are accessed as separate MTD devices.
106 mtd0 and mtd2 are the two BIOS drives, which use the resident
107 flash disk (RFD) flash translation layer.
109 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
111 Note that jumper 3 ("Write Enable Drive A") must be set
112 otherwise detection won't succeed.
115 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
116 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
118 This provides a driver for the on-board flash of Arcom Control
119 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
120 By default the flash is split into 3 partitions which are accessed
121 as separate MTD devices. This board utilizes Intel StrataFlash.
123 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
126 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
127 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
129 This provides a driver for the on-board flash of the Intel
130 'Lubbock' XScale evaluation board.
133 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
134 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
135 select MTD_PARTITIONS
137 This provides a driver for the on-board flash of the Intel
138 'Mainstone PXA27x evaluation board.
141 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
142 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
144 This provides a 'mapping' driver which supports the way in which
145 the flash chips are connected in the Octagon-5066 Single Board
146 Computer. More information on the board is available at
147 <http://www.octagonsystems.com/CPUpages/5066.html>.
150 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
151 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
153 This provides a 'mapping' driver which supports the way in which
154 the flash chips are connected in the Tempustech VMAX SBC301 Single
155 Board Computer. More information on the board is available at
156 <http://www.tempustech.com/>.
158 config MTD_SCx200_DOCFLASH
159 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
160 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
162 Enable support for a flash chip mapped using the DOCCS signal on a
163 National Semiconductor SCx200 processor.
165 If you don't know what to do here, say N.
167 If compiled as a module, it will be called scx200_docflash.
170 tristate "BIOS flash chip on AMD76x southbridge"
171 depends on X86 && MTD_JEDECPROBE
173 Support for treating the BIOS flash chip on AMD76x motherboards
174 as an MTD device - with this you can reprogram your BIOS.
179 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
180 depends on X86 && MTD_JEDECPROBE
182 Support for treating the BIOS flash chip on ICHX motherboards
183 as an MTD device - with this you can reprogram your BIOS.
188 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
189 depends on X86 && MTD_JEDECPROBE
191 Support for treating the BIOS flash chip on ESB2 motherboards
192 as an MTD device - with this you can reprogram your BIOS.
197 tristate "BIOS flash chip on Nvidia CK804"
198 depends on X86 && MTD_JEDECPROBE
200 Support for treating the BIOS flash chip on nvidia motherboards
201 as an MTD device - with this you can reprogram your BIOS.
205 config MTD_SCB2_FLASH
206 tristate "BIOS flash chip on Intel SCB2 boards"
207 depends on X86 && MTD_JEDECPROBE
209 Support for treating the BIOS flash chip on Intel SCB2 boards
210 as an MTD device - with this you can reprogram your BIOS.
215 tristate "Flash chips on Tsunami TIG bus"
216 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
218 Support for the flash chip on Tsunami TIG bus.
221 tristate "LASAT flash device"
222 depends on LASAT && MTD_CFI
224 Support for the flash chips on the Lasat 100 and 200 boards.
227 tristate "CFI flash device on SnapGear/SecureEdge"
228 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
230 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
233 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
234 depends on SOC_AU1X00
236 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
239 tristate "4G Systems MTX-1 Flash device"
240 depends on MIPS && MIPS_MTX1
242 Flash memory access on 4G Systems MTX-1 Board. If you have one of
243 these boards and would like to use the flash chips on it, say 'Y'.
246 tristate "CFI Flash device mapped on DIL/Net PC"
247 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
249 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
250 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
251 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
253 config MTD_DILNETPC_BOOTSIZE
254 hex "Size of DIL/Net PC flash boot partition"
255 depends on MTD_DILNETPC
258 The amount of space taken up by the kernel or Etherboot
259 on the DIL/Net PC flash chips.
262 tristate "BIOS flash chip on Intel L440GX boards"
263 depends on X86 && MTD_JEDECPROBE
265 Support for treating the BIOS flash chip on Intel L440GX motherboards
266 as an MTD device - with this you can reprogram your BIOS.
271 tristate "Flash device on SBC8240"
272 depends on MTD_JEDECPROBE && 8260
274 Flash access on the SBC8240 board from Wind River. See
275 <http://www.windriver.com/products/sbc8240/>
278 tristate "CFI Flash device mapped on TQM8XXL"
279 depends on MTD_CFI && TQM8xxL
281 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
282 chips, currently uses AMD one. This 'mapping' driver supports
283 that arrangement, allowing the CFI probe and command set driver
284 code to communicate with the chips on the TQM8xxL board. More at
285 <http://www.denx.de/embedded-ppc-en.html>.
288 tristate "CFI Flash device mapped on RPX Lite or CLLF"
289 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
291 The RPXLite PowerPC board has CFI-compliant chips mapped in
292 a strange sparse mapping. This 'mapping' driver supports that
293 arrangement, allowing the CFI probe and command set driver code
294 to communicate with the chips on the RPXLite board. More at
295 <http://www.embeddedplanet.com/>.
298 tristate "System flash on MBX860 board"
299 depends on MTD_CFI && MBX
301 This enables access routines for the flash chips on the Motorola
302 MBX860 board. If you have one of these boards and would like
303 to use the flash chips on it, say 'Y'.
306 tristate "CFI Flash device mapped on D-Box2"
307 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
309 This enables access routines for the flash chips on the Nokia/Sagem
310 D-Box 2 board. If you have one of these boards and would like to use
311 the flash chips on it, say 'Y'.
313 config MTD_CFI_FLAGADM
314 tristate "CFI Flash device mapping on FlagaDM"
315 depends on 8xx && MTD_CFI
317 Mapping for the Flaga digital module. If you don't have one, ignore
321 tristate "CFI Flash device mapped on IBM 405LP Beech"
322 depends on MTD_CFI && BEECH
324 This enables access routines for the flash chips on the IBM
325 405LP Beech board. If you have one of these boards and would like
326 to use the flash chips on it, say 'Y'.
329 tristate "CFI Flash device mapped on IBM 405LP Arctic"
330 depends on MTD_CFI && ARCTIC2
332 This enables access routines for the flash chips on the IBM 405LP
333 Arctic board. If you have one of these boards and would like to
334 use the flash chips on it, say 'Y'.
337 tristate "Flash device mapped on IBM 405GP Walnut"
338 depends on MTD_JEDECPROBE && WALNUT
340 This enables access routines for the flash chips on the IBM 405GP
341 Walnut board. If you have one of these boards and would like to
342 use the flash chips on it, say 'Y'.
345 tristate "Flash devices mapped on IBM 440GP Ebony"
346 depends on MTD_JEDECPROBE && EBONY
348 This enables access routines for the flash chips on the IBM 440GP
349 Ebony board. If you have one of these boards and would like to
350 use the flash chips on it, say 'Y'.
353 tristate "Flash devices mapped on IBM 440GX Ocotea"
354 depends on MTD_CFI && OCOTEA
356 This enables access routines for the flash chips on the IBM 440GX
357 Ocotea board. If you have one of these boards and would like to
358 use the flash chips on it, say 'Y'.
361 tristate "CFI Flash devices mapped on IBM Redwood"
362 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
364 This enables access routines for the flash chips on the IBM
365 Redwood board. If you have one of these boards and would like to
366 use the flash chips on it, say 'Y'.
369 tristate "Flash device mapped on TQ Components TQM834x Boards"
370 depends on MTD_CFI && TQM834x
372 This enables access routines for the flash chips on the
373 TQ Components TQM834x boards. If you have one of these boards
374 and would like to use the flash chips on it, say 'Y'.
376 config MTD_CSTM_MIPS_IXX
377 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
378 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
380 This provides a mapping driver for the Integrated Technology
381 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
382 Reference Board. It provides the necessary addressing, length,
383 buswidth, vpp code and addition setup of the flash device for
384 these boards. In addition, this mapping driver can be used for
385 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
386 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
387 using one partition. The start address can be offset from the
388 beginning of flash and the len can be less than the total flash
389 device size to allow a window into the flash. Both CFI and JEDEC
392 config MTD_CSTM_MIPS_IXX_START
393 hex "Physical start address of flash mapping"
394 depends on MTD_CSTM_MIPS_IXX
397 This is the physical memory location that the MTD driver will
398 use for the flash chips on your particular target board.
399 Refer to the memory map which should hopefully be in the
400 documentation for your board.
402 config MTD_CSTM_MIPS_IXX_LEN
403 hex "Physical length of flash mapping"
404 depends on MTD_CSTM_MIPS_IXX
407 This is the total length that the MTD driver will use for the
408 flash chips on your particular board. Refer to the memory
409 map which should hopefully be in the documentation for your
412 config MTD_CSTM_MIPS_IXX_BUSWIDTH
413 int "Bus width in octets"
414 depends on MTD_CSTM_MIPS_IXX
417 This is the total bus width of the mapping of the flash chips
418 on your particular board.
421 tristate "Momenco Ocelot boot flash device"
422 depends on MIPS && MOMENCO_OCELOT
424 This enables access routines for the boot flash device and for the
425 NVRAM on the Momenco Ocelot board. If you have one of these boards
426 and would like access to either of these, say 'Y'.
428 config MTD_SOLUTIONENGINE
429 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
430 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
432 This enables access to the flash chips on the Hitachi SolutionEngine and
433 similar boards. Say 'Y' if you are building a kernel for such a board.
435 config MTD_ARM_INTEGRATOR
436 tristate "CFI Flash device mapped on ARM Integrator/P720T"
437 depends on ARM && MTD_CFI
440 tristate "Cirrus CDB89712 evaluation board mappings"
441 depends on MTD_CFI && ARCH_CDB89712
443 This enables access to the flash or ROM chips on the CDB89712 board.
444 If you have such a board, say 'Y'.
447 tristate "CFI Flash device mapped on StrongARM SA11x0"
448 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
450 This enables access to the flash chips on most platforms based on
451 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
452 If you have such a board, say 'Y'.
455 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
456 depends on IPAQ_HANDHELD && MTD_CFI
458 This provides a driver for the on-board flash of the iPAQ.
461 tristate "CFI Flash device mapped on DC21285 Footbridge"
462 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
464 This provides a driver for the flash accessed using Intel's
465 21285 bridge used with Intel's StrongARM processors. More info at
466 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
469 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
470 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
472 This enables MTD access to flash devices on platforms based
473 on Intel's IXP4xx family of network processors such as the
474 IXDP425 and Coyote. If you have an IXP4xx based board and
475 would like to use the flash chips on it, say 'Y'.
478 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
479 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
481 This enables MTD access to flash devices on platforms based
482 on Intel's IXP2000 family of network processors such as the
483 IXDP425 and Coyote. If you have an IXP2000 based board and
484 would like to use the flash chips on it, say 'Y'.
487 tristate "CFI Flash device mapped on the FortuNet board"
488 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
490 This enables access to the Flash on the FortuNet board. If you
491 have such a board, say 'Y'.
494 tristate "NV-RAM mapping AUTCPU12 board"
495 depends on ARCH_AUTCPU12
497 This enables access to the NV-RAM on autronix autcpu12 board.
498 If you have such a board, say 'Y'.
501 tristate "CFI Flash device mapped on EDB7312"
502 depends on ARCH_EDB7312 && MTD_CFI
504 This enables access to the CFI Flash on the Cogent EDB7312 board.
505 If you have such a board, say 'Y' here.
508 tristate "JEDEC Flash device mapped on impA7"
509 depends on ARM && MTD_JEDECPROBE
511 This enables access to the NOR Flash on the impA7 board of
512 implementa GmbH. If you have such a board, say 'Y' here.
515 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
516 depends on MTD_JEDECPROBE && ARCH_CEIVA
518 This enables access to the flash chips on the Ceiva/Polaroid
519 PhotoMax Digital Picture Frame.
520 If you have such a device, say 'Y'.
523 tristate "NOR Flash device on TOTO board"
524 depends on ARCH_OMAP && OMAP_TOTO
526 This enables access to the NOR flash on the Texas Instruments
530 tristate "Hynix evaluation board mappings"
531 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
533 This enables access to the flash chips on the Hynix evaluation boards.
534 If you have such a board, say 'Y'.
537 tristate "CFI Flash device mapped on Interface MPC-1211"
538 depends on SH_MPC1211 && MTD_CFI
540 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
541 If you have such a board, say 'Y'.
544 tristate "TI OMAP board mappings"
545 depends on MTD_CFI && ARCH_OMAP
547 This enables access to the NOR flash chips on TI OMAP-based
548 boards defining flash platform devices and flash platform data.
549 These boards include the Innovator, H2, H3, OSK, Perseus2, and
550 more. If you have such a board, say 'Y'.
552 # This needs CFI or JEDEC, depending on the cards found.
554 tristate "PCI MTD driver"
555 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
557 Mapping for accessing flash devices on add-in cards like the Intel XScale
558 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
559 (please see the manual for the link settings).
561 If you are not sure, say N.
564 tristate "PCMCIA MTD driver"
565 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
567 Map driver for accessing PCMCIA linear flash memory cards. These
568 cards are usually around 4-16MiB in size. This does not include
569 Compact Flash cards which are treated as IDE devices.
571 config MTD_PCMCIA_ANONYMOUS
572 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
573 depends on MTD_PCMCIA
575 If this option is enabled, PCMCIA cards which do not report
576 anything about themselves are assumed to be MTD cards.
581 tristate "Generic uClinux RAM/ROM filesystem support"
582 depends on MTD_PARTITIONS && !MMU
584 Map driver to support image based filesystems for uClinux.
587 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
588 depends on (SBC82xx || SBC8560)
589 select MTD_PARTITIONS
590 select MTD_MAP_BANK_WIDTH_4
591 select MTD_MAP_BANK_WIDTH_1
595 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
596 all three flash regions on CS0, CS1 and CS6 if they are configured
597 correctly by the boot loader.
600 tristate "Map driver for Dy-4 SVME/DMV-182 board."
602 select MTD_PARTITIONS
603 select MTD_MAP_BANK_WIDTH_32
605 select MTD_CFI_AMDSTD
607 Map driver for Dy-4 SVME/DMV-182 board.
610 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
611 depends on ARCH_BAST || MACH_VR1000
612 select MTD_PARTITIONS
613 select MTD_MAP_BANK_WIDTH_16
614 select MTD_JEDECPROBE
616 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
619 Note, this driver *cannot* over-ride the WP link on the
620 board, or currently detect the state of the link.
622 config MTD_BAST_MAXSIZE
623 int "Maximum size for BAST flash area (MiB)"
628 bool "ROM maped on Sharp SL Series"
629 depends on MTD && ARCH_PXA
631 This enables access to the flash chip on the Sharp SL Series of PDAs.
634 tristate "Map driver for platform device RAM (mtd-ram)"
638 Map driver for RAM areas described via the platform device
641 This selection automatically selects the map_ram driver.