1 # drivers/mtd/maps/Kconfig
3 menu "Self-contained MTD device drivers"
7 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
10 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
11 from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
12 These devices come in memory configurations from 32M - 1G. If you
13 have one, you probably want to enable this.
15 If this driver is compiled as a module you get the ability to select
16 the size of the aperture window pointing into the devices memory.
17 What this means is that if you have a 1G card, normally the kernel
18 will use a 1G memory map as its view of the device. As a module,
19 you can select a 1M window into the memory and the driver will
20 "slide" the window around the PMC551's memory. This was
21 particularly useful on the 2.2 kernels on PPC architectures as there
22 was limited kernel space to deal with.
24 config MTD_PMC551_BUGFIX
25 bool "PMC551 256M DRAM Bugfix"
28 Some of Ramix's PMC551 boards with 256M configurations have invalid
29 column and row mux values. This option will fix them, but will
30 break other memory configurations. If unsure say N.
32 config MTD_PMC551_DEBUG
33 bool "PMC551 Debugging"
36 This option makes the PMC551 more verbose during its operation and
37 is only really useful if you are developing on this driver or
38 suspect a possible hardware or driver bug. If unsure say N.
41 tristate "DEC MS02-NV NVRAM module support"
42 depends on MACH_DECSTATION
44 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
45 backed-up NVRAM module. The module was originally meant as an NFS
46 accelerator. Say Y here if you have a DECstation 5000/2x0 or a
47 DECsystem 5900 equipped with such a module.
49 If you want to compile this driver as a module ( = code which can be
50 inserted in and removed from the running kernel whenever you want),
51 say M here and read <file:Documentation/kbuild/modules.txt>.
52 The module will be called ms02-nv.ko.
55 tristate "Support for AT45xxx DataFlash"
56 depends on SPI_MASTER && EXPERIMENTAL
58 This enables access to AT45xxx DataFlash chips, using SPI.
59 Sometimes DataFlash chips are packaged inside MMC-format
60 cards; at this writing, the MMC stack won't handle those.
62 config MTD_DATAFLASH_OTP
63 bool "DataFlash OTP support (Security Register)"
64 depends on MTD_DATAFLASH
67 Newer DataFlash chips (revisions C and D) support 128 bytes of
68 one-time-programmable (OTP) data. The first half may be written
69 (once) with up to 64 bytes of data, such as a serial number or
70 other key product data. The second half is programmed with a
71 unique-to-each-chip bit pattern at the factory.
74 tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
75 depends on SPI_MASTER && EXPERIMENTAL
77 This enables access to most modern SPI flash chips, used for
78 program and data storage. Series supported include Atmel AT26DF,
79 Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips
80 are supported as well. See the driver source for the current list,
81 or to add other chips.
83 Note that the original DataFlash chips (AT45 series, not AT26DF),
84 need an entirely different driver.
86 Set up your spi devices with the right board-specific platform data,
87 if you want to specify device partitioning or to use a device which
88 doesn't support the JEDEC ID instruction.
90 config M25PXX_USE_FAST_READ
91 bool "Use FAST_READ OPCode allowing SPI CLK <= 50MHz"
95 This option enables FAST_READ access supported by ST M25Pxx.
98 tristate "Uncached system RAM"
100 If your CPU cannot cache all of the physical memory in your machine,
101 you can still use it for storage or swap by using this driver to
102 present it to the system as a Memory Technology Device.
105 tristate "Physical system RAM"
107 This is a re-implementation of the slram driver above.
109 Use this driver to access physical memory that the kernel proper
110 doesn't have access to, memory beyond the mem=xxx limit, nvram,
111 memory on the video card, etc...
114 tristate "28F160xx flash driver for LART"
115 depends on SA1100_LART
117 This enables the flash driver for LART. Please note that you do
118 not need any mapping/chip driver for LART. This one does it all
119 for you, so go disable all of those if you enabled some of them (:
122 tristate "Test driver using RAM"
124 This enables a test MTD device driver which uses vmalloc() to
125 provide storage. You probably want to say 'N' unless you're
128 config MTDRAM_TOTAL_SIZE
129 int "MTDRAM device size in KiB"
130 depends on MTD_MTDRAM
133 This allows you to configure the total size of the MTD device
134 emulated by the MTDRAM driver. If the MTDRAM driver is built
135 as a module, it is also possible to specify this as a parameter when
138 config MTDRAM_ERASE_SIZE
139 int "MTDRAM erase block size in KiB"
140 depends on MTD_MTDRAM
143 This allows you to configure the size of the erase blocks in the
144 device emulated by the MTDRAM driver. If the MTDRAM driver is built
145 as a module, it is also possible to specify this as a parameter when
148 #If not a module (I don't want to test it as a module)
149 config MTDRAM_ABS_POS
150 hex "SRAM Hexadecimal Absolute position or 0"
151 depends on MTD_MTDRAM=y
154 If you have system RAM accessible by the CPU but not used by Linux
155 in normal operation, you can give the physical address at which the
156 available RAM starts, and the MTDRAM driver will use it instead of
157 allocating space from Linux's available memory. Otherwise, leave
158 this set to zero. Most people will want to leave this as zero.
161 tristate "MTD using block device"
164 This driver allows a block device to appear as an MTD. It would
165 generally be used in the following cases:
167 Using Compact Flash as an MTD, these usually present themselves to
168 the system as an ATA drive.
169 Testing MTD users (eg JFFS2) on large media and media that might
170 be removed during a write (using the floppy drive).
172 comment "Disk-On-Chip Device Drivers"
175 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
179 This provides an MTD device driver for the M-Systems DiskOnChip
180 2000 and Millennium devices. Originally designed for the DiskOnChip
181 2000, it also now includes support for the DiskOnChip Millennium.
182 If you have problems with this driver and the DiskOnChip Millennium,
183 you may wish to try the alternative Millennium driver below. To use
184 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
185 in the <file:drivers/mtd/devices/docprobe.c> source code.
187 If you use this device, you probably also want to enable the NFTL
188 'NAND Flash Translation Layer' option below, which is used to
189 emulate a block device by using a kind of file system on the flash
192 NOTE: This driver is deprecated and will probably be removed soon.
193 Please try the new DiskOnChip driver under "NAND Flash Device
197 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
201 This provides an alternative MTD device driver for the M-Systems
202 DiskOnChip Millennium devices. Use this if you have problems with
203 the combined DiskOnChip 2000 and Millennium driver above. To get
204 the DiskOnChip probe code to load and use this driver instead of
205 the other one, you will need to undefine DOC_SINGLE_DRIVER near
206 the beginning of <file:drivers/mtd/devices/docprobe.c>.
208 If you use this device, you probably also want to enable the NFTL
209 'NAND Flash Translation Layer' option below, which is used to
210 emulate a block device by using a kind of file system on the flash
213 NOTE: This driver is deprecated and will probably be removed soon.
214 Please try the new DiskOnChip driver under "NAND Flash Device
217 config MTD_DOC2001PLUS
218 tristate "M-Systems Disk-On-Chip Millennium Plus"
222 This provides an MTD device driver for the M-Systems DiskOnChip
223 Millennium Plus devices.
225 If you use this device, you probably also want to enable the INFTL
226 'Inverse NAND Flash Translation Layer' option below, which is used
227 to emulate a block device by using a kind of file system on the
230 NOTE: This driver will soon be replaced by the new DiskOnChip driver
231 under "NAND Flash Device Drivers" (currently that driver does not
232 support all Millennium Plus devices).
241 config MTD_DOCPROBE_ADVANCED
242 bool "Advanced detection options for DiskOnChip"
243 depends on MTD_DOCPROBE
245 This option allows you to specify nonstandard address at which to
246 probe for a DiskOnChip, or to change the detection options. You
247 are unlikely to need any of this unless you are using LinuxBIOS.
250 config MTD_DOCPROBE_ADDRESS
251 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
252 depends on MTD_DOCPROBE
253 default "0x0000" if MTD_DOCPROBE_ADVANCED
254 default "0" if !MTD_DOCPROBE_ADVANCED
256 By default, the probe for DiskOnChip devices will look for a
257 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
258 This option allows you to specify a single address at which to probe
259 for the device, which is useful if you have other devices in that
260 range which get upset when they are probed.
262 (Note that on PowerPC, the normal probe will only check at
265 Normally, you should leave this set to zero, to allow the probe at
266 the normal addresses.
268 config MTD_DOCPROBE_HIGH
269 bool "Probe high addresses"
270 depends on MTD_DOCPROBE_ADVANCED
272 By default, the probe for DiskOnChip devices will look for a
273 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
274 This option changes to make it probe between 0xFFFC8000 and
275 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
276 useful to you. Say 'N'.
278 config MTD_DOCPROBE_55AA
279 bool "Probe for 0x55 0xAA BIOS Extension Signature"
280 depends on MTD_DOCPROBE_ADVANCED
282 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
283 continue with probing if it is absent. The signature will always be
284 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
285 Only if you have overwritten the first block of a DiskOnChip
286 Millennium will it be absent. Enable this option if you are using
287 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
288 you have managed to wipe the first block.