1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.54 2005/06/30 22:41:36 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 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>.
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.
187 config MTD_SCB2_FLASH
188 tristate "BIOS flash chip on Intel SCB2 boards"
189 depends on X86 && MTD_JEDECPROBE
191 Support for treating the BIOS flash chip on Intel SCB2 boards
192 as an MTD device - with this you can reprogram your BIOS.
197 tristate "Flash chips on Tsunami TIG bus"
198 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
200 Support for the flash chip on Tsunami TIG bus.
203 tristate "Flash chips on LASAT board"
206 Support for the flash chips on the Lasat 100 and 200 boards.
209 tristate "CFI flash device on SnapGear/SecureEdge"
210 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
212 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
215 tristate ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support'
216 depends on MIPS && SOC_AU1X00
218 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
221 tristate "CFI Flash device mapped on DIL/Net PC"
222 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
224 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
225 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
226 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
228 config MTD_DILNETPC_BOOTSIZE
229 hex "Size of DIL/Net PC flash boot partition"
230 depends on MTD_DILNETPC
233 The amount of space taken up by the kernel or Etherboot
234 on the DIL/Net PC flash chips.
237 tristate "BIOS flash chip on Intel L440GX boards"
238 depends on X86 && MTD_JEDECPROBE
240 Support for treating the BIOS flash chip on Intel L440GX motherboards
241 as an MTD device - with this you can reprogram your BIOS.
246 tristate "Flash device on SBC8240"
247 depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260
249 Flash access on the SBC8240 board from Wind River. See
250 <http://www.windriver.com/products/sbc8240/>
253 tristate "CFI Flash device mapped on TQM8XXL"
254 depends on MTD_CFI && PPC32 && 8xx && TQM8xxL
256 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
257 chips, currently uses AMD one. This 'mapping' driver supports
258 that arrangement, allowing the CFI probe and command set driver
259 code to communicate with the chips on the TQM8xxL board. More at
260 <http://www.denx.de/embedded-ppc-en.html>.
263 tristate "CFI Flash device mapped on RPX Lite or CLLF"
264 depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)
266 The RPXLite PowerPC board has CFI-compliant chips mapped in
267 a strange sparse mapping. This 'mapping' driver supports that
268 arrangement, allowing the CFI probe and command set driver code
269 to communicate with the chips on the RPXLite board. More at
270 <http://www.embeddedplanet.com/>.
273 tristate "System flash on MBX860 board"
274 depends on MTD_CFI && PPC32 && 8xx && MBX
276 This enables access routines for the flash chips on the Motorola
277 MBX860 board. If you have one of these boards and would like
278 to use the flash chips on it, say 'Y'.
281 tristate "CFI Flash device mapped on D-Box2"
282 depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
284 This enables access routines for the flash chips on the Nokia/Sagem
285 D-Box 2 board. If you have one of these boards and would like to use
286 the flash chips on it, say 'Y'.
288 config MTD_CFI_FLAGADM
289 tristate "CFI Flash device mapping on FlagaDM"
290 depends on PPC32 && 8xx && MTD_CFI
292 Mapping for the Flaga digital module. If you don't have one, ignore
296 tristate "CFI Flash device mapped on IBM 405LP Beech"
297 depends on MTD_CFI && PPC32 && 40x && BEECH
299 This enables access routines for the flash chips on the IBM
300 405LP Beech board. If you have one of these boards and would like
301 to use the flash chips on it, say 'Y'.
304 tristate "CFI Flash device mapped on IBM 405LP Arctic"
305 depends on MTD_CFI && PPC32 && 40x && ARCTIC2
307 This enables access routines for the flash chips on the IBM 405LP
308 Arctic board. If you have one of these boards and would like to
309 use the flash chips on it, say 'Y'.
312 tristate "Flash device mapped on IBM 405GP Walnut"
313 depends on MTD_JEDECPROBE && PPC32 && 40x && WALNUT
315 This enables access routines for the flash chips on the IBM 405GP
316 Walnut board. If you have one of these boards and would like to
317 use the flash chips on it, say 'Y'.
320 tristate "Flash devices mapped on IBM 440GP Ebony"
321 depends on MTD_JEDECPROBE && PPC32 && 44x && EBONY
323 This enables access routines for the flash chips on the IBM 440GP
324 Ebony board. If you have one of these boards and would like to
325 use the flash chips on it, say 'Y'.
328 tristate "Flash devices mapped on IBM 440GX Ocotea"
329 depends on MTD_CFI && PPC32 && 44x && OCOTEA
331 This enables access routines for the flash chips on the IBM 440GX
332 Ocotea board. If you have one of these boards and would like to
333 use the flash chips on it, say 'Y'.
336 tristate "CFI Flash devices mapped on IBM Redwood"
337 depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
339 This enables access routines for the flash chips on the IBM
340 Redwood board. If you have one of these boards and would like to
341 use the flash chips on it, say 'Y'.
343 config MTD_CSTM_MIPS_IXX
344 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
345 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
347 This provides a mapping driver for the Integrated Technology
348 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
349 Reference Board. It provides the necessary addressing, length,
350 buswidth, vpp code and addition setup of the flash device for
351 these boards. In addition, this mapping driver can be used for
352 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
353 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
354 using one partition. The start address can be offset from the
355 beginning of flash and the len can be less than the total flash
356 device size to allow a window into the flash. Both CFI and JEDEC
359 config MTD_CSTM_MIPS_IXX_START
360 hex "Physical start address of flash mapping"
361 depends on MTD_CSTM_MIPS_IXX
364 This is the physical memory location that the MTD driver will
365 use for the flash chips on your particular target board.
366 Refer to the memory map which should hopefully be in the
367 documentation for your board.
369 config MTD_CSTM_MIPS_IXX_LEN
370 hex "Physical length of flash mapping"
371 depends on MTD_CSTM_MIPS_IXX
374 This is the total length that the MTD driver will use for the
375 flash chips on your particular board. Refer to the memory
376 map which should hopefully be in the documentation for your
379 config MTD_CSTM_MIPS_IXX_BUSWIDTH
380 int "Bus width in octets"
381 depends on MTD_CSTM_MIPS_IXX
384 This is the total bus width of the mapping of the flash chips
385 on your particular board.
388 tristate "Momenco Ocelot boot flash device"
389 depends on MIPS && MOMENCO_OCELOT
391 This enables access routines for the boot flash device and for the
392 NVRAM on the Momenco Ocelot board. If you have one of these boards
393 and would like access to either of these, say 'Y'.
395 config MTD_SOLUTIONENGINE
396 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
397 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
399 This enables access to the flash chips on the Hitachi SolutionEngine and
400 similar boards. Say 'Y' if you are building a kernel for such a board.
402 config MTD_ARM_INTEGRATOR
403 tristate "CFI Flash device mapped on ARM Integrator/P720T"
404 depends on ARM && MTD_CFI
407 tristate "Cirrus CDB89712 evaluation board mappings"
408 depends on ARM && MTD_CFI && ARCH_CDB89712
410 This enables access to the flash or ROM chips on the CDB89712 board.
411 If you have such a board, say 'Y'.
414 tristate "CFI Flash device mapped on StrongARM SA11x0"
415 depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
417 This enables access to the flash chips on most platforms based on
418 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
419 If you have such a board, say 'Y'.
422 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
423 depends on ARM && IPAQ_HANDHELD && MTD_CFI
425 This provides a driver for the on-board flash of the iPAQ.
428 tristate "CFI Flash device mapped on DC21285 Footbridge"
429 depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
431 This provides a driver for the flash accessed using Intel's
432 21285 bridge used with Intel's StrongARM processors. More info at
433 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
436 tristate "CFI Flash device mapped on the XScale IQ80310 board"
437 depends on ARM && MTD_CFI && ARCH_IQ80310
439 This enables access routines for the flash chips on the Intel XScale
440 IQ80310 evaluation board. If you have one of these boards and would
441 like to use the flash chips on it, say 'Y'.
444 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
445 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
447 This enables MTD access to flash devices on platforms based
448 on Intel's IXP4xx family of network processors such as the
449 IXDP425 and Coyote. If you have an IXP4xx based board and
450 would like to use the flash chips on it, say 'Y'.
453 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
454 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
456 This enables MTD access to flash devices on platforms based
457 on Intel's IXP2000 family of network processors such as the
458 IXDP425 and Coyote. If you have an IXP2000 based board and
459 would like to use the flash chips on it, say 'Y'.
462 tristate "CFI Flash device mapped on Epxa10db"
463 depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
465 This enables support for the flash devices on the Altera
466 Excalibur XA10 Development Board. If you are building a kernel
467 for on of these boards then you should say 'Y' otherwise say 'N'.
470 tristate "CFI Flash device mapped on the FortuNet board"
471 depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
473 This enables access to the Flash on the FortuNet board. If you
474 have such a board, say 'Y'.
477 tristate "NV-RAM mapping AUTCPU12 board"
478 depends on ARM && ARCH_AUTCPU12
480 This enables access to the NV-RAM on autronix autcpu12 board.
481 If you have such a board, say 'Y'.
484 tristate "CFI Flash device mapped on EDB7312"
485 depends on ARM && MTD_CFI
487 This enables access to the CFI Flash on the Cogent EDB7312 board.
488 If you have such a board, say 'Y' here.
491 tristate "JEDEC Flash device mapped on impA7"
492 depends on ARM && MTD_JEDECPROBE
494 This enables access to the NOR Flash on the impA7 board of
495 implementa GmbH. If you have such a board, say 'Y' here.
498 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
499 depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA
501 This enables access to the flash chips on the Ceiva/Polaroid
502 PhotoMax Digital Picture Frame.
503 If you have such a device, say 'Y'.
506 tristate "NOR Flash device on TOTO board"
507 depends on ARM && ARCH_OMAP && OMAP_TOTO
509 This enables access to the NOR flash on the Texas Instruments
513 tristate "Hynix evaluation board mappings"
514 depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
516 This enables access to the flash chips on the Hynix evaluation boards.
517 If you have such a board, say 'Y'.
520 tristate "CFI Flash device mapped on Interface MPC-1211"
521 depends on SUPERH && SH_MPC1211 && MTD_CFI
523 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
524 If you have such a board, say 'Y'.
526 # This needs CFI or JEDEC, depending on the cards found.
528 tristate "PCI MTD driver"
529 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
531 Mapping for accessing flash devices on add-in cards like the Intel XScale
532 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
533 (please see the manual for the link settings).
535 If you are not sure, say N.
538 tristate "PCMCIA MTD driver"
539 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
541 Map driver for accessing PCMCIA linear flash memory cards. These
542 cards are usually around 4-16MiB in size. This does not include
543 Compact Flash cards which are treated as IDE devices.
546 tristate "Generic uClinux RAM/ROM filesystem support"
547 depends on MTD_PARTITIONS && !MMU
549 Map driver to support image based filesystems for uClinux.
552 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
553 depends on (SBC82xx || SBC8560)
554 select MTD_PARTITIONS
555 select MTD_MAP_BANK_WIDTH_4
556 select MTD_MAP_BANK_WIDTH_1
560 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
561 all three flash regions on CS0, CS1 and CS6 if they are configured
562 correctly by the boot loader.
565 tristate "Map driver for Dy-4 SVME/DMV-182 board."
567 select MTD_PARTITIONS
568 select MTD_MAP_BANK_WIDTH_32
570 select MTD_CFI_AMDSTD
572 Map driver for Dy-4 SVME/DMV-182 board.
575 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
576 depends on ARCH_BAST || MACH_VR1000
577 select MTD_PARTITIONS
578 select MTD_MAP_BANK_WIDTH_16
579 select MTD_JEDECPROBE
581 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
584 Note, this driver *cannot* over-ride the WP link on the
585 board, or currently detect the state of the link.
587 config MTD_BAST_MAXSIZE
588 int "Maximum size for BAST flash area (MiB)"
593 bool "ROM maped on Sharp SL Series"
594 depends on MTD && ARCH_PXA
596 This enables access to the flash chip on the Sharp SL Series of PDAs.
599 tristate "Map driver for platform device RAM (mtd-ram)"
603 Map driver for RAM areas described via the platform device
606 This selection automatically selects the map_ram driver.