How to configure the Linux kernel/Device drivers/Memory Technology Devices (MTD)/Mapping drivers for chip access

Howto configure the Linux kernel / drivers / mtd / maps


 * drivers/mtd/maps]]
 * $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner Exp $

Mapping drivers for chip access

 * depends on MTD!=n


 * Option: MTD_COMPLEX_MAPPINGS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Support non-linear mappings of flash chips
 * depends on MTD
 * This causes the chip drivers to allow for complicated paged mappings of flash chips.


 * Option: MTD_PHYSMAP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device in physical memory map
 * depends on MTD_CFI
 * This provides a 'mapping' driver which allows the CFI probe and command set driver code to communicate with flash chips which are mapped physically into the CPU's memory. You will need to configure the physical address and size of the flash chips on your particular board as well as the bus width, either statically with config options or at run-time.

"Physical start address of flash mapping"
 * Option: MTD_PHYSMAP_START
 * Kernel Versions: 2.6.15.6 ...
 * depends on MTD_PHYSMAP
 * default "0x8000000"
 * This is the physical memory location at which the flash chips are mapped on your particular target board. Refer to the memory map which should hopefully be in the documentation for your board. Ignore this option if you use run-time physmap configuration (i.e., run-time calling physmap_configure).

"Physical length of flash mapping"
 * Option: MTD_PHYSMAP_LEN
 * Kernel Versions: 2.6.15.6 ...
 * depends on MTD_PHYSMAP
 * default "0x4000000"
 * This is the total length of the mapping of the flash chips on your particular board. If there is space, or aliases, in the physical memory map between the chips, this could be larger than the total amount of flash present. Refer to the memory map which should hopefully be in the documentation for your board. Ignore this option if you use run-time physmap configuration (i.e., run-time calling physmap_configure).

