1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.10 2004/07/15 00:34:49 dwmw2 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 "Uncached system RAM"
54 If your CPU cannot cache all of the physical memory in your machine,
55 you can still use it for storage or swap by using this driver to
56 present it to the system as a Memory Technology Device.
59 tristate "Physical system RAM"
62 This is a re-implementation of the slram driver above.
64 Use this driver to access physical memory that the kernel proper
65 doesn't have access to, memory beyond the mem=xxx limit, nvram,
66 memory on the video card, etc...
69 tristate "28F160xx flash driver for LART"
70 depends on SA1100_LART && MTD
72 This enables the flash driver for LART. Please note that you do
73 not need any mapping/chip driver for LART. This one does it all
74 for you, so go disable all of those if you enabled some of them (:
77 tristate "Test driver using RAM"
80 This enables a test MTD device driver which uses vmalloc() to
81 provide storage. You probably want to say 'N' unless you're
84 config MTDRAM_TOTAL_SIZE
85 int "MTDRAM device size in KiB"
89 This allows you to configure the total size of the MTD device
90 emulated by the MTDRAM driver. If the MTDRAM driver is built
91 as a module, it is also possible to specify this as a parameter when
94 config MTDRAM_ERASE_SIZE
95 int "MTDRAM erase block size in KiB"
99 This allows you to configure the size of the erase blocks in the
100 device emulated by the MTDRAM driver. If the MTDRAM driver is built
101 as a module, it is also possible to specify this as a parameter when
104 #If not a module (I don't want to test it as a module)
105 config MTDRAM_ABS_POS
106 hex "SRAM Hexadecimal Absolute position or 0"
107 depends on MTD_MTDRAM=y
110 If you have system RAM accessible by the CPU but not used by Linux
111 in normal operation, you can give the physical address at which the
112 available RAM starts, and the MTDRAM driver will use it instead of
113 allocating space from Linux's available memory. Otherwise, leave
114 this set to zero. Most people will want to leave this as zero.
117 tristate "MTD emulation using block device"
120 This driver allows a block device to appear as an MTD. It would
121 generally be used in the following cases:
123 Using Compact Flash as an MTD, these usually present themselves to
124 the system as an ATA drive.
125 Testing MTD users (eg JFFS2) on large media and media that might
126 be removed during a write (using the floppy drive).
128 comment "Disk-On-Chip Device Drivers"
131 tristate "M-Systems Disk-On-Chip 2000 and Millennium"
134 This provides an MTD device driver for the M-Systems DiskOnChip
135 2000 and Millennium devices. Originally designed for the DiskOnChip
136 2000, it also now includes support for the DiskOnChip Millennium.
137 If you have problems with this driver and the DiskOnChip Millennium,
138 you may wish to try the alternative Millennium driver below. To use
139 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
140 in the <file:drivers/mtd/devices/docprobe.c> source code.
142 If you use this device, you probably also want to enable the NFTL
143 'NAND Flash Translation Layer' option below, which is used to
144 emulate a block device by using a kind of file system on the flash
148 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (see help)"
151 This provides an alternative MTD device driver for the M-Systems
152 DiskOnChip Millennium devices. Use this if you have problems with
153 the combined DiskOnChip 2000 and Millennium driver above. To get
154 the DiskOnChip probe code to load and use this driver instead of
155 the other one, you will need to undefine DOC_SINGLE_DRIVER near
156 the beginning of <file:drivers/mtd/devices/docprobe.c>.
158 If you use this device, you probably also want to enable the NFTL
159 'NAND Flash Translation Layer' option below, which is used to
160 emulate a block device by using a kind of file system on the flash
163 config MTD_DOC2001PLUS
164 tristate "M-Systems Disk-On-Chip Millennium Plus"
167 This provides an MTD device driver for the M-Systems DiskOnChip
168 Millennium Plus devices.
170 If you use this device, you probably also want to enable the INFTL
171 'Inverse NAND Flash Translation Layer' option below, which is used
172 to emulate a block device by using a kind of file system on the
177 default m if MTD_DOC2001!=y && MTD_DOC2000!=y && MTD_DOC2001PLUS!=y && (MTD_DOC2001=m || MTD_DOC2000=m || MTD_DOC2001PLUS=m)
178 default y if MTD_DOC2001=y || MTD_DOC2000=y || MTD_DOC2001PLUS=y
180 This isn't a real config option, it's derived.
184 default m if MTD_DOCPROBE!=y && MTD_NAND_DISKONCHIP!=y && (MTD_DOCPROBE=m || MTD_NAND_DISKONCHIP=m)
185 default y if MTD_DOCPROBE=y || MTD_NAND_DISKONCHIP=y
187 This isn't a real config option, it's derived.
189 config MTD_DOCPROBE_ADVANCED
190 bool "Advanced detection options for DiskOnChip"
191 depends on MTD_DOCPROBE
193 This option allows you to specify nonstandard address at which to
194 probe for a DiskOnChip, or to change the detection options. You
195 are unlikely to need any of this unless you are using LinuxBIOS.
198 config MTD_DOCPROBE_ADDRESS
199 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
200 depends on MTD_DOCPROBE
201 default "0x0000" if MTD_DOCPROBE_ADVANCED
202 default "0" if !MTD_DOCPROBE_ADVANCED
204 By default, the probe for DiskOnChip devices will look for a
205 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
206 This option allows you to specify a single address at which to probe
207 for the device, which is useful if you have other devices in that
208 range which get upset when they are probed.
210 (Note that on PowerPC, the normal probe will only check at
213 Normally, you should leave this set to zero, to allow the probe at
214 the normal addresses.
216 config MTD_DOCPROBE_HIGH
217 bool "Probe high addresses"
218 depends on MTD_DOCPROBE_ADVANCED
220 By default, the probe for DiskOnChip devices will look for a
221 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
222 This option changes to make it probe between 0xFFFC8000 and
223 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
224 useful to you. Say 'N'.
226 config MTD_DOCPROBE_55AA
227 bool "Probe for 0x55 0xAA BIOS Extension Signature"
228 depends on MTD_DOCPROBE_ADVANCED
230 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
231 continue with probing if it is absent. The signature will always be
232 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
233 Only if you have overwritten the first block of a DiskOnChip
234 Millennium will it be absent. Enable this option if you are using
235 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
236 you have managed to wipe the first block.