Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
1# drivers/mtd/maps/Kconfig
2# $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $
3
4menu "Self-contained MTD device drivers"
5 depends on MTD!=n
6
7config MTD_PMC551
8 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
9 depends on MTD && PCI
10 ---help---
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.
15
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.
24
25config MTD_PMC551_BUGFIX
26 bool "PMC551 256M DRAM Bugfix"
27 depends on MTD_PMC551
28 help
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.
32
33config MTD_PMC551_DEBUG
34 bool "PMC551 Debugging"
35 depends on MTD_PMC551
36 help
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.
40
41config MTD_MS02NV
42 tristate "DEC MS02-NV NVRAM module support"
43 depends on MTD && MACH_DECSTATION
44 help
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.
49
50config MTD_DATAFLASH
51 tristate "Support for AT45xxx DataFlash"
52 depends on MTD && SPI_MASTER && EXPERIMENTAL
53 help
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.
57
58config MTD_M25P80
59 tristate "Support for M25 SPI Flash"
60 depends on MTD && SPI_MASTER && EXPERIMENTAL
61 help
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.
65
66config MTD_SLRAM
67 tristate "Uncached system RAM"
68 depends on MTD
69 help
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.
73
74config MTD_PHRAM
75 tristate "Physical system RAM"
76 depends on MTD
77 help
78 This is a re-implementation of the slram driver above.
79
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...
83
84config MTD_LART
85 tristate "28F160xx flash driver for LART"
86 depends on SA1100_LART && MTD
87 help
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 (:
91
92config MTD_MTDRAM
93 tristate "Test driver using RAM"
94 depends on MTD
95 help
96 This enables a test MTD device driver which uses vmalloc() to
97 provide storage. You probably want to say 'N' unless you're
98 testing stuff.
99
100config MTDRAM_TOTAL_SIZE
101 int "MTDRAM device size in KiB"
102 depends on MTD_MTDRAM
103 default "4096"
104 help
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
108 loading the module.
109
110config MTDRAM_ERASE_SIZE
111 int "MTDRAM erase block size in KiB"
112 depends on MTD_MTDRAM
113 default "128"
114 help
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
118 loading the module.
119
120#If not a module (I don't want to test it as a module)
121config MTDRAM_ABS_POS
122 hex "SRAM Hexadecimal Absolute position or 0"
123 depends on MTD_MTDRAM=y
124 default "0"
125 help
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.
131
132config MTD_BLKMTD
133 tristate "MTD emulation using block device"
134 depends on MTD
135 help
136 This driver allows a block device to appear as an MTD. It would
137 generally be used in the following cases:
138
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).
143
144config MTD_BLOCK2MTD
145 tristate "MTD using block device (rewrite)"
146 depends on MTD && EXPERIMENTAL
147 help
148 This driver is basically the same at MTD_BLKMTD above, but
149 experienced some interface changes plus serious speedups. In
150 the long term, it should replace MTD_BLKMTD. Right now, you
151 shouldn't entrust important data to it yet.
152
153comment "Disk-On-Chip Device Drivers"
154
155config MTD_DOC2000
156 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
157 depends on MTD
158 select MTD_DOCPROBE
159 select MTD_NAND_IDS
160 ---help---
161 This provides an MTD device driver for the M-Systems DiskOnChip
162 2000 and Millennium devices. Originally designed for the DiskOnChip
163 2000, it also now includes support for the DiskOnChip Millennium.
164 If you have problems with this driver and the DiskOnChip Millennium,
165 you may wish to try the alternative Millennium driver below. To use
166 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
167 in the <file:drivers/mtd/devices/docprobe.c> source code.
168
169 If you use this device, you probably also want to enable the NFTL
170 'NAND Flash Translation Layer' option below, which is used to
171 emulate a block device by using a kind of file system on the flash
172 chips.
173
174 NOTE: This driver is deprecated and will probably be removed soon.
175 Please try the new DiskOnChip driver under "NAND Flash Device
176 Drivers".
177
178config MTD_DOC2001
179 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
180 depends on MTD
181 select MTD_DOCPROBE
182 select MTD_NAND_IDS
183 ---help---
184 This provides an alternative MTD device driver for the M-Systems
185 DiskOnChip Millennium devices. Use this if you have problems with
186 the combined DiskOnChip 2000 and Millennium driver above. To get
187 the DiskOnChip probe code to load and use this driver instead of
188 the other one, you will need to undefine DOC_SINGLE_DRIVER near
189 the beginning of <file:drivers/mtd/devices/docprobe.c>.
190
191 If you use this device, you probably also want to enable the NFTL
192 'NAND Flash Translation Layer' option below, which is used to
193 emulate a block device by using a kind of file system on the flash
194 chips.
195
196 NOTE: This driver is deprecated and will probably be removed soon.
197 Please try the new DiskOnChip driver under "NAND Flash Device
198 Drivers".
199
200config MTD_DOC2001PLUS
201 tristate "M-Systems Disk-On-Chip Millennium Plus"
202 depends on MTD
203 select MTD_DOCPROBE
204 select MTD_NAND_IDS
205 ---help---
206 This provides an MTD device driver for the M-Systems DiskOnChip
207 Millennium Plus devices.
208
209 If you use this device, you probably also want to enable the INFTL
210 'Inverse NAND Flash Translation Layer' option below, which is used
211 to emulate a block device by using a kind of file system on the
212 flash chips.
213
214 NOTE: This driver will soon be replaced by the new DiskOnChip driver
215 under "NAND Flash Device Drivers" (currently that driver does not
216 support all Millennium Plus devices).
217
218config MTD_DOCPROBE
219 tristate
220 select MTD_DOCECC
221 select OBSOLETE_INTERMODULE
222
223config MTD_DOCECC
224 tristate
225
226config MTD_DOCPROBE_ADVANCED
227 bool "Advanced detection options for DiskOnChip"
228 depends on MTD_DOCPROBE
229 help
230 This option allows you to specify nonstandard address at which to
231 probe for a DiskOnChip, or to change the detection options. You
232 are unlikely to need any of this unless you are using LinuxBIOS.
233 Say 'N'.
234
235config MTD_DOCPROBE_ADDRESS
236 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
237 depends on MTD_DOCPROBE
238 default "0x0000" if MTD_DOCPROBE_ADVANCED
239 default "0" if !MTD_DOCPROBE_ADVANCED
240 ---help---
241 By default, the probe for DiskOnChip devices will look for a
242 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
243 This option allows you to specify a single address at which to probe
244 for the device, which is useful if you have other devices in that
245 range which get upset when they are probed.
246
247 (Note that on PowerPC, the normal probe will only check at
248 0xE4000000.)
249
250 Normally, you should leave this set to zero, to allow the probe at
251 the normal addresses.
252
253config MTD_DOCPROBE_HIGH
254 bool "Probe high addresses"
255 depends on MTD_DOCPROBE_ADVANCED
256 help
257 By default, the probe for DiskOnChip devices will look for a
258 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
259 This option changes to make it probe between 0xFFFC8000 and
260 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
261 useful to you. Say 'N'.
262
263config MTD_DOCPROBE_55AA
264 bool "Probe for 0x55 0xAA BIOS Extension Signature"
265 depends on MTD_DOCPROBE_ADVANCED
266 help
267 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
268 continue with probing if it is absent. The signature will always be
269 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
270 Only if you have overwritten the first block of a DiskOnChip
271 Millennium will it be absent. Enable this option if you are using
272 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
273 you have managed to wipe the first block.
274
275endmenu
276