"Bank width in octets"
 * Option: MTD_PHYSMAP_BANKWIDTH
 * Kernel Versions: 2.6.15.6 ...
 * depends on MTD_PHYSMAP
 * default "2"
 * This is the total width of the data bus of the flash devices in octets. For example, if you have a data bus width of 32 bits, you would set the bus width octect value to 4. This is used internally by the CFI drivers. Ignore this option if you use run-time physmap configuration (i.e., run-time calling physmap_configure).


 * Option: MTD_SUN_UFLASH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Sun Microsystems userflash support
 * depends on SPARC && MTD_CFI
 * This provides a 'mapping' driver which supports the way in which user-programmable flash chips are connected on various Sun Microsystems boardsets. This driver will require CFI support in the kernel, so if you did not enable CFI previously, do that now.


 * Option: MTD_PNC2000
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Photron PNC-2000
 * depends on X86 && MTD_CFI && MTD_PARTITIONS
 * PNC-2000 is the name of Network Camera product from PHOTRON Ltd. in Japan. It uses CFI-compliant flash.


 * Option: MTD_SC520CDP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on AMD SC520 CDP
 * depends on X86 && MTD_CFI
 * The SC520 CDP board has two banks of CFI-compliant chips and one Dual-in-line JEDEC chip. This 'mapping' driver supports that arrangement, implementing three MTD devices.


 * Option: MTD_NETSC520
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on AMD NetSc520
 * depends on X86 && MTD_CFI && MTD_PARTITIONS
 * This enables access routines for the flash chips on the AMD NetSc520 demonstration board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_TS5500
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) JEDEC Flash device mapped on Technologic Systems TS-5500
 * depends on X86
 * select MTD_PARTITIONS
 * select MTD_JEDECPROBE
 * select MTD_CFI_AMDSTD
 * This provides a driver for the on-board flash of the Technologic System's TS-5500 board. The 2MB flash is split into 3 partitions which are accessed as separate MTD devices.
 * mtd0 and mtd2 are the two BIOS drives, which use the resident flash disk (RFD) flash translation layer.
 * mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
 * Note that jumper 3 ("Write Enable Drive A") must be set otherwise detection won't succeeed.


 * Option: MTD_SBC_GXX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Arcom SBC-GXx boards
 * depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
 * This provides a driver for the on-board flash of Arcom Control Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. By default the flash is split into 3 partitions which are accessed as separate MTD devices. This board utilizes Intel StrataFlash. More info at .


 * Option: MTD_LUBBOCK
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Intel Lubbock XScale eval board
 * depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
 * This provides a driver for the on-board flash of the Intel 'Lubbock' XScale evaluation board.


 * Option: MTD_MAINSTONE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Intel Mainstone XScale eval board
 * depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
 * select MTD_PARTITIONS
 * This provides a driver for the on-board flash of the Intel 'Mainstone PXA27x evaluation board.


 * Option: MTD_OCTAGON
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) JEDEC Flash device mapped on Octagon 5066 SBC
 * depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
 * This provides a 'mapping' driver which supports the way in which the flash chips are connected in the Octagon-5066 Single Board Computer. More information on the board is available at .


 * Option: MTD_VMAX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) JEDEC Flash device mapped on Tempustech VMAX SBC301
 * depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
 * This provides a 'mapping' driver which supports the way in which the flash chips are connected in the Tempustech VMAX SBC301 Single Board Computer. More information on the board is available at .


 * Option: MTD_SCx200_DOCFLASH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash device mapped with DOCCS on NatSemi SCx200
 * depends on SCx200 && MTD_CFI && MTD_PARTITIONS
 * Enable support for a flash chip mapped using the DOCCS signal on a National Semiconductor SCx200 processor.
 * If you don't know what to do here, say N.
 * If compiled as a module, it will be called scx200_docflash.


 * Option: MTD_AMD76XROM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) BIOS flash chip on AMD76x southbridge
 * depends on X86 && MTD_JEDECPROBE
 * Support for treating the BIOS flash chip on AMD76x motherboards as an MTD device - with this you can reprogram your BIOS.
 * BE VERY CAREFUL.


 * Option: MTD_ICHXROM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) BIOS flash chip on Intel Controller Hub 2/3/4/5
 * depends on X86 && MTD_JEDECPROBE
 * Support for treating the BIOS flash chip on ICHX motherboards as an MTD device - with this you can reprogram your BIOS.
 * BE VERY CAREFUL.


 * Option: MTD_SCB2_FLASH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) BIOS flash chip on Intel SCB2 boards
 * depends on X86 && MTD_JEDECPROBE
 * Support for treating the BIOS flash chip on Intel SCB2 boards as an MTD device - with this you can reprogram your BIOS.
 * BE VERY CAREFUL.


 * Option: MTD_TSUNAMI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash chips on Tsunami TIG bus
 * depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
 * Support for the flash chip on Tsunami TIG bus.


 * Option: MTD_LASAT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash chips on LASAT board
 * depends on LASAT
 * Support for the flash chips on the Lasat 100 and 200 boards.


 * Option: MTD_NETtel
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI flash device on SnapGear/SecureEdge
 * depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
 * Support for flash chips on NETtel/SecureEdge/SnapGear boards.


 * Option: MTD_ALCHEMY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) '  AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support'
 * depends on SOC_AU1X00
 * Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards


 * Option: MTD_MTX1
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) 4G Systems MTX-1 Flash device
 * depends on MIPS && MIPS_MTX1
 * Flash memory access on 4G Systems MTX-1 Board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_DILNETPC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on DIL/Net PC
 * depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
 * MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP". For details, see  and 

