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.
51 tristate "Support for AT45xxx DataFlash"
52 depends on MTD && SPI_MASTER && EXPERIMENTAL
54 This enables access to AT45xxx DataFlash chips, using SPI.
55 Sometimes DataFlash chips are packaged inside MMC-format
56 cards; at this writing, the MMC stack won't handle those.
59 tristate "Support for M25 SPI Flash"
60 depends on MTD && SPI_MASTER && EXPERIMENTAL
62 This enables access to ST M25P80 and similar SPI flash chips,
63 used for program and data storage. Set up your spi devices
64 with the right board-specific platform data.
67 tristate "Uncached system RAM"
70 If your CPU cannot cache all of the physical memory in your machine,
71 you can still use it for storage or swap by using this driver to
72 present it to the system as a Memory Technology Device.
75 tristate "Physical system RAM"
78 This is a re-implementation of the slram driver above.
80 Use this driver to access physical memory that the kernel proper
81 doesn't have access to, memory beyond the mem=xxx limit, nvram,
82 memory on the video card, etc...
85 tristate "28F160xx flash driver for LART"
86 depends on SA1100_LART && MTD
88 This enables the flash driver for LART. Please note that you do
89 not need any mapping/chip driver for LART. This one does it all
90 for you, so go disable all of those if you enabled some of them (:
93 tristate "Test driver using RAM"
96 This enables a test MTD device driver which uses vmalloc() to
97 provide storage. You probably want to say 'N' unless you're
100 config MTDRAM_TOTAL_SIZE
101 int "MTDRAM device size in KiB"
102 depends on MTD_MTDRAM
105 This allows you to configure the total size of the MTD device
106 emulated by the MTDRAM driver. If the MTDRAM driver is built
107 as a module, it is also possible to specify this as a parameter when
110 config MTDRAM_ERASE_SIZE
111 int "MTDRAM erase block size in KiB"
112 depends on MTD_MTDRAM
115 This allows you to configure the size of the erase blocks in the
116 device emulated by the MTDRAM driver. If the MTDRAM driver is built
117 as a module, it is also possible to specify this as a parameter when
120 #If not a module (I don't want to test it as a module)
121 config MTDRAM_ABS_POS
122 hex "SRAM Hexadecimal Absolute position or 0"
123 depends on MTD_MTDRAM=y
126 If you have system RAM accessible by the CPU but not used by Linux
127 in normal operation, you can give the physical address at which the
128 available RAM starts, and the MTDRAM driver will use it instead of
129 allocating space from Linux's available memory. Otherwise, leave
130 this set to zero. Most people will want to leave this as zero.
133 tristate "MTD using block device"
136 This driver allows a block device to appear as an MTD. It would
137 generally be used in the following cases:
139 Using Compact Flash as an MTD, these usually present themselves to
140 the system as an ATA drive.
141 Testing MTD users (eg JFFS2) on large media and media that might
142 be removed during a write (using the floppy drive).
144 comment "Disk-On-Chip Device Drivers"
147 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
152 This provides an MTD device driver for the M-Systems DiskOnChip
153 2000 and Millennium devices. Originally designed for the DiskOnChip
154 2000, it also now includes support for the DiskOnChip Millennium.
155 If you have problems with this driver and the DiskOnChip Millennium,
156 you may wish to try the alternative Millennium driver below. To use
157 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
158 in the <file:drivers/mtd/devices/docprobe.c> source code.
160 If you use this device, you probably also want to enable the NFTL
161 'NAND Flash Translation Layer' option below, which is used to
162 emulate a block device by using a kind of file system on the flash
165 NOTE: This driver is deprecated and will probably be removed soon.
166 Please try the new DiskOnChip driver under "NAND Flash Device
170 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
175 This provides an alternative MTD device driver for the M-Systems
176 DiskOnChip Millennium devices. Use this if you have problems with
177 the combined DiskOnChip 2000 and Millennium driver above. To get
178 the DiskOnChip probe code to load and use this driver instead of
179 the other one, you will need to undefine DOC_SINGLE_DRIVER near
180 the beginning of <file:drivers/mtd/devices/docprobe.c>.
182 If you use this device, you probably also want to enable the NFTL
183 'NAND Flash Translation Layer' option below, which is used to
184 emulate a block device by using a kind of file system on the flash
187 NOTE: This driver is deprecated and will probably be removed soon.
188 Please try the new DiskOnChip driver under "NAND Flash Device
191 config MTD_DOC2001PLUS
192 tristate "M-Systems Disk-On-Chip Millennium Plus"
197 This provides an MTD device driver for the M-Systems DiskOnChip
198 Millennium Plus devices.
200 If you use this device, you probably also want to enable the INFTL
201 'Inverse NAND Flash Translation Layer' option below, which is used
202 to emulate a block device by using a kind of file system on the
205 NOTE: This driver will soon be replaced by the new DiskOnChip driver
206 under "NAND Flash Device Drivers" (currently that driver does not
207 support all Millennium Plus devices).
212 select OBSOLETE_INTERMODULE
217 config MTD_DOCPROBE_ADVANCED
218 bool "Advanced detection options for DiskOnChip"
219 depends on MTD_DOCPROBE
221 This option allows you to specify nonstandard address at which to
222 probe for a DiskOnChip, or to change the detection options. You
223 are unlikely to need any of this unless you are using LinuxBIOS.
226 config MTD_DOCPROBE_ADDRESS
227 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
228 depends on MTD_DOCPROBE
229 default "0x0000" if MTD_DOCPROBE_ADVANCED
230 default "0" if !MTD_DOCPROBE_ADVANCED
232 By default, the probe for DiskOnChip devices will look for a
233 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
234 This option allows you to specify a single address at which to probe
235 for the device, which is useful if you have other devices in that
236 range which get upset when they are probed.
238 (Note that on PowerPC, the normal probe will only check at
241 Normally, you should leave this set to zero, to allow the probe at
242 the normal addresses.
244 config MTD_DOCPROBE_HIGH
245 bool "Probe high addresses"
246 depends on MTD_DOCPROBE_ADVANCED
248 By default, the probe for DiskOnChip devices will look for a
249 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
250 This option changes to make it probe between 0xFFFC8000 and
251 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
252 useful to you. Say 'N'.
254 config MTD_DOCPROBE_55AA
255 bool "Probe for 0x55 0xAA BIOS Extension Signature"
256 depends on MTD_DOCPROBE_ADVANCED
258 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
259 continue with probing if it is absent. The signature will always be
260 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
261 Only if you have overwritten the first block of a DiskOnChip
262 Millennium will it be absent. Enable this option if you are using
263 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
264 you have managed to wipe the first block.