1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.45 2005/02/27 21:50:21 ppopov 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 SCx200 && MTD_CFI && MTD_PARTITIONS
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 ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support'
218 depends on MIPS && SOC_AU1X00
220 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
223 tristate "CFI Flash device mapped on DIL/Net PC"
224 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
226 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
227 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
228 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
230 config MTD_DILNETPC_BOOTSIZE
231 hex "Size of DIL/Net PC flash boot partition"
232 depends on MTD_DILNETPC
235 The amount of space taken up by the kernel or Etherboot
236 on the DIL/Net PC flash chips.
239 tristate "BIOS flash chip on Intel L440GX boards"
240 depends on X86 && MTD_JEDECPROBE
242 Support for treating the BIOS flash chip on Intel L440GX motherboards
243 as an MTD device - with this you can reprogram your BIOS.
248 tristate "Flash device on SBC8240"
249 depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260
251 Flash access on the SBC8240 board from Wind River. See
252 <http://www.windriver.com/products/sbc8240/>
255 tristate "CFI Flash device mapped on TQM8XXL"
256 depends on MTD_CFI && PPC32 && 8xx && TQM8xxL
258 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
259 chips, currently uses AMD one. This 'mapping' driver supports
260 that arrangement, allowing the CFI probe and command set driver
261 code to communicate with the chips on the TQM8xxL board. More at
262 <http://www.denx.de/embedded-ppc-en.html>.
265 tristate "CFI Flash device mapped on RPX Lite or CLLF"
266 depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)
268 The RPXLite PowerPC board has CFI-compliant chips mapped in
269 a strange sparse mapping. This 'mapping' driver supports that
270 arrangement, allowing the CFI probe and command set driver code
271 to communicate with the chips on the RPXLite board. More at
272 <http://www.embeddedplanet.com/>.
275 tristate "System flash on MBX860 board"
276 depends on MTD_CFI && PPC32 && 8xx && MBX
278 This enables access routines for the flash chips on the Motorola
279 MBX860 board. If you have one of these boards and would like
280 to use the flash chips on it, say 'Y'.
283 tristate "CFI Flash device mapped on D-Box2"
284 depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
286 This enables access routines for the flash chips on the Nokia/Sagem
287 D-Box 2 board. If you have one of these boards and would like to use
288 the flash chips on it, say 'Y'.
290 config MTD_CFI_FLAGADM
291 tristate "CFI Flash device mapping on FlagaDM"
292 depends on PPC32 && 8xx && MTD_CFI
294 Mapping for the Flaga digital module. If you don't have one, ignore
298 tristate "CFI Flash device mapped on IBM 405LP Beech"
299 depends on MTD_CFI && PPC32 && 40x && BEECH
301 This enables access routines for the flash chips on the IBM
302 405LP Beech 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 IBM 405LP Arctic"
307 depends on MTD_CFI && PPC32 && 40x && ARCTIC2
309 This enables access routines for the flash chips on the IBM 405LP
310 Arctic board. If you have one of these boards and would like to
311 use the flash chips on it, say 'Y'.
314 tristate "Flash device mapped on IBM 405GP Walnut"
315 depends on MTD_JEDECPROBE && PPC32 && 40x && WALNUT
317 This enables access routines for the flash chips on the IBM 405GP
318 Walnut board. If you have one of these boards and would like to
319 use the flash chips on it, say 'Y'.
322 tristate "Flash devices mapped on IBM 440GP Ebony"
323 depends on MTD_JEDECPROBE && PPC32 && 44x && EBONY
325 This enables access routines for the flash chips on the IBM 440GP
326 Ebony board. If you have one of these boards and would like to
327 use the flash chips on it, say 'Y'.
330 tristate "Flash devices mapped on IBM 440GX Ocotea"
331 depends on MTD_CFI && PPC32 && 44x && OCOTEA
333 This enables access routines for the flash chips on the IBM 440GX
334 Ocotea board. If you have one of these boards and would like to
335 use the flash chips on it, say 'Y'.
338 tristate "CFI Flash devices mapped on IBM Redwood"
339 depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
341 This enables access routines for the flash chips on the IBM
342 Redwood board. If you have one of these boards and would like to
343 use the flash chips on it, say 'Y'.
345 config MTD_CSTM_MIPS_IXX
346 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
347 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
349 This provides a mapping driver for the Integrated Technology
350 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
351 Reference Board. It provides the necessary addressing, length,
352 buswidth, vpp code and addition setup of the flash device for
353 these boards. In addition, this mapping driver can be used for
354 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
355 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
356 using one partition. The start address can be offset from the
357 beginning of flash and the len can be less than the total flash
358 device size to allow a window into the flash. Both CFI and JEDEC
361 config MTD_CSTM_MIPS_IXX_START
362 hex "Physical start address of flash mapping"
363 depends on MTD_CSTM_MIPS_IXX
366 This is the physical memory location that the MTD driver will
367 use for the flash chips on your particular target board.
368 Refer to the memory map which should hopefully be in the
369 documentation for your board.
371 config MTD_CSTM_MIPS_IXX_LEN
372 hex "Physical length of flash mapping"
373 depends on MTD_CSTM_MIPS_IXX
376 This is the total length that the MTD driver will use for the
377 flash chips on your particular board. Refer to the memory
378 map which should hopefully be in the documentation for your
381 config MTD_CSTM_MIPS_IXX_BUSWIDTH
382 int "Bus width in octets"
383 depends on MTD_CSTM_MIPS_IXX
386 This is the total bus width of the mapping of the flash chips
387 on your particular board.
390 tristate "Momenco Ocelot boot flash device"
391 depends on MIPS && MOMENCO_OCELOT
393 This enables access routines for the boot flash device and for the
394 NVRAM on the Momenco Ocelot board. If you have one of these boards
395 and would like access to either of these, say 'Y'.
397 config MTD_SOLUTIONENGINE
398 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
399 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
401 This enables access to the flash chips on the Hitachi SolutionEngine and
402 similar boards. Say 'Y' if you are building a kernel for such a board.
404 config MTD_ARM_INTEGRATOR
405 tristate "CFI Flash device mapped on ARM Integrator/P720T"
406 depends on ARM && MTD_CFI
409 tristate "Cirrus CDB89712 evaluation board mappings"
410 depends on ARM && MTD_CFI && ARCH_CDB89712
412 This enables access to the flash or ROM chips on the CDB89712 board.
413 If you have such a board, say 'Y'.
416 tristate "CFI Flash device mapped on StrongARM SA11x0"
417 depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
419 This enables access to the flash chips on most platforms based on
420 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
421 If you have such a board, say 'Y'.
424 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
425 depends on ARM && IPAQ_HANDHELD && MTD_CFI
427 This provides a driver for the on-board flash of the iPAQ.
430 tristate "CFI Flash device mapped on DC21285 Footbridge"
431 depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
433 This provides a driver for the flash accessed using Intel's
434 21285 bridge used with Intel's StrongARM processors. More info at
435 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
438 tristate "CFI Flash device mapped on the XScale IQ80310 board"
439 depends on ARM && MTD_CFI && ARCH_IQ80310
441 This enables access routines for the flash chips on the Intel XScale
442 IQ80310 evaluation board. If you have one of these boards and would
443 like to use the flash chips on it, say 'Y'.
446 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
447 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
449 This enables MTD access to flash devices on platforms based
450 on Intel's IXP4xx family of network processors such as the
451 IXDP425 and Coyote. If you have an IXP4xx based board and
452 would like to use the flash chips on it, say 'Y'.
455 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
456 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
458 This enables MTD access to flash devices on platforms based
459 on Intel's IXP2000 family of network processors such as the
460 IXDP425 and Coyote. If you have an IXP2000 based board and
461 would like to use the flash chips on it, say 'Y'.
464 tristate "CFI Flash device mapped on Epxa10db"
465 depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
467 This enables support for the flash devices on the Altera
468 Excalibur XA10 Development Board. If you are building a kernel
469 for on of these boards then you should say 'Y' otherwise say 'N'.
472 tristate "CFI Flash device mapped on the FortuNet board"
473 depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
475 This enables access to the Flash on the FortuNet board. If you
476 have such a board, say 'Y'.
479 tristate "NV-RAM mapping AUTCPU12 board"
480 depends on ARM && ARCH_AUTCPU12
482 This enables access to the NV-RAM on autronix autcpu12 board.
483 If you have such a board, say 'Y'.
486 tristate "CFI Flash device mapped on EDB7312"
487 depends on ARM && MTD_CFI
489 This enables access to the CFI Flash on the Cogent EDB7312 board.
490 If you have such a board, say 'Y' here.
493 tristate "JEDEC Flash device mapped on impA7"
494 depends on ARM && MTD_JEDECPROBE
496 This enables access to the NOR Flash on the impA7 board of
497 implementa GmbH. If you have such a board, say 'Y' here.
500 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
501 depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA
503 This enables access to the flash chips on the Ceiva/Polaroid
504 PhotoMax Digital Picture Frame.
505 If you have such a device, say 'Y'.
508 tristate "NOR Flash device on TOTO board"
509 depends on ARM && ARCH_OMAP && OMAP_TOTO
511 This enables access to the NOR flash on the Texas Instruments
515 tristate "Hynix evaluation board mappings"
516 depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
518 This enables access to the flash chips on the Hynix evaluation boards.
519 If you have such a board, say 'Y'.
522 tristate "CFI Flash device mapped on Interface MPC-1211"
523 depends on SUPERH && SH_MPC1211 && MTD_CFI
525 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
526 If you have such a board, say 'Y'.
528 # This needs CFI or JEDEC, depending on the cards found.
530 tristate "PCI MTD driver"
531 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
533 Mapping for accessing flash devices on add-in cards like the Intel XScale
534 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
535 (please see the manual for the link settings).
537 If you are not sure, say N.
540 tristate "PCMCIA MTD driver"
541 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
543 Map driver for accessing PCMCIA linear flash memory cards. These
544 cards are usually around 4-16MiB in size. This does not include
545 Compact Flash cards which are treated as IDE devices.
548 tristate "Generic uClinux RAM/ROM filesystem support"
549 depends on MTD_PARTITIONS && !MMU
551 Map driver to support image based filesystems for uClinux.
554 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
555 depends on (SBC82xx || SBC8560)
556 select MTD_PARTITIONS
557 select MTD_MAP_BANK_WIDTH_4
558 select MTD_MAP_BANK_WIDTH_1
562 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
563 all three flash regions on CS0, CS1 and CS6 if they are configured
564 correctly by the boot loader.
567 tristate "Map driver for Dy-4 SVME/DMV-182 board."
569 select MTD_PARTITIONS
570 select MTD_MAP_BANK_WIDTH_32
572 select MTD_CFI_AMDSTD
574 Map driver for Dy-4 SVME/DMV-182 board.
577 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
578 depends on ARCH_BAST || MACH_VR1000
579 select MTD_PARTITIONS
580 select MTD_MAP_BANK_WIDTH_16
581 select MTD_JEDECPROBE
583 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
586 Note, this driver *cannot* over-ride the WP link on the
587 board, or currently detect the state of the link.
589 config MTD_BAST_MAXSIZE
590 int "Maximum size for BAST flash area (MiB)"
595 bool "ROM maped on Sharp SL Series"
596 depends on MTD && ARCH_PXA
598 This enables access to the flash chip on the Sharp SL Series of PDAs.
601 tristate "Map driver for platfrom device RAM (mtd-ram)"
605 Map driver for RAM areas described via the platform device
608 This selection automatically selects the map_ram driver.