"Size of DIL/Net PC flash boot partition"
 * Option: MTD_DILNETPC_BOOTSIZE
 * Kernel Versions: 2.6.15.6 ...
 * depends on MTD_DILNETPC
 * default "0x80000"
 * The amount of space taken up by the kernel or Etherboot on the DIL/Net PC flash chips.


 * Option: MTD_L440GX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) BIOS flash chip on Intel L440GX boards
 * depends on X86 && MTD_JEDECPROBE
 * Support for treating the BIOS flash chip on Intel L440GX motherboards as an MTD device - with this you can reprogram your BIOS.
 * BE VERY CAREFUL.


 * Option: MTD_SBC8240
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash device on SBC8240
 * depends on MTD_JEDECPROBE && 8260
 * Flash access on the SBC8240 board from Wind River. See         


 * Option: MTD_TQM8XXL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on TQM8XXL
 * depends on MTD_CFI && TQM8xxL
 * The TQM8xxL PowerPC board has up to two banks of CFI-compliant chips, currently uses AMD one. This 'mapping' driver supports that arrangement, allowing the CFI probe and command set driver code to communicate with the chips on the TQM8xxL board. More at .


 * Option: MTD_RPXLITE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on RPX Lite or CLLF
 * depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
 * The RPXLite PowerPC board has CFI-compliant chips mapped in a strange sparse mapping. This 'mapping' driver supports that arrangement, allowing the CFI probe and command set driver code to communicate with the chips on the RPXLite board. More at .


 * Option: MTD_MBX860
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) System flash on MBX860 board
 * depends on MTD_CFI && MBX
 * This enables access routines for the flash chips on the Motorola MBX860 board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_DBOX2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on D-Box2
 * depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
 * This enables access routines for the flash chips on the Nokia/Sagem D-Box 2 board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_CFI_FLAGADM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapping on FlagaDM
 * depends on 8xx && MTD_CFI
 * Mapping for the Flaga digital module. If you don't have one, ignore this setting.


 * Option: MTD_BEECH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on IBM 405LP Beech
 * depends on MTD_CFI && BEECH
 * This enables access routines for the flash chips on the IBM 405LP Beech board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_ARCTIC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on IBM 405LP Arctic
 * depends on MTD_CFI && ARCTIC2
 * This enables access routines for the flash chips on the IBM 405LP Arctic board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_WALNUT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash device mapped on IBM 405GP Walnut
 * depends on MTD_JEDECPROBE && WALNUT
 * This enables access routines for the flash chips on the IBM 405GP Walnut board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_EBONY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash devices mapped on IBM 440GP Ebony
 * depends on MTD_JEDECPROBE && EBONY
 * This enables access routines for the flash chips on the IBM 440GP Ebony board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_OCOTEA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash devices mapped on IBM 440GX Ocotea
 * depends on MTD_CFI && OCOTEA
 * This enables access routines for the flash chips on the IBM 440GX Ocotea board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_REDWOOD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash devices mapped on IBM Redwood
 * depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
 * This enables access routines for the flash chips on the IBM Redwood board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_TQM834x
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash device mapped on TQ Components TQM834x Boards
 * depends on MTD_CFI && TQM834x
 * This enables access routines for the flash chips on the TQ Components TQM834x boards. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_CSTM_MIPS_IXX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board
 * depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
 * This provides a mapping driver for the Integrated Technology Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR Reference Board. It provides the necessary addressing, length, buswidth, vpp code and addition setup of the flash device for these boards. In addition, this mapping driver can be used for other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/ LEN/BUSWIDTH parameters. This mapping will provide one mtd device using one partition. The start address can be offset from the beginning of flash and the len can be less than the total flash device size to allow a window into the flash. Both CFI and JEDEC probes are called.

"Physical start address of flash mapping"
 * Option: MTD_CSTM_MIPS_IXX_START
 * Kernel Versions: 2.6.15.6 ...
 * depends on MTD_CSTM_MIPS_IXX
 * default "0x8000000"
 * This is the physical memory location that the MTD driver will use for the flash chips on your particular target board. Refer to the memory map which should hopefully be in the documentation for your board.

"Physical length of flash mapping"
 * Option: MTD_CSTM_MIPS_IXX_LEN
 * Kernel Versions: 2.6.15.6 ...
 * depends on MTD_CSTM_MIPS_IXX
 * default "0x4000000"
 * This is the total length that the MTD driver will use for the flash chips on your particular board. Refer to the memory map which should hopefully be in the documentation for your board.

