menu "Self-contained MTD device drivers"
depends on [31mCONFIG_MTD[0m!=n
depends on [31mCONFIG_HAS_IOMEM[0m
config [31mCONFIG_MTD_PMC551[0m
tristate "Ramix PMC551 PCI Mezzanine RAM card support"
depends on [31mCONFIG_PCI[0m
---help---
This provides a [31mCONFIG_MTD[0m device driver for the Ramix PMC551 RAM [31mCONFIG_PCI[0m card
from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
These devices come in memory configurations from 32M - 1G. If you
have one, you probably want to enable this.
If this driver is compiled as a module you get the ability to select
the size of the aperture window pointing into the devices memory.
What this means is that if you have a 1G card, normally the kernel
will use a 1G memory map as its view of the device. As a module,
you can select a 1M window into the memory and the driver will
"slide" the window around the PMC551's memory. This was
particularly useful on the 2.2 kernels on [31mCONFIG_PPC[0m architectures as there
was limited kernel space to deal with.
config [31mCONFIG_MTD_PMC551_BUGFIX[0m
bool "PMC551 256M DRAM Bugfix"
depends on [31mCONFIG_MTD_PMC551[0m
help
Some of Ramix's PMC551 boards with 256M configurations have invalid
column and row mux values. This option will fix them, but will
break other memory configurations. If unsure say N.
config [31mCONFIG_MTD_PMC551_DEBUG[0m
bool "PMC551 Debugging"
depends on [31mCONFIG_MTD_PMC551[0m
help
This option makes the PMC551 more verbose during its operation and
is only really useful if you are developing on this driver or
suspect a possible hardware or driver bug. If unsure say N.
config [31mCONFIG_MTD_MS02NV[0m
tristate "DEC MS02-NV NVRAM module support"
depends on [31mCONFIG_MACH_DECSTATION[0m
help
This is an [31mCONFIG_MTD[0m driver for the DEC's MS02-NV (54-20948-01) battery
backed-up [31mCONFIG_NVRAM[0m module. The module was originally meant as an NFS
accelerator. Say Y here if you have a DECstation 5000/2x0 or a
DECsystem 5900 equipped with such a module.
If you want to compile this driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say [31mCONFIG_M[0m here and read <file:Documentation/kbuild/modules.txt>.
The module will be called ms02-nv.
config [31mCONFIG_MTD_DATAFLASH[0m
tristate "Support for AT45xxx DataFlash"
depends on [31mCONFIG_SPI_MASTER[0m
help
This enables access to AT45xxx DataFlash chips, using [31mCONFIG_SPI[0m.
Sometimes DataFlash chips are packaged inside [31mCONFIG_MMC[0m-format
cards; at this writing, the [31mCONFIG_MMC[0m stack won't handle those.
config [31mCONFIG_MTD_DATAFLASH_WRITE_VERIFY[0m
bool "Verify DataFlash page writes"
depends on [31mCONFIG_MTD_DATAFLASH[0m
help
This adds an extra check when data is written to the flash.
It may help if you are verifying chip setup (timings etc) on
your board. There is a rare possibility that even though the
device thinks the write was successful, a bit could have been
flipped accidentally due to device wear or something else.
config [31mCONFIG_MTD_DATAFLASH_OTP[0m
bool "DataFlash OTP support (Security Register)"
depends on [31mCONFIG_MTD_DATAFLASH[0m
help
Newer DataFlash chips (revisions [31mCONFIG_C[0m and [31mCONFIG_D[0m) support 128 bytes of
one-time-programmable (OTP) data. The first half may be written
(once) with up to 64 bytes of data, such as a serial number or
other key product data. The second half is programmed with a
unique-to-each-chip bit pattern at the factory.
config [31mCONFIG_MTD_M25P80[0m
tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
depends on [31mCONFIG_SPI_MASTER[0m && [31mCONFIG_MTD_SPI_NOR[0m
help
This enables access to most modern [31mCONFIG_SPI[0m flash chips, used for
program and data storage. Series supported include Atmel AT26DF,
Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips
are supported as well. See the driver source for the current list,
or to add other chips.
Note that the original DataFlash chips (AT45 series, not AT26DF),
need an entirely different driver.
Set up your spi devices with the right board-specific platform data,
if you want to specify device partitioning or to use a device which
doesn't support the JEDEC ID instruction.
config [31mCONFIG_MTD_SPEAR_SMI[0m
tristate "SPEAR MTD NOR Support through SMI controller"
depends on [31mCONFIG_PLAT_SPEAR[0m
default y
help
This enable SNOR support on SPEAR platforms using SMI controller
config [31mCONFIG_MTD_SST25L[0m
tristate "Support SST25L (non JEDEC) SPI Flash chips"
depends on [31mCONFIG_SPI_MASTER[0m
help
This enables access to the non JEDEC SST25L [31mCONFIG_SPI[0m flash chips, used
for program and data storage.
Set up your spi devices with the right board-specific platform data,
if you want to specify device partitioning.
config [31mCONFIG_MTD_BCM47XXSFLASH[0m
tristate "Support for serial flash on BCMA bus"
depends on [31mCONFIG_BCMA_SFLASH[0m && ([31mCONFIG_MIPS[0m || [31mCONFIG_ARM[0m)
help
[31mCONFIG_BCMA[0m bus can have various flash memories attached, they are
registered by bcma as platform devices. This enables driver for
serial flash memories.
config [31mCONFIG_MTD_SLRAM[0m
tristate "Uncached system RAM"
help
If your CPU cannot cache all of the physical memory in your machine,
you can still use it for storage or swap by using this driver to
present it to the system as a Memory Technology Device.
config [31mCONFIG_MTD_PHRAM[0m
tristate "Physical system RAM"
help
This is a re-implementation of the slram driver above.
Use this driver to access physical memory that the kernel proper
doesn't have access to, memory beyond the mem=xxx limit, nvram,
memory on the video card, etc...
config [31mCONFIG_MTD_LART[0m
tristate "28F160xx flash driver for LART"
depends on [31mCONFIG_SA1100_LART[0m
help
This enables the flash driver for LART. Please note that you do
not need any mapping/chip driver for LART. This one does it all
for you, so go disable all of those if you enabled some of them (:
config [31mCONFIG_MTD_MTDRAM[0m
tristate "Test driver using RAM"
help
This enables a test [31mCONFIG_MTD[0m device driver which uses vmalloc() to
provide storage. You probably want to say 'N' unless you're
testing stuff.
config [31mCONFIG_MTDRAM_TOTAL_SIZE[0m
int "MTDRAM device size in KiB"
depends on [31mCONFIG_MTD_MTDRAM[0m
default "4096"
help
This allows you to configure the total size of the [31mCONFIG_MTD[0m device
emulated by the MTDRAM driver. If the MTDRAM driver is built
as a module, it is also possible to specify this as a parameter when
loading the module.
config [31mCONFIG_MTDRAM_ERASE_SIZE[0m
int "MTDRAM erase block size in KiB"
depends on [31mCONFIG_MTD_MTDRAM[0m
default "128"
help
This allows you to configure the size of the erase blocks in the
device emulated by the MTDRAM driver. If the MTDRAM driver is built
as a module, it is also possible to specify this as a parameter when
loading the module.
config [31mCONFIG_MTD_BLOCK2MTD[0m
tristate "MTD using block device"
depends on [31mCONFIG_BLOCK[0m
help
This driver allows a block device to appear as an [31mCONFIG_MTD[0m. It would
generally be used in the following cases:
Using Compact Flash as an [31mCONFIG_MTD[0m, these usually present themselves to
the system as an [31mCONFIG_ATA[0m drive.
Testing [31mCONFIG_MTD[0m users (eg JFFS2) on large media and media that might
be removed during a write (using the floppy drive).
config [31mCONFIG_MTD_POWERNV_FLASH[0m
tristate "powernv flash MTD driver"
depends on [31mCONFIG_PPC_POWERNV[0m
help
This provides an [31mCONFIG_MTD[0m device to access flash on powernv OPAL
platforms from Linux. This device abstracts away the
firmware interface for flash access.
comment "Disk-On-Chip Device Drivers"
config [31mCONFIG_MTD_DOCG3[0m
tristate "M-Systems Disk-On-Chip G3"
select [31mCONFIG_BCH[0m
select [31mCONFIG_BCH_CONST_PARAMS[0m
select [31mCONFIG_BITREVERSE[0m
---help---
This provides an [31mCONFIG_MTD[0m device driver for the [31mCONFIG_M[0m-Systems DiskOnChip
G3 devices.
The driver provides access to G3 DiskOnChip, distributed by
[31mCONFIG_M[0m-Systems and now Sandisk. The support is very experimental,
and doesn't give access to any write operations.
config [31mCONFIG_MTD_ST_SPI_FSM[0m
tristate "ST Microelectronics SPI FSM Serial Flash Controller"
depends on [31mCONFIG_ARCH_STI[0m
help
This provides an [31mCONFIG_MTD[0m device driver for the ST Microelectronics
[31mCONFIG_SPI[0m Fast Sequence Mode (FSM) Serial Flash Controller and support
for a subset of connected Serial Flash devices.
if [31mCONFIG_MTD_DOCG3[0m
config [31mCONFIG_BCH_CONST_M[0m
default 14
config [31mCONFIG_BCH_CONST_T[0m
default 4
endif
endmenu