1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.55 2005/07/02 01:53:24 tpoynor 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 "CFI Flash device mapped on DIL/Net PC"
219 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
221 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
222 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
223 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
225 config MTD_DILNETPC_BOOTSIZE
226 hex "Size of DIL/Net PC flash boot partition"
227 depends on MTD_DILNETPC
230 The amount of space taken up by the kernel or Etherboot
231 on the DIL/Net PC flash chips.
234 tristate "BIOS flash chip on Intel L440GX boards"
235 depends on X86 && MTD_JEDECPROBE
237 Support for treating the BIOS flash chip on Intel L440GX motherboards
238 as an MTD device - with this you can reprogram your BIOS.
243 tristate "Flash device on SBC8240"
244 depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260
246 Flash access on the SBC8240 board from Wind River. See
247 <http://www.windriver.com/products/sbc8240/>
250 tristate "CFI Flash device mapped on TQM8XXL"
251 depends on MTD_CFI && PPC32 && 8xx && TQM8xxL
253 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
254 chips, currently uses AMD one. This 'mapping' driver supports
255 that arrangement, allowing the CFI probe and command set driver
256 code to communicate with the chips on the TQM8xxL board. More at
257 <http://www.denx.de/embedded-ppc-en.html>.
260 tristate "CFI Flash device mapped on RPX Lite or CLLF"
261 depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)
263 The RPXLite PowerPC board has CFI-compliant chips mapped in
264 a strange sparse mapping. This 'mapping' driver supports that
265 arrangement, allowing the CFI probe and command set driver code
266 to communicate with the chips on the RPXLite board. More at
267 <http://www.embeddedplanet.com/>.
270 tristate "System flash on MBX860 board"
271 depends on MTD_CFI && PPC32 && 8xx && MBX
273 This enables access routines for the flash chips on the Motorola
274 MBX860 board. If you have one of these boards and would like
275 to use the flash chips on it, say 'Y'.
278 tristate "CFI Flash device mapped on D-Box2"
279 depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
281 This enables access routines for the flash chips on the Nokia/Sagem
282 D-Box 2 board. If you have one of these boards and would like to use
283 the flash chips on it, say 'Y'.
285 config MTD_CFI_FLAGADM
286 tristate "CFI Flash device mapping on FlagaDM"
287 depends on PPC32 && 8xx && MTD_CFI
289 Mapping for the Flaga digital module. If you don't have one, ignore
293 tristate "CFI Flash device mapped on IBM 405LP Beech"
294 depends on MTD_CFI && PPC32 && 40x && BEECH
296 This enables access routines for the flash chips on the IBM
297 405LP Beech board. If you have one of these boards and would like
298 to use the flash chips on it, say 'Y'.
301 tristate "CFI Flash device mapped on IBM 405LP Arctic"
302 depends on MTD_CFI && PPC32 && 40x && ARCTIC2
304 This enables access routines for the flash chips on the IBM 405LP
305 Arctic board. If you have one of these boards and would like to
306 use the flash chips on it, say 'Y'.
309 tristate "Flash device mapped on IBM 405GP Walnut"
310 depends on MTD_JEDECPROBE && PPC32 && 40x && WALNUT
312 This enables access routines for the flash chips on the IBM 405GP
313 Walnut board. If you have one of these boards and would like to
314 use the flash chips on it, say 'Y'.
317 tristate "Flash devices mapped on IBM 440GP Ebony"
318 depends on MTD_JEDECPROBE && PPC32 && 44x && EBONY
320 This enables access routines for the flash chips on the IBM 440GP
321 Ebony board. If you have one of these boards and would like to
322 use the flash chips on it, say 'Y'.
325 tristate "Flash devices mapped on IBM 440GX Ocotea"
326 depends on MTD_CFI && PPC32 && 44x && OCOTEA
328 This enables access routines for the flash chips on the IBM 440GX
329 Ocotea board. If you have one of these boards and would like to
330 use the flash chips on it, say 'Y'.
333 tristate "CFI Flash devices mapped on IBM Redwood"
334 depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
336 This enables access routines for the flash chips on the IBM
337 Redwood board. If you have one of these boards and would like to
338 use the flash chips on it, say 'Y'.
340 config MTD_CSTM_MIPS_IXX
341 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
342 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
344 This provides a mapping driver for the Integrated Technology
345 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
346 Reference Board. It provides the necessary addressing, length,
347 buswidth, vpp code and addition setup of the flash device for
348 these boards. In addition, this mapping driver can be used for
349 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
350 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
351 using one partition. The start address can be offset from the
352 beginning of flash and the len can be less than the total flash
353 device size to allow a window into the flash. Both CFI and JEDEC
356 config MTD_CSTM_MIPS_IXX_START
357 hex "Physical start address of flash mapping"
358 depends on MTD_CSTM_MIPS_IXX
361 This is the physical memory location that the MTD driver will
362 use for the flash chips on your particular target board.
363 Refer to the memory map which should hopefully be in the
364 documentation for your board.
366 config MTD_CSTM_MIPS_IXX_LEN
367 hex "Physical length of flash mapping"
368 depends on MTD_CSTM_MIPS_IXX
371 This is the total length that the MTD driver will use for the
372 flash chips on your particular board. Refer to the memory
373 map which should hopefully be in the documentation for your
376 config MTD_CSTM_MIPS_IXX_BUSWIDTH
377 int "Bus width in octets"
378 depends on MTD_CSTM_MIPS_IXX
381 This is the total bus width of the mapping of the flash chips
382 on your particular board.
385 tristate "Momenco Ocelot boot flash device"
386 depends on MIPS && MOMENCO_OCELOT
388 This enables access routines for the boot flash device and for the
389 NVRAM on the Momenco Ocelot board. If you have one of these boards
390 and would like access to either of these, say 'Y'.
392 config MTD_SOLUTIONENGINE
393 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
394 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
396 This enables access to the flash chips on the Hitachi SolutionEngine and
397 similar boards. Say 'Y' if you are building a kernel for such a board.
399 config MTD_ARM_INTEGRATOR
400 tristate "CFI Flash device mapped on ARM Integrator/P720T"
401 depends on ARM && MTD_CFI
404 tristate "Cirrus CDB89712 evaluation board mappings"
405 depends on ARM && MTD_CFI && ARCH_CDB89712
407 This enables access to the flash or ROM chips on the CDB89712 board.
408 If you have such a board, say 'Y'.
411 tristate "CFI Flash device mapped on StrongARM SA11x0"
412 depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
414 This enables access to the flash chips on most platforms based on
415 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
416 If you have such a board, say 'Y'.
419 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
420 depends on ARM && IPAQ_HANDHELD && MTD_CFI
422 This provides a driver for the on-board flash of the iPAQ.
425 tristate "CFI Flash device mapped on DC21285 Footbridge"
426 depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
428 This provides a driver for the flash accessed using Intel's
429 21285 bridge used with Intel's StrongARM processors. More info at
430 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
433 tristate "CFI Flash device mapped on the XScale IQ80310 board"
434 depends on ARM && MTD_CFI && ARCH_IQ80310
436 This enables access routines for the flash chips on the Intel XScale
437 IQ80310 evaluation board. If you have one of these boards and would
438 like to use the flash chips on it, say 'Y'.
441 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
442 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
444 This enables MTD access to flash devices on platforms based
445 on Intel's IXP4xx family of network processors such as the
446 IXDP425 and Coyote. If you have an IXP4xx based board and
447 would like to use the flash chips on it, say 'Y'.
450 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
451 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
453 This enables MTD access to flash devices on platforms based
454 on Intel's IXP2000 family of network processors such as the
455 IXDP425 and Coyote. If you have an IXP2000 based board and
456 would like to use the flash chips on it, say 'Y'.
459 tristate "CFI Flash device mapped on Epxa10db"
460 depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
462 This enables support for the flash devices on the Altera
463 Excalibur XA10 Development Board. If you are building a kernel
464 for on of these boards then you should say 'Y' otherwise say 'N'.
467 tristate "CFI Flash device mapped on the FortuNet board"
468 depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
470 This enables access to the Flash on the FortuNet board. If you
471 have such a board, say 'Y'.
474 tristate "NV-RAM mapping AUTCPU12 board"
475 depends on ARM && ARCH_AUTCPU12
477 This enables access to the NV-RAM on autronix autcpu12 board.
478 If you have such a board, say 'Y'.
481 tristate "CFI Flash device mapped on EDB7312"
482 depends on ARM && MTD_CFI
484 This enables access to the CFI Flash on the Cogent EDB7312 board.
485 If you have such a board, say 'Y' here.
488 tristate "JEDEC Flash device mapped on impA7"
489 depends on ARM && MTD_JEDECPROBE
491 This enables access to the NOR Flash on the impA7 board of
492 implementa GmbH. If you have such a board, say 'Y' here.
495 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
496 depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA
498 This enables access to the flash chips on the Ceiva/Polaroid
499 PhotoMax Digital Picture Frame.
500 If you have such a device, say 'Y'.
503 tristate "NOR Flash device on TOTO board"
504 depends on ARM && ARCH_OMAP && OMAP_TOTO
506 This enables access to the NOR flash on the Texas Instruments
510 tristate "Hynix evaluation board mappings"
511 depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
513 This enables access to the flash chips on the Hynix evaluation boards.
514 If you have such a board, say 'Y'.
517 tristate "CFI Flash device mapped on Interface MPC-1211"
518 depends on SUPERH && SH_MPC1211 && MTD_CFI
520 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
521 If you have such a board, say 'Y'.
524 tristate "TI OMAP board mappings"
525 depends on MTD_CFI && ARCH_OMAP
527 This enables access to the NOR flash chips on TI OMAP-based
528 boards defining flash platform devices and flash platform data.
529 These boards include the Innovator, H2, H3, OSK, Perseus2, and
530 more. If you have such a board, say 'Y'.
532 # This needs CFI or JEDEC, depending on the cards found.
534 tristate "PCI MTD driver"
535 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
537 Mapping for accessing flash devices on add-in cards like the Intel XScale
538 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
539 (please see the manual for the link settings).
541 If you are not sure, say N.
544 tristate "PCMCIA MTD driver"
545 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
547 Map driver for accessing PCMCIA linear flash memory cards. These
548 cards are usually around 4-16MiB in size. This does not include
549 Compact Flash cards which are treated as IDE devices.
551 config MTD_PCMCIA_ANONYMOUS
552 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
553 depends on MTD_PCMCIA
556 If this option is enabled, PCMCIA cards which do not report
557 anything about themselves are assumed to be MTD cards.
562 tristate "Generic uClinux RAM/ROM filesystem support"
563 depends on MTD_PARTITIONS && !MMU
565 Map driver to support image based filesystems for uClinux.
568 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
569 depends on (SBC82xx || SBC8560)
570 select MTD_PARTITIONS
571 select MTD_MAP_BANK_WIDTH_4
572 select MTD_MAP_BANK_WIDTH_1
576 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
577 all three flash regions on CS0, CS1 and CS6 if they are configured
578 correctly by the boot loader.
581 tristate "Map driver for Dy-4 SVME/DMV-182 board."
583 select MTD_PARTITIONS
584 select MTD_MAP_BANK_WIDTH_32
586 select MTD_CFI_AMDSTD
588 Map driver for Dy-4 SVME/DMV-182 board.
591 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
592 depends on ARCH_BAST || MACH_VR1000
593 select MTD_PARTITIONS
594 select MTD_MAP_BANK_WIDTH_16
595 select MTD_JEDECPROBE
597 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
600 Note, this driver *cannot* over-ride the WP link on the
601 board, or currently detect the state of the link.
603 config MTD_BAST_MAXSIZE
604 int "Maximum size for BAST flash area (MiB)"
609 bool "ROM maped on Sharp SL Series"
610 depends on MTD && ARCH_PXA
612 This enables access to the flash chip on the Sharp SL Series of PDAs.
615 tristate "Map driver for platform device RAM (mtd-ram)"
619 Map driver for RAM areas described via the platform device
622 This selection automatically selects the map_ram driver.