1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner 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"
16 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
18 This provides a 'mapping' driver which allows the NOR Flash and
19 ROM driver code to communicate with chips which are mapped
20 physically into the CPU's memory. You will need to configure
21 the physical address and size of the flash chips on your
22 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 SPARC && 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 && MTD_CONCAT
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"
100 select MTD_CFI_AMDSTD
102 This provides a driver for the on-board flash of the Technologic
103 System's TS-5500 board. The 2MB flash is split into 3 partitions
104 which are accessed as separate MTD devices.
106 mtd0 and mtd2 are the two BIOS drives, which use the resident
107 flash disk (RFD) flash translation layer.
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 succeed.
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 "LASAT flash device"
204 depends on LASAT && MTD_CFI
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.
216 tristate "CFI Flash device mapped on Moxa UC7110-LX board"
217 depends on MTD_CFI && MTD_PARTITIONS
219 Support for flash chips on the Moxa UC7110-LX version2 platform.
222 tristate "CFI flash device on SnapGear/GEODE boards"
223 depends on X86 && MTD_PARTITIONS
225 Support for flash chips on SnapGear GEODE based boards.
228 tristate 'CFI Flash device mapped on SnapGear/Cyberguard ARM/XSCALE boards'
229 depends on MTD_CFI && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
231 Support for flash chips on the SnapGear/Cyberguard ARM/XSCALE platforms.
234 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
235 depends on SOC_AU1X00
237 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
240 tristate "4G Systems MTX-1 Flash device"
241 depends on MIPS && MIPS_MTX1
243 Flash memory access on 4G Systems MTX-1 Board. If you have one of
244 these boards and would like to use the flash chips on it, say 'Y'.
247 tristate "CFI Flash device mapped on DIL/Net PC"
248 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
250 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
251 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
252 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
254 config MTD_DILNETPC_BOOTSIZE
255 hex "Size of DIL/Net PC flash boot partition"
256 depends on MTD_DILNETPC
259 The amount of space taken up by the kernel or Etherboot
260 on the DIL/Net PC flash chips.
263 tristate "BIOS flash chip on Intel L440GX boards"
264 depends on X86 && MTD_JEDECPROBE
266 Support for treating the BIOS flash chip on Intel L440GX motherboards
267 as an MTD device - with this you can reprogram your BIOS.
272 tristate "Flash device on SBC8240"
273 depends on MTD_JEDECPROBE && 8260
275 Flash access on the SBC8240 board from Wind River. See
276 <http://www.windriver.com/products/sbc8240/>
279 tristate "CFI Flash device mapped on TQM8XXL"
280 depends on MTD_CFI && TQM8xxL
282 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
283 chips, currently uses AMD one. This 'mapping' driver supports
284 that arrangement, allowing the CFI probe and command set driver
285 code to communicate with the chips on the TQM8xxL board. More at
286 <http://www.denx.de/embedded-ppc-en.html>.
289 tristate "CFI Flash device mapped on RPX Lite or CLLF"
290 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
292 The RPXLite PowerPC board has CFI-compliant chips mapped in
293 a strange sparse mapping. This 'mapping' driver supports that
294 arrangement, allowing the CFI probe and command set driver code
295 to communicate with the chips on the RPXLite board. More at
296 <http://www.embeddedplanet.com/>.
299 tristate "System flash on MBX860 board"
300 depends on MTD_CFI && MBX
302 This enables access routines for the flash chips on the Motorola
303 MBX860 board. If you have one of these boards and would like
304 to use the flash chips on it, say 'Y'.
307 tristate "CFI Flash device mapped on D-Box2"
308 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
310 This enables access routines for the flash chips on the Nokia/Sagem
311 D-Box 2 board. If you have one of these boards and would like to use
312 the flash chips on it, say 'Y'.
314 config MTD_CFI_FLAGADM
315 tristate "CFI Flash device mapping on FlagaDM"
316 depends on 8xx && MTD_CFI
318 Mapping for the Flaga digital module. If you don't have one, ignore
322 tristate "CFI Flash device mapped on IBM 405LP Beech"
323 depends on MTD_CFI && BEECH
325 This enables access routines for the flash chips on the IBM
326 405LP Beech board. If you have one of these boards and would like
327 to use the flash chips on it, say 'Y'.
330 tristate "CFI Flash device mapped on IBM 405LP Arctic"
331 depends on MTD_CFI && ARCTIC2
333 This enables access routines for the flash chips on the IBM 405LP
334 Arctic board. If you have one of these boards and would like to
335 use the flash chips on it, say 'Y'.
338 tristate "Flash device mapped on IBM 405GP Walnut"
339 depends on MTD_JEDECPROBE && WALNUT
341 This enables access routines for the flash chips on the IBM 405GP
342 Walnut board. If you have one of these boards and would like to
343 use the flash chips on it, say 'Y'.
346 tristate "Flash devices mapped on IBM 440GP Ebony"
347 depends on MTD_JEDECPROBE && EBONY
349 This enables access routines for the flash chips on the IBM 440GP
350 Ebony board. If you have one of these boards and would like to
351 use the flash chips on it, say 'Y'.
354 tristate "Flash devices mapped on IBM 440GX Ocotea"
355 depends on MTD_CFI && OCOTEA
357 This enables access routines for the flash chips on the IBM 440GX
358 Ocotea board. If you have one of these boards and would like to
359 use the flash chips on it, say 'Y'.
362 tristate "CFI Flash devices mapped on IBM Redwood"
363 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
365 This enables access routines for the flash chips on the IBM
366 Redwood board. If you have one of these boards and would like to
367 use the flash chips on it, say 'Y'.
370 tristate "Flash device mapped on TQ Components TQM834x Boards"
371 depends on MTD_CFI && TQM834x
373 This enables access routines for the flash chips on the
374 TQ Components TQM834x boards. If you have one of these boards
375 and would like to use the flash chips on it, say 'Y'.
377 config MTD_CSTM_MIPS_IXX
378 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
379 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
381 This provides a mapping driver for the Integrated Technology
382 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
383 Reference Board. It provides the necessary addressing, length,
384 buswidth, vpp code and addition setup of the flash device for
385 these boards. In addition, this mapping driver can be used for
386 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
387 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
388 using one partition. The start address can be offset from the
389 beginning of flash and the len can be less than the total flash
390 device size to allow a window into the flash. Both CFI and JEDEC
393 config MTD_CSTM_MIPS_IXX_START
394 hex "Physical start address of flash mapping"
395 depends on MTD_CSTM_MIPS_IXX
398 This is the physical memory location that the MTD driver will
399 use for the flash chips on your particular target board.
400 Refer to the memory map which should hopefully be in the
401 documentation for your board.
403 config MTD_CSTM_MIPS_IXX_LEN
404 hex "Physical length of flash mapping"
405 depends on MTD_CSTM_MIPS_IXX
408 This is the total length that the MTD driver will use for the
409 flash chips on your particular board. Refer to the memory
410 map which should hopefully be in the documentation for your
413 config MTD_CSTM_MIPS_IXX_BUSWIDTH
414 int "Bus width in octets"
415 depends on MTD_CSTM_MIPS_IXX
418 This is the total bus width of the mapping of the flash chips
419 on your particular board.
422 tristate "Momenco Ocelot boot flash device"
423 depends on MIPS && MOMENCO_OCELOT
425 This enables access routines for the boot flash device and for the
426 NVRAM on the Momenco Ocelot board. If you have one of these boards
427 and would like access to either of these, say 'Y'.
429 config MTD_SOLUTIONENGINE
430 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
431 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
433 This enables access to the flash chips on the Hitachi SolutionEngine and
434 similar boards. Say 'Y' if you are building a kernel for such a board.
436 config MTD_ARM_INTEGRATOR
437 tristate "CFI Flash device mapped on ARM Integrator/P720T"
438 depends on ARM && MTD_CFI
441 tristate "Cirrus CDB89712 evaluation board mappings"
442 depends on MTD_CFI && ARCH_CDB89712
444 This enables access to the flash or ROM chips on the CDB89712 board.
445 If you have such a board, say 'Y'.
448 tristate "CFI Flash device mapped on StrongARM SA11x0"
449 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
451 This enables access to the flash chips on most platforms based on
452 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
453 If you have such a board, say 'Y'.
456 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
457 depends on IPAQ_HANDHELD && MTD_CFI
459 This provides a driver for the on-board flash of the iPAQ.
462 tristate "CFI Flash device mapped on DC21285 Footbridge"
463 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
465 This provides a driver for the flash accessed using Intel's
466 21285 bridge used with Intel's StrongARM processors. More info at
467 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
470 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
471 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
473 This enables MTD access to flash devices on platforms based
474 on Intel's IXP4xx family of network processors such as the
475 IXDP425 and Coyote. If you have an IXP4xx based board and
476 would like to use the flash chips on it, say 'Y'.
479 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
480 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
482 This enables MTD access to flash devices on platforms based
483 on Intel's IXP2000 family of network processors such as the
484 IXDP425 and Coyote. If you have an IXP2000 based board and
485 would like to use the flash chips on it, say 'Y'.
488 tristate "CFI Flash device mapped on the FortuNet board"
489 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
491 This enables access to the Flash on the FortuNet board. If you
492 have such a board, say 'Y'.
495 tristate "NV-RAM mapping AUTCPU12 board"
496 depends on ARCH_AUTCPU12
498 This enables access to the NV-RAM on autronix autcpu12 board.
499 If you have such a board, say 'Y'.
502 tristate "CFI Flash device mapped on EDB7312"
503 depends on ARCH_EDB7312 && MTD_CFI
505 This enables access to the CFI Flash on the Cogent EDB7312 board.
506 If you have such a board, say 'Y' here.
509 tristate "JEDEC Flash device mapped on impA7"
510 depends on ARM && MTD_JEDECPROBE
512 This enables access to the NOR Flash on the impA7 board of
513 implementa GmbH. If you have such a board, say 'Y' here.
516 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
517 depends on MTD_JEDECPROBE && ARCH_CEIVA
519 This enables access to the flash chips on the Ceiva/Polaroid
520 PhotoMax Digital Picture Frame.
521 If you have such a device, say 'Y'.
524 tristate "NOR Flash device on TOTO board"
525 depends on ARCH_OMAP && OMAP_TOTO
527 This enables access to the NOR flash on the Texas Instruments
531 tristate "Hynix evaluation board mappings"
532 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
534 This enables access to the flash chips on the Hynix evaluation boards.
535 If you have such a board, say 'Y'.
538 tristate "CFI Flash device mapped on Interface MPC-1211"
539 depends on SH_MPC1211 && MTD_CFI
541 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
542 If you have such a board, say 'Y'.
545 tristate "TI OMAP board mappings"
546 depends on MTD_CFI && ARCH_OMAP
548 This enables access to the NOR flash chips on TI OMAP-based
549 boards defining flash platform devices and flash platform data.
550 These boards include the Innovator, H2, H3, OSK, Perseus2, and
551 more. If you have such a board, say 'Y'.
553 # This needs CFI or JEDEC, depending on the cards found.
555 tristate "PCI MTD driver"
556 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
558 Mapping for accessing flash devices on add-in cards like the Intel XScale
559 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
560 (please see the manual for the link settings).
562 If you are not sure, say N.
565 tristate "PCMCIA MTD driver"
566 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
568 Map driver for accessing PCMCIA linear flash memory cards. These
569 cards are usually around 4-16MiB in size. This does not include
570 Compact Flash cards which are treated as IDE devices.
572 config MTD_PCMCIA_ANONYMOUS
573 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
574 depends on MTD_PCMCIA
576 If this option is enabled, PCMCIA cards which do not report
577 anything about themselves are assumed to be MTD cards.
582 tristate "Generic uClinux RAM/ROM filesystem support"
583 depends on MTD_PARTITIONS && !MMU
585 Map driver to support image based filesystems for uClinux.
587 config MTD_UCLINUX_EBSS
588 bool "uClinux RAM/ROM filesystem is located at ebss"
589 depends on MTD_UCLINUX
592 The filesystem is located directly after the kernel in memory.
594 config MTD_UCLINUX_ADDRESS
595 hex "uClinux RAM/ROM filesystem address"
597 depends on MTD_UCLINUX && !MTD_UCLINUX_EBSS
599 The filesystem is located at the given address.
602 prompt "uClinux RAM/ROM is located in ROM/RAM"
603 default MTD_UCLINUX_RAM
604 depends on MTD_UCLINUX && !MTD_UCLINUX_EBSS
606 config MTD_UCLINUX_RAM
608 config MTD_UCLINUX_ROM
613 tristate "Cobra5329 mapping"
614 depends on MTD_PARTITIONS && COBRA5329
616 Map driver to support Cobra5329 Flash.
618 config MTD_SNAPGEARuC
619 tristate "SnapGear uClinux RAM/ROM filesystem support"
620 depends on MTD_PARTITIONS
622 Map driver for Flash and RAM in the SnapGear devices.
625 tristate "Freescale M520xEVB Flash filesystem support"
626 depends on MTD_PARTITIONS
628 Map for M5208EVB & M5207EVB Flash Partition.
631 tristate "RAM/ROM filesystem support for Sarasvati from Sneha Technologies S.L."
632 depends on MTD_PARTITIONS && SNEHA && CPU16B
634 Map driver to support image based filesystems for CPU16B.
638 depends on MTD_SNAPGEARuC
661 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
662 depends on (SBC82xx || SBC8560)
663 select MTD_PARTITIONS
664 select MTD_MAP_BANK_WIDTH_4
665 select MTD_MAP_BANK_WIDTH_1
669 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
670 all three flash regions on CS0, CS1 and CS6 if they are configured
671 correctly by the boot loader.
674 tristate "Map driver for Dy-4 SVME/DMV-182 board."
676 select MTD_PARTITIONS
677 select MTD_MAP_BANK_WIDTH_32
679 select MTD_CFI_AMDSTD
681 Map driver for Dy-4 SVME/DMV-182 board.
684 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
685 depends on ARCH_BAST || MACH_VR1000
686 select MTD_PARTITIONS
687 select MTD_MAP_BANK_WIDTH_16
688 select MTD_JEDECPROBE
690 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
693 Note, this driver *cannot* over-ride the WP link on the
694 board, or currently detect the state of the link.
696 config MTD_BAST_MAXSIZE
697 int "Maximum size for BAST flash area (MiB)"
702 tristate "CFI Flash device mapped on TI TMS320DM270"
703 depends on ARM && MACH_DM270 && MTD_CFI
705 This enables access to the flash chips on TI TMS320DM270 based
709 bool "ROM maped on Sharp SL Series"
710 depends on MTD && ARCH_PXA
712 This enables access to the flash chip on the Sharp SL Series of PDAs.
715 tristate "Flash device mapped on COBRA5272"
716 depends on MTD && COBRA5272
718 This enables access to the flash chips (2MB) on the COBRA5272.
719 If you have such board, say 'Y'.
722 tristate "Flash device mapped on COBRA5282"
723 depends on MTD && COBRA5282
725 This enables access to the flash chips (4MB) on the COBRA5282.
726 If you have such board, say 'Y'.
730 tristate "Map driver for platform device RAM (mtd-ram)"
734 Map driver for RAM areas described via the platform device
737 This selection automatically selects the map_ram driver.
740 tristate "CFI Flash device mapped on AVNET5282"
741 depends on MTD_PARTITIONS && !MMU
743 Support for flash chip on Avnet5282 board
745 config MTD_MICROTRONIX
746 tristate "Maps for Microtronix boards, or Altera Cyclone 1C12 Eval board"
747 depends on MTD_PARTITIONS && !MMU && ( MICROTRONIX_UKIT || MICROTRONIX_STRATIX || MICROTRONIX_CYCLONE || ALTERA_CYCLONE_1C12_EVAL || MICROTRONIX_PSK)
750 Map driver for accessing flash memory on Microtronix Development
751 board (including Stratix, Cyclone and ukit), or Altera Cyclone 1C12
755 tristate "Maps for Altera EPCS Configuration Device"
756 depends on MTD_PARTITIONS && !MMU && MTD_EPCS
759 Map driver for accessing EPCS Flash by Altera. Please edit epcs_map.c
760 to setup the appropriate partitions. Since the driver will automatically
761 detect the EPCS chip present, it is your responsibility to setup
762 appropriate partition sizes/offsets such that you do not conflict with
763 the detected size. IE: Don't specify a partition size of 4 Megabytes when
764 you only have a 1 Megabit chip available!
767 tristate "Maps for Altera Nios Development Kit"
768 depends on MTD_PARTITIONS && !MMU && ( ALTERA_STRATIX || ALTERA_STRATIX_PRO || ALTERA_CYCLONE || ALTERA_STRATIX_II)
771 Map driver for accessing flash memory on Altera Nios Development kit,
772 Cyclone, Stratix or Stratix Pro edition.