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