1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.12 2003/06/23 07:38:11 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.
24 config MTD_PHYSMAP_START
25 hex "Physical start address of flash mapping"
26 depends on MTD_PHYSMAP
29 This is the physical memory location at which the flash chips
30 are mapped on your particular target board. Refer to the
31 memory map which should hopefully be in the documentation for
34 config MTD_PHYSMAP_LEN
35 hex "Physical length of flash mapping"
36 depends on MTD_PHYSMAP
39 This is the total length of the mapping of the flash chips on
40 your particular board. If there is space, or aliases, in the
41 physical memory map between the chips, this could be larger
42 than the total amount of flash present. Refer to the memory
43 map which should hopefully be in the documentation for your
46 config MTD_PHYSMAP_BUSWIDTH
47 int "Bus width in octets"
48 depends on MTD_PHYSMAP
51 This is the total width of the data bus of the flash devices
52 in octets. For example, if you have a data bus width of 32
53 bits, you would set the bus width octect value to 4. This is
54 used internally by the CFI drivers.
57 tristate "Sun Microsystems userflash support"
58 depends on (SPARC32 || SPARC64) && MTD_CFI
60 This provides a 'mapping' driver which supports the way in
61 which user-programmable flash chips are connected on various
62 Sun Microsystems boardsets. This driver will require CFI support
63 in the kernel, so if you did not enable CFI previously, do that now.
66 tristate "CFI Flash device mapped on Photron PNC-2000"
67 depends on X86 && MTD_CFI && MTD_PARTITIONS
69 PNC-2000 is the name of Network Camera product from PHOTRON
70 Ltd. in Japan. It uses CFI-compliant flash.
73 tristate "CFI Flash device mapped on AMD SC520 CDP"
74 depends on X86 && MTD_CFI
76 The SC520 CDP board has two banks of CFI-compliant chips and one
77 Dual-in-line JEDEC chip. This 'mapping' driver supports that
78 arrangement, implementing three MTD devices.
81 tristate "CFI Flash device mapped on AMD NetSc520"
82 depends on X86 && MTD_CFI && MTD_PARTITIONS
84 This enables access routines for the flash chips on the AMD NetSc520
85 demonstration board. If you have one of these boards and would like
86 to use the flash chips on it, say 'Y'.
89 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
90 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
92 This provides a driver for the on-board flash of Arcom Control
93 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
94 By default the flash is split into 3 partitions which are accessed
95 as separate MTD devices. This board utilizes Intel StrataFlash.
97 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
100 tristate "CFI Flash device mapped on Arcom ELAN-104NC"
101 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
103 This provides a driver for the on-board flash of the Arcom Control
104 System's ELAN-104NC development board. By default the flash
105 is split into 3 partitions which are accessed as separate MTD
106 devices. This board utilizes Intel StrataFlash. More info at
107 <http://www.arcomcontrols.com/products/icp/pc104/processors/ELAN104NC.htm>.
110 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
111 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
113 This provides a driver for the on-board flash of the Intel
114 'Lubbock' XScale evaluation board.
117 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
118 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
120 This provides a 'mapping' driver which supports the way in which
121 the flash chips are connected in the Octagon-5066 Single Board
122 Computer. More information on the board is available at
123 <http://www.octagonsystems.com/CPUpages/5066.html>.
126 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
127 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
129 This provides a 'mapping' driver which supports the way in which
130 the flash chips are connected in the Tempustech VMAX SBC301 Single
131 Board Computer. More information on the board is available at
132 <http://www.tempustech.com/>.
134 config MTD_SCx200_DOCFLASH
135 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
136 depends on X86 && MTD_CFI
138 Enable support for a flash chip mapped using the DOCCS signal on a
139 National Semiconductor SCx200 processor.
141 If you don't know what to do here, say N.
143 If compiled as a module, it will be called scx200_docflash.
146 tristate "BIOS flash chip on AMD76x southbridge"
147 depends on X86 && MTD_JEDECPROBE
149 Support for treating the BIOS flash chip on AMD76x motherboards
150 as an MTD device - with this you can reprogram your BIOS.
155 tristate "BIOS flash chip on Intel Hub Controller 2"
156 depends on X86 && MTD_JEDECPROBE && MTD_COMPLEX_MAPPINGS
158 Support for treating the BIOS flash chip on ICH2 motherboards
159 as an MTD device - with this you can reprogram your BIOS.
163 config MTD_SCB2_FLASH
164 tristate "BIOS flash chip on Intel SCB2 boards"
165 depends on X86 && MTD_JEDECPROBE
167 Support for treating the BIOS flash chip on Intel SCB2 boards
168 as an MTD device - with this you can reprogram your BIOS.
173 tristate "Flash chips on Tsunami TIG bus"
174 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
176 Support for the flash chip on Tsunami TIG bus.
179 tristate "Flash chips on LASAT board"
180 depends on LASAT && MTD_CFI
182 Support for the flash chips on the Lasat 100 and 200 boards.
185 tristate "CFI flash device on SnapGear/SecureEdge"
186 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
188 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
191 tristate "Flash devices on Alchemy PB1xxx boards"
192 depends on MIPS && ( MIPS_PB1000 || MIPS_PB1100 || MIPS_PB1500 )
194 Flash memory access on Alchemy Pb1000/Pb1100/Pb1500 boards
196 config MTD_PB1XXX_BOOT
197 bool "PB1x00 boot flash device"
198 depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 )
200 Use the first of the two 32MiB flash banks on Pb1100/Pb1500 board.
201 You can say 'Y' to both this and 'MTD_PB1XXX_USER' below, to use
204 config MTD_PB1XXX_USER
205 bool "PB1x00 user flash device"
206 depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 )
207 default y if MTD_PB1XX_BOOT = n
209 Use the second of the two 32MiB flash banks on Pb1100/Pb1500 board.
210 You can say 'Y' to both this and 'MTD_PB1XXX_BOOT' above, to use
214 tristate "CFI Flash device mapped on DIL/Net PC"
215 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
217 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
218 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
219 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
221 config MTD_DILNETPC_BOOTSIZE
222 hex "Size of DIL/Net PC flash boot partition"
223 depends on MTD_DILNETPC
226 The amount of space taken up by the kernel or Etherboot
227 on the DIL/Net PC flash chips.
230 tristate "BIOS flash chip on Intel L440GX boards"
231 depends on X86 && MTD_JEDECPROBE
233 Support for treating the BIOS flash chip on Intel L440GX motherboards
234 as an MTD device - with this you can reprogram your BIOS.
239 tristate "CFI Flash device mapped on TQM8XXL"
240 depends on MTD_CFI && PPC32 && 8xx && TQM8xxL
242 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
243 chips, currently uses AMD one. This 'mapping' driver supports
244 that arrangement, allowing the CFI probe and command set driver
245 code to communicate with the chips on the TQM8xxL board. More at
246 <http://www.denx.de/embedded-ppc-en.html>.
249 tristate "CFI Flash device mapped on RPX Lite or CLLF"
250 depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)
252 The RPXLite PowerPC board has CFI-compliant chips mapped in
253 a strange sparse mapping. This 'mapping' driver supports that
254 arrangement, allowing the CFI probe and command set driver code
255 to communicate with the chips on the RPXLite board. More at
256 <http://www.embeddedplanet.com/>.
259 tristate "System flash on MBX860 board"
260 depends on MTD_CFI && PPC32 && 8xx && MBX
262 This enables access routines for the flash chips on the Motorola
263 MBX860 board. If you have one of these boards and would like
264 to use the flash chips on it, say 'Y'.
267 tristate "CFI Flash device mapped on D-Box2"
268 depends on PPC32 && 8xx && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
270 This enables access routines for the flash chips on the Nokia/Sagem
271 D-Box 2 board. If you have one of these boards and would like to use
272 the flash chips on it, say 'Y'.
274 config MTD_CFI_FLAGADM
275 tristate "CFI Flash device mapping on FlagaDM"
276 depends on PPC32 && 8xx && MTD_CFI
278 Mapping for the Flaga digital module. If you don´t have one, ignore
282 tristate "CFI Flash device mapped on IBM 405LP Beech"
283 depends on MTD_CFI && PPC32 && 40x && BEECH
285 This enables access routines for the flash chips on the IBM
286 405LP Beech board. If you have one of these boards and would like
287 to use the flash chips on it, say 'Y'.
290 tristate "CFI Flash device mapped on IBM 405LP Arctic"
291 depends on MTD_CFI && PPC32 && 40x && ARCTIC2
293 This enables access routines for the flash chips on the IBM 405LP
294 Arctic board. If you have one of these boards and would like to
295 use the flash chips on it, say 'Y'.
298 tristate "CFI Flash device mapped on IBM 440GP Ebony"
299 depends on MTD_CFI && PPC32 && 440 && EBONY
301 This enables access routines for the flash chips on the IBM 440GP
302 Ebony board. If you have one of these boards and would like to
303 use the flash chips on it, say 'Y'.
306 tristate "CFI Flash devices mapped on IBM Redwood"
307 depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
309 This enables access routines for the flash chips on the IBM
310 Redwood board. If you have one of these boards and would like to
311 use the flash chips on it, say 'Y'.
313 config MTD_CSTM_MIPS_IXX
314 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
315 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
317 This provides a mapping driver for the Integrated Tecnology
318 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
319 Reference Board. It provides the necessary addressing, length,
320 buswidth, vpp code and addition setup of the flash device for
321 these boards. In addition, this mapping driver can be used for
322 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
323 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
324 using one partition. The start address can be offset from the
325 beginning of flash and the len can be less than the total flash
326 device size to allow a window into the flash. Both CFI and JEDEC
329 config MTD_CSTM_MIPS_IXX_START
330 hex "Physical start address of flash mapping"
331 depends on MTD_CSTM_MIPS_IXX
334 This is the physical memory location that the MTD driver will
335 use for the flash chips on your particular target board.
336 Refer to the memory map which should hopefully be in the
337 documentation for your board.
339 config MTD_CSTM_MIPS_IXX_LEN
340 hex "Physical length of flash mapping"
341 depends on MTD_CSTM_MIPS_IXX
344 This is the total length that the MTD driver will use for the
345 flash chips on your particular board. Refer to the memory
346 map which should hopefully be in the documentation for your
349 config MTD_CSTM_MIPS_IXX_BUSWIDTH
350 int "Bus width in octets"
351 depends on MTD_CSTM_MIPS_IXX
354 This is the total bus width of the mapping of the flash chips
355 on your particular board.
358 tristate "Momenco Ocelot boot flash device"
359 depends on MIPS && MOMENCO_OCELOT
361 This enables access routines for the boot flash device and for the
362 NVRAM on the Momenco Ocelot board. If you have one of these boards
363 and would like access to either of these, say 'Y'.
365 config MTD_SOLUTIONENGINE
366 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
367 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
369 This enables access to the flash chips on the Hitachi SolutionEngine and
370 similar boards. Say 'Y' if you are building a kernel for such a board.
372 config MTD_ARM_INTEGRATOR
373 tristate "CFI Flash device mapped on ARM Integrator/P720T"
374 depends on ARM && MTD_CFI
377 tristate "Cirrus CDB89712 evaluation board mappings"
378 depends on ARM && MTD_CFI && ARCH_CDB89712
380 This enables access to the flash or ROM chips on the CDB89712 board.
381 If you have such a board, say 'Y'.
384 tristate "CFI Flash device mapped on StrongARM SA11x0"
385 depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
387 This enables access to the flash chips on most platforms based on
388 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
389 If you have such a board, say 'Y'.
392 tristate "CFI Flash device mapped on DC21285 Footbridge"
393 depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
395 This provides a driver for the flash accessed using Intel's
396 21285 bridge used with Intel's StrongARM processors. More info at
397 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
400 tristate "CFI Flash device mapped on the XScale IQ80310 board"
401 depends on ARM && MTD_CFI && ARCH_IQ80310
403 This enables access routines for the flash chips on the Intel XScale
404 IQ80310 evaluation board. If you have one of these boards and would
405 like to use the flash chips on it, say 'Y'.
408 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
409 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
411 This eables MTD access to flash devices on platforms based
412 on Intel's IXP4xx family of network processors such as the
413 IXDP425 and Coyote. If you have an IXP4xx based board and
414 would like to use the flash chips on it, say 'Y'.
417 tristate "CFI Flash device mapped on Epxa10db"
418 depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
420 This enables support for the flash devices on the Altera
421 Excalibur XA10 Development Board. If you are building a kernel
422 for on of these boards then you should say 'Y' otherwise say 'N'.
425 tristate "CFI Flash device mapped on the FortuNet board"
426 depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
428 This enables access to the Flash on the FortuNet board. If you
429 have such a board, say 'Y'.
432 tristate "NV-RAM mapping AUTCPU12 board"
433 depends on ARM && ARCH_AUTCPU12
435 This enables access to the NV-RAM on autronix autcpu12 board.
436 If you have such a board, say 'Y'.
439 tristate "CFI Flash device mapped on EDB7312"
440 depends on ARM && MTD_CFI
442 This enables access to the CFI Flash on the Cogent EDB7312 board.
443 If you have such a board, say 'Y' here.
446 tristate "JEDEC Flash device mapped on impA7"
447 depends on ARM && MTD_JEDECPROBE
449 This enables access to the NOR Flash on the impA7 board of
450 implementa GmbH. If you have such a board, say 'Y' here.
453 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
454 depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA
456 This enables access to the flash chips on the Ceiva/Polaroid
457 PhotoMax Digital Picture Frame.
458 If you have such a device, say 'Y'.
461 tristate "Hynix evaluation board mappings"
462 depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
464 This enables access to the flash chips on the Hynix evaluation boards.
465 If you have such a board, say 'Y'.
467 # This needs CFI or JEDEC, depending on the cards found.
469 tristate "PCI MTD driver"
470 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
472 Mapping for accessing flash devices on add-in cards like the Intel XScale
473 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
474 (please see the manual for the link settings).
476 If you are not sure, say N.
479 tristate "PCMCIA MTD driver"
480 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
482 Map driver for accessing PCMCIA linear flash memory cards. These
483 cards are usually around 4-16MiB in size. This does not include
484 Compact Flash cards which are treated as IDE devices.
487 tristate "Generic uClinux RAM/ROM filesystem support"
488 depends on MTD_PARTITIONS && !MMU
490 Map driver to support image based filesystems for uClinux.
493 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
494 depends on MTD_PARTITIONS && SBC82xx
496 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
497 all three flash regions on CS0, CS1 and CS6 if they are configured
498 correctly by the boot loader.