This causes the chip drivers to allow for complicated
paged mappings of flash chips.

This provides a 'mapping' driver which allows the NOR Flash and
ROM driver code to communicate with 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.

To compile this driver as a module, choose M here: the
module will be called physmap.

Setup a simple mapping via the Kconfig options.  Normally the
physmap configuration options are done via your board's
resource file.

If unsure, say N here.

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()).

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()).

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 octet 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()).

This provides a 'mapping' driver which allows the NOR Flash and
ROM driver code to communicate with chips which are mapped
physically into the CPU's memory. The mapping description here is
taken from OF device tree.

This provides a 'mapping' driver which supports the way
in which user-programmable flash chips are connected on the
PMC-Sierra MSP eval/demo boards.

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.

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.

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'.

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 succeed.

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
<http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.

This provides a driver for the NOR flash attached to a PXA2xx chip.

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
<http://www.octagonsystems.com/products/5066.aspx>.

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
<http://www.tempustech.com/>.

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.

Support for treating the BIOS flash chip on AMD76x motherboards
as an MTD device - with this you can reprogram your BIOS.

BE VERY CAREFUL.

Support for treating the BIOS flash chip on ICHX motherboards
as an MTD device - with this you can reprogram your BIOS.

BE VERY CAREFUL.

Support for treating the BIOS flash chip on ESB2 motherboards
as an MTD device - with this you can reprogram your BIOS.

BE VERY CAREFUL.

Support for treating the BIOS flash chip on nvidia motherboards
as an MTD device - with this you can reprogram your BIOS.

BE VERY CAREFUL.

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.

Support for the flash chip on Tsunami TIG bus.

Support for flash chips on NETtel/SecureEdge/SnapGear boards.

Support for parsing CFE image tag and creating MTD partitions on
Broadcom BCM63xx boards.

Support for NOR flash attached to the Lantiq SoC's External Bus Unit.

MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>

The amount of space taken up by the kernel or Etherboot
on the DIL/Net PC flash chips.

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.

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
<http://www.denx.de/wiki/PPCEmbedded/>.

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
<http://www.embeddedplanet.com/>.

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'.

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'.

Mapping for the Flaga digital module. If you don't have one, ignore
this setting.

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.

This enables access to the flash or ROM chips on the CDB89712 board.
If you have such a board, say 'Y'.

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'.

This provides a driver for the flash accessed using Intel's
21285 bridge used with Intel's StrongARM processors. More info at
<http://www.intel.com/design/bridge/docs/21285_documentation.htm>.

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'.

This enables MTD access to flash devices on platforms based
on Intel's IXP2000 family of network processors. If you have an
IXP2000 based board and would like to use the flash chips on it,
say 'Y'.

This enables access to the Flash on the FortuNet board.  If you
have such a board, say 'Y'.

This enables access to the NV-RAM on autronix autcpu12 board.
If you have such a board, say 'Y'.

This enables access to the CFI Flash on the Cogent EDB7312 board.
If you have such a board, say 'Y' here.

This enables access to the NOR Flash on the impA7 board of
implementa GmbH. If you have such a board, say 'Y' here.

This enables access to the flash chips on the Ceiva/Polaroid
PhotoMax Digital Picture Frame.
If you have such a device, say 'Y'.

This enables access to the flash chips on the Hynix evaluation boards.
If you have such a board, say 'Y'.

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.

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.

If this option is enabled, PCMCIA cards which do not report
anything about themselves are assumed to be MTD cards.

If unsure, say N.

Map driver which allows for simultaneous utilization of
ethernet and CFI parallel flash.

If compiled as a module, it will be called bfin-async-flash.

Map driver which allows flashes to be partially physically addressed
and assisted by GPIOs.

If compiled as a module, it will be called gpio-addr-flash.

Map driver to support image based filesystems for uClinux.

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.

Map driver for Dy-4 SVME/DMV-182 board.

Map driver for a NOR flash bank located on the Expansion Bus of the
Intel Vermilion Range chipset.

Map driver for NOR flash chips on RBTX4939 board.

Map driver for RAM areas described via the platform device
system.

This selection automatically selects the map_ram driver.

This driver enables access to the Dreamcast Visual Memory Unit (VMU).

Most Dreamcast users will want to say Y here.

To build this as a module select M here, the module will be called
vmu-flash.

This driver allows for discovery of PISMO modules - see
<http://www.pismoworld.org/>.  These are small modules containing
up to five memory devices (eg, SRAM, flash, DOC) described by an
I2C EEPROM.

This driver does not create any MTD maps itself; instead it
creates MTD physmap and MTD SRAM platform devices.  If you
enable this option, you should consider enabling MTD_PHYSMAP
and/or MTD_PLATRAM according to the devices on your module.

When built as a module, it will be called pismo.ko

Map driver which allows flashes to be partially physically addressed
and have the upper address lines set by a board specific code.

If compiled as a module, it will be called latch-addr-flash.