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