1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.30 2004/07/21 00:16:14 jwboyer 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 "CFI Flash device mapped on Arcom SBC-GXx boards"
97 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
99 This provides a driver for the on-board flash of Arcom Control
100 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
101 By default the flash is split into 3 partitions which are accessed
102 as separate MTD devices. This board utilizes Intel StrataFlash.
104 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
106 config MTD_ELAN_104NC
107 tristate "CFI Flash device mapped on Arcom ELAN-104NC"
108 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
110 This provides a driver for the on-board flash of the Arcom Control
111 System's ELAN-104NC development board. By default the flash
112 is split into 3 partitions which are accessed as separate MTD
113 devices. This board utilizes Intel StrataFlash. More info at
114 <http://www.arcomcontrols.com/products/icp/pc104/processors/ELAN104NC.htm>.
117 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
118 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
120 This provides a driver for the on-board flash of the Intel
121 'Lubbock' XScale evaluation board.
124 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
125 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
127 This provides a 'mapping' driver which supports the way in which
128 the flash chips are connected in the Octagon-5066 Single Board
129 Computer. More information on the board is available at
130 <http://www.octagonsystems.com/CPUpages/5066.html>.
133 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
134 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
136 This provides a 'mapping' driver which supports the way in which
137 the flash chips are connected in the Tempustech VMAX SBC301 Single
138 Board Computer. More information on the board is available at
139 <http://www.tempustech.com/>.
141 config MTD_SCx200_DOCFLASH
142 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
143 depends on X86 && MTD_CFI
145 Enable support for a flash chip mapped using the DOCCS signal on a
146 National Semiconductor SCx200 processor.
148 If you don't know what to do here, say N.
150 If compiled as a module, it will be called scx200_docflash.
153 tristate "BIOS flash chip on AMD76x southbridge"
154 depends on X86 && MTD_JEDECPROBE
156 Support for treating the BIOS flash chip on AMD76x motherboards
157 as an MTD device - with this you can reprogram your BIOS.
162 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
163 depends on X86 && MTD_JEDECPROBE && MTD_COMPLEX_MAPPINGS
165 Support for treating the BIOS flash chip on ICHX motherboards
166 as an MTD device - with this you can reprogram your BIOS.
170 config MTD_SCB2_FLASH
171 tristate "BIOS flash chip on Intel SCB2 boards"
172 depends on X86 && MTD_JEDECPROBE
174 Support for treating the BIOS flash chip on Intel SCB2 boards
175 as an MTD device - with this you can reprogram your BIOS.
180 tristate "Flash chips on Tsunami TIG bus"
181 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
183 Support for the flash chip on Tsunami TIG bus.
186 tristate "Flash chips on LASAT board"
189 Support for the flash chips on the Lasat 100 and 200 boards.
192 tristate "CFI flash device on SnapGear/SecureEdge"
193 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
195 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
198 tristate "Flash devices on Alchemy PB1xxx boards"
199 depends on MIPS && ( MIPS_PB1000 || MIPS_PB1100 || MIPS_PB1500 )
201 Flash memory access on Alchemy Pb1000/Pb1100/Pb1500 boards
203 config MTD_PB1XXX_BOOT
204 bool "PB1x00 boot flash device"
205 depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 )
207 Use the first of the two 32MiB flash banks on Pb1100/Pb1500 board.
208 You can say 'Y' to both this and 'MTD_PB1XXX_USER' below, to use
211 config MTD_PB1XXX_USER
212 bool "PB1x00 user flash device"
213 depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 )
214 default y if MTD_PB1XX_BOOT = n
216 Use the second of the two 32MiB flash banks on Pb1100/Pb1500 board.
217 You can say 'Y' to both this and 'MTD_PB1XXX_BOOT' above, to use
221 tristate "Flash devices on Alchemy PB1550 board"
222 depends on MIPS && MIPS_PB1550
224 Flash memory access on Alchemy Pb1550 board
226 config MTD_PB1550_BOOT
227 bool "PB1550 boot flash device"
228 depends on MTD_PB1550
230 Use the first of the two 64MiB flash banks on Pb1550 board.
231 You can say 'Y' to both this and 'MTD_PB1550_USER' below, to use
234 config MTD_PB1550_USER
235 bool "PB1550 user flash device"
236 depends on MTD_PB1550
237 default y if MTD_PB1550_BOOT = n
239 Use the second of the two 64MiB flash banks on Pb1550 board.
240 You can say 'Y' to both this and 'MTD_PB1550_BOOT' above, to use
244 tristate "Flash devices on Alchemy DB1550 board"
245 depends on MIPS && MIPS_DB1550
247 Flash memory access on Alchemy Db1550 board
249 config MTD_DB1550_BOOT
250 bool "DB1550 boot flash device"
251 depends on MTD_DB1550
253 Use the first of the two 64MiB flash banks on Db1550 board.
254 You can say 'Y' to both this and 'MTD_DB1550_USER' below, to use
257 config MTD_DB1550_USER
258 bool "DB1550 user flash device"
259 depends on MTD_DB1550
260 default y if MTD_DB1550_BOOT = n
262 Use the second of the two 64MiB flash banks on Db1550 board.
263 You can say 'Y' to both this and 'MTD_DB1550_BOOT' above, to use
267 tristate "CFI Flash device mapped on DIL/Net PC"
268 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
270 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
271 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
272 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
274 config MTD_DILNETPC_BOOTSIZE
275 hex "Size of DIL/Net PC flash boot partition"
276 depends on MTD_DILNETPC
279 The amount of space taken up by the kernel or Etherboot
280 on the DIL/Net PC flash chips.
283 tristate "BIOS flash chip on Intel L440GX boards"
284 depends on X86 && MTD_JEDECPROBE
286 Support for treating the BIOS flash chip on Intel L440GX motherboards
287 as an MTD device - with this you can reprogram your BIOS.
292 tristate "Flash device on SBC8240"
293 depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260
295 Flash access on the SBC8240 board from Wind River. See
296 <http://www.windriver.com/products/sbc8240/>
299 tristate "CFI Flash device mapped on TQM8XXL"
300 depends on MTD_CFI && PPC32 && 8xx && TQM8xxL
302 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
303 chips, currently uses AMD one. This 'mapping' driver supports
304 that arrangement, allowing the CFI probe and command set driver
305 code to communicate with the chips on the TQM8xxL board. More at
306 <http://www.denx.de/embedded-ppc-en.html>.
309 tristate "CFI Flash device mapped on RPX Lite or CLLF"
310 depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)
312 The RPXLite PowerPC board has CFI-compliant chips mapped in
313 a strange sparse mapping. This 'mapping' driver supports that
314 arrangement, allowing the CFI probe and command set driver code
315 to communicate with the chips on the RPXLite board. More at
316 <http://www.embeddedplanet.com/>.
319 tristate "System flash on MBX860 board"
320 depends on MTD_CFI && PPC32 && 8xx && MBX
322 This enables access routines for the flash chips on the Motorola
323 MBX860 board. If you have one of these boards and would like
324 to use the flash chips on it, say 'Y'.
327 tristate "CFI Flash device mapped on D-Box2"
328 depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
330 This enables access routines for the flash chips on the Nokia/Sagem
331 D-Box 2 board. If you have one of these boards and would like to use
332 the flash chips on it, say 'Y'.
334 config MTD_CFI_FLAGADM
335 tristate "CFI Flash device mapping on FlagaDM"
336 depends on PPC32 && 8xx && MTD_CFI
338 Mapping for the Flaga digital module. If you don´t have one, ignore
342 tristate "CFI Flash device mapped on IBM 405LP Beech"
343 depends on MTD_CFI && PPC32 && 40x && BEECH
345 This enables access routines for the flash chips on the IBM
346 405LP Beech board. If you have one of these boards and would like
347 to use the flash chips on it, say 'Y'.
350 tristate "CFI Flash device mapped on IBM 405LP Arctic"
351 depends on MTD_CFI && PPC32 && 40x && ARCTIC2
353 This enables access routines for the flash chips on the IBM 405LP
354 Arctic board. If you have one of these boards and would like to
355 use the flash chips on it, say 'Y'.
358 tristate "CFI Flash device mapped on IBM 440GP Ebony"
359 depends on MTD_CFI && PPC32 && 440 && EBONY
361 This enables access routines for the flash chips on the IBM 440GP
362 Ebony board. If you have one of these boards and would like to
363 use the flash chips on it, say 'Y'.
366 tristate "CFI Flash devices mapped on IBM Redwood"
367 depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
369 This enables access routines for the flash chips on the IBM
370 Redwood board. If you have one of these boards and would like to
371 use the flash chips on it, say 'Y'.
373 config MTD_CSTM_MIPS_IXX
374 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
375 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
377 This provides a mapping driver for the Integrated Tecnology
378 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
379 Reference Board. It provides the necessary addressing, length,
380 buswidth, vpp code and addition setup of the flash device for
381 these boards. In addition, this mapping driver can be used for
382 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
383 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
384 using one partition. The start address can be offset from the
385 beginning of flash and the len can be less than the total flash
386 device size to allow a window into the flash. Both CFI and JEDEC
389 config MTD_CSTM_MIPS_IXX_START
390 hex "Physical start address of flash mapping"
391 depends on MTD_CSTM_MIPS_IXX
394 This is the physical memory location that the MTD driver will
395 use for the flash chips on your particular target board.
396 Refer to the memory map which should hopefully be in the
397 documentation for your board.
399 config MTD_CSTM_MIPS_IXX_LEN
400 hex "Physical length of flash mapping"
401 depends on MTD_CSTM_MIPS_IXX
404 This is the total length that the MTD driver will use for the
405 flash chips on your particular board. Refer to the memory
406 map which should hopefully be in the documentation for your
409 config MTD_CSTM_MIPS_IXX_BUSWIDTH
410 int "Bus width in octets"
411 depends on MTD_CSTM_MIPS_IXX
414 This is the total bus width of the mapping of the flash chips
415 on your particular board.
418 tristate "Momenco Ocelot boot flash device"
419 depends on MIPS && MOMENCO_OCELOT
421 This enables access routines for the boot flash device and for the
422 NVRAM on the Momenco Ocelot board. If you have one of these boards
423 and would like access to either of these, say 'Y'.
425 config MTD_SOLUTIONENGINE
426 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
427 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
429 This enables access to the flash chips on the Hitachi SolutionEngine and
430 similar boards. Say 'Y' if you are building a kernel for such a board.
432 config MTD_ARM_INTEGRATOR
433 tristate "CFI Flash device mapped on ARM Integrator/P720T"
434 depends on ARM && MTD_CFI
437 tristate "Cirrus CDB89712 evaluation board mappings"
438 depends on ARM && MTD_CFI && ARCH_CDB89712
440 This enables access to the flash or ROM chips on the CDB89712 board.
441 If you have such a board, say 'Y'.
444 tristate "CFI Flash device mapped on StrongARM SA11x0"
445 depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
447 This enables access to the flash chips on most platforms based on
448 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
449 If you have such a board, say 'Y'.
452 tristate "CFI Flash device mapped on DC21285 Footbridge"
453 depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
455 This provides a driver for the flash accessed using Intel's
456 21285 bridge used with Intel's StrongARM processors. More info at
457 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
460 tristate "CFI Flash device mapped on the XScale IQ80310 board"
461 depends on ARM && MTD_CFI && ARCH_IQ80310
463 This enables access routines for the flash chips on the Intel XScale
464 IQ80310 evaluation board. If you have one of these boards and would
465 like to use the flash chips on it, say 'Y'.
468 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
469 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
471 This eables MTD access to flash devices on platforms based
472 on Intel's IXP4xx family of network processors such as the
473 IXDP425 and Coyote. If you have an IXP4xx based board and
474 would like to use the flash chips on it, say 'Y'.
477 tristate "CFI Flash device mapped on Epxa10db"
478 depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
480 This enables support for the flash devices on the Altera
481 Excalibur XA10 Development Board. If you are building a kernel
482 for on of these boards then you should say 'Y' otherwise say 'N'.
485 tristate "CFI Flash device mapped on the FortuNet board"
486 depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
488 This enables access to the Flash on the FortuNet board. If you
489 have such a board, say 'Y'.
492 tristate "NV-RAM mapping AUTCPU12 board"
493 depends on ARM && ARCH_AUTCPU12
495 This enables access to the NV-RAM on autronix autcpu12 board.
496 If you have such a board, say 'Y'.
499 tristate "CFI Flash device mapped on EDB7312"
500 depends on ARM && MTD_CFI
502 This enables access to the CFI Flash on the Cogent EDB7312 board.
503 If you have such a board, say 'Y' here.
506 tristate "JEDEC Flash device mapped on impA7"
507 depends on ARM && MTD_JEDECPROBE
509 This enables access to the NOR Flash on the impA7 board of
510 implementa GmbH. If you have such a board, say 'Y' here.
513 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
514 depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA
516 This enables access to the flash chips on the Ceiva/Polaroid
517 PhotoMax Digital Picture Frame.
518 If you have such a device, say 'Y'.
521 tristate "NOR Flash device on TOTO board"
522 depends on ARM && ARCH_OMAP && OMAP_TOTO
524 This enables access to the NOR flash on the Texas Instruments
528 tristate "Hynix evaluation board mappings"
529 depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
531 This enables access to the flash chips on the Hynix evaluation boards.
532 If you have such a board, say 'Y'.
535 tristate "CFI Flash device mapped on Interface MPC-1211"
536 depends on SUPERH && SH_MPC1211 && MTD_CFI
538 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
539 If you have such a board, say 'Y'.
541 # This needs CFI or JEDEC, depending on the cards found.
543 tristate "PCI MTD driver"
544 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
546 Mapping for accessing flash devices on add-in cards like the Intel XScale
547 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
548 (please see the manual for the link settings).
550 If you are not sure, say N.
553 tristate "PCMCIA MTD driver"
554 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
556 Map driver for accessing PCMCIA linear flash memory cards. These
557 cards are usually around 4-16MiB in size. This does not include
558 Compact Flash cards which are treated as IDE devices.
561 tristate "Generic uClinux RAM/ROM filesystem support"
562 depends on MTD_PARTITIONS && !MMU
564 Map driver to support image based filesystems for uClinux.
567 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
568 depends on (SBC82xx || SBC8560)
569 select MTD_PARTITIONS
570 select MTD_MAP_BANK_WIDTH_4
571 select MTD_MAP_BANK_WIDTH_1
575 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
576 all three flash regions on CS0, CS1 and CS6 if they are configured
577 correctly by the boot loader.
580 tristate "Map driver for Dy-4 SVME/DMV-182 board."
582 select MTD_PARTITIONS
583 select MTD_MAP_BANK_WIDTH_32
585 select MTD_CFI_AMDSTD
587 Map driver for Dy-4 SVME/DMV-182 board.