Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | menu "Mapping drivers for chip access" |
2 | depends on MTD!=n | |
9310da0b | 3 | depends on HAS_IOMEM |
1da177e4 LT |
4 | |
5 | config MTD_COMPLEX_MAPPINGS | |
6 | bool "Support non-linear mappings of flash chips" | |
1da177e4 LT |
7 | help |
8 | This causes the chip drivers to allow for complicated | |
9 | paged mappings of flash chips. | |
10 | ||
11 | config MTD_PHYSMAP | |
d8140830 AK |
12 | tristate "Flash device in physical memory map" |
13 | depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR | |
1da177e4 | 14 | help |
79b9cd58 TY |
15 | This provides a 'mapping' driver which allows the NOR Flash and |
16 | ROM driver code to communicate with chips which are mapped | |
17 | physically into the CPU's memory. You will need to configure | |
18 | the physical address and size of the flash chips on your | |
19 | particular board as well as the bus width, either statically | |
1da177e4 LT |
20 | with config options or at run-time. |
21 | ||
41bdf960 MF |
22 | To compile this driver as a module, choose M here: the |
23 | module will be called physmap. | |
24 | ||
dcb3e137 MF |
25 | config MTD_PHYSMAP_COMPAT |
26 | bool "Physmap compat support" | |
27 | depends on MTD_PHYSMAP | |
28 | default n | |
29 | help | |
30 | Setup a simple mapping via the Kconfig options. Normally the | |
31 | physmap configuration options are done via your board's | |
32 | resource file. | |
33 | ||
34 | If unsure, say N here. | |
35 | ||
1da177e4 LT |
36 | config MTD_PHYSMAP_START |
37 | hex "Physical start address of flash mapping" | |
dcb3e137 | 38 | depends on MTD_PHYSMAP_COMPAT |
1da177e4 LT |
39 | default "0x8000000" |
40 | help | |
41 | This is the physical memory location at which the flash chips | |
42 | are mapped on your particular target board. Refer to the | |
43 | memory map which should hopefully be in the documentation for | |
44 | your board. | |
1da177e4 LT |
45 | |
46 | config MTD_PHYSMAP_LEN | |
47 | hex "Physical length of flash mapping" | |
dcb3e137 | 48 | depends on MTD_PHYSMAP_COMPAT |
73566edf | 49 | default "0" |
1da177e4 LT |
50 | help |
51 | This is the total length of the mapping of the flash chips on | |
52 | your particular board. If there is space, or aliases, in the | |
53 | physical memory map between the chips, this could be larger | |
54 | than the total amount of flash present. Refer to the memory | |
55 | map which should hopefully be in the documentation for your | |
56 | board. | |
1da177e4 LT |
57 | |
58 | config MTD_PHYSMAP_BANKWIDTH | |
59 | int "Bank width in octets" | |
dcb3e137 | 60 | depends on MTD_PHYSMAP_COMPAT |
1da177e4 LT |
61 | default "2" |
62 | help | |
63 | This is the total width of the data bus of the flash devices | |
64 | in octets. For example, if you have a data bus width of 32 | |
01dd2fbf | 65 | bits, you would set the bus width octet value to 4. This is |
1da177e4 | 66 | used internally by the CFI drivers. |
1da177e4 | 67 | |
a2c2fe4b | 68 | config MTD_PHYSMAP_OF |
a982ac06 | 69 | tristate "Flash device in physical memory map based on OF description" |
236cdc7b | 70 | depends on OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM) |
a2c2fe4b VW |
71 | help |
72 | This provides a 'mapping' driver which allows the NOR Flash and | |
73 | ROM driver code to communicate with chips which are mapped | |
74 | physically into the CPU's memory. The mapping description here is | |
75 | taken from OF device tree. | |
76 | ||
68aa0fa8 MSJ |
77 | config MTD_PMC_MSP_EVM |
78 | tristate "CFI Flash device mapped on PMC-Sierra MSP" | |
79 | depends on PMC_MSP && MTD_CFI | |
68aa0fa8 | 80 | help |
01dd2fbf ML |
81 | This provides a 'mapping' driver which supports the way |
82 | in which user-programmable flash chips are connected on the | |
83 | PMC-Sierra MSP eval/demo boards. | |
68aa0fa8 MSJ |
84 | |
85 | choice | |
01dd2fbf | 86 | prompt "Maximum mappable memory available for flash IO" |
68aa0fa8 MSJ |
87 | depends on MTD_PMC_MSP_EVM |
88 | default MSP_FLASH_MAP_LIMIT_32M | |
89 | ||
90 | config MSP_FLASH_MAP_LIMIT_32M | |
91 | bool "32M" | |
92 | ||
93 | endchoice | |
94 | ||
95 | config MSP_FLASH_MAP_LIMIT | |
96 | hex | |
97 | default "0x02000000" | |
98 | depends on MSP_FLASH_MAP_LIMIT_32M | |
99 | ||
1da177e4 LT |
100 | config MTD_SUN_UFLASH |
101 | tristate "Sun Microsystems userflash support" | |
e0e5de00 | 102 | depends on SPARC && MTD_CFI && PCI |
1da177e4 | 103 | help |
69f34c98 TG |
104 | This provides a 'mapping' driver which supports the way in |
105 | which user-programmable flash chips are connected on various | |
106 | Sun Microsystems boardsets. This driver will require CFI support | |
1da177e4 LT |
107 | in the kernel, so if you did not enable CFI previously, do that now. |
108 | ||
1da177e4 LT |
109 | config MTD_SC520CDP |
110 | tristate "CFI Flash device mapped on AMD SC520 CDP" | |
e1d6ee72 | 111 | depends on X86 && MTD_CFI |
1da177e4 LT |
112 | help |
113 | The SC520 CDP board has two banks of CFI-compliant chips and one | |
114 | Dual-in-line JEDEC chip. This 'mapping' driver supports that | |
115 | arrangement, implementing three MTD devices. | |
116 | ||
117 | config MTD_NETSC520 | |
118 | tristate "CFI Flash device mapped on AMD NetSc520" | |
6a8a98b2 | 119 | depends on X86 && MTD_CFI |
1da177e4 LT |
120 | help |
121 | This enables access routines for the flash chips on the AMD NetSc520 | |
69f34c98 | 122 | demonstration board. If you have one of these boards and would like |
1da177e4 LT |
123 | to use the flash chips on it, say 'Y'. |
124 | ||
125 | config MTD_TS5500 | |
126 | tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" | |
ef63d004 | 127 | depends on X86 |
01ac742d SY |
128 | select MTD_JEDECPROBE |
129 | select MTD_CFI_AMDSTD | |
1da177e4 LT |
130 | help |
131 | This provides a driver for the on-board flash of the Technologic | |
e27a9960 | 132 | System's TS-5500 board. The 2MB flash is split into 3 partitions |
1da177e4 LT |
133 | which are accessed as separate MTD devices. |
134 | ||
e27a9960 SY |
135 | mtd0 and mtd2 are the two BIOS drives, which use the resident |
136 | flash disk (RFD) flash translation layer. | |
1da177e4 LT |
137 | |
138 | mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. | |
139 | ||
140 | Note that jumper 3 ("Write Enable Drive A") must be set | |
4992a9e8 | 141 | otherwise detection won't succeed. |
1da177e4 LT |
142 | |
143 | config MTD_SBC_GXX | |
144 | tristate "CFI Flash device mapped on Arcom SBC-GXx boards" | |
6a8a98b2 | 145 | depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS |
1da177e4 LT |
146 | help |
147 | This provides a driver for the on-board flash of Arcom Control | |
148 | Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. | |
149 | By default the flash is split into 3 partitions which are accessed | |
150 | as separate MTD devices. This board utilizes Intel StrataFlash. | |
151 | More info at | |
152 | <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>. | |
153 | ||
e644f7d6 TP |
154 | config MTD_PXA2XX |
155 | tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards" | |
156 | depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT | |
cbec19ae | 157 | help |
e644f7d6 | 158 | This provides a driver for the NOR flash attached to a PXA2xx chip. |
cbec19ae | 159 | |
1da177e4 LT |
160 | config MTD_OCTAGON |
161 | tristate "JEDEC Flash device mapped on Octagon 5066 SBC" | |
162 | depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS | |
163 | help | |
164 | This provides a 'mapping' driver which supports the way in which | |
165 | the flash chips are connected in the Octagon-5066 Single Board | |
166 | Computer. More information on the board is available at | |
631dd1a8 | 167 | <http://www.octagonsystems.com/products/5066.aspx>. |
1da177e4 LT |
168 | |
169 | config MTD_VMAX | |
170 | tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301" | |
171 | depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS | |
172 | help | |
173 | This provides a 'mapping' driver which supports the way in which | |
174 | the flash chips are connected in the Tempustech VMAX SBC301 Single | |
175 | Board Computer. More information on the board is available at | |
176 | <http://www.tempustech.com/>. | |
177 | ||
178 | config MTD_SCx200_DOCFLASH | |
179 | tristate "Flash device mapped with DOCCS on NatSemi SCx200" | |
f6c11c18 | 180 | depends on SCx200 && MTD_CFI |
1da177e4 LT |
181 | help |
182 | Enable support for a flash chip mapped using the DOCCS signal on a | |
183 | National Semiconductor SCx200 processor. | |
184 | ||
185 | If you don't know what to do here, say N. | |
186 | ||
187 | If compiled as a module, it will be called scx200_docflash. | |
188 | ||
189 | config MTD_AMD76XROM | |
190 | tristate "BIOS flash chip on AMD76x southbridge" | |
191 | depends on X86 && MTD_JEDECPROBE | |
192 | help | |
193 | Support for treating the BIOS flash chip on AMD76x motherboards | |
194 | as an MTD device - with this you can reprogram your BIOS. | |
195 | ||
196 | BE VERY CAREFUL. | |
197 | ||
198 | config MTD_ICHXROM | |
199 | tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" | |
200 | depends on X86 && MTD_JEDECPROBE | |
201 | help | |
202 | Support for treating the BIOS flash chip on ICHX motherboards | |
203 | as an MTD device - with this you can reprogram your BIOS. | |
204 | ||
205 | BE VERY CAREFUL. | |
206 | ||
29175778 LG |
207 | config MTD_ESB2ROM |
208 | tristate "BIOS flash chip on Intel ESB Controller Hub 2" | |
dffbc42b | 209 | depends on X86 && MTD_JEDECPROBE && PCI |
29175778 LG |
210 | help |
211 | Support for treating the BIOS flash chip on ESB2 motherboards | |
212 | as an MTD device - with this you can reprogram your BIOS. | |
213 | ||
214 | BE VERY CAREFUL. | |
215 | ||
90afffc8 DO |
216 | config MTD_CK804XROM |
217 | tristate "BIOS flash chip on Nvidia CK804" | |
862c93b9 | 218 | depends on X86 && MTD_JEDECPROBE && PCI |
90afffc8 DO |
219 | help |
220 | Support for treating the BIOS flash chip on nvidia motherboards | |
221 | as an MTD device - with this you can reprogram your BIOS. | |
222 | ||
223 | BE VERY CAREFUL. | |
224 | ||
1da177e4 LT |
225 | config MTD_SCB2_FLASH |
226 | tristate "BIOS flash chip on Intel SCB2 boards" | |
227 | depends on X86 && MTD_JEDECPROBE | |
228 | help | |
229 | Support for treating the BIOS flash chip on Intel SCB2 boards | |
230 | as an MTD device - with this you can reprogram your BIOS. | |
231 | ||
232 | BE VERY CAREFUL. | |
233 | ||
234 | config MTD_TSUNAMI | |
235 | tristate "Flash chips on Tsunami TIG bus" | |
236 | depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS | |
237 | help | |
238 | Support for the flash chip on Tsunami TIG bus. | |
239 | ||
1da177e4 LT |
240 | config MTD_NETtel |
241 | tristate "CFI flash device on SnapGear/SecureEdge" | |
6a8a98b2 | 242 | depends on X86 && MTD_JEDECPROBE |
1da177e4 LT |
243 | help |
244 | Support for flash chips on NETtel/SecureEdge/SnapGear boards. | |
245 | ||
3c544739 JC |
246 | config MTD_LANTIQ |
247 | tristate "Lantiq SoC NOR support" | |
248 | depends on LANTIQ | |
3c544739 JC |
249 | help |
250 | Support for NOR flash attached to the Lantiq SoC's External Bus Unit. | |
251 | ||
1da177e4 LT |
252 | config MTD_DILNETPC |
253 | tristate "CFI Flash device mapped on DIL/Net PC" | |
6a8a98b2 | 254 | depends on X86 && MTD_CFI_INTELEXT && BROKEN |
1da177e4 LT |
255 | help |
256 | MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP". | |
257 | For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm> | |
258 | and <http://www.ssv-embedded.de/ssv/pc104/p170.htm> | |
259 | ||
260 | config MTD_DILNETPC_BOOTSIZE | |
261 | hex "Size of DIL/Net PC flash boot partition" | |
262 | depends on MTD_DILNETPC | |
263 | default "0x80000" | |
264 | help | |
265 | The amount of space taken up by the kernel or Etherboot | |
266 | on the DIL/Net PC flash chips. | |
267 | ||
268 | config MTD_L440GX | |
269 | tristate "BIOS flash chip on Intel L440GX boards" | |
270 | depends on X86 && MTD_JEDECPROBE | |
271 | help | |
272 | Support for treating the BIOS flash chip on Intel L440GX motherboards | |
273 | as an MTD device - with this you can reprogram your BIOS. | |
274 | ||
275 | BE VERY CAREFUL. | |
276 | ||
1da177e4 LT |
277 | config MTD_TQM8XXL |
278 | tristate "CFI Flash device mapped on TQM8XXL" | |
01ac742d | 279 | depends on MTD_CFI && TQM8xxL |
1da177e4 LT |
280 | help |
281 | The TQM8xxL PowerPC board has up to two banks of CFI-compliant | |
282 | chips, currently uses AMD one. This 'mapping' driver supports | |
283 | that arrangement, allowing the CFI probe and command set driver | |
284 | code to communicate with the chips on the TQM8xxL board. More at | |
631dd1a8 | 285 | <http://www.denx.de/wiki/PPCEmbedded/>. |
1da177e4 LT |
286 | |
287 | config MTD_RPXLITE | |
288 | tristate "CFI Flash device mapped on RPX Lite or CLLF" | |
01ac742d | 289 | depends on MTD_CFI && (RPXCLASSIC || RPXLITE) |
1da177e4 LT |
290 | help |
291 | The RPXLite PowerPC board has CFI-compliant chips mapped in | |
292 | a strange sparse mapping. This 'mapping' driver supports that | |
293 | arrangement, allowing the CFI probe and command set driver code | |
294 | to communicate with the chips on the RPXLite board. More at | |
295 | <http://www.embeddedplanet.com/>. | |
296 | ||
297 | config MTD_MBX860 | |
298 | tristate "System flash on MBX860 board" | |
01ac742d | 299 | depends on MTD_CFI && MBX |
1da177e4 LT |
300 | help |
301 | This enables access routines for the flash chips on the Motorola | |
302 | MBX860 board. If you have one of these boards and would like | |
303 | to use the flash chips on it, say 'Y'. | |
304 | ||
305 | config MTD_DBOX2 | |
306 | tristate "CFI Flash device mapped on D-Box2" | |
01ac742d | 307 | depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD |
1da177e4 LT |
308 | help |
309 | This enables access routines for the flash chips on the Nokia/Sagem | |
310 | D-Box 2 board. If you have one of these boards and would like to use | |
311 | the flash chips on it, say 'Y'. | |
312 | ||
313 | config MTD_CFI_FLAGADM | |
314 | tristate "CFI Flash device mapping on FlagaDM" | |
01ac742d | 315 | depends on 8xx && MTD_CFI |
1da177e4 LT |
316 | help |
317 | Mapping for the Flaga digital module. If you don't have one, ignore | |
318 | this setting. | |
319 | ||
1da177e4 LT |
320 | config MTD_SOLUTIONENGINE |
321 | tristate "CFI Flash device mapped on Hitachi SolutionEngine" | |
e35e283f | 322 | depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS |
1da177e4 LT |
323 | help |
324 | This enables access to the flash chips on the Hitachi SolutionEngine and | |
325 | similar boards. Say 'Y' if you are building a kernel for such a board. | |
326 | ||
1da177e4 LT |
327 | config MTD_CDB89712 |
328 | tristate "Cirrus CDB89712 evaluation board mappings" | |
01ac742d | 329 | depends on MTD_CFI && ARCH_CDB89712 |
1da177e4 LT |
330 | help |
331 | This enables access to the flash or ROM chips on the CDB89712 board. | |
332 | If you have such a board, say 'Y'. | |
333 | ||
334 | config MTD_SA1100 | |
335 | tristate "CFI Flash device mapped on StrongARM SA11x0" | |
2fe2e24e | 336 | depends on MTD_CFI && ARCH_SA1100 |
1da177e4 LT |
337 | help |
338 | This enables access to the flash chips on most platforms based on | |
339 | the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. | |
340 | If you have such a board, say 'Y'. | |
341 | ||
1da177e4 LT |
342 | config MTD_DC21285 |
343 | tristate "CFI Flash device mapped on DC21285 Footbridge" | |
01ac742d | 344 | depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS |
1da177e4 LT |
345 | help |
346 | This provides a driver for the flash accessed using Intel's | |
347 | 21285 bridge used with Intel's StrongARM processors. More info at | |
348 | <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. | |
349 | ||
1da177e4 LT |
350 | config MTD_IXP4XX |
351 | tristate "CFI Flash device mapped on Intel IXP4xx based systems" | |
01ac742d | 352 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX |
1da177e4 | 353 | help |
69f34c98 | 354 | This enables MTD access to flash devices on platforms based |
1da177e4 LT |
355 | on Intel's IXP4xx family of network processors such as the |
356 | IXDP425 and Coyote. If you have an IXP4xx based board and | |
357 | would like to use the flash chips on it, say 'Y'. | |
358 | ||
359 | config MTD_IXP2000 | |
360 | tristate "CFI Flash device mapped on Intel IXP2000 based systems" | |
01ac742d | 361 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 |
1da177e4 | 362 | help |
69f34c98 | 363 | This enables MTD access to flash devices on platforms based |
86185af9 KH |
364 | on Intel's IXP2000 family of network processors. If you have an |
365 | IXP2000 based board and would like to use the flash chips on it, | |
366 | say 'Y'. | |
1da177e4 | 367 | |
1da177e4 LT |
368 | config MTD_FORTUNET |
369 | tristate "CFI Flash device mapped on the FortuNet board" | |
6a8a98b2 | 370 | depends on MTD_CFI && SA1100_FORTUNET |
1da177e4 LT |
371 | help |
372 | This enables access to the Flash on the FortuNet board. If you | |
373 | have such a board, say 'Y'. | |
374 | ||
375 | config MTD_AUTCPU12 | |
376 | tristate "NV-RAM mapping AUTCPU12 board" | |
01ac742d | 377 | depends on ARCH_AUTCPU12 |
1da177e4 LT |
378 | help |
379 | This enables access to the NV-RAM on autronix autcpu12 board. | |
380 | If you have such a board, say 'Y'. | |
381 | ||
1da177e4 LT |
382 | config MTD_IMPA7 |
383 | tristate "JEDEC Flash device mapped on impA7" | |
384 | depends on ARM && MTD_JEDECPROBE | |
385 | help | |
386 | This enables access to the NOR Flash on the impA7 board of | |
387 | implementa GmbH. If you have such a board, say 'Y' here. | |
388 | ||
1da177e4 LT |
389 | config MTD_H720X |
390 | tristate "Hynix evaluation board mappings" | |
01ac742d | 391 | depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 ) |
1da177e4 LT |
392 | help |
393 | This enables access to the flash chips on the Hynix evaluation boards. | |
394 | If you have such a board, say 'Y'. | |
395 | ||
1da177e4 LT |
396 | # This needs CFI or JEDEC, depending on the cards found. |
397 | config MTD_PCI | |
398 | tristate "PCI MTD driver" | |
ec98c681 | 399 | depends on PCI && MTD_COMPLEX_MAPPINGS |
1da177e4 LT |
400 | help |
401 | Mapping for accessing flash devices on add-in cards like the Intel XScale | |
402 | IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode | |
403 | (please see the manual for the link settings). | |
404 | ||
405 | If you are not sure, say N. | |
406 | ||
407 | config MTD_PCMCIA | |
408 | tristate "PCMCIA MTD driver" | |
f6763c98 | 409 | depends on PCMCIA && MTD_COMPLEX_MAPPINGS |
1da177e4 LT |
410 | help |
411 | Map driver for accessing PCMCIA linear flash memory cards. These | |
412 | cards are usually around 4-16MiB in size. This does not include | |
413 | Compact Flash cards which are treated as IDE devices. | |
414 | ||
11d28a30 DB |
415 | config MTD_PCMCIA_ANONYMOUS |
416 | bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards" | |
417 | depends on MTD_PCMCIA | |
11d28a30 DB |
418 | help |
419 | If this option is enabled, PCMCIA cards which do not report | |
420 | anything about themselves are assumed to be MTD cards. | |
421 | ||
422 | If unsure, say N. | |
423 | ||
2e3c22f5 MF |
424 | config MTD_BFIN_ASYNC |
425 | tristate "Blackfin BF533-STAMP Flash Chip Support" | |
ab00d682 | 426 | depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS |
2e3c22f5 MF |
427 | default y |
428 | help | |
429 | Map driver which allows for simultaneous utilization of | |
430 | ethernet and CFI parallel flash. | |
431 | ||
432 | If compiled as a module, it will be called bfin-async-flash. | |
433 | ||
d79c326c MF |
434 | config MTD_GPIO_ADDR |
435 | tristate "GPIO-assisted Flash Chip Support" | |
de19d02b | 436 | depends on GENERIC_GPIO || GPIOLIB |
d79c326c | 437 | depends on MTD_COMPLEX_MAPPINGS |
d79c326c MF |
438 | help |
439 | Map driver which allows flashes to be partially physically addressed | |
440 | and assisted by GPIOs. | |
441 | ||
442 | If compiled as a module, it will be called gpio-addr-flash. | |
443 | ||
1da177e4 | 444 | config MTD_UCLINUX |
6ae392cc | 445 | bool "Generic uClinux RAM/ROM filesystem support" |
5e7e9686 | 446 | depends on MTD_RAM=y && !MMU |
1da177e4 LT |
447 | help |
448 | Map driver to support image based filesystems for uClinux. | |
449 | ||
450 | config MTD_WRSBC8260 | |
451 | tristate "Map driver for WindRiver PowerQUICC II MPC82xx board" | |
452 | depends on (SBC82xx || SBC8560) | |
1da177e4 LT |
453 | select MTD_MAP_BANK_WIDTH_4 |
454 | select MTD_MAP_BANK_WIDTH_1 | |
455 | select MTD_CFI_I1 | |
456 | select MTD_CFI_I4 | |
457 | help | |
458 | Map driver for WindRiver PowerQUICC II MPC82xx board. Drives | |
459 | all three flash regions on CS0, CS1 and CS6 if they are configured | |
460 | correctly by the boot loader. | |
461 | ||
462 | config MTD_DMV182 | |
463 | tristate "Map driver for Dy-4 SVME/DMV-182 board." | |
464 | depends on DMV182 | |
1da177e4 LT |
465 | select MTD_MAP_BANK_WIDTH_32 |
466 | select MTD_CFI_I8 | |
467 | select MTD_CFI_AMDSTD | |
468 | help | |
469 | Map driver for Dy-4 SVME/DMV-182 board. | |
470 | ||
0bac5111 DW |
471 | config MTD_INTEL_VR_NOR |
472 | tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0" | |
473 | depends on PCI | |
474 | help | |
475 | Map driver for a NOR flash bank located on the Expansion Bus of the | |
476 | Intel Vermilion Range chipset. | |
477 | ||
610f75e7 AN |
478 | config MTD_RBTX4939 |
479 | tristate "Map driver for RBTX4939 board" | |
480 | depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS | |
481 | help | |
482 | Map driver for NOR flash chips on RBTX4939 board. | |
483 | ||
99f2a8ae | 484 | config MTD_PLATRAM |
3c45e00a | 485 | tristate "Map driver for platform device RAM (mtd-ram)" |
99f2a8ae BD |
486 | select MTD_RAM |
487 | help | |
488 | Map driver for RAM areas described via the platform device | |
489 | system. | |
490 | ||
491 | This selection automatically selects the map_ram driver. | |
492 | ||
47a72688 AM |
493 | config MTD_VMU |
494 | tristate "Map driver for Dreamcast VMU" | |
495 | depends on MAPLE | |
496 | help | |
497 | This driver enables access to the Dreamcast Visual Memory Unit (VMU). | |
498 | ||
499 | Most Dreamcast users will want to say Y here. | |
1da177e4 | 500 | |
47a72688 AM |
501 | To build this as a module select M here, the module will be called |
502 | vmu-flash. | |
503 | ||
f6a8c609 RKAL |
504 | config MTD_PISMO |
505 | tristate "MTD discovery driver for PISMO modules" | |
506 | depends on I2C | |
507 | depends on ARCH_VERSATILE | |
508 | help | |
509 | This driver allows for discovery of PISMO modules - see | |
510 | <http://www.pismoworld.org/>. These are small modules containing | |
511 | up to five memory devices (eg, SRAM, flash, DOC) described by an | |
512 | I2C EEPROM. | |
513 | ||
514 | This driver does not create any MTD maps itself; instead it | |
515 | creates MTD physmap and MTD SRAM platform devices. If you | |
516 | enable this option, you should consider enabling MTD_PHYSMAP | |
517 | and/or MTD_PLATRAM according to the devices on your module. | |
518 | ||
519 | When built as a module, it will be called pismo.ko | |
520 | ||
dcfb81d6 DG |
521 | config MTD_LATCH_ADDR |
522 | tristate "Latch-assisted Flash Chip Support" | |
523 | depends on MTD_COMPLEX_MAPPINGS | |
524 | help | |
525 | Map driver which allows flashes to be partially physically addressed | |
526 | and have the upper address lines set by a board specific code. | |
527 | ||
528 | If compiled as a module, it will be called latch-addr-flash. | |
529 | ||
47a72688 | 530 | endmenu |