"Bus width in octets"
 * Option: MTD_CSTM_MIPS_IXX_BUSWIDTH
 * Kernel Versions: 2.6.15.6 ...
 * depends on MTD_CSTM_MIPS_IXX
 * default "2"
 * This is the total bus width of the mapping of the flash chips on your particular board.


 * Option: MTD_OCELOT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Momenco Ocelot boot flash device
 * depends on MIPS && MOMENCO_OCELOT
 * This enables access routines for the boot flash device and for the NVRAM on the Momenco Ocelot board. If you have one of these boards and would like access to either of these, say 'Y'.


 * Option: MTD_SOLUTIONENGINE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Hitachi SolutionEngine
 * depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
 * This enables access to the flash chips on the Hitachi SolutionEngine and similar boards. Say 'Y' if you are building a kernel for such a board.


 * Option: MTD_ARM_INTEGRATOR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on ARM Integrator/P720T
 * depends on ARM && MTD_CFI


 * Option: MTD_CDB89712
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Cirrus CDB89712 evaluation board mappings
 * depends on MTD_CFI && ARCH_CDB89712
 * This enables access to the flash or ROM chips on the CDB89712 board. If you have such a board, say 'Y'.


 * Option: MTD_SA1100
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on StrongARM SA11x0
 * depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
 * This enables access to the flash chips on most platforms based on the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. If you have such a board, say 'Y'.


 * Option: MTD_IPAQ
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Compaq/HP iPAQ
 * depends on IPAQ_HANDHELD && MTD_CFI
 * This provides a driver for the on-board flash of the iPAQ.


 * Option: MTD_DC21285
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on DC21285 Footbridge
 * depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
 * This provides a driver for the flash accessed using Intel's 21285 bridge used with Intel's StrongARM processors. More info at .


 * Option: MTD_IQ80310
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on the XScale IQ80310 board
 * depends on MTD_CFI && ARCH_IQ80310
 * This enables access routines for the flash chips on the Intel XScale IQ80310 evaluation board. If you have one of these boards and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_IXP4XX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Intel IXP4xx based systems
 * depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
 * This enables MTD access to flash devices on platforms based on Intel's IXP4xx family of network processors such as the IXDP425 and Coyote. If you have an IXP4xx based board and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_IXP2000
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Intel IXP2000 based systems
 * depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
 * This enables MTD access to flash devices on platforms based on Intel's IXP2000 family of network processors such as the IXDP425 and Coyote. If you have an IXP2000 based board and would like to use the flash chips on it, say 'Y'.


 * Option: MTD_EPXA10DB
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Epxa10db
 * depends on MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
 * This enables support for the flash devices on the Altera Excalibur XA10 Development Board. If you are building a kernel for on of these boards then you should say 'Y' otherwise say 'N'.


 * Option: MTD_FORTUNET
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on the FortuNet board
 * depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
 * This enables access to the Flash on the FortuNet board. If you have such a board, say 'Y'.


 * Option: MTD_AUTCPU12
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) NV-RAM mapping AUTCPU12 board
 * depends on ARCH_AUTCPU12
 * This enables access to the NV-RAM on autronix autcpu12 board. If you have such a board, say 'Y'.


 * Option: MTD_EDB7312
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on EDB7312
 * depends on ARCH_EDB7312 && MTD_CFI
 * This enables access to the CFI Flash on the Cogent EDB7312 board. If you have such a board, say 'Y' here.


 * Option: MTD_IMPA7
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) JEDEC Flash device mapped on impA7
 * depends on ARM && MTD_JEDECPROBE
 * This enables access to the NOR Flash on the impA7 board of implementa GmbH. If you have such a board, say 'Y' here.


 * Option: MTD_CEIVA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame
 * depends on MTD_JEDECPROBE && ARCH_CEIVA
 * This enables access to the flash chips on the Ceiva/Polaroid PhotoMax Digital Picture Frame. If you have such a device, say 'Y'.


 * Option: MTD_NOR_TOTO
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) NOR Flash device on TOTO board
 * depends on ARCH_OMAP && OMAP_TOTO
 * This enables access to the NOR flash on the Texas Instruments TOTO board.


 * Option: MTD_H720X
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Hynix evaluation board mappings
 * depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
 * This enables access to the flash chips on the Hynix evaluation boards. If you have such a board, say 'Y'.


 * Option: MTD_MPC1211
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) CFI Flash device mapped on Interface MPC-1211
 * depends on SH_MPC1211 && MTD_CFI
 * This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02). If you have such a board, say 'Y'.


 * Option: MTD_OMAP_NOR
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) TI OMAP board mappings
 * depends on MTD_CFI && ARCH_OMAP
 * This enables access to the NOR flash chips on TI OMAP-based boards defining flash platform devices and flash platform data. These boards include the Innovator, H2, H3, OSK, Perseus2, and more. If you have such a board, say 'Y'.


 * This needs CFI or JEDEC, depending on the cards found.


 * Option: MTD_PCI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) PCI MTD driver
 * depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
 * Mapping for accessing flash devices on add-in cards like the Intel XScale IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode (please see the manual for the link settings).
 * If you are not sure, say N.


 * Option: MTD_PCMCIA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) PCMCIA MTD driver
 * depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
 * Map driver for accessing PCMCIA linear flash memory cards. These cards are usually around 4-16MiB in size. This does not include Compact Flash cards which are treated as IDE devices.


 * Option: MTD_PCMCIA_ANONYMOUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) Use PCMCIA MTD drivers for anonymous PCMCIA cards
 * depends on MTD_PCMCIA
 * default N
 * If this option is enabled, PCMCIA cards which do not report anything about themselves are assumed to be MTD cards.
 * If unsure, say N.


 * Option: MTD_UCLINUX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Generic uClinux RAM/ROM filesystem support
 * depends on MTD_PARTITIONS && !MMU
 * Map driver to support image based filesystems for uClinux.


 * Option: MTD_WRSBC8260
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Map driver for WindRiver PowerQUICC II MPC82xx board
 * depends on (SBC82xx || SBC8560)
 * select MTD_PARTITIONS
 * select MTD_MAP_BANK_WIDTH_4
 * select MTD_MAP_BANK_WIDTH_1
 * select MTD_CFI_I1
 * select MTD_CFI_I4
 * Map driver for WindRiver PowerQUICC II MPC82xx board. Drives all three flash regions on CS0, CS1 and CS6 if they are configured correctly by the boot loader.


 * Option: MTD_DMV182
 * Kernel Versions: 2.6.15.6 ...      tristate Map driver for Dy-4 SVME/DMV-182 board.       depends on DMV182       select MTD_PARTITIONS
 * select MTD_MAP_BANK_WIDTH_32
 * select MTD_CFI_I8
 * select MTD_CFI_AMDSTD      help         Map driver for Dy-4 SVME/DMV-182 board.


 * Option: MTD_BAST
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000
 * depends on ARCH_BAST || MACH_VR1000
 * select MTD_PARTITIONS
 * select MTD_MAP_BANK_WIDTH_16
 * select MTD_JEDECPROBE
 * Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the Thorcom VR1000
 * Note, this driver *cannot* over-ride the WP link on the board, or currently detect the state of the link.

"Maximum size for BAST flash area (MiB)"
 * Option: MTD_BAST_MAXSIZE
 * Kernel Versions: 2.6.15.6 ...
 * depends on MTD_BAST
 * default "4"


 * Option: MTD_SHARP_SL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) ROM maped on Sharp SL Series
 * depends on MTD && ARCH_PXA
 * This enables access to the flash chip on the Sharp SL Series of PDAs.


 * Option: MTD_PLATRAM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) Map driver for platform device RAM (mtd-ram)
 * depends on MTD
 * select MTD_RAM
 * Map driver for RAM areas described via the platform device system.
 * This selection automatically selects the map_ram driver.

Linux Kernel Configuration