menu "Mapping drivers for chip access"
depends on [31mCONFIG_MTD[0m!=n
depends on [31mCONFIG_HAS_IOMEM[0m
config [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
bool "Support non-linear mappings of flash chips"
help
This causes the chip drivers to allow for complicated
paged mappings of flash chips.
config [31mCONFIG_MTD_PHYSMAP[0m
tristate "Flash device in physical memory map"
depends on [31mCONFIG_MTD_CFI[0m || [31mCONFIG_MTD_JEDECPROBE[0m || [31mCONFIG_MTD_ROM[0m || [31mCONFIG_MTD_LPDDR[0m
help
This provides a 'mapping' driver which allows the NOR Flash and
[31mCONFIG_ROM[0m 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 [31mCONFIG_M[0m here: the
module will be called physmap.
config [31mCONFIG_MTD_PHYSMAP_COMPAT[0m
bool "Physmap compat support"
depends on [31mCONFIG_MTD_PHYSMAP[0m
default n
help
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.
config [31mCONFIG_MTD_PHYSMAP_START[0m
hex "Physical start address of flash mapping"
depends on [31mCONFIG_MTD_PHYSMAP_COMPAT[0m
default "0x8000000"
help
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.
config [31mCONFIG_MTD_PHYSMAP_LEN[0m
hex "Physical length of flash mapping"
depends on [31mCONFIG_MTD_PHYSMAP_COMPAT[0m
default "0"
help
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.
config [31mCONFIG_MTD_PHYSMAP_BANKWIDTH[0m
int "Bank width in octets"
depends on [31mCONFIG_MTD_PHYSMAP_COMPAT[0m
default "2"
help
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.
config [31mCONFIG_MTD_PHYSMAP_OF[0m
tristate "Memory device in physical memory map based on OF description"
depends on [31mCONFIG_OF[0m && ([31mCONFIG_MTD_CFI[0m || [31mCONFIG_MTD_JEDECPROBE[0m || [31mCONFIG_MTD_ROM[0m || [31mCONFIG_MTD_RAM[0m)
help
This provides a 'mapping' driver which allows the NOR Flash, [31mCONFIG_ROM[0m
and RAM driver code to communicate with chips which are mapped
physically into the CPU's memory. The mapping description here is
taken from [31mCONFIG_OF[0m device tree.
config [31mCONFIG_MTD_PHYSMAP_OF_VERSATILE[0m
bool "Support ARM Versatile physmap OF"
depends on [31mCONFIG_MTD_PHYSMAP_OF[0m
depends on [31mCONFIG_MFD_SYSCON[0m
default y if ([31mCONFIG_ARCH_INTEGRATOR[0m || [31mCONFIG_ARCH_VERSATILE[0m || [31mCONFIG_ARCH_REALVIEW[0m)
help
This provides some extra DT physmap parsing for the [31mCONFIG_ARM[0m Versatile
platforms, basically to add a VPP (write protection) callback so
the flash can be taken out of write protection.
config [31mCONFIG_MTD_PMC_MSP_EVM[0m
tristate "CFI Flash device mapped on PMC-Sierra MSP"
depends on [31mCONFIG_PMC_MSP[0m && [31mCONFIG_MTD_CFI[0m
help
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.
choice
prompt "Maximum mappable memory available for flash IO"
depends on [31mCONFIG_MTD_PMC_MSP_EVM[0m
default [31mCONFIG_MSP_FLASH_MAP_LIMIT_32M[0m
config [31mCONFIG_MSP_FLASH_MAP_LIMIT_32M[0m
bool "32M"
endchoice
config [31mCONFIG_MSP_FLASH_MAP_LIMIT[0m
hex
default "0x02000000"
depends on [31mCONFIG_MSP_FLASH_MAP_LIMIT_32M[0m
config [31mCONFIG_MTD_SUN_UFLASH[0m
tristate "Sun Microsystems userflash support"
depends on [31mCONFIG_SPARC[0m && [31mCONFIG_MTD_CFI[0m && [31mCONFIG_PCI[0m
help
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.
config [31mCONFIG_MTD_SC520CDP[0m
tristate "CFI Flash device mapped on AMD SC520 CDP"
depends on ([31mCONFIG_MELAN[0m || [31mCONFIG_COMPILE_TEST[0m) && [31mCONFIG_MTD_CFI[0m
help
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 [31mCONFIG_MTD[0m devices.
config [31mCONFIG_MTD_NETSC520[0m
tristate "CFI Flash device mapped on AMD NetSc520"
depends on ([31mCONFIG_MELAN[0m || [31mCONFIG_COMPILE_TEST[0m) && [31mCONFIG_MTD_CFI[0m
help
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'.
config [31mCONFIG_MTD_TS5500[0m
tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
depends on [31mCONFIG_TS5500[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_MTD_JEDECPROBE[0m
select [31mCONFIG_MTD_CFI_AMDSTD[0m
help
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 [31mCONFIG_MTD[0m 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.
config [31mCONFIG_MTD_SBC_GXX[0m
tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
depends on [31mCONFIG_X86[0m && [31mCONFIG_MTD_CFI_INTELEXT[0m && [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
help
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 [31mCONFIG_MTD[0m devices. This board utilizes Intel StrataFlash.
More info at
<http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
config [31mCONFIG_MTD_PXA2XX[0m
tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
depends on ([31mCONFIG_PXA25x[0m || [31mCONFIG_PXA27x[0m) && [31mCONFIG_MTD_CFI_INTELEXT[0m
help
This provides a driver for the NOR flash attached to a PXA2xx chip.
config [31mCONFIG_MTD_SCx200_DOCFLASH[0m
tristate "Flash device mapped with DOCCS on NatSemi SCx200"
depends on [31mCONFIG_SCx200[0m && [31mCONFIG_MTD_CFI[0m
help
Enable support for a flash chip mapped using the DOCCS signal on a
National Semiconductor [31mCONFIG_SCx200[0m processor.
If you don't know what to do here, say N.
If compiled as a module, it will be called scx200_docflash.
config [31mCONFIG_MTD_AMD76XROM[0m
tristate "BIOS flash chip on AMD76x southbridge"
depends on [31mCONFIG_X86[0m && [31mCONFIG_MTD_JEDECPROBE[0m
help
Support for treating the BIOS flash chip on AMD76x motherboards
as an [31mCONFIG_MTD[0m device - with this you can reprogram your BIOS.
BE VERY CAREFUL.
config [31mCONFIG_MTD_ICHXROM[0m
tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
depends on [31mCONFIG_X86[0m && [31mCONFIG_MTD_JEDECPROBE[0m
help
Support for treating the BIOS flash chip on ICHX motherboards
as an [31mCONFIG_MTD[0m device - with this you can reprogram your BIOS.
BE VERY CAREFUL.
config [31mCONFIG_MTD_ESB2ROM[0m
tristate "BIOS flash chip on Intel ESB Controller Hub 2"
depends on [31mCONFIG_X86[0m && [31mCONFIG_MTD_JEDECPROBE[0m && [31mCONFIG_PCI[0m
help
Support for treating the BIOS flash chip on ESB2 motherboards
as an [31mCONFIG_MTD[0m device - with this you can reprogram your BIOS.
BE VERY CAREFUL.
config [31mCONFIG_MTD_CK804XROM[0m
tristate "BIOS flash chip on Nvidia CK804"
depends on [31mCONFIG_X86[0m && [31mCONFIG_MTD_JEDECPROBE[0m && [31mCONFIG_PCI[0m
help
Support for treating the BIOS flash chip on nvidia motherboards
as an [31mCONFIG_MTD[0m device - with this you can reprogram your BIOS.
BE VERY CAREFUL.
config [31mCONFIG_MTD_SCB2_FLASH[0m
tristate "BIOS flash chip on Intel SCB2 boards"
depends on [31mCONFIG_X86[0m && [31mCONFIG_MTD_JEDECPROBE[0m && [31mCONFIG_PCI[0m
help
Support for treating the BIOS flash chip on Intel SCB2 boards
as an [31mCONFIG_MTD[0m device - with this you can reprogram your BIOS.
BE VERY CAREFUL.
config [31mCONFIG_MTD_TSUNAMI[0m
tristate "Flash chips on Tsunami TIG bus"
depends on [31mCONFIG_ALPHA_TSUNAMI[0m && [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
help
Support for the flash chip on Tsunami TIG bus.
config [31mCONFIG_MTD_NETtel[0m
tristate "CFI flash device on SnapGear/SecureEdge"
depends on [31mCONFIG_X86[0m && [31mCONFIG_MTD_JEDECPROBE[0m
help
Support for flash chips on [31mCONFIG_NETtel[0m/SecureEdge/SnapGear boards.
config [31mCONFIG_MTD_LANTIQ[0m
tristate "Lantiq SoC NOR support"
depends on [31mCONFIG_LANTIQ[0m
help
Support for NOR flash attached to the Lantiq SoC's External Bus Unit.
config [31mCONFIG_MTD_L440GX[0m
tristate "BIOS flash chip on Intel L440GX boards"
depends on [31mCONFIG_X86[0m && [31mCONFIG_MTD_JEDECPROBE[0m
help
Support for treating the BIOS flash chip on Intel L440GX motherboards
as an [31mCONFIG_MTD[0m device - with this you can reprogram your BIOS.
BE VERY CAREFUL.
config [31mCONFIG_MTD_CFI_FLAGADM[0m
tristate "CFI Flash device mapping on FlagaDM"
depends on [31mCONFIG_PPC_8xx[0m && [31mCONFIG_MTD_CFI[0m
help
Mapping for the Flaga digital module. If you don't have one, ignore
this setting.
config [31mCONFIG_MTD_SOLUTIONENGINE[0m
tristate "CFI Flash device mapped on Hitachi SolutionEngine"
depends on [31mCONFIG_SOLUTION_ENGINE[0m && [31mCONFIG_MTD_CFI[0m && [31mCONFIG_MTD_REDBOOT_PARTS[0m
help
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.
config [31mCONFIG_MTD_SA1100[0m
tristate "CFI Flash device mapped on StrongARM SA11x0"
depends on [31mCONFIG_MTD_CFI[0m && [31mCONFIG_ARCH_SA1100[0m
help
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'.
config [31mCONFIG_MTD_DC21285[0m
tristate "CFI Flash device mapped on DC21285 Footbridge"
depends on [31mCONFIG_MTD_CFI[0m && [31mCONFIG_ARCH_FOOTBRIDGE[0m && [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
help
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>.
config [31mCONFIG_MTD_IXP4XX[0m
tristate "CFI Flash device mapped on Intel IXP4xx based systems"
depends on [31mCONFIG_MTD_CFI[0m && [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m && [31mCONFIG_ARCH_IXP4XX[0m
help
This enables [31mCONFIG_MTD[0m 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'.
config [31mCONFIG_MTD_IMPA7[0m
tristate "JEDEC Flash device mapped on impA7"
depends on [31mCONFIG_ARM[0m && [31mCONFIG_MTD_JEDECPROBE[0m
help
This enables access to the NOR Flash on the impA7 board of
implementa GmbH. If you have such a board, say 'Y' here.
# This needs CFI or JEDEC, depending on the cards found.
config [31mCONFIG_MTD_PCI[0m
tristate "PCI MTD driver"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
help
Mapping for accessing flash devices on add-in cards like the Intel XScale
IQ80310 card, and the Intel EBSA285 card in blank [31mCONFIG_ROM[0m programming mode
(please see the manual for the link settings).
If you are not sure, say N.
config [31mCONFIG_MTD_PCMCIA[0m
tristate "PCMCIA MTD driver"
depends on [31mCONFIG_PCMCIA[0m && [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
help
Map driver for accessing [31mCONFIG_PCMCIA[0m linear flash memory cards. These
cards are usually around 4-16MiB in size. This does not include
Compact Flash cards which are treated as [31mCONFIG_IDE[0m devices.
config [31mCONFIG_MTD_PCMCIA_ANONYMOUS[0m
bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
depends on [31mCONFIG_MTD_PCMCIA[0m
help
If this option is enabled, [31mCONFIG_PCMCIA[0m cards which do not report
anything about themselves are assumed to be [31mCONFIG_MTD[0m cards.
If unsure, say N.
config [31mCONFIG_MTD_BFIN_ASYNC[0m
tristate "Blackfin BF533-STAMP Flash Chip Support"
depends on [31mCONFIG_BFIN533_STAMP[0m && [31mCONFIG_MTD_CFI[0m && [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
default y
help
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.
config [31mCONFIG_MTD_GPIO_ADDR[0m
tristate "GPIO-assisted Flash Chip Support"
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
help
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.
config [31mCONFIG_MTD_UCLINUX[0m
bool "Generic uClinux RAM/ROM filesystem support"
depends on ([31mCONFIG_MTD_RAM[0m=y || [31mCONFIG_MTD_ROM[0m=y) && (![31mCONFIG_MMU[0m || [31mCONFIG_COLDFIRE[0m)
help
Map driver to support image based filesystems for uClinux.
config [31mCONFIG_MTD_INTEL_VR_NOR[0m
tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
depends on [31mCONFIG_PCI[0m
help
Map driver for a NOR flash bank located on the Expansion Bus of the
Intel Vermilion Range chipset.
config [31mCONFIG_MTD_RBTX4939[0m
tristate "Map driver for RBTX4939 board"
depends on [31mCONFIG_TOSHIBA_RBTX4939[0m && [31mCONFIG_MTD_CFI[0m && [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
help
Map driver for NOR flash chips on RBTX4939 board.
config [31mCONFIG_MTD_PLATRAM[0m
tristate "Map driver for platform device RAM (mtd-ram)"
select [31mCONFIG_MTD_RAM[0m
help
Map driver for RAM areas described via the platform device
system.
This selection automatically selects the map_ram driver.
config [31mCONFIG_MTD_VMU[0m
tristate "Map driver for Dreamcast VMU"
depends on [31mCONFIG_MAPLE[0m
help
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 [31mCONFIG_M[0m here, the module will be called
vmu-flash.
config [31mCONFIG_MTD_PISMO[0m
tristate "MTD discovery driver for PISMO modules"
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_ARCH_VERSATILE[0m
help
This driver allows for discovery of PISMO modules - see
<http://www.pismoworld.org/>. These are small modules containing
up to five memory devices (eg, [31mCONFIG_SRAM[0m, flash, DOC) described by an
[31mCONFIG_I2C[0m EEPROM.
This driver does not create any [31mCONFIG_MTD[0m maps itself; instead it
creates [31mCONFIG_MTD[0m physmap and [31mCONFIG_MTD[0m [31mCONFIG_SRAM[0m platform devices. If you
enable this option, you should consider enabling [31mCONFIG_MTD_PHYSMAP[0m
and/or [31mCONFIG_MTD_PLATRAM[0m according to the devices on your module.
When built as a module, it will be called pismo.ko
config [31mCONFIG_MTD_LATCH_ADDR[0m
tristate "Latch-assisted Flash Chip Support"
depends on [31mCONFIG_MTD_COMPLEX_MAPPINGS[0m
help
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.
endmenu