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.
73 tristate "Sun Microsystems userflash support"
74 depends on SPARC && MTD_CFI
76 This provides a 'mapping' driver which supports the way in
77 which user-programmable flash chips are connected on various
78 Sun Microsystems boardsets. This driver will require CFI support
79 in the kernel, so if you did not enable CFI previously, do that now.
82 tristate "CFI Flash device mapped on Photron PNC-2000"
83 depends on X86 && MTD_CFI && MTD_PARTITIONS
85 PNC-2000 is the name of Network Camera product from PHOTRON
86 Ltd. in Japan. It uses CFI-compliant flash.
89 tristate "CFI Flash device mapped on AMD SC520 CDP"
90 depends on X86 && MTD_CFI && MTD_CONCAT
92 The SC520 CDP board has two banks of CFI-compliant chips and one
93 Dual-in-line JEDEC chip. This 'mapping' driver supports that
94 arrangement, implementing three MTD devices.
97 tristate "CFI Flash device mapped on AMD NetSc520"
98 depends on X86 && MTD_CFI && MTD_PARTITIONS
100 This enables access routines for the flash chips on the AMD NetSc520
101 demonstration board. If you have one of these boards and would like
102 to use the flash chips on it, say 'Y'.
105 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
107 select MTD_PARTITIONS
108 select MTD_JEDECPROBE
109 select MTD_CFI_AMDSTD
111 This provides a driver for the on-board flash of the Technologic
112 System's TS-5500 board. The 2MB flash is split into 3 partitions
113 which are accessed as separate MTD devices.
115 mtd0 and mtd2 are the two BIOS drives, which use the resident
116 flash disk (RFD) flash translation layer.
118 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
120 Note that jumper 3 ("Write Enable Drive A") must be set
121 otherwise detection won't succeed.
124 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
125 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
127 This provides a driver for the on-board flash of Arcom Control
128 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
129 By default the flash is split into 3 partitions which are accessed
130 as separate MTD devices. This board utilizes Intel StrataFlash.
132 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
135 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
136 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
138 This provides a driver for the on-board flash of the Intel
139 'Lubbock' XScale evaluation board.
142 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
143 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
144 select MTD_PARTITIONS
146 This provides a driver for the on-board flash of the Intel
147 'Mainstone PXA27x evaluation board.
150 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
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 Octagon-5066 Single Board
155 Computer. More information on the board is available at
156 <http://www.octagonsystems.com/CPUpages/5066.html>.
159 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
160 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
162 This provides a 'mapping' driver which supports the way in which
163 the flash chips are connected in the Tempustech VMAX SBC301 Single
164 Board Computer. More information on the board is available at
165 <http://www.tempustech.com/>.
167 config MTD_SCx200_DOCFLASH
168 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
169 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
171 Enable support for a flash chip mapped using the DOCCS signal on a
172 National Semiconductor SCx200 processor.
174 If you don't know what to do here, say N.
176 If compiled as a module, it will be called scx200_docflash.
179 tristate "BIOS flash chip on AMD76x southbridge"
180 depends on X86 && MTD_JEDECPROBE
182 Support for treating the BIOS flash chip on AMD76x motherboards
183 as an MTD device - with this you can reprogram your BIOS.
188 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
189 depends on X86 && MTD_JEDECPROBE
191 Support for treating the BIOS flash chip on ICHX motherboards
192 as an MTD device - with this you can reprogram your BIOS.
197 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
198 depends on X86 && MTD_JEDECPROBE
200 Support for treating the BIOS flash chip on ESB2 motherboards
201 as an MTD device - with this you can reprogram your BIOS.
206 tristate "BIOS flash chip on Nvidia CK804"
207 depends on X86 && MTD_JEDECPROBE
209 Support for treating the BIOS flash chip on nvidia motherboards
210 as an MTD device - with this you can reprogram your BIOS.
214 config MTD_SCB2_FLASH
215 tristate "BIOS flash chip on Intel SCB2 boards"
216 depends on X86 && MTD_JEDECPROBE
218 Support for treating the BIOS flash chip on Intel SCB2 boards
219 as an MTD device - with this you can reprogram your BIOS.
224 tristate "Flash chips on Tsunami TIG bus"
225 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
227 Support for the flash chip on Tsunami TIG bus.
230 tristate "LASAT flash device"
231 depends on LASAT && MTD_CFI
233 Support for the flash chips on the Lasat 100 and 200 boards.
236 tristate "CFI flash device on SnapGear/SecureEdge"
237 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
239 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
242 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
243 depends on SOC_AU1X00
245 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
248 tristate "4G Systems MTX-1 Flash device"
249 depends on MIPS && MIPS_MTX1
251 Flash memory access on 4G Systems MTX-1 Board. If you have one of
252 these boards and would like to use the flash chips on it, say 'Y'.
255 tristate "CFI Flash device mapped on DIL/Net PC"
256 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
258 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
259 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
260 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
262 config MTD_DILNETPC_BOOTSIZE
263 hex "Size of DIL/Net PC flash boot partition"
264 depends on MTD_DILNETPC
267 The amount of space taken up by the kernel or Etherboot
268 on the DIL/Net PC flash chips.
271 tristate "BIOS flash chip on Intel L440GX boards"
272 depends on X86 && MTD_JEDECPROBE
274 Support for treating the BIOS flash chip on Intel L440GX motherboards
275 as an MTD device - with this you can reprogram your BIOS.
280 tristate "Flash device on SBC8240"
281 depends on MTD_JEDECPROBE && 8260
283 Flash access on the SBC8240 board from Wind River. See
284 <http://www.windriver.com/products/sbc8240/>
287 tristate "CFI Flash device mapped on TQM8XXL"
288 depends on MTD_CFI && TQM8xxL
290 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
291 chips, currently uses AMD one. This 'mapping' driver supports
292 that arrangement, allowing the CFI probe and command set driver
293 code to communicate with the chips on the TQM8xxL board. More at
294 <http://www.denx.de/embedded-ppc-en.html>.
297 tristate "CFI Flash device mapped on RPX Lite or CLLF"
298 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
300 The RPXLite PowerPC board has CFI-compliant chips mapped in
301 a strange sparse mapping. This 'mapping' driver supports that
302 arrangement, allowing the CFI probe and command set driver code
303 to communicate with the chips on the RPXLite board. More at
304 <http://www.embeddedplanet.com/>.
307 tristate "System flash on MBX860 board"
308 depends on MTD_CFI && MBX
310 This enables access routines for the flash chips on the Motorola
311 MBX860 board. If you have one of these boards and would like
312 to use the flash chips on it, say 'Y'.
315 tristate "CFI Flash device mapped on D-Box2"
316 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
318 This enables access routines for the flash chips on the Nokia/Sagem
319 D-Box 2 board. If you have one of these boards and would like to use
320 the flash chips on it, say 'Y'.
322 config MTD_CFI_FLAGADM
323 tristate "CFI Flash device mapping on FlagaDM"
324 depends on 8xx && MTD_CFI
326 Mapping for the Flaga digital module. If you don't have one, ignore
330 tristate "CFI Flash device mapped on IBM 405LP Beech"
331 depends on MTD_CFI && BEECH
333 This enables access routines for the flash chips on the IBM
334 405LP Beech board. If you have one of these boards and would like
335 to use the flash chips on it, say 'Y'.
338 tristate "CFI Flash device mapped on IBM 405LP Arctic"
339 depends on MTD_CFI && ARCTIC2
341 This enables access routines for the flash chips on the IBM 405LP
342 Arctic board. If you have one of these boards and would like to
343 use the flash chips on it, say 'Y'.
346 tristate "Flash device mapped on IBM 405GP Walnut"
347 depends on MTD_JEDECPROBE && WALNUT
349 This enables access routines for the flash chips on the IBM 405GP
350 Walnut board. If you have one of these boards and would like to
351 use the flash chips on it, say 'Y'.
354 tristate "Flash devices mapped on IBM 440GP Ebony"
355 depends on MTD_JEDECPROBE && EBONY
357 This enables access routines for the flash chips on the IBM 440GP
358 Ebony board. If you have one of these boards and would like to
359 use the flash chips on it, say 'Y'.
362 tristate "Flash devices mapped on IBM 440GX Ocotea"
363 depends on MTD_CFI && OCOTEA
365 This enables access routines for the flash chips on the IBM 440GX
366 Ocotea board. If you have one of these boards and would like to
367 use the flash chips on it, say 'Y'.
370 tristate "CFI Flash devices mapped on IBM Redwood"
371 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
373 This enables access routines for the flash chips on the IBM
374 Redwood board. If you have one of these boards and would like to
375 use the flash chips on it, say 'Y'.
378 tristate "Flash device mapped on TQ Components TQM834x Boards"
379 depends on MTD_CFI && TQM834x
381 This enables access routines for the flash chips on the
382 TQ Components TQM834x boards. If you have one of these boards
383 and would like to use the flash chips on it, say 'Y'.
385 config MTD_CSTM_MIPS_IXX
386 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
387 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
389 This provides a mapping driver for the Integrated Technology
390 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
391 Reference Board. It provides the necessary addressing, length,
392 buswidth, vpp code and addition setup of the flash device for
393 these boards. In addition, this mapping driver can be used for
394 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
395 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
396 using one partition. The start address can be offset from the
397 beginning of flash and the len can be less than the total flash
398 device size to allow a window into the flash. Both CFI and JEDEC
401 config MTD_CSTM_MIPS_IXX_START
402 hex "Physical start address of flash mapping"
403 depends on MTD_CSTM_MIPS_IXX
406 This is the physical memory location that the MTD driver will
407 use for the flash chips on your particular target board.
408 Refer to the memory map which should hopefully be in the
409 documentation for your board.
411 config MTD_CSTM_MIPS_IXX_LEN
412 hex "Physical length of flash mapping"
413 depends on MTD_CSTM_MIPS_IXX
416 This is the total length that the MTD driver will use for the
417 flash chips on your particular board. Refer to the memory
418 map which should hopefully be in the documentation for your
421 config MTD_CSTM_MIPS_IXX_BUSWIDTH
422 int "Bus width in octets"
423 depends on MTD_CSTM_MIPS_IXX
426 This is the total bus width of the mapping of the flash chips
427 on your particular board.
430 tristate "Momenco Ocelot boot flash device"
431 depends on MIPS && MOMENCO_OCELOT
433 This enables access routines for the boot flash device and for the
434 NVRAM on the Momenco Ocelot board. If you have one of these boards
435 and would like access to either of these, say 'Y'.
437 config MTD_SOLUTIONENGINE
438 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
439 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
441 This enables access to the flash chips on the Hitachi SolutionEngine and
442 similar boards. Say 'Y' if you are building a kernel for such a board.
444 config MTD_ARM_INTEGRATOR
445 tristate "CFI Flash device mapped on ARM Integrator/P720T"
446 depends on ARM && MTD_CFI
449 tristate "Cirrus CDB89712 evaluation board mappings"
450 depends on MTD_CFI && ARCH_CDB89712
452 This enables access to the flash or ROM chips on the CDB89712 board.
453 If you have such a board, say 'Y'.
456 tristate "CFI Flash device mapped on StrongARM SA11x0"
457 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
459 This enables access to the flash chips on most platforms based on
460 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
461 If you have such a board, say 'Y'.
464 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
465 depends on IPAQ_HANDHELD && MTD_CFI
467 This provides a driver for the on-board flash of the iPAQ.
470 tristate "CFI Flash device mapped on DC21285 Footbridge"
471 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
473 This provides a driver for the flash accessed using Intel's
474 21285 bridge used with Intel's StrongARM processors. More info at
475 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
478 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
479 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
481 This enables MTD access to flash devices on platforms based
482 on Intel's IXP4xx family of network processors such as the
483 IXDP425 and Coyote. If you have an IXP4xx based board and
484 would like to use the flash chips on it, say 'Y'.
487 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
488 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
490 This enables MTD access to flash devices on platforms based
491 on Intel's IXP2000 family of network processors such as the
492 IXDP425 and Coyote. If you have an IXP2000 based board and
493 would like to use the flash chips on it, say 'Y'.
496 tristate "CFI Flash device mapped on the FortuNet board"
497 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
499 This enables access to the Flash on the FortuNet board. If you
500 have such a board, say 'Y'.
503 tristate "NV-RAM mapping AUTCPU12 board"
504 depends on ARCH_AUTCPU12
506 This enables access to the NV-RAM on autronix autcpu12 board.
507 If you have such a board, say 'Y'.
510 tristate "CFI Flash device mapped on EDB7312"
511 depends on ARCH_EDB7312 && MTD_CFI
513 This enables access to the CFI Flash on the Cogent EDB7312 board.
514 If you have such a board, say 'Y' here.
517 tristate "JEDEC Flash device mapped on impA7"
518 depends on ARM && MTD_JEDECPROBE
520 This enables access to the NOR Flash on the impA7 board of
521 implementa GmbH. If you have such a board, say 'Y' here.
524 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
525 depends on MTD_JEDECPROBE && ARCH_CEIVA
527 This enables access to the flash chips on the Ceiva/Polaroid
528 PhotoMax Digital Picture Frame.
529 If you have such a device, say 'Y'.
532 tristate "NOR Flash device on TOTO board"
533 depends on ARCH_OMAP && OMAP_TOTO
535 This enables access to the NOR flash on the Texas Instruments
539 tristate "Hynix evaluation board mappings"
540 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
542 This enables access to the flash chips on the Hynix evaluation boards.
543 If you have such a board, say 'Y'.
546 tristate "CFI Flash device mapped on Interface MPC-1211"
547 depends on SH_MPC1211 && MTD_CFI
549 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
550 If you have such a board, say 'Y'.
553 tristate "TI OMAP board mappings"
554 depends on MTD_CFI && ARCH_OMAP
556 This enables access to the NOR flash chips on TI OMAP-based
557 boards defining flash platform devices and flash platform data.
558 These boards include the Innovator, H2, H3, OSK, Perseus2, and
559 more. If you have such a board, say 'Y'.
561 # This needs CFI or JEDEC, depending on the cards found.
563 tristate "PCI MTD driver"
564 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
566 Mapping for accessing flash devices on add-in cards like the Intel XScale
567 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
568 (please see the manual for the link settings).
570 If you are not sure, say N.
573 tristate "PCMCIA MTD driver"
574 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
576 Map driver for accessing PCMCIA linear flash memory cards. These
577 cards are usually around 4-16MiB in size. This does not include
578 Compact Flash cards which are treated as IDE devices.
580 config MTD_PCMCIA_ANONYMOUS
581 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
582 depends on MTD_PCMCIA
584 If this option is enabled, PCMCIA cards which do not report
585 anything about themselves are assumed to be MTD cards.
590 tristate "Generic uClinux RAM/ROM filesystem support"
591 depends on MTD_PARTITIONS && !MMU
593 Map driver to support image based filesystems for uClinux.
596 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
597 depends on (SBC82xx || SBC8560)
598 select MTD_PARTITIONS
599 select MTD_MAP_BANK_WIDTH_4
600 select MTD_MAP_BANK_WIDTH_1
604 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
605 all three flash regions on CS0, CS1 and CS6 if they are configured
606 correctly by the boot loader.
609 tristate "Map driver for Dy-4 SVME/DMV-182 board."
611 select MTD_PARTITIONS
612 select MTD_MAP_BANK_WIDTH_32
614 select MTD_CFI_AMDSTD
616 Map driver for Dy-4 SVME/DMV-182 board.
619 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
620 depends on ARCH_BAST || MACH_VR1000
621 select MTD_PARTITIONS
622 select MTD_MAP_BANK_WIDTH_16
623 select MTD_JEDECPROBE
625 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
628 Note, this driver *cannot* over-ride the WP link on the
629 board, or currently detect the state of the link.
631 config MTD_BAST_MAXSIZE
632 int "Maximum size for BAST flash area (MiB)"
637 bool "ROM maped on Sharp SL Series"
638 depends on MTD && ARCH_PXA
640 This enables access to the flash chip on the Sharp SL Series of PDAs.
643 tristate "Map driver for platform device RAM (mtd-ram)"
647 Map driver for RAM areas described via the platform device
650 This selection automatically selects the map_ram driver.