2005-04-16 22:20:36 +00:00
|
|
|
menu "Mapping drivers for chip access"
|
|
|
|
|
depends on MTD!=n
|
2012-02-07 00:22:50 +00:00
|
|
|
depends on HAS_IOMEM
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
config MTD_COMPLEX_MAPPINGS
|
|
|
|
|
bool "Support non-linear mappings of flash chips"
|
|
|
|
|
help
|
|
|
|
|
This causes the chip drivers to allow for complicated
|
|
|
|
|
paged mappings of flash chips.
|
|
|
|
|
|
|
|
|
|
config MTD_PHYSMAP
|
2008-12-16 18:22:39 +00:00
|
|
|
tristate "Flash device in physical memory map"
|
|
|
|
|
depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
2006-08-15 12:26:32 +00:00
|
|
|
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
|
2005-04-16 22:20:36 +00:00
|
|
|
with config options or at run-time.
|
|
|
|
|
|
2008-04-18 20:44:10 +00:00
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called physmap.
|
|
|
|
|
|
2008-12-01 22:23:40 +00:00
|
|
|
config MTD_PHYSMAP_COMPAT
|
|
|
|
|
bool "Physmap compat support"
|
|
|
|
|
depends on MTD_PHYSMAP
|
|
|
|
|
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.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config MTD_PHYSMAP_START
|
|
|
|
|
hex "Physical start address of flash mapping"
|
2008-12-01 22:23:40 +00:00
|
|
|
depends on MTD_PHYSMAP_COMPAT
|
2005-04-16 22:20:36 +00:00
|
|
|
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 MTD_PHYSMAP_LEN
|
|
|
|
|
hex "Physical length of flash mapping"
|
2008-12-01 22:23:40 +00:00
|
|
|
depends on MTD_PHYSMAP_COMPAT
|
[MTD] Convert physmap to platform driver
After dwmw2 let me know it ought to be done, I rewrote the physmap map
driver to be a platform driver. I know zilch about the driver model,
so I probably botched it in some way, but I've done some tests on an
ixp23xx board which uses physmap, and it all seems to work.
In order to not break existing physmap users, I've added some compat
code that will instantiate a platform device iff CONFIG_MTD_PHYSMAP_LEN
is defined and != 0. Also, I've changed the default value for
CONFIG_MTD_PHYSMAP_LEN to zero, so that people who inadvertently
compile in physmap (or new, platform-style, users of physmap) don't get
burned.
This works pretty well -- the new physmap driver is a drop-in replacement
for the old one, and works on said ixp23xx board without any code changes
needed. (This should hold as long as users don't touch 'physmap_map'
directly.)
Once all physmap users have been converted to instantiate their own
platform devices, the compat code can go. (Or we decide that we can
change all the in-tree users at the same time, and never merge the
compat code.)
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
2006-05-07 16:16:36 +00:00
|
|
|
default "0"
|
2005-04-16 22:20:36 +00:00
|
|
|
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 MTD_PHYSMAP_BANKWIDTH
|
|
|
|
|
int "Bank width in octets"
|
2008-12-01 22:23:40 +00:00
|
|
|
depends on MTD_PHYSMAP_COMPAT
|
2005-04-16 22:20:36 +00:00
|
|
|
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
|
2007-10-19 23:34:40 +00:00
|
|
|
bits, you would set the bus width octet value to 4. This is
|
2005-04-16 22:20:36 +00:00
|
|
|
used internally by the CFI drivers.
|
|
|
|
|
|
2006-12-06 10:17:49 +00:00
|
|
|
config MTD_PHYSMAP_OF
|
2014-03-05 23:00:00 +00:00
|
|
|
tristate "Memory device in physical memory map based on OF description"
|
|
|
|
|
depends on OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM)
|
2006-12-06 10:17:49 +00:00
|
|
|
help
|
2014-03-05 23:00:00 +00:00
|
|
|
This provides a 'mapping' driver which allows the NOR Flash, ROM
|
|
|
|
|
and RAM driver code to communicate with chips which are mapped
|
2006-12-06 10:17:49 +00:00
|
|
|
physically into the CPU's memory. The mapping description here is
|
|
|
|
|
taken from OF device tree.
|
|
|
|
|
|
2007-03-27 05:45:41 +00:00
|
|
|
config MTD_PMC_MSP_EVM
|
|
|
|
|
tristate "CFI Flash device mapped on PMC-Sierra MSP"
|
|
|
|
|
depends on PMC_MSP && MTD_CFI
|
|
|
|
|
help
|
2007-10-19 23:34:40 +00:00
|
|
|
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.
|
2007-03-27 05:45:41 +00:00
|
|
|
|
|
|
|
|
choice
|
2007-10-19 23:34:40 +00:00
|
|
|
prompt "Maximum mappable memory available for flash IO"
|
2007-03-27 05:45:41 +00:00
|
|
|
depends on MTD_PMC_MSP_EVM
|
|
|
|
|
default MSP_FLASH_MAP_LIMIT_32M
|
|
|
|
|
|
|
|
|
|
config MSP_FLASH_MAP_LIMIT_32M
|
|
|
|
|
bool "32M"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config MSP_FLASH_MAP_LIMIT
|
|
|
|
|
hex
|
|
|
|
|
default "0x02000000"
|
|
|
|
|
depends on MSP_FLASH_MAP_LIMIT_32M
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config MTD_SUN_UFLASH
|
|
|
|
|
tristate "Sun Microsystems userflash support"
|
2007-07-26 16:33:09 +00:00
|
|
|
depends on SPARC && MTD_CFI && PCI
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
2005-11-07 11:15:40 +00:00
|
|
|
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
|
2005-04-16 22:20:36 +00:00
|
|
|
in the kernel, so if you did not enable CFI previously, do that now.
|
|
|
|
|
|
|
|
|
|
config MTD_SC520CDP
|
|
|
|
|
tristate "CFI Flash device mapped on AMD SC520 CDP"
|
2014-03-14 17:14:20 +00:00
|
|
|
depends on (MELAN || COMPILE_TEST) && MTD_CFI
|
2005-04-16 22:20:36 +00:00
|
|
|
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 MTD devices.
|
|
|
|
|
|
|
|
|
|
config MTD_NETSC520
|
|
|
|
|
tristate "CFI Flash device mapped on AMD NetSc520"
|
2014-03-14 17:14:20 +00:00
|
|
|
depends on (MELAN || COMPILE_TEST) && MTD_CFI
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
This enables access routines for the flash chips on the AMD NetSc520
|
2005-11-07 11:15:40 +00:00
|
|
|
demonstration board. If you have one of these boards and would like
|
2005-04-16 22:20:36 +00:00
|
|
|
to use the flash chips on it, say 'Y'.
|
|
|
|
|
|
|
|
|
|
config MTD_TS5500
|
|
|
|
|
tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
|
2014-02-23 09:32:01 +00:00
|
|
|
depends on TS5500 || COMPILE_TEST
|
2005-06-29 09:46:19 +00:00
|
|
|
select MTD_JEDECPROBE
|
|
|
|
|
select MTD_CFI_AMDSTD
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
This provides a driver for the on-board flash of the Technologic
|
2005-06-16 08:49:33 +00:00
|
|
|
System's TS-5500 board. The 2MB flash is split into 3 partitions
|
2005-04-16 22:20:36 +00:00
|
|
|
which are accessed as separate MTD devices.
|
|
|
|
|
|
2005-06-16 08:49:33 +00:00
|
|
|
mtd0 and mtd2 are the two BIOS drives, which use the resident
|
|
|
|
|
flash disk (RFD) flash translation layer.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
|
|
|
|
|
|
|
|
|
|
Note that jumper 3 ("Write Enable Drive A") must be set
|
2006-05-12 16:35:02 +00:00
|
|
|
otherwise detection won't succeed.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
config MTD_SBC_GXX
|
|
|
|
|
tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
|
2011-05-23 09:23:43 +00:00
|
|
|
depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS
|
2005-04-16 22:20:36 +00:00
|
|
|
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 MTD devices. This board utilizes Intel StrataFlash.
|
|
|
|
|
More info at
|
|
|
|
|
<http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
|
|
|
|
|
|
2005-11-07 21:47:48 +00:00
|
|
|
config MTD_PXA2XX
|
|
|
|
|
tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
|
|
|
|
|
depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
|
2005-07-01 22:55:24 +00:00
|
|
|
help
|
2005-11-07 21:47:48 +00:00
|
|
|
This provides a driver for the NOR flash attached to a PXA2xx chip.
|
2005-07-01 22:55:24 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config MTD_SCx200_DOCFLASH
|
|
|
|
|
tristate "Flash device mapped with DOCCS on NatSemi SCx200"
|
2011-05-23 09:23:10 +00:00
|
|
|
depends on SCx200 && MTD_CFI
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config MTD_AMD76XROM
|
|
|
|
|
tristate "BIOS flash chip on AMD76x southbridge"
|
|
|
|
|
depends on X86 && MTD_JEDECPROBE
|
|
|
|
|
help
|
|
|
|
|
Support for treating the BIOS flash chip on AMD76x motherboards
|
|
|
|
|
as an MTD device - with this you can reprogram your BIOS.
|
|
|
|
|
|
|
|
|
|
BE VERY CAREFUL.
|
|
|
|
|
|
|
|
|
|
config MTD_ICHXROM
|
|
|
|
|
tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
|
|
|
|
|
depends on X86 && MTD_JEDECPROBE
|
|
|
|
|
help
|
|
|
|
|
Support for treating the BIOS flash chip on ICHX motherboards
|
|
|
|
|
as an MTD device - with this you can reprogram your BIOS.
|
|
|
|
|
|
|
|
|
|
BE VERY CAREFUL.
|
|
|
|
|
|
2006-10-20 21:41:04 +00:00
|
|
|
config MTD_ESB2ROM
|
|
|
|
|
tristate "BIOS flash chip on Intel ESB Controller Hub 2"
|
2006-12-04 23:03:00 +00:00
|
|
|
depends on X86 && MTD_JEDECPROBE && PCI
|
2006-10-20 21:41:04 +00:00
|
|
|
help
|
|
|
|
|
Support for treating the BIOS flash chip on ESB2 motherboards
|
|
|
|
|
as an MTD device - with this you can reprogram your BIOS.
|
|
|
|
|
|
|
|
|
|
BE VERY CAREFUL.
|
|
|
|
|
|
2006-11-06 23:33:57 +00:00
|
|
|
config MTD_CK804XROM
|
|
|
|
|
tristate "BIOS flash chip on Nvidia CK804"
|
2007-01-25 23:15:17 +00:00
|
|
|
depends on X86 && MTD_JEDECPROBE && PCI
|
2006-11-06 23:33:57 +00:00
|
|
|
help
|
|
|
|
|
Support for treating the BIOS flash chip on nvidia motherboards
|
|
|
|
|
as an MTD device - with this you can reprogram your BIOS.
|
|
|
|
|
|
|
|
|
|
BE VERY CAREFUL.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config MTD_SCB2_FLASH
|
|
|
|
|
tristate "BIOS flash chip on Intel SCB2 boards"
|
2012-04-16 19:50:37 +00:00
|
|
|
depends on X86 && MTD_JEDECPROBE && PCI
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config MTD_TSUNAMI
|
|
|
|
|
tristate "Flash chips on Tsunami TIG bus"
|
|
|
|
|
depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
|
|
|
|
|
help
|
|
|
|
|
Support for the flash chip on Tsunami TIG bus.
|
|
|
|
|
|
|
|
|
|
config MTD_NETtel
|
|
|
|
|
tristate "CFI flash device on SnapGear/SecureEdge"
|
2011-05-23 09:23:43 +00:00
|
|
|
depends on X86 && MTD_JEDECPROBE
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Support for flash chips on NETtel/SecureEdge/SnapGear boards.
|
|
|
|
|
|
2011-04-12 16:10:01 +00:00
|
|
|
config MTD_LANTIQ
|
|
|
|
|
tristate "Lantiq SoC NOR support"
|
|
|
|
|
depends on LANTIQ
|
|
|
|
|
help
|
|
|
|
|
Support for NOR flash attached to the Lantiq SoC's External Bus Unit.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config MTD_L440GX
|
|
|
|
|
tristate "BIOS flash chip on Intel L440GX boards"
|
|
|
|
|
depends on X86 && MTD_JEDECPROBE
|
|
|
|
|
help
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config MTD_CFI_FLAGADM
|
|
|
|
|
tristate "CFI Flash device mapping on FlagaDM"
|
2015-03-12 15:24:04 +00:00
|
|
|
depends on PPC_8xx && MTD_CFI
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Mapping for the Flaga digital module. If you don't have one, ignore
|
|
|
|
|
this setting.
|
|
|
|
|
|
|
|
|
|
config MTD_SOLUTIONENGINE
|
|
|
|
|
tristate "CFI Flash device mapped on Hitachi SolutionEngine"
|
2014-07-22 02:07:56 +00:00
|
|
|
depends on SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
|
2005-04-16 22:20:36 +00:00
|
|
|
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 MTD_SA1100
|
|
|
|
|
tristate "CFI Flash device mapped on StrongARM SA11x0"
|
2011-05-23 09:23:09 +00:00
|
|
|
depends on MTD_CFI && ARCH_SA1100
|
2005-04-16 22:20:36 +00:00
|
|
|
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 MTD_DC21285
|
|
|
|
|
tristate "CFI Flash device mapped on DC21285 Footbridge"
|
2005-06-29 09:46:19 +00:00
|
|
|
depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
|
2005-04-16 22:20:36 +00:00
|
|
|
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 MTD_IXP4XX
|
|
|
|
|
tristate "CFI Flash device mapped on Intel IXP4xx based systems"
|
2005-06-29 09:46:19 +00:00
|
|
|
depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
2005-11-07 11:15:40 +00:00
|
|
|
This enables MTD access to flash devices on platforms based
|
2005-04-16 22:20:36 +00:00
|
|
|
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 MTD_IMPA7
|
|
|
|
|
tristate "JEDEC Flash device mapped on impA7"
|
|
|
|
|
depends on ARM && MTD_JEDECPROBE
|
|
|
|
|
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 MTD_PCI
|
|
|
|
|
tristate "PCI MTD driver"
|
2007-04-19 21:21:41 +00:00
|
|
|
depends on PCI && MTD_COMPLEX_MAPPINGS
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config MTD_PCMCIA
|
|
|
|
|
tristate "PCMCIA MTD driver"
|
2010-05-13 09:59:59 +00:00
|
|
|
depends on PCMCIA && MTD_COMPLEX_MAPPINGS
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
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.
|
|
|
|
|
|
2005-06-27 23:28:32 +00:00
|
|
|
config MTD_PCMCIA_ANONYMOUS
|
|
|
|
|
bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
|
|
|
|
|
depends on MTD_PCMCIA
|
|
|
|
|
help
|
|
|
|
|
If this option is enabled, PCMCIA cards which do not report
|
|
|
|
|
anything about themselves are assumed to be MTD cards.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2008-05-19 10:32:24 +00:00
|
|
|
config MTD_BFIN_ASYNC
|
|
|
|
|
tristate "Blackfin BF533-STAMP Flash Chip Support"
|
2009-02-11 21:12:19 +00:00
|
|
|
depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS
|
2008-05-19 10:32:24 +00:00
|
|
|
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.
|
|
|
|
|
|
2009-05-20 16:04:09 +00:00
|
|
|
config MTD_GPIO_ADDR
|
|
|
|
|
tristate "GPIO-assisted Flash Chip Support"
|
2013-03-28 11:34:56 +00:00
|
|
|
depends on GPIOLIB
|
2009-05-20 16:04:09 +00:00
|
|
|
depends on MTD_COMPLEX_MAPPINGS
|
|
|
|
|
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.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config MTD_UCLINUX
|
2009-05-26 23:33:18 +00:00
|
|
|
bool "Generic uClinux RAM/ROM filesystem support"
|
2013-01-16 14:36:55 +00:00
|
|
|
depends on (MTD_RAM=y || MTD_ROM=y) && (!MMU || COLDFIRE)
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Map driver to support image based filesystems for uClinux.
|
|
|
|
|
|
2007-09-23 17:51:25 +00:00
|
|
|
config MTD_INTEL_VR_NOR
|
|
|
|
|
tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
|
|
|
|
|
depends on PCI
|
|
|
|
|
help
|
|
|
|
|
Map driver for a NOR flash bank located on the Expansion Bus of the
|
|
|
|
|
Intel Vermilion Range chipset.
|
|
|
|
|
|
2009-03-04 20:01:34 +00:00
|
|
|
config MTD_RBTX4939
|
|
|
|
|
tristate "Map driver for RBTX4939 board"
|
|
|
|
|
depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS
|
|
|
|
|
help
|
|
|
|
|
Map driver for NOR flash chips on RBTX4939 board.
|
|
|
|
|
|
2005-01-24 00:37:04 +00:00
|
|
|
config MTD_PLATRAM
|
2005-03-18 02:07:24 +00:00
|
|
|
tristate "Map driver for platform device RAM (mtd-ram)"
|
2005-01-24 00:37:04 +00:00
|
|
|
select MTD_RAM
|
|
|
|
|
help
|
|
|
|
|
Map driver for RAM areas described via the platform device
|
|
|
|
|
system.
|
|
|
|
|
|
|
|
|
|
This selection automatically selects the map_ram driver.
|
|
|
|
|
|
2009-03-04 00:31:04 +00:00
|
|
|
config MTD_VMU
|
|
|
|
|
tristate "Map driver for Dreamcast VMU"
|
|
|
|
|
depends on MAPLE
|
|
|
|
|
help
|
|
|
|
|
This driver enables access to the Dreamcast Visual Memory Unit (VMU).
|
|
|
|
|
|
|
|
|
|
Most Dreamcast users will want to say Y here.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2009-03-04 00:31:04 +00:00
|
|
|
To build this as a module select M here, the module will be called
|
|
|
|
|
vmu-flash.
|
|
|
|
|
|
2009-11-29 15:23:51 +00:00
|
|
|
config MTD_PISMO
|
|
|
|
|
tristate "MTD discovery driver for PISMO modules"
|
|
|
|
|
depends on I2C
|
|
|
|
|
depends on ARCH_VERSATILE
|
|
|
|
|
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, 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
|
|
|
|
|
|
2010-11-30 10:02:05 +00:00
|
|
|
config MTD_LATCH_ADDR
|
|
|
|
|
tristate "Latch-assisted Flash Chip Support"
|
|
|
|
|
depends on MTD_COMPLEX_MAPPINGS
|
|
|
|
|
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.
|
|
|
|
|
|
2009-03-04 00:31:04 +00:00
|
|
|
endmenu
|
