1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.37 2004/10/20 22:57:18 dwmw2 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 flash is split into 3 partitions
101 which are accessed as separate MTD devices.
103 mtd0 and mtd2 are the two BIOS drives. Unfortunately the BIOS
104 uses a proprietary flash translation layer from General Software,
105 which is not supported (the drives cannot be mounted). You can
106 create your own file system (jffs for example), but the BIOS
107 won't be able to boot from it.
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 succeeed.
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>.
125 config MTD_ELAN_104NC
126 tristate "CFI Flash device mapped on Arcom ELAN-104NC"
127 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
129 This provides a driver for the on-board flash of the Arcom Control
130 System's ELAN-104NC development board. By default the flash
131 is split into 3 partitions which are accessed as separate MTD
132 devices. This board utilizes Intel StrataFlash. More info at
133 <http://www.arcomcontrols.com/products/icp/pc104/processors/ELAN104NC.htm>.
136 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
137 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
139 This provides a driver for the on-board flash of the Intel
140 'Lubbock' XScale evaluation board.
143 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
144 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
146 This provides a 'mapping' driver which supports the way in which
147 the flash chips are connected in the Octagon-5066 Single Board
148 Computer. More information on the board is available at
149 <http://www.octagonsystems.com/CPUpages/5066.html>.
152 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
153 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
155 This provides a 'mapping' driver which supports the way in which
156 the flash chips are connected in the Tempustech VMAX SBC301 Single
157 Board Computer. More information on the board is available at
158 <http://www.tempustech.com/>.
160 config MTD_SCx200_DOCFLASH
161 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
162 depends on X86 && MTD_CFI
164 Enable support for a flash chip mapped using the DOCCS signal on a
165 National Semiconductor SCx200 processor.
167 If you don't know what to do here, say N.
169 If compiled as a module, it will be called scx200_docflash.
172 tristate "BIOS flash chip on AMD76x southbridge"
173 depends on X86 && MTD_JEDECPROBE
175 Support for treating the BIOS flash chip on AMD76x motherboards
176 as an MTD device - with this you can reprogram your BIOS.
181 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
182 depends on X86 && MTD_JEDECPROBE
184 Support for treating the BIOS flash chip on ICHX motherboards
185 as an MTD device - with this you can reprogram your BIOS.
189 config MTD_SCB2_FLASH
190 tristate "BIOS flash chip on Intel SCB2 boards"
191 depends on X86 && MTD_JEDECPROBE
193 Support for treating the BIOS flash chip on Intel SCB2 boards
194 as an MTD device - with this you can reprogram your BIOS.
199 tristate "Flash chips on Tsunami TIG bus"
200 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
202 Support for the flash chip on Tsunami TIG bus.
205 tristate "Flash chips on LASAT board"
208 Support for the flash chips on the Lasat 100 and 200 boards.
211 tristate "CFI flash device on SnapGear/SecureEdge"
212 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
214 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
217 tristate "Flash devices on Alchemy PB1xxx boards"
218 depends on MIPS && ( MIPS_PB1000 || MIPS_PB1100 || MIPS_PB1500 )
220 Flash memory access on Alchemy Pb1000/Pb1100/Pb1500 boards
222 config MTD_PB1XXX_BOOT
223 bool "PB1x00 boot flash device"
224 depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 )
226 Use the first of the two 32MiB flash banks on Pb1100/Pb1500 board.
227 You can say 'Y' to both this and 'MTD_PB1XXX_USER' below, to use
230 config MTD_PB1XXX_USER
231 bool "PB1x00 user flash device"
232 depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 )
233 default y if MTD_PB1XX_BOOT = n
235 Use the second of the two 32MiB flash banks on Pb1100/Pb1500 board.
236 You can say 'Y' to both this and 'MTD_PB1XXX_BOOT' above, to use
240 tristate "Flash devices on Alchemy PB1550 board"
241 depends on MIPS && MIPS_PB1550
243 Flash memory access on Alchemy Pb1550 board
245 config MTD_PB1550_BOOT
246 bool "PB1550 boot flash device"
247 depends on MTD_PB1550
249 Use the first of the two 64MiB flash banks on Pb1550 board.
250 You can say 'Y' to both this and 'MTD_PB1550_USER' below, to use
253 config MTD_PB1550_USER
254 bool "PB1550 user flash device"
255 depends on MTD_PB1550
256 default y if MTD_PB1550_BOOT = n
258 Use the second of the two 64MiB flash banks on Pb1550 board.
259 You can say 'Y' to both this and 'MTD_PB1550_BOOT' above, to use
263 tristate "Flash devices on Alchemy DB1550 board"
264 depends on MIPS && MIPS_DB1550
266 Flash memory access on Alchemy Db1550 board
268 config MTD_DB1550_BOOT
269 bool "DB1550 boot flash device"
270 depends on MTD_DB1550
272 Use the first of the two 64MiB flash banks on Db1550 board.
273 You can say 'Y' to both this and 'MTD_DB1550_USER' below, to use
276 config MTD_DB1550_USER
277 bool "DB1550 user flash device"
278 depends on MTD_DB1550
279 default y if MTD_DB1550_BOOT = n
281 Use the second of the two 64MiB flash banks on Db1550 board.
282 You can say 'Y' to both this and 'MTD_DB1550_BOOT' above, to use
286 tristate "CFI Flash device mapped on DIL/Net PC"
287 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
289 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
290 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
291 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
293 config MTD_DILNETPC_BOOTSIZE
294 hex "Size of DIL/Net PC flash boot partition"
295 depends on MTD_DILNETPC
298 The amount of space taken up by the kernel or Etherboot
299 on the DIL/Net PC flash chips.
302 tristate "BIOS flash chip on Intel L440GX boards"
303 depends on X86 && MTD_JEDECPROBE
305 Support for treating the BIOS flash chip on Intel L440GX motherboards
306 as an MTD device - with this you can reprogram your BIOS.
311 tristate "Flash device on SBC8240"
312 depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260
314 Flash access on the SBC8240 board from Wind River. See
315 <http://www.windriver.com/products/sbc8240/>
318 tristate "CFI Flash device mapped on TQM8XXL"
319 depends on MTD_CFI && PPC32 && 8xx && TQM8xxL
321 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
322 chips, currently uses AMD one. This 'mapping' driver supports
323 that arrangement, allowing the CFI probe and command set driver
324 code to communicate with the chips on the TQM8xxL board. More at
325 <http://www.denx.de/embedded-ppc-en.html>.
328 tristate "CFI Flash device mapped on RPX Lite or CLLF"
329 depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)
331 The RPXLite PowerPC board has CFI-compliant chips mapped in
332 a strange sparse mapping. This 'mapping' driver supports that
333 arrangement, allowing the CFI probe and command set driver code
334 to communicate with the chips on the RPXLite board. More at
335 <http://www.embeddedplanet.com/>.
338 tristate "System flash on MBX860 board"
339 depends on MTD_CFI && PPC32 && 8xx && MBX
341 This enables access routines for the flash chips on the Motorola
342 MBX860 board. If you have one of these boards and would like
343 to use the flash chips on it, say 'Y'.
346 tristate "CFI Flash device mapped on D-Box2"
347 depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
349 This enables access routines for the flash chips on the Nokia/Sagem
350 D-Box 2 board. If you have one of these boards and would like to use
351 the flash chips on it, say 'Y'.
353 config MTD_CFI_FLAGADM
354 tristate "CFI Flash device mapping on FlagaDM"
355 depends on PPC32 && 8xx && MTD_CFI
357 Mapping for the Flaga digital module. If you don´t have one, ignore
361 tristate "CFI Flash device mapped on IBM 405LP Beech"
362 depends on MTD_CFI && PPC32 && 40x && BEECH
364 This enables access routines for the flash chips on the IBM
365 405LP Beech board. If you have one of these boards and would like
366 to use the flash chips on it, say 'Y'.
369 tristate "CFI Flash device mapped on IBM 405LP Arctic"
370 depends on MTD_CFI && PPC32 && 40x && ARCTIC2
372 This enables access routines for the flash chips on the IBM 405LP
373 Arctic board. If you have one of these boards and would like to
374 use the flash chips on it, say 'Y'.
377 tristate "Flash devices mapped on IBM 440GP Ebony"
378 depends on MTD_CFI && PPC32 && 44x && EBONY
380 This enables access routines for the flash chips on the IBM 440GP
381 Ebony board. If you have one of these boards and would like to
382 use the flash chips on it, say 'Y'.
385 tristate "Flash devices mapped on IBM 440GX Ocotea"
386 depends on MTD_CFI && PPC32 && 44x && OCOTEA
388 This enables access routines for the flash chips on the IBM 440GX
389 Ocotea board. If you have one of these boards and would like to
390 use the flash chips on it, say 'Y'.
393 tristate "CFI Flash devices mapped on IBM Redwood"
394 depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
396 This enables access routines for the flash chips on the IBM
397 Redwood board. If you have one of these boards and would like to
398 use the flash chips on it, say 'Y'.
400 config MTD_CSTM_MIPS_IXX
401 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
402 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
404 This provides a mapping driver for the Integrated Tecnology
405 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
406 Reference Board. It provides the necessary addressing, length,
407 buswidth, vpp code and addition setup of the flash device for
408 these boards. In addition, this mapping driver can be used for
409 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
410 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
411 using one partition. The start address can be offset from the
412 beginning of flash and the len can be less than the total flash
413 device size to allow a window into the flash. Both CFI and JEDEC
416 config MTD_CSTM_MIPS_IXX_START
417 hex "Physical start address of flash mapping"
418 depends on MTD_CSTM_MIPS_IXX
421 This is the physical memory location that the MTD driver will
422 use for the flash chips on your particular target board.
423 Refer to the memory map which should hopefully be in the
424 documentation for your board.
426 config MTD_CSTM_MIPS_IXX_LEN
427 hex "Physical length of flash mapping"
428 depends on MTD_CSTM_MIPS_IXX
431 This is the total length that the MTD driver will use for the
432 flash chips on your particular board. Refer to the memory
433 map which should hopefully be in the documentation for your
436 config MTD_CSTM_MIPS_IXX_BUSWIDTH
437 int "Bus width in octets"
438 depends on MTD_CSTM_MIPS_IXX
441 This is the total bus width of the mapping of the flash chips
442 on your particular board.
445 tristate "Momenco Ocelot boot flash device"
446 depends on MIPS && MOMENCO_OCELOT
448 This enables access routines for the boot flash device and for the
449 NVRAM on the Momenco Ocelot board. If you have one of these boards
450 and would like access to either of these, say 'Y'.
452 config MTD_SOLUTIONENGINE
453 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
454 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
456 This enables access to the flash chips on the Hitachi SolutionEngine and
457 similar boards. Say 'Y' if you are building a kernel for such a board.
459 config MTD_ARM_INTEGRATOR
460 tristate "CFI Flash device mapped on ARM Integrator/P720T"
461 depends on ARM && MTD_CFI
464 tristate "Cirrus CDB89712 evaluation board mappings"
465 depends on ARM && MTD_CFI && ARCH_CDB89712
467 This enables access to the flash or ROM chips on the CDB89712 board.
468 If you have such a board, say 'Y'.
471 tristate "CFI Flash device mapped on StrongARM SA11x0"
472 depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
474 This enables access to the flash chips on most platforms based on
475 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
476 If you have such a board, say 'Y'.
479 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
480 depends on ARM && IPAQ_HANDHELD && MTD_CFI
482 This provides a driver for the on-board flash of the iPAQ.
485 tristate "CFI Flash device mapped on DC21285 Footbridge"
486 depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
488 This provides a driver for the flash accessed using Intel's
489 21285 bridge used with Intel's StrongARM processors. More info at
490 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
493 tristate "CFI Flash device mapped on the XScale IQ80310 board"
494 depends on ARM && MTD_CFI && ARCH_IQ80310
496 This enables access routines for the flash chips on the Intel XScale
497 IQ80310 evaluation board. If you have one of these boards and would
498 like to use the flash chips on it, say 'Y'.
501 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
502 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
504 This enables MTD access to flash devices on platforms based
505 on Intel's IXP4xx family of network processors such as the
506 IXDP425 and Coyote. If you have an IXP4xx based board and
507 would like to use the flash chips on it, say 'Y'.
510 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
511 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
513 This enables MTD access to flash devices on platforms based
514 on Intel's IXP2000 family of network processors such as the
515 IXDP425 and Coyote. If you have an IXP2000 based board and
516 would like to use the flash chips on it, say 'Y'.
519 tristate "CFI Flash device mapped on Epxa10db"
520 depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
522 This enables support for the flash devices on the Altera
523 Excalibur XA10 Development Board. If you are building a kernel
524 for on of these boards then you should say 'Y' otherwise say 'N'.
527 tristate "CFI Flash device mapped on the FortuNet board"
528 depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
530 This enables access to the Flash on the FortuNet board. If you
531 have such a board, say 'Y'.
534 tristate "NV-RAM mapping AUTCPU12 board"
535 depends on ARM && ARCH_AUTCPU12
537 This enables access to the NV-RAM on autronix autcpu12 board.
538 If you have such a board, say 'Y'.
541 tristate "CFI Flash device mapped on EDB7312"
542 depends on ARM && MTD_CFI
544 This enables access to the CFI Flash on the Cogent EDB7312 board.
545 If you have such a board, say 'Y' here.
548 tristate "JEDEC Flash device mapped on impA7"
549 depends on ARM && MTD_JEDECPROBE
551 This enables access to the NOR Flash on the impA7 board of
552 implementa GmbH. If you have such a board, say 'Y' here.
555 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
556 depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA
558 This enables access to the flash chips on the Ceiva/Polaroid
559 PhotoMax Digital Picture Frame.
560 If you have such a device, say 'Y'.
563 tristate "NOR Flash device on TOTO board"
564 depends on ARM && ARCH_OMAP && OMAP_TOTO
566 This enables access to the NOR flash on the Texas Instruments
570 tristate "Hynix evaluation board mappings"
571 depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
573 This enables access to the flash chips on the Hynix evaluation boards.
574 If you have such a board, say 'Y'.
577 tristate "CFI Flash device mapped on Interface MPC-1211"
578 depends on SUPERH && SH_MPC1211 && MTD_CFI
580 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
581 If you have such a board, say 'Y'.
583 # This needs CFI or JEDEC, depending on the cards found.
585 tristate "PCI MTD driver"
586 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
588 Mapping for accessing flash devices on add-in cards like the Intel XScale
589 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
590 (please see the manual for the link settings).
592 If you are not sure, say N.
595 tristate "PCMCIA MTD driver"
596 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
598 Map driver for accessing PCMCIA linear flash memory cards. These
599 cards are usually around 4-16MiB in size. This does not include
600 Compact Flash cards which are treated as IDE devices.
603 tristate "Generic uClinux RAM/ROM filesystem support"
604 depends on MTD_PARTITIONS && !MMU
606 Map driver to support image based filesystems for uClinux.
609 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
610 depends on (SBC82xx || SBC8560)
611 select MTD_PARTITIONS
612 select MTD_MAP_BANK_WIDTH_4
613 select MTD_MAP_BANK_WIDTH_1
617 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
618 all three flash regions on CS0, CS1 and CS6 if they are configured
619 correctly by the boot loader.
622 tristate "Map driver for Dy-4 SVME/DMV-182 board."
624 select MTD_PARTITIONS
625 select MTD_MAP_BANK_WIDTH_32
627 select MTD_CFI_AMDSTD
629 Map driver for Dy-4 SVME/DMV-182 board.
632 tristate "Map driver for Simtec BAST (EB2410ITX)"
634 select MTD_PARTITIONS
635 select MTD_MAP_BANK_WIDTH_16
636 select MTD_JEDECPROBE
638 Map driver for NOR flash on the Simtec BAST (EB2410ITX).
640 Note, this driver *cannot* over-ride the WP link on the
641 board, or currently detect the state of the link.
643 config MTD_BAST_MAXSIZE
644 int "Maximum size for BAST flash area (MiB)"