1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $
4 menu "Self-contained MTD device drivers"
8 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
11 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
12 from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
13 These devices come in memory configurations from 32M - 1G. If you
14 have one, you probably want to enable this.
16 If this driver is compiled as a module you get the ability to select
17 the size of the aperture window pointing into the devices memory.
18 What this means is that if you have a 1G card, normally the kernel
19 will use a 1G memory map as its view of the device. As a module,
20 you can select a 1M window into the memory and the driver will
21 "slide" the window around the PMC551's memory. This was
22 particularly useful on the 2.2 kernels on PPC architectures as there
23 was limited kernel space to deal with.
25 config MTD_PMC551_BUGFIX
26 bool "PMC551 256M DRAM Bugfix"
29 Some of Ramix's PMC551 boards with 256M configurations have invalid
30 column and row mux values. This option will fix them, but will
31 break other memory configurations. If unsure say N.
33 config MTD_PMC551_DEBUG
34 bool "PMC551 Debugging"
37 This option makes the PMC551 more verbose during its operation and
38 is only really useful if you are developing on this driver or
39 suspect a possible hardware or driver bug. If unsure say N.
42 tristate "DEC MS02-NV NVRAM module support"
43 depends on MTD && MACH_DECSTATION
45 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
46 backed-up NVRAM module. The module was originally meant as an NFS
47 accelerator. Say Y here if you have a DECstation 5000/2x0 or a
48 DECsystem 5900 equipped with such a module.
50 If you want to compile this driver as a module ( = code which can be
51 inserted in and removed from the running kernel whenever you want),
52 say M here and read <file:Documentation/modules.txt>. The module will
56 tristate "Support for AT45xxx DataFlash"
57 depends on MTD && SPI_MASTER && EXPERIMENTAL
59 This enables access to AT45xxx DataFlash chips, using SPI.
60 Sometimes DataFlash chips are packaged inside MMC-format
61 cards; at this writing, the MMC stack won't handle those.
63 config MTD_DATAFLASH26
64 tristate "AT91RM9200 DataFlash AT26xxx"
65 depends on MTD && ARCH_AT91RM9200 && AT91_SPI
67 This enables access to the DataFlash chip (AT26xxx) on an
68 AT91RM9200-based board.
69 If you have such a board and such a DataFlash, say 'Y'.
72 tristate "Support for M25 SPI Flash"
73 depends on MTD && SPI_MASTER && EXPERIMENTAL
75 This enables access to ST M25P80 and similar SPI flash chips,
76 used for program and data storage. Set up your spi devices
77 with the right board-specific platform data.
80 tristate "Uncached system RAM"
83 If your CPU cannot cache all of the physical memory in your machine,
84 you can still use it for storage or swap by using this driver to
85 present it to the system as a Memory Technology Device.
88 tristate "Physical system RAM"
91 This is a re-implementation of the slram driver above.
93 Use this driver to access physical memory that the kernel proper
94 doesn't have access to, memory beyond the mem=xxx limit, nvram,
95 memory on the video card, etc...
98 tristate "28F160xx flash driver for LART"
99 depends on SA1100_LART && MTD
101 This enables the flash driver for LART. Please note that you do
102 not need any mapping/chip driver for LART. This one does it all
103 for you, so go disable all of those if you enabled some of them (:
106 tristate "Test driver using RAM"
109 This enables a test MTD device driver which uses vmalloc() to
110 provide storage. You probably want to say 'N' unless you're
113 config MTDRAM_TOTAL_SIZE
114 int "MTDRAM device size in KiB"
115 depends on MTD_MTDRAM
118 This allows you to configure the total size of the MTD device
119 emulated by the MTDRAM driver. If the MTDRAM driver is built
120 as a module, it is also possible to specify this as a parameter when
123 config MTDRAM_ERASE_SIZE
124 int "MTDRAM erase block size in KiB"
125 depends on MTD_MTDRAM
128 This allows you to configure the size of the erase blocks in the
129 device emulated by the MTDRAM driver. If the MTDRAM driver is built
130 as a module, it is also possible to specify this as a parameter when
133 #If not a module (I don't want to test it as a module)
134 config MTDRAM_ABS_POS
135 hex "SRAM Hexadecimal Absolute position or 0"
136 depends on MTD_MTDRAM=y
139 If you have system RAM accessible by the CPU but not used by Linux
140 in normal operation, you can give the physical address at which the
141 available RAM starts, and the MTDRAM driver will use it instead of
142 allocating space from Linux's available memory. Otherwise, leave
143 this set to zero. Most people will want to leave this as zero.
146 tristate "MTD using block device"
147 depends on MTD && BLOCK
149 This driver allows a block device to appear as an MTD. It would
150 generally be used in the following cases:
152 Using Compact Flash as an MTD, these usually present themselves to
153 the system as an ATA drive.
154 Testing MTD users (eg JFFS2) on large media and media that might
155 be removed during a write (using the floppy drive).
157 comment "Disk-On-Chip Device Drivers"
160 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
165 This provides an MTD device driver for the M-Systems DiskOnChip
166 2000 and Millennium devices. Originally designed for the DiskOnChip
167 2000, it also now includes support for the DiskOnChip Millennium.
168 If you have problems with this driver and the DiskOnChip Millennium,
169 you may wish to try the alternative Millennium driver below. To use
170 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
171 in the <file:drivers/mtd/devices/docprobe.c> source code.
173 If you use this device, you probably also want to enable the NFTL
174 'NAND Flash Translation Layer' option below, which is used to
175 emulate a block device by using a kind of file system on the flash
178 NOTE: This driver is deprecated and will probably be removed soon.
179 Please try the new DiskOnChip driver under "NAND Flash Device
183 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
188 This provides an alternative MTD device driver for the M-Systems
189 DiskOnChip Millennium devices. Use this if you have problems with
190 the combined DiskOnChip 2000 and Millennium driver above. To get
191 the DiskOnChip probe code to load and use this driver instead of
192 the other one, you will need to undefine DOC_SINGLE_DRIVER near
193 the beginning of <file:drivers/mtd/devices/docprobe.c>.
195 If you use this device, you probably also want to enable the NFTL
196 'NAND Flash Translation Layer' option below, which is used to
197 emulate a block device by using a kind of file system on the flash
200 NOTE: This driver is deprecated and will probably be removed soon.
201 Please try the new DiskOnChip driver under "NAND Flash Device
204 config MTD_DOC2001PLUS
205 tristate "M-Systems Disk-On-Chip Millennium Plus"
210 This provides an MTD device driver for the M-Systems DiskOnChip
211 Millennium Plus devices.
213 If you use this device, you probably also want to enable the INFTL
214 'Inverse NAND Flash Translation Layer' option below, which is used
215 to emulate a block device by using a kind of file system on the
218 NOTE: This driver will soon be replaced by the new DiskOnChip driver
219 under "NAND Flash Device Drivers" (currently that driver does not
220 support all Millennium Plus devices).
229 config MTD_DOCPROBE_ADVANCED
230 bool "Advanced detection options for DiskOnChip"
231 depends on MTD_DOCPROBE
233 This option allows you to specify nonstandard address at which to
234 probe for a DiskOnChip, or to change the detection options. You
235 are unlikely to need any of this unless you are using LinuxBIOS.
238 config MTD_DOCPROBE_ADDRESS
239 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
240 depends on MTD_DOCPROBE
241 default "0x0000" if MTD_DOCPROBE_ADVANCED
242 default "0" if !MTD_DOCPROBE_ADVANCED
244 By default, the probe for DiskOnChip devices will look for a
245 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
246 This option allows you to specify a single address at which to probe
247 for the device, which is useful if you have other devices in that
248 range which get upset when they are probed.
250 (Note that on PowerPC, the normal probe will only check at
253 Normally, you should leave this set to zero, to allow the probe at
254 the normal addresses.
256 config MTD_DOCPROBE_HIGH
257 bool "Probe high addresses"
258 depends on MTD_DOCPROBE_ADVANCED
260 By default, the probe for DiskOnChip devices will look for a
261 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
262 This option changes to make it probe between 0xFFFC8000 and
263 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
264 useful to you. Say 'N'.
266 config MTD_DOCPROBE_55AA
267 bool "Probe for 0x55 0xAA BIOS Extension Signature"
268 depends on MTD_DOCPROBE_ADVANCED
270 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
271 continue with probing if it is absent. The signature will always be
272 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
273 Only if you have overwritten the first block of a DiskOnChip
274 Millennium will it be absent. Enable this option if you are using
275 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
276 you have managed to wipe the first block.