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