]>
Commit | Line | Data |
---|---|---|
1da177e4 | 1 | # drivers/mtd/maps/Kconfig |
e5580fbe | 2 | # $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $ |
1da177e4 LT |
3 | |
4 | menu "Self-contained MTD device drivers" | |
5 | depends on MTD!=n | |
6 | ||
7 | config 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 | ||
25 | config 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 | ||
33 | config 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 | ||
41 | config 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 | ||
be21ce11 MM |
50 | If you want to compile this driver as a module ( = code which can be |
51 | inserted in and removed from the running kernel whenever you want), | |
52 | say M here and read <file:Documentation/modules.txt>. The module will | |
53 | be called ms02-nv.o. | |
54 | ||
1d6432fe DB |
55 | config MTD_DATAFLASH |
56 | tristate "Support for AT45xxx DataFlash" | |
57 | depends on MTD && SPI_MASTER && EXPERIMENTAL | |
58 | help | |
59 | This enables access to AT45xxx DataFlash chips, using SPI. | |
60 | Sometimes DataFlash chips are packaged inside MMC-format | |
61 | cards; at this writing, the MMC stack won't handle those. | |
62 | ||
2f9f7628 ML |
63 | config MTD_M25P80 |
64 | tristate "Support for M25 SPI Flash" | |
65 | depends on MTD && SPI_MASTER && EXPERIMENTAL | |
66 | help | |
67 | This enables access to ST M25P80 and similar SPI flash chips, | |
68 | used for program and data storage. Set up your spi devices | |
69 | with the right board-specific platform data. | |
70 | ||
1da177e4 LT |
71 | config MTD_SLRAM |
72 | tristate "Uncached system RAM" | |
73 | depends on MTD | |
74 | help | |
75 | If your CPU cannot cache all of the physical memory in your machine, | |
76 | you can still use it for storage or swap by using this driver to | |
77 | present it to the system as a Memory Technology Device. | |
78 | ||
79 | config MTD_PHRAM | |
80 | tristate "Physical system RAM" | |
81 | depends on MTD | |
82 | help | |
83 | This is a re-implementation of the slram driver above. | |
84 | ||
85 | Use this driver to access physical memory that the kernel proper | |
86 | doesn't have access to, memory beyond the mem=xxx limit, nvram, | |
87 | memory on the video card, etc... | |
88 | ||
89 | config MTD_LART | |
90 | tristate "28F160xx flash driver for LART" | |
91 | depends on SA1100_LART && MTD | |
92 | help | |
93 | This enables the flash driver for LART. Please note that you do | |
94 | not need any mapping/chip driver for LART. This one does it all | |
95 | for you, so go disable all of those if you enabled some of them (: | |
96 | ||
97 | config MTD_MTDRAM | |
98 | tristate "Test driver using RAM" | |
99 | depends on MTD | |
100 | help | |
101 | This enables a test MTD device driver which uses vmalloc() to | |
102 | provide storage. You probably want to say 'N' unless you're | |
103 | testing stuff. | |
104 | ||
105 | config MTDRAM_TOTAL_SIZE | |
106 | int "MTDRAM device size in KiB" | |
107 | depends on MTD_MTDRAM | |
108 | default "4096" | |
109 | help | |
110 | This allows you to configure the total size of the MTD device | |
111 | emulated by the MTDRAM driver. If the MTDRAM driver is built | |
112 | as a module, it is also possible to specify this as a parameter when | |
113 | loading the module. | |
114 | ||
115 | config MTDRAM_ERASE_SIZE | |
116 | int "MTDRAM erase block size in KiB" | |
117 | depends on MTD_MTDRAM | |
118 | default "128" | |
119 | help | |
120 | This allows you to configure the size of the erase blocks in the | |
121 | device emulated by the MTDRAM driver. If the MTDRAM driver is built | |
122 | as a module, it is also possible to specify this as a parameter when | |
123 | loading the module. | |
124 | ||
125 | #If not a module (I don't want to test it as a module) | |
126 | config MTDRAM_ABS_POS | |
127 | hex "SRAM Hexadecimal Absolute position or 0" | |
128 | depends on MTD_MTDRAM=y | |
129 | default "0" | |
130 | help | |
131 | If you have system RAM accessible by the CPU but not used by Linux | |
132 | in normal operation, you can give the physical address at which the | |
133 | available RAM starts, and the MTDRAM driver will use it instead of | |
e5580fbe | 134 | allocating space from Linux's available memory. Otherwise, leave |
1da177e4 LT |
135 | this set to zero. Most people will want to leave this as zero. |
136 | ||
acc8dadc JE |
137 | config MTD_BLOCK2MTD |
138 | tristate "MTD using block device" | |
9361401e | 139 | depends on MTD && BLOCK |
1da177e4 LT |
140 | help |
141 | This driver allows a block device to appear as an MTD. It would | |
142 | generally be used in the following cases: | |
143 | ||
144 | Using Compact Flash as an MTD, these usually present themselves to | |
145 | the system as an ATA drive. | |
146 | Testing MTD users (eg JFFS2) on large media and media that might | |
147 | be removed during a write (using the floppy drive). | |
148 | ||
1da177e4 LT |
149 | comment "Disk-On-Chip Device Drivers" |
150 | ||
151 | config MTD_DOC2000 | |
152 | tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)" | |
153 | depends on MTD | |
154 | select MTD_DOCPROBE | |
155 | select MTD_NAND_IDS | |
156 | ---help--- | |
157 | This provides an MTD device driver for the M-Systems DiskOnChip | |
158 | 2000 and Millennium devices. Originally designed for the DiskOnChip | |
159 | 2000, it also now includes support for the DiskOnChip Millennium. | |
160 | If you have problems with this driver and the DiskOnChip Millennium, | |
161 | you may wish to try the alternative Millennium driver below. To use | |
162 | the alternative driver, you will need to undefine DOC_SINGLE_DRIVER | |
163 | in the <file:drivers/mtd/devices/docprobe.c> source code. | |
164 | ||
165 | If you use this device, you probably also want to enable the NFTL | |
166 | 'NAND Flash Translation Layer' option below, which is used to | |
167 | emulate a block device by using a kind of file system on the flash | |
168 | chips. | |
169 | ||
170 | NOTE: This driver is deprecated and will probably be removed soon. | |
171 | Please try the new DiskOnChip driver under "NAND Flash Device | |
172 | Drivers". | |
173 | ||
174 | config MTD_DOC2001 | |
175 | tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)" | |
176 | depends on MTD | |
177 | select MTD_DOCPROBE | |
178 | select MTD_NAND_IDS | |
179 | ---help--- | |
e5580fbe | 180 | This provides an alternative MTD device driver for the M-Systems |
1da177e4 LT |
181 | DiskOnChip Millennium devices. Use this if you have problems with |
182 | the combined DiskOnChip 2000 and Millennium driver above. To get | |
183 | the DiskOnChip probe code to load and use this driver instead of | |
184 | the other one, you will need to undefine DOC_SINGLE_DRIVER near | |
185 | the beginning of <file:drivers/mtd/devices/docprobe.c>. | |
186 | ||
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 | |
190 | chips. | |
191 | ||
192 | NOTE: This driver is deprecated and will probably be removed soon. | |
193 | Please try the new DiskOnChip driver under "NAND Flash Device | |
194 | Drivers". | |
195 | ||
196 | config MTD_DOC2001PLUS | |
197 | tristate "M-Systems Disk-On-Chip Millennium Plus" | |
198 | depends on MTD | |
199 | select MTD_DOCPROBE | |
200 | select MTD_NAND_IDS | |
201 | ---help--- | |
202 | This provides an MTD device driver for the M-Systems DiskOnChip | |
203 | Millennium Plus devices. | |
204 | ||
205 | If you use this device, you probably also want to enable the INFTL | |
206 | 'Inverse NAND Flash Translation Layer' option below, which is used | |
e5580fbe | 207 | to emulate a block device by using a kind of file system on the |
1da177e4 LT |
208 | flash chips. |
209 | ||
210 | NOTE: This driver will soon be replaced by the new DiskOnChip driver | |
211 | under "NAND Flash Device Drivers" (currently that driver does not | |
212 | support all Millennium Plus devices). | |
213 | ||
214 | config MTD_DOCPROBE | |
215 | tristate | |
216 | select MTD_DOCECC | |
217 | ||
218 | config MTD_DOCECC | |
219 | tristate | |
220 | ||
221 | config MTD_DOCPROBE_ADVANCED | |
222 | bool "Advanced detection options for DiskOnChip" | |
223 | depends on MTD_DOCPROBE | |
224 | help | |
225 | This option allows you to specify nonstandard address at which to | |
226 | probe for a DiskOnChip, or to change the detection options. You | |
227 | are unlikely to need any of this unless you are using LinuxBIOS. | |
228 | Say 'N'. | |
229 | ||
230 | config MTD_DOCPROBE_ADDRESS | |
231 | hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED | |
232 | depends on MTD_DOCPROBE | |
233 | default "0x0000" if MTD_DOCPROBE_ADVANCED | |
234 | default "0" if !MTD_DOCPROBE_ADVANCED | |
235 | ---help--- | |
236 | By default, the probe for DiskOnChip devices will look for a | |
237 | DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. | |
238 | This option allows you to specify a single address at which to probe | |
239 | for the device, which is useful if you have other devices in that | |
240 | range which get upset when they are probed. | |
241 | ||
242 | (Note that on PowerPC, the normal probe will only check at | |
243 | 0xE4000000.) | |
244 | ||
245 | Normally, you should leave this set to zero, to allow the probe at | |
246 | the normal addresses. | |
247 | ||
248 | config MTD_DOCPROBE_HIGH | |
249 | bool "Probe high addresses" | |
250 | depends on MTD_DOCPROBE_ADVANCED | |
251 | help | |
252 | By default, the probe for DiskOnChip devices will look for a | |
253 | DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. | |
254 | This option changes to make it probe between 0xFFFC8000 and | |
255 | 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be | |
256 | useful to you. Say 'N'. | |
257 | ||
258 | config MTD_DOCPROBE_55AA | |
259 | bool "Probe for 0x55 0xAA BIOS Extension Signature" | |
260 | depends on MTD_DOCPROBE_ADVANCED | |
261 | help | |
262 | Check for the 0x55 0xAA signature of a DiskOnChip, and do not | |
263 | continue with probing if it is absent. The signature will always be | |
264 | present for a DiskOnChip 2000 or a normal DiskOnChip Millennium. | |
265 | Only if you have overwritten the first block of a DiskOnChip | |
266 | Millennium will it be absent. Enable this option if you are using | |
267 | LinuxBIOS or if you need to recover a DiskOnChip Millennium on which | |
268 | you have managed to wipe the first block. | |
269 | ||
270 | endmenu | |
271 |