1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.4 2003/05/28 15:18:54 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/>. These devices come
13 in memory configurations from 32M - 1G. If you have one, you
14 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 CONFIG_DECSTATION
45 Support for NVRAM module on DECstation.
48 tristate "Uncached system RAM"
51 If your CPU cannot cache all of the physical memory in your machine,
52 you can still use it for storage or swap by using this driver to
53 present it to the system as a Memory Technology Device.
56 tristate "28F160xx flash driver for LART"
57 depends on SA1100_LART && MTD
59 This enables the flash driver for LART. Please note that you do
60 not need any mapping/chip driver for LART. This one does it all
61 for you, so go disable all of those if you enabled some of them (:
64 tristate "Test driver using RAM"
67 This enables a test MTD device driver which uses vmalloc() to
68 provide storage. You probably want to say 'N' unless you're
71 config MTDRAM_TOTAL_SIZE
72 int "MTDRAM device size in KiB"
76 This allows you to configure the total size of the MTD device
77 emulated by the MTDRAM driver. If the MTDRAM driver is built
78 as a module, it is also possible to specify this as a parameter when
81 config MTDRAM_ERASE_SIZE
82 int "MTDRAM erase block size in KiB"
86 This allows you to configure the size of the erase blocks in the
87 device emulated by the MTDRAM driver. If the MTDRAM driver is built
88 as a module, it is also possible to specify this as a parameter when
91 #If not a module (I don't want to test it as a module)
93 hex "SRAM Hexadecimal Absolute position or 0"
94 depends on MTD_MTDRAM=y
97 If you have system RAM accessible by the CPU but not used by Linux
98 in normal operation, you can give the physical address at which the
99 available RAM starts, and the MTDRAM driver will use it instead of
100 allocating space from Linux's available memory. Otherwise, leave
101 this set to zero. Most people will want to leave this as zero.
104 tristate "MTD emulation using block device"
107 This driver allows a block device to appear as an MTD. It would
108 generally be used in the following cases:
110 Using Compact Flash as an MTD, these usually present themselves to
111 the system as an ATA drive.
112 Testing MTD users (eg JFFS2) on large media and media that might
113 be removed during a write (using the floppy drive).
115 comment "Disk-On-Chip Device Drivers"
118 tristate "M-Systems Disk-On-Chip 2000 and Millennium"
121 This provides an MTD device driver for the M-Systems DiskOnChip
122 2000 and Millennium devices. Originally designed for the DiskOnChip
123 2000, it also now includes support for the DiskOnChip Millennium.
124 If you have problems with this driver and the DiskOnChip Millennium,
125 you may wish to try the alternative Millennium driver below. To use
126 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
127 in the <file:drivers/mtd/devices/docprobe.c> source code.
129 If you use this device, you probably also want to enable the NFTL
130 'NAND Flash Translation Layer' option below, which is used to
131 emulate a block device by using a kind of file system on the flash
135 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (see help)"
138 This provides an alternative MTD device driver for the M-Systems
139 DiskOnChip Millennium devices. Use this if you have problems with
140 the combined DiskOnChip 2000 and Millennium driver above. To get
141 the DiskOnChip probe code to load and use this driver instead of
142 the other one, you will need to undefine DOC_SINGLE_DRIVER near
143 the beginning of <file:drivers/mtd/devices/docprobe.c>.
145 If you use this device, you probably also want to enable the NFTL
146 'NAND Flash Translation Layer' option below, which is used to
147 emulate a block device by using a kind of file system on the flash
150 config MTD_DOC2001PLUS
151 tristate "M-Systems Disk-On-Chip Millennium Plus"
154 This provides an MTD device driver for the M-Systems DiskOnChip
155 Millennium Plus devices.
157 If you use this device, you probably also want to enable the INFTL
158 'Inverse NAND Flash Translation Layer' option below, which is used
159 to emulate a block device by using a kind of file system on the
164 default m if MTD_DOC2001!=y && MTD_DOC2000!=y && MTD_DOC2001PLUS!=y && (MTD_DOC2001=m || MTD_DOC2000=m || MOD_DOC2001PLUS=m)
165 default y if MTD_DOC2001=y || MTD_DOC2000=y || MTD_DOC2001PLUS=y
167 This isn't a real config option, it's derived.
169 config MTD_DOCPROBE_ADVANCED
170 bool "Advanced detection options for DiskOnChip"
171 depends on MTD_DOCPROBE
173 This option allows you to specify nonstandard address at which to
174 probe for a DiskOnChip, or to change the detection options. You
175 are unlikely to need any of this unless you are using LinuxBIOS.
178 config MTD_DOCPROBE_ADDRESS
179 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
180 depends on MTD_DOCPROBE
181 default "0x0000" if MTD_DOCPROBE_ADVANCED
182 default "0" if !MTD_DOCPROBE_ADVANCED
184 By default, the probe for DiskOnChip devices will look for a
185 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
186 This option allows you to specify a single address at which to probe
187 for the device, which is useful if you have other devices in that
188 range which get upset when they are probed.
190 (Note that on PowerPC, the normal probe will only check at
193 Normally, you should leave this set to zero, to allow the probe at
194 the normal addresses.
196 config MTD_DOCPROBE_HIGH
197 bool "Probe high addresses"
198 depends on MTD_DOCPROBE_ADVANCED
200 By default, the probe for DiskOnChip devices will look for a
201 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
202 This option changes to make it probe between 0xFFFC8000 and
203 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
204 useful to you. Say 'N'.
206 config MTD_DOCPROBE_55AA
207 bool "Probe for 0x55 0xAA BIOS Extension Signature"
208 depends on MTD_DOCPROBE_ADVANCED
210 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
211 continue with probing if it is absent. The signature will always be
212 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
213 Only if you have overwritten the first block of a DiskOnChip
214 Millennium will it be absent. Enable this option if you are using
215 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
216 you have managed to wipe the first block.