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" | |
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" | |
79b9cd58 | 16 | depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM |
1da177e4 | 17 | help |
79b9cd58 TY |
18 | This provides a 'mapping' driver which allows the NOR Flash and |
19 | ROM driver code to communicate with chips which are mapped | |
20 | physically into the CPU's memory. You will need to configure | |
21 | the physical address and size of the flash chips on your | |
22 | particular board as well as the bus width, either statically | |
1da177e4 LT |
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 | |
73566edf | 40 | default "0" |
1da177e4 LT |
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" | |
0b57ee9e | 65 | depends on SPARC && MTD_CFI |
1da177e4 | 66 | help |
69f34c98 TG |
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 | |
1da177e4 LT |
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" | |
fbbc21c6 | 81 | depends on X86 && MTD_CFI && MTD_CONCAT |
1da177e4 LT |
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 | |
69f34c98 | 92 | demonstration board. If you have one of these boards and would like |
1da177e4 LT |
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" | |
ef63d004 | 97 | depends on X86 |
01ac742d SY |
98 | select MTD_PARTITIONS |
99 | select MTD_JEDECPROBE | |
100 | select MTD_CFI_AMDSTD | |
1da177e4 LT |
101 | help |
102 | This provides a driver for the on-board flash of the Technologic | |
e27a9960 | 103 | System's TS-5500 board. The 2MB flash is split into 3 partitions |
1da177e4 LT |
104 | which are accessed as separate MTD devices. |
105 | ||
e27a9960 SY |
106 | mtd0 and mtd2 are the two BIOS drives, which use the resident |
107 | flash disk (RFD) flash translation layer. | |
1da177e4 LT |
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 | |
4992a9e8 | 112 | otherwise detection won't succeed. |
1da177e4 LT |
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 | ||
cbec19ae NP |
132 | config MTD_MAINSTONE |
133 | tristate "CFI Flash device mapped on Intel Mainstone XScale eval board" | |
134 | depends on MACH_MAINSTONE && MTD_CFI_INTELEXT | |
135 | select MTD_PARTITIONS | |
136 | help | |
137 | This provides a driver for the on-board flash of the Intel | |
138 | 'Mainstone PXA27x evaluation board. | |
139 | ||
1da177e4 LT |
140 | config MTD_OCTAGON |
141 | tristate "JEDEC Flash device mapped on Octagon 5066 SBC" | |
142 | depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS | |
143 | help | |
144 | This provides a 'mapping' driver which supports the way in which | |
145 | the flash chips are connected in the Octagon-5066 Single Board | |
146 | Computer. More information on the board is available at | |
147 | <http://www.octagonsystems.com/CPUpages/5066.html>. | |
148 | ||
149 | config MTD_VMAX | |
150 | tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301" | |
151 | depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS | |
152 | help | |
153 | This provides a 'mapping' driver which supports the way in which | |
154 | the flash chips are connected in the Tempustech VMAX SBC301 Single | |
155 | Board Computer. More information on the board is available at | |
156 | <http://www.tempustech.com/>. | |
157 | ||
158 | config MTD_SCx200_DOCFLASH | |
159 | tristate "Flash device mapped with DOCCS on NatSemi SCx200" | |
160 | depends on SCx200 && MTD_CFI && MTD_PARTITIONS | |
161 | help | |
162 | Enable support for a flash chip mapped using the DOCCS signal on a | |
163 | National Semiconductor SCx200 processor. | |
164 | ||
165 | If you don't know what to do here, say N. | |
166 | ||
167 | If compiled as a module, it will be called scx200_docflash. | |
168 | ||
169 | config MTD_AMD76XROM | |
170 | tristate "BIOS flash chip on AMD76x southbridge" | |
171 | depends on X86 && MTD_JEDECPROBE | |
172 | help | |
173 | Support for treating the BIOS flash chip on AMD76x motherboards | |
174 | as an MTD device - with this you can reprogram your BIOS. | |
175 | ||
176 | BE VERY CAREFUL. | |
177 | ||
178 | config MTD_ICHXROM | |
179 | tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" | |
180 | depends on X86 && MTD_JEDECPROBE | |
181 | help | |
182 | Support for treating the BIOS flash chip on ICHX motherboards | |
183 | as an MTD device - with this you can reprogram your BIOS. | |
184 | ||
185 | BE VERY CAREFUL. | |
186 | ||
29175778 LG |
187 | config MTD_ESB2ROM |
188 | tristate "BIOS flash chip on Intel ESB Controller Hub 2" | |
189 | depends on X86 && MTD_JEDECPROBE | |
190 | help | |
191 | Support for treating the BIOS flash chip on ESB2 motherboards | |
192 | as an MTD device - with this you can reprogram your BIOS. | |
193 | ||
194 | BE VERY CAREFUL. | |
195 | ||
90afffc8 DO |
196 | config MTD_CK804XROM |
197 | tristate "BIOS flash chip on Nvidia CK804" | |
198 | depends on X86 && MTD_JEDECPROBE | |
199 | help | |
200 | Support for treating the BIOS flash chip on nvidia motherboards | |
201 | as an MTD device - with this you can reprogram your BIOS. | |
202 | ||
203 | BE VERY CAREFUL. | |
204 | ||
1da177e4 LT |
205 | config MTD_SCB2_FLASH |
206 | tristate "BIOS flash chip on Intel SCB2 boards" | |
207 | depends on X86 && MTD_JEDECPROBE | |
208 | help | |
209 | Support for treating the BIOS flash chip on Intel SCB2 boards | |
210 | as an MTD device - with this you can reprogram your BIOS. | |
211 | ||
212 | BE VERY CAREFUL. | |
213 | ||
214 | config MTD_TSUNAMI | |
215 | tristate "Flash chips on Tsunami TIG bus" | |
216 | depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS | |
217 | help | |
218 | Support for the flash chip on Tsunami TIG bus. | |
219 | ||
220 | config MTD_LASAT | |
ceb31db1 MM |
221 | tristate "LASAT flash device" |
222 | depends on LASAT && MTD_CFI | |
1da177e4 LT |
223 | help |
224 | Support for the flash chips on the Lasat 100 and 200 boards. | |
225 | ||
226 | config MTD_NETtel | |
227 | tristate "CFI flash device on SnapGear/SecureEdge" | |
228 | depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE | |
229 | help | |
230 | Support for flash chips on NETtel/SecureEdge/SnapGear boards. | |
231 | ||
002fa301 | 232 | config MTD_ALCHEMY |
e55a3e8a | 233 | tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support" |
01ac742d | 234 | depends on SOC_AU1X00 |
1da177e4 | 235 | help |
002fa301 | 236 | Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards |
1da177e4 | 237 | |
b523b3ba JE |
238 | config MTD_MTX1 |
239 | tristate "4G Systems MTX-1 Flash device" | |
240 | depends on MIPS && MIPS_MTX1 | |
241 | help | |
242 | Flash memory access on 4G Systems MTX-1 Board. If you have one of | |
243 | these boards and would like to use the flash chips on it, say 'Y'. | |
244 | ||
1da177e4 LT |
245 | config MTD_DILNETPC |
246 | tristate "CFI Flash device mapped on DIL/Net PC" | |
247 | depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT | |
248 | help | |
249 | MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP". | |
250 | For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm> | |
251 | and <http://www.ssv-embedded.de/ssv/pc104/p170.htm> | |
252 | ||
253 | config MTD_DILNETPC_BOOTSIZE | |
254 | hex "Size of DIL/Net PC flash boot partition" | |
255 | depends on MTD_DILNETPC | |
256 | default "0x80000" | |
257 | help | |
258 | The amount of space taken up by the kernel or Etherboot | |
259 | on the DIL/Net PC flash chips. | |
260 | ||
261 | config MTD_L440GX | |
262 | tristate "BIOS flash chip on Intel L440GX boards" | |
263 | depends on X86 && MTD_JEDECPROBE | |
264 | help | |
265 | Support for treating the BIOS flash chip on Intel L440GX motherboards | |
266 | as an MTD device - with this you can reprogram your BIOS. | |
267 | ||
268 | BE VERY CAREFUL. | |
269 | ||
270 | config MTD_SBC8240 | |
271 | tristate "Flash device on SBC8240" | |
01ac742d | 272 | depends on MTD_JEDECPROBE && 8260 |
1da177e4 LT |
273 | help |
274 | Flash access on the SBC8240 board from Wind River. See | |
275 | <http://www.windriver.com/products/sbc8240/> | |
276 | ||
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 | |
285 | <http://www.denx.de/embedded-ppc-en.html>. | |
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 | ||
320 | config MTD_BEECH | |
321 | tristate "CFI Flash device mapped on IBM 405LP Beech" | |
01ac742d | 322 | depends on MTD_CFI && BEECH |
1da177e4 LT |
323 | help |
324 | This enables access routines for the flash chips on the IBM | |
325 | 405LP Beech board. If you have one of these boards and would like | |
326 | to use the flash chips on it, say 'Y'. | |
327 | ||
328 | config MTD_ARCTIC | |
329 | tristate "CFI Flash device mapped on IBM 405LP Arctic" | |
01ac742d | 330 | depends on MTD_CFI && ARCTIC2 |
1da177e4 LT |
331 | help |
332 | This enables access routines for the flash chips on the IBM 405LP | |
333 | Arctic board. If you have one of these boards and would like to | |
334 | use the flash chips on it, say 'Y'. | |
335 | ||
336 | config MTD_WALNUT | |
337 | tristate "Flash device mapped on IBM 405GP Walnut" | |
01ac742d | 338 | depends on MTD_JEDECPROBE && WALNUT |
1da177e4 LT |
339 | help |
340 | This enables access routines for the flash chips on the IBM 405GP | |
341 | Walnut board. If you have one of these boards and would like to | |
342 | use the flash chips on it, say 'Y'. | |
343 | ||
344 | config MTD_EBONY | |
345 | tristate "Flash devices mapped on IBM 440GP Ebony" | |
01ac742d | 346 | depends on MTD_JEDECPROBE && EBONY |
1da177e4 LT |
347 | help |
348 | This enables access routines for the flash chips on the IBM 440GP | |
349 | Ebony board. If you have one of these boards and would like to | |
350 | use the flash chips on it, say 'Y'. | |
351 | ||
352 | config MTD_OCOTEA | |
353 | tristate "Flash devices mapped on IBM 440GX Ocotea" | |
01ac742d | 354 | depends on MTD_CFI && OCOTEA |
1da177e4 LT |
355 | help |
356 | This enables access routines for the flash chips on the IBM 440GX | |
357 | Ocotea board. If you have one of these boards and would like to | |
358 | use the flash chips on it, say 'Y'. | |
359 | ||
360 | config MTD_REDWOOD | |
361 | tristate "CFI Flash devices mapped on IBM Redwood" | |
01ac742d | 362 | depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 ) |
1da177e4 LT |
363 | help |
364 | This enables access routines for the flash chips on the IBM | |
365 | Redwood board. If you have one of these boards and would like to | |
366 | use the flash chips on it, say 'Y'. | |
367 | ||
be30c10f MB |
368 | config MTD_TQM834x |
369 | tristate "Flash device mapped on TQ Components TQM834x Boards" | |
370 | depends on MTD_CFI && TQM834x | |
371 | help | |
372 | This enables access routines for the flash chips on the | |
373 | TQ Components TQM834x boards. If you have one of these boards | |
374 | and would like to use the flash chips on it, say 'Y'. | |
375 | ||
1da177e4 LT |
376 | config MTD_CSTM_MIPS_IXX |
377 | tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board" | |
378 | depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS | |
379 | help | |
380 | This provides a mapping driver for the Integrated Technology | |
381 | Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR | |
382 | Reference Board. It provides the necessary addressing, length, | |
383 | buswidth, vpp code and addition setup of the flash device for | |
384 | these boards. In addition, this mapping driver can be used for | |
385 | other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/ | |
386 | LEN/BUSWIDTH parameters. This mapping will provide one mtd device | |
387 | using one partition. The start address can be offset from the | |
388 | beginning of flash and the len can be less than the total flash | |
389 | device size to allow a window into the flash. Both CFI and JEDEC | |
390 | probes are called. | |
391 | ||
392 | config MTD_CSTM_MIPS_IXX_START | |
393 | hex "Physical start address of flash mapping" | |
394 | depends on MTD_CSTM_MIPS_IXX | |
395 | default "0x8000000" | |
396 | help | |
397 | This is the physical memory location that the MTD driver will | |
69f34c98 TG |
398 | use for the flash chips on your particular target board. |
399 | Refer to the memory map which should hopefully be in the | |
1da177e4 LT |
400 | documentation for your board. |
401 | ||
402 | config MTD_CSTM_MIPS_IXX_LEN | |
403 | hex "Physical length of flash mapping" | |
404 | depends on MTD_CSTM_MIPS_IXX | |
405 | default "0x4000000" | |
406 | help | |
69f34c98 | 407 | This is the total length that the MTD driver will use for the |
1da177e4 LT |
408 | flash chips on your particular board. Refer to the memory |
409 | map which should hopefully be in the documentation for your | |
410 | board. | |
411 | ||
412 | config MTD_CSTM_MIPS_IXX_BUSWIDTH | |
413 | int "Bus width in octets" | |
414 | depends on MTD_CSTM_MIPS_IXX | |
415 | default "2" | |
416 | help | |
417 | This is the total bus width of the mapping of the flash chips | |
418 | on your particular board. | |
419 | ||
420 | config MTD_OCELOT | |
421 | tristate "Momenco Ocelot boot flash device" | |
422 | depends on MIPS && MOMENCO_OCELOT | |
423 | help | |
424 | This enables access routines for the boot flash device and for the | |
425 | NVRAM on the Momenco Ocelot board. If you have one of these boards | |
426 | and would like access to either of these, say 'Y'. | |
427 | ||
428 | config MTD_SOLUTIONENGINE | |
429 | tristate "CFI Flash device mapped on Hitachi SolutionEngine" | |
430 | depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS | |
431 | help | |
432 | This enables access to the flash chips on the Hitachi SolutionEngine and | |
433 | similar boards. Say 'Y' if you are building a kernel for such a board. | |
434 | ||
435 | config MTD_ARM_INTEGRATOR | |
436 | tristate "CFI Flash device mapped on ARM Integrator/P720T" | |
437 | depends on ARM && MTD_CFI | |
438 | ||
439 | config MTD_CDB89712 | |
440 | tristate "Cirrus CDB89712 evaluation board mappings" | |
01ac742d | 441 | depends on MTD_CFI && ARCH_CDB89712 |
1da177e4 LT |
442 | help |
443 | This enables access to the flash or ROM chips on the CDB89712 board. | |
444 | If you have such a board, say 'Y'. | |
445 | ||
446 | config MTD_SA1100 | |
447 | tristate "CFI Flash device mapped on StrongARM SA11x0" | |
01ac742d | 448 | depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS |
1da177e4 LT |
449 | help |
450 | This enables access to the flash chips on most platforms based on | |
451 | the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. | |
452 | If you have such a board, say 'Y'. | |
453 | ||
454 | config MTD_IPAQ | |
455 | tristate "CFI Flash device mapped on Compaq/HP iPAQ" | |
01ac742d | 456 | depends on IPAQ_HANDHELD && MTD_CFI |
1da177e4 LT |
457 | help |
458 | This provides a driver for the on-board flash of the iPAQ. | |
459 | ||
460 | config MTD_DC21285 | |
461 | tristate "CFI Flash device mapped on DC21285 Footbridge" | |
01ac742d | 462 | depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS |
1da177e4 LT |
463 | help |
464 | This provides a driver for the flash accessed using Intel's | |
465 | 21285 bridge used with Intel's StrongARM processors. More info at | |
466 | <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. | |
467 | ||
1da177e4 LT |
468 | config MTD_IXP4XX |
469 | tristate "CFI Flash device mapped on Intel IXP4xx based systems" | |
01ac742d | 470 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX |
1da177e4 | 471 | help |
69f34c98 | 472 | This enables MTD access to flash devices on platforms based |
1da177e4 LT |
473 | on Intel's IXP4xx family of network processors such as the |
474 | IXDP425 and Coyote. If you have an IXP4xx based board and | |
475 | would like to use the flash chips on it, say 'Y'. | |
476 | ||
477 | config MTD_IXP2000 | |
478 | tristate "CFI Flash device mapped on Intel IXP2000 based systems" | |
01ac742d | 479 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 |
1da177e4 | 480 | help |
69f34c98 | 481 | This enables MTD access to flash devices on platforms based |
1da177e4 LT |
482 | on Intel's IXP2000 family of network processors such as the |
483 | IXDP425 and Coyote. If you have an IXP2000 based board and | |
484 | would like to use the flash chips on it, say 'Y'. | |
485 | ||
1da177e4 LT |
486 | config MTD_FORTUNET |
487 | tristate "CFI Flash device mapped on the FortuNet board" | |
01ac742d | 488 | depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET |
1da177e4 LT |
489 | help |
490 | This enables access to the Flash on the FortuNet board. If you | |
491 | have such a board, say 'Y'. | |
492 | ||
493 | config MTD_AUTCPU12 | |
494 | tristate "NV-RAM mapping AUTCPU12 board" | |
01ac742d | 495 | depends on ARCH_AUTCPU12 |
1da177e4 LT |
496 | help |
497 | This enables access to the NV-RAM on autronix autcpu12 board. | |
498 | If you have such a board, say 'Y'. | |
499 | ||
500 | config MTD_EDB7312 | |
501 | tristate "CFI Flash device mapped on EDB7312" | |
01ac742d | 502 | depends on ARCH_EDB7312 && MTD_CFI |
1da177e4 LT |
503 | help |
504 | This enables access to the CFI Flash on the Cogent EDB7312 board. | |
505 | If you have such a board, say 'Y' here. | |
506 | ||
507 | config MTD_IMPA7 | |
508 | tristate "JEDEC Flash device mapped on impA7" | |
509 | depends on ARM && MTD_JEDECPROBE | |
510 | help | |
511 | This enables access to the NOR Flash on the impA7 board of | |
512 | implementa GmbH. If you have such a board, say 'Y' here. | |
513 | ||
514 | config MTD_CEIVA | |
515 | tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame" | |
01ac742d | 516 | depends on MTD_JEDECPROBE && ARCH_CEIVA |
1da177e4 LT |
517 | help |
518 | This enables access to the flash chips on the Ceiva/Polaroid | |
519 | PhotoMax Digital Picture Frame. | |
520 | If you have such a device, say 'Y'. | |
521 | ||
522 | config MTD_NOR_TOTO | |
523 | tristate "NOR Flash device on TOTO board" | |
01ac742d | 524 | depends on ARCH_OMAP && OMAP_TOTO |
1da177e4 LT |
525 | help |
526 | This enables access to the NOR flash on the Texas Instruments | |
527 | TOTO board. | |
528 | ||
529 | config MTD_H720X | |
530 | tristate "Hynix evaluation board mappings" | |
01ac742d | 531 | depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 ) |
1da177e4 LT |
532 | help |
533 | This enables access to the flash chips on the Hynix evaluation boards. | |
534 | If you have such a board, say 'Y'. | |
535 | ||
536 | config MTD_MPC1211 | |
537 | tristate "CFI Flash device mapped on Interface MPC-1211" | |
01ac742d | 538 | depends on SH_MPC1211 && MTD_CFI |
1da177e4 LT |
539 | help |
540 | This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02). | |
541 | If you have such a board, say 'Y'. | |
542 | ||
10c96f2e TP |
543 | config MTD_OMAP_NOR |
544 | tristate "TI OMAP board mappings" | |
545 | depends on MTD_CFI && ARCH_OMAP | |
546 | help | |
547 | This enables access to the NOR flash chips on TI OMAP-based | |
548 | boards defining flash platform devices and flash platform data. | |
549 | These boards include the Innovator, H2, H3, OSK, Perseus2, and | |
550 | more. If you have such a board, say 'Y'. | |
551 | ||
1da177e4 LT |
552 | # This needs CFI or JEDEC, depending on the cards found. |
553 | config MTD_PCI | |
554 | tristate "PCI MTD driver" | |
555 | depends on MTD && PCI && MTD_COMPLEX_MAPPINGS | |
556 | help | |
557 | Mapping for accessing flash devices on add-in cards like the Intel XScale | |
558 | IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode | |
559 | (please see the manual for the link settings). | |
560 | ||
561 | If you are not sure, say N. | |
562 | ||
563 | config MTD_PCMCIA | |
564 | tristate "PCMCIA MTD driver" | |
565 | depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN | |
566 | help | |
567 | Map driver for accessing PCMCIA linear flash memory cards. These | |
568 | cards are usually around 4-16MiB in size. This does not include | |
569 | Compact Flash cards which are treated as IDE devices. | |
570 | ||
11d28a30 DB |
571 | config MTD_PCMCIA_ANONYMOUS |
572 | bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards" | |
573 | depends on MTD_PCMCIA | |
11d28a30 DB |
574 | help |
575 | If this option is enabled, PCMCIA cards which do not report | |
576 | anything about themselves are assumed to be MTD cards. | |
577 | ||
578 | If unsure, say N. | |
579 | ||
1da177e4 LT |
580 | config MTD_UCLINUX |
581 | tristate "Generic uClinux RAM/ROM filesystem support" | |
582 | depends on MTD_PARTITIONS && !MMU | |
583 | help | |
584 | Map driver to support image based filesystems for uClinux. | |
585 | ||
586 | config MTD_WRSBC8260 | |
587 | tristate "Map driver for WindRiver PowerQUICC II MPC82xx board" | |
588 | depends on (SBC82xx || SBC8560) | |
589 | select MTD_PARTITIONS | |
590 | select MTD_MAP_BANK_WIDTH_4 | |
591 | select MTD_MAP_BANK_WIDTH_1 | |
592 | select MTD_CFI_I1 | |
593 | select MTD_CFI_I4 | |
594 | help | |
595 | Map driver for WindRiver PowerQUICC II MPC82xx board. Drives | |
596 | all three flash regions on CS0, CS1 and CS6 if they are configured | |
597 | correctly by the boot loader. | |
598 | ||
599 | config MTD_DMV182 | |
600 | tristate "Map driver for Dy-4 SVME/DMV-182 board." | |
601 | depends on DMV182 | |
602 | select MTD_PARTITIONS | |
603 | select MTD_MAP_BANK_WIDTH_32 | |
604 | select MTD_CFI_I8 | |
605 | select MTD_CFI_AMDSTD | |
606 | help | |
607 | Map driver for Dy-4 SVME/DMV-182 board. | |
608 | ||
609 | config MTD_BAST | |
76853596 BD |
610 | tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000" |
611 | depends on ARCH_BAST || MACH_VR1000 | |
1da177e4 LT |
612 | select MTD_PARTITIONS |
613 | select MTD_MAP_BANK_WIDTH_16 | |
614 | select MTD_JEDECPROBE | |
615 | help | |
76853596 BD |
616 | Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the |
617 | Thorcom VR1000 | |
1da177e4 LT |
618 | |
619 | Note, this driver *cannot* over-ride the WP link on the | |
620 | board, or currently detect the state of the link. | |
621 | ||
622 | config MTD_BAST_MAXSIZE | |
623 | int "Maximum size for BAST flash area (MiB)" | |
624 | depends on MTD_BAST | |
625 | default "4" | |
626 | ||
627 | config MTD_SHARP_SL | |
628 | bool "ROM maped on Sharp SL Series" | |
629 | depends on MTD && ARCH_PXA | |
630 | help | |
631 | This enables access to the flash chip on the Sharp SL Series of PDAs. | |
632 | ||
99f2a8ae | 633 | config MTD_PLATRAM |
3c45e00a | 634 | tristate "Map driver for platform device RAM (mtd-ram)" |
99f2a8ae BD |
635 | depends on MTD |
636 | select MTD_RAM | |
637 | help | |
638 | Map driver for RAM areas described via the platform device | |
639 | system. | |
640 | ||
641 | This selection automatically selects the map_ram driver. | |
642 | ||
1da177e4 LT |
643 | endmenu |
644 |