diff options
author | Linus Torvalds <torvalds@g5.osdl.org> | 2005-11-07 13:24:08 -0500 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-11-07 13:24:08 -0500 |
commit | b3ce1debe2685383a9ad6ace9c49869c3968c013 (patch) | |
tree | dcb606fac467d6ce78a9c608a1e0d2323af44f2b /drivers/mtd/maps/Kconfig | |
parent | 5b2f7ffcb734d3046144dfbd5ac6d76254a9e522 (diff) | |
parent | c2965f1129ee54afcc4ef293ff0f25fa3a7e7392 (diff) |
Merge master.kernel.org:/pub/scm/linux/kernel/git/tglx/mtd-2.6
Some manual fixups for clashing kfree() cleanups etc.
Diffstat (limited to 'drivers/mtd/maps/Kconfig')
-rw-r--r-- | drivers/mtd/maps/Kconfig | 115 |
1 files changed, 68 insertions, 47 deletions
diff --git a/drivers/mtd/maps/Kconfig b/drivers/mtd/maps/Kconfig index 44781a83b2e7..48638c8097a5 100644 --- a/drivers/mtd/maps/Kconfig +++ b/drivers/mtd/maps/Kconfig | |||
@@ -1,5 +1,5 @@ | |||
1 | # drivers/mtd/maps/Kconfig | 1 | # drivers/mtd/maps/Kconfig |
2 | # $Id: Kconfig,v 1.55 2005/07/02 01:53:24 tpoynor Exp $ | 2 | # $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner Exp $ |
3 | 3 | ||
4 | menu "Mapping drivers for chip access" | 4 | menu "Mapping drivers for chip access" |
5 | depends on MTD!=n | 5 | depends on MTD!=n |
@@ -64,9 +64,9 @@ config MTD_SUN_UFLASH | |||
64 | tristate "Sun Microsystems userflash support" | 64 | tristate "Sun Microsystems userflash support" |
65 | depends on (SPARC32 || SPARC64) && MTD_CFI | 65 | depends on (SPARC32 || SPARC64) && MTD_CFI |
66 | help | 66 | help |
67 | This provides a 'mapping' driver which supports the way in | 67 | This provides a 'mapping' driver which supports the way in |
68 | which user-programmable flash chips are connected on various | 68 | which user-programmable flash chips are connected on various |
69 | Sun Microsystems boardsets. This driver will require CFI support | 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. | 70 | in the kernel, so if you did not enable CFI previously, do that now. |
71 | 71 | ||
72 | config MTD_PNC2000 | 72 | config MTD_PNC2000 |
@@ -89,22 +89,22 @@ config MTD_NETSC520 | |||
89 | depends on X86 && MTD_CFI && MTD_PARTITIONS | 89 | depends on X86 && MTD_CFI && MTD_PARTITIONS |
90 | help | 90 | help |
91 | This enables access routines for the flash chips on the AMD NetSc520 | 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 | 92 | demonstration board. If you have one of these boards and would like |
93 | to use the flash chips on it, say 'Y'. | 93 | to use the flash chips on it, say 'Y'. |
94 | 94 | ||
95 | config MTD_TS5500 | 95 | config MTD_TS5500 |
96 | tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" | 96 | tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" |
97 | depends on X86 && MTD_JEDECPROBE && MTD_PARTITIONS | 97 | depends on ELAN |
98 | select MTD_PARTITIONS | ||
99 | select MTD_JEDECPROBE | ||
100 | select MTD_CFI_AMDSTD | ||
98 | help | 101 | help |
99 | This provides a driver for the on-board flash of the Technologic | 102 | 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 | 103 | System's TS-5500 board. The 2MB flash is split into 3 partitions |
101 | which are accessed as separate MTD devices. | 104 | which are accessed as separate MTD devices. |
102 | 105 | ||
103 | mtd0 and mtd2 are the two BIOS drives. Unfortunately the BIOS | 106 | mtd0 and mtd2 are the two BIOS drives, which use the resident |
104 | uses a proprietary flash translation layer from General Software, | 107 | flash disk (RFD) flash translation layer. |
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 | 108 | ||
109 | mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. | 109 | mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. |
110 | 110 | ||
@@ -212,11 +212,18 @@ config MTD_NETtel | |||
212 | Support for flash chips on NETtel/SecureEdge/SnapGear boards. | 212 | Support for flash chips on NETtel/SecureEdge/SnapGear boards. |
213 | 213 | ||
214 | config MTD_ALCHEMY | 214 | config MTD_ALCHEMY |
215 | tristate ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support' | 215 | tristate ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support' |
216 | depends on MIPS && SOC_AU1X00 | 216 | depends on SOC_AU1X00 |
217 | help | 217 | help |
218 | Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards | 218 | Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards |
219 | 219 | ||
220 | config MTD_MTX1 | ||
221 | tristate "4G Systems MTX-1 Flash device" | ||
222 | depends on MIPS && MIPS_MTX1 | ||
223 | help | ||
224 | Flash memory access on 4G Systems MTX-1 Board. If you have one of | ||
225 | these boards and would like to use the flash chips on it, say 'Y'. | ||
226 | |||
220 | config MTD_DILNETPC | 227 | config MTD_DILNETPC |
221 | tristate "CFI Flash device mapped on DIL/Net PC" | 228 | tristate "CFI Flash device mapped on DIL/Net PC" |
222 | depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT | 229 | depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT |
@@ -244,14 +251,14 @@ config MTD_L440GX | |||
244 | 251 | ||
245 | config MTD_SBC8240 | 252 | config MTD_SBC8240 |
246 | tristate "Flash device on SBC8240" | 253 | tristate "Flash device on SBC8240" |
247 | depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260 | 254 | depends on MTD_JEDECPROBE && 8260 |
248 | help | 255 | help |
249 | Flash access on the SBC8240 board from Wind River. See | 256 | Flash access on the SBC8240 board from Wind River. See |
250 | <http://www.windriver.com/products/sbc8240/> | 257 | <http://www.windriver.com/products/sbc8240/> |
251 | 258 | ||
252 | config MTD_TQM8XXL | 259 | config MTD_TQM8XXL |
253 | tristate "CFI Flash device mapped on TQM8XXL" | 260 | tristate "CFI Flash device mapped on TQM8XXL" |
254 | depends on MTD_CFI && PPC32 && 8xx && TQM8xxL | 261 | depends on MTD_CFI && TQM8xxL |
255 | help | 262 | help |
256 | The TQM8xxL PowerPC board has up to two banks of CFI-compliant | 263 | The TQM8xxL PowerPC board has up to two banks of CFI-compliant |
257 | chips, currently uses AMD one. This 'mapping' driver supports | 264 | chips, currently uses AMD one. This 'mapping' driver supports |
@@ -261,7 +268,7 @@ config MTD_TQM8XXL | |||
261 | 268 | ||
262 | config MTD_RPXLITE | 269 | config MTD_RPXLITE |
263 | tristate "CFI Flash device mapped on RPX Lite or CLLF" | 270 | tristate "CFI Flash device mapped on RPX Lite or CLLF" |
264 | depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE) | 271 | depends on MTD_CFI && (RPXCLASSIC || RPXLITE) |
265 | help | 272 | help |
266 | The RPXLite PowerPC board has CFI-compliant chips mapped in | 273 | The RPXLite PowerPC board has CFI-compliant chips mapped in |
267 | a strange sparse mapping. This 'mapping' driver supports that | 274 | a strange sparse mapping. This 'mapping' driver supports that |
@@ -271,7 +278,7 @@ config MTD_RPXLITE | |||
271 | 278 | ||
272 | config MTD_MBX860 | 279 | config MTD_MBX860 |
273 | tristate "System flash on MBX860 board" | 280 | tristate "System flash on MBX860 board" |
274 | depends on MTD_CFI && PPC32 && 8xx && MBX | 281 | depends on MTD_CFI && MBX |
275 | help | 282 | help |
276 | This enables access routines for the flash chips on the Motorola | 283 | This enables access routines for the flash chips on the Motorola |
277 | MBX860 board. If you have one of these boards and would like | 284 | MBX860 board. If you have one of these boards and would like |
@@ -279,7 +286,7 @@ config MTD_MBX860 | |||
279 | 286 | ||
280 | config MTD_DBOX2 | 287 | config MTD_DBOX2 |
281 | tristate "CFI Flash device mapped on D-Box2" | 288 | tristate "CFI Flash device mapped on D-Box2" |
282 | depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD | 289 | depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD |
283 | help | 290 | help |
284 | This enables access routines for the flash chips on the Nokia/Sagem | 291 | This enables access routines for the flash chips on the Nokia/Sagem |
285 | D-Box 2 board. If you have one of these boards and would like to use | 292 | D-Box 2 board. If you have one of these boards and would like to use |
@@ -287,14 +294,14 @@ config MTD_DBOX2 | |||
287 | 294 | ||
288 | config MTD_CFI_FLAGADM | 295 | config MTD_CFI_FLAGADM |
289 | tristate "CFI Flash device mapping on FlagaDM" | 296 | tristate "CFI Flash device mapping on FlagaDM" |
290 | depends on PPC32 && 8xx && MTD_CFI | 297 | depends on 8xx && MTD_CFI |
291 | help | 298 | help |
292 | Mapping for the Flaga digital module. If you don't have one, ignore | 299 | Mapping for the Flaga digital module. If you don't have one, ignore |
293 | this setting. | 300 | this setting. |
294 | 301 | ||
295 | config MTD_BEECH | 302 | config MTD_BEECH |
296 | tristate "CFI Flash device mapped on IBM 405LP Beech" | 303 | tristate "CFI Flash device mapped on IBM 405LP Beech" |
297 | depends on MTD_CFI && PPC32 && 40x && BEECH | 304 | depends on MTD_CFI && BEECH |
298 | help | 305 | help |
299 | This enables access routines for the flash chips on the IBM | 306 | This enables access routines for the flash chips on the IBM |
300 | 405LP Beech board. If you have one of these boards and would like | 307 | 405LP Beech board. If you have one of these boards and would like |
@@ -302,7 +309,7 @@ config MTD_BEECH | |||
302 | 309 | ||
303 | config MTD_ARCTIC | 310 | config MTD_ARCTIC |
304 | tristate "CFI Flash device mapped on IBM 405LP Arctic" | 311 | tristate "CFI Flash device mapped on IBM 405LP Arctic" |
305 | depends on MTD_CFI && PPC32 && 40x && ARCTIC2 | 312 | depends on MTD_CFI && ARCTIC2 |
306 | help | 313 | help |
307 | This enables access routines for the flash chips on the IBM 405LP | 314 | This enables access routines for the flash chips on the IBM 405LP |
308 | Arctic board. If you have one of these boards and would like to | 315 | Arctic board. If you have one of these boards and would like to |
@@ -310,7 +317,7 @@ config MTD_ARCTIC | |||
310 | 317 | ||
311 | config MTD_WALNUT | 318 | config MTD_WALNUT |
312 | tristate "Flash device mapped on IBM 405GP Walnut" | 319 | tristate "Flash device mapped on IBM 405GP Walnut" |
313 | depends on MTD_JEDECPROBE && PPC32 && 40x && WALNUT | 320 | depends on MTD_JEDECPROBE && WALNUT |
314 | help | 321 | help |
315 | This enables access routines for the flash chips on the IBM 405GP | 322 | This enables access routines for the flash chips on the IBM 405GP |
316 | Walnut board. If you have one of these boards and would like to | 323 | Walnut board. If you have one of these boards and would like to |
@@ -318,7 +325,7 @@ config MTD_WALNUT | |||
318 | 325 | ||
319 | config MTD_EBONY | 326 | config MTD_EBONY |
320 | tristate "Flash devices mapped on IBM 440GP Ebony" | 327 | tristate "Flash devices mapped on IBM 440GP Ebony" |
321 | depends on MTD_JEDECPROBE && PPC32 && 44x && EBONY | 328 | depends on MTD_JEDECPROBE && EBONY |
322 | help | 329 | help |
323 | This enables access routines for the flash chips on the IBM 440GP | 330 | This enables access routines for the flash chips on the IBM 440GP |
324 | Ebony board. If you have one of these boards and would like to | 331 | Ebony board. If you have one of these boards and would like to |
@@ -326,7 +333,7 @@ config MTD_EBONY | |||
326 | 333 | ||
327 | config MTD_OCOTEA | 334 | config MTD_OCOTEA |
328 | tristate "Flash devices mapped on IBM 440GX Ocotea" | 335 | tristate "Flash devices mapped on IBM 440GX Ocotea" |
329 | depends on MTD_CFI && PPC32 && 44x && OCOTEA | 336 | depends on MTD_CFI && OCOTEA |
330 | help | 337 | help |
331 | This enables access routines for the flash chips on the IBM 440GX | 338 | This enables access routines for the flash chips on the IBM 440GX |
332 | Ocotea board. If you have one of these boards and would like to | 339 | Ocotea board. If you have one of these boards and would like to |
@@ -334,12 +341,20 @@ config MTD_OCOTEA | |||
334 | 341 | ||
335 | config MTD_REDWOOD | 342 | config MTD_REDWOOD |
336 | tristate "CFI Flash devices mapped on IBM Redwood" | 343 | tristate "CFI Flash devices mapped on IBM Redwood" |
337 | depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 ) | 344 | depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 ) |
338 | help | 345 | help |
339 | This enables access routines for the flash chips on the IBM | 346 | This enables access routines for the flash chips on the IBM |
340 | Redwood board. If you have one of these boards and would like to | 347 | Redwood board. If you have one of these boards and would like to |
341 | use the flash chips on it, say 'Y'. | 348 | use the flash chips on it, say 'Y'. |
342 | 349 | ||
350 | config MTD_TQM834x | ||
351 | tristate "Flash device mapped on TQ Components TQM834x Boards" | ||
352 | depends on MTD_CFI && TQM834x | ||
353 | help | ||
354 | This enables access routines for the flash chips on the | ||
355 | TQ Components TQM834x boards. If you have one of these boards | ||
356 | and would like to use the flash chips on it, say 'Y'. | ||
357 | |||
343 | config MTD_CSTM_MIPS_IXX | 358 | config MTD_CSTM_MIPS_IXX |
344 | tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board" | 359 | tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board" |
345 | depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS | 360 | depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS |
@@ -362,8 +377,8 @@ config MTD_CSTM_MIPS_IXX_START | |||
362 | default "0x8000000" | 377 | default "0x8000000" |
363 | help | 378 | help |
364 | This is the physical memory location that the MTD driver will | 379 | This is the physical memory location that the MTD driver will |
365 | use for the flash chips on your particular target board. | 380 | use for the flash chips on your particular target board. |
366 | Refer to the memory map which should hopefully be in the | 381 | Refer to the memory map which should hopefully be in the |
367 | documentation for your board. | 382 | documentation for your board. |
368 | 383 | ||
369 | config MTD_CSTM_MIPS_IXX_LEN | 384 | config MTD_CSTM_MIPS_IXX_LEN |
@@ -371,7 +386,7 @@ config MTD_CSTM_MIPS_IXX_LEN | |||
371 | depends on MTD_CSTM_MIPS_IXX | 386 | depends on MTD_CSTM_MIPS_IXX |
372 | default "0x4000000" | 387 | default "0x4000000" |
373 | help | 388 | help |
374 | This is the total length that the MTD driver will use for the | 389 | This is the total length that the MTD driver will use for the |
375 | flash chips on your particular board. Refer to the memory | 390 | flash chips on your particular board. Refer to the memory |
376 | map which should hopefully be in the documentation for your | 391 | map which should hopefully be in the documentation for your |
377 | board. | 392 | board. |
@@ -405,14 +420,14 @@ config MTD_ARM_INTEGRATOR | |||
405 | 420 | ||
406 | config MTD_CDB89712 | 421 | config MTD_CDB89712 |
407 | tristate "Cirrus CDB89712 evaluation board mappings" | 422 | tristate "Cirrus CDB89712 evaluation board mappings" |
408 | depends on ARM && MTD_CFI && ARCH_CDB89712 | 423 | depends on MTD_CFI && ARCH_CDB89712 |
409 | help | 424 | help |
410 | This enables access to the flash or ROM chips on the CDB89712 board. | 425 | This enables access to the flash or ROM chips on the CDB89712 board. |
411 | If you have such a board, say 'Y'. | 426 | If you have such a board, say 'Y'. |
412 | 427 | ||
413 | config MTD_SA1100 | 428 | config MTD_SA1100 |
414 | tristate "CFI Flash device mapped on StrongARM SA11x0" | 429 | tristate "CFI Flash device mapped on StrongARM SA11x0" |
415 | depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS | 430 | depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS |
416 | help | 431 | help |
417 | This enables access to the flash chips on most platforms based on | 432 | This enables access to the flash chips on most platforms based on |
418 | the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. | 433 | the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. |
@@ -420,13 +435,13 @@ config MTD_SA1100 | |||
420 | 435 | ||
421 | config MTD_IPAQ | 436 | config MTD_IPAQ |
422 | tristate "CFI Flash device mapped on Compaq/HP iPAQ" | 437 | tristate "CFI Flash device mapped on Compaq/HP iPAQ" |
423 | depends on ARM && IPAQ_HANDHELD && MTD_CFI | 438 | depends on IPAQ_HANDHELD && MTD_CFI |
424 | help | 439 | help |
425 | This provides a driver for the on-board flash of the iPAQ. | 440 | This provides a driver for the on-board flash of the iPAQ. |
426 | 441 | ||
427 | config MTD_DC21285 | 442 | config MTD_DC21285 |
428 | tristate "CFI Flash device mapped on DC21285 Footbridge" | 443 | tristate "CFI Flash device mapped on DC21285 Footbridge" |
429 | depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS | 444 | depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS |
430 | help | 445 | help |
431 | This provides a driver for the flash accessed using Intel's | 446 | This provides a driver for the flash accessed using Intel's |
432 | 21285 bridge used with Intel's StrongARM processors. More info at | 447 | 21285 bridge used with Intel's StrongARM processors. More info at |
@@ -434,33 +449,33 @@ config MTD_DC21285 | |||
434 | 449 | ||
435 | config MTD_IQ80310 | 450 | config MTD_IQ80310 |
436 | tristate "CFI Flash device mapped on the XScale IQ80310 board" | 451 | tristate "CFI Flash device mapped on the XScale IQ80310 board" |
437 | depends on ARM && MTD_CFI && ARCH_IQ80310 | 452 | depends on MTD_CFI && ARCH_IQ80310 |
438 | help | 453 | help |
439 | This enables access routines for the flash chips on the Intel XScale | 454 | This enables access routines for the flash chips on the Intel XScale |
440 | IQ80310 evaluation board. If you have one of these boards and would | 455 | IQ80310 evaluation board. If you have one of these boards and would |
441 | like to use the flash chips on it, say 'Y'. | 456 | like to use the flash chips on it, say 'Y'. |
442 | 457 | ||
443 | config MTD_IXP4XX | 458 | config MTD_IXP4XX |
444 | tristate "CFI Flash device mapped on Intel IXP4xx based systems" | 459 | tristate "CFI Flash device mapped on Intel IXP4xx based systems" |
445 | depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX | 460 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX |
446 | help | 461 | help |
447 | This enables MTD access to flash devices on platforms based | 462 | This enables MTD access to flash devices on platforms based |
448 | on Intel's IXP4xx family of network processors such as the | 463 | on Intel's IXP4xx family of network processors such as the |
449 | IXDP425 and Coyote. If you have an IXP4xx based board and | 464 | IXDP425 and Coyote. If you have an IXP4xx based board and |
450 | would like to use the flash chips on it, say 'Y'. | 465 | would like to use the flash chips on it, say 'Y'. |
451 | 466 | ||
452 | config MTD_IXP2000 | 467 | config MTD_IXP2000 |
453 | tristate "CFI Flash device mapped on Intel IXP2000 based systems" | 468 | tristate "CFI Flash device mapped on Intel IXP2000 based systems" |
454 | depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 | 469 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 |
455 | help | 470 | help |
456 | This enables MTD access to flash devices on platforms based | 471 | This enables MTD access to flash devices on platforms based |
457 | on Intel's IXP2000 family of network processors such as the | 472 | on Intel's IXP2000 family of network processors such as the |
458 | IXDP425 and Coyote. If you have an IXP2000 based board and | 473 | IXDP425 and Coyote. If you have an IXP2000 based board and |
459 | would like to use the flash chips on it, say 'Y'. | 474 | would like to use the flash chips on it, say 'Y'. |
460 | 475 | ||
461 | config MTD_EPXA10DB | 476 | config MTD_EPXA10DB |
462 | tristate "CFI Flash device mapped on Epxa10db" | 477 | tristate "CFI Flash device mapped on Epxa10db" |
463 | depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT | 478 | depends on MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT |
464 | help | 479 | help |
465 | This enables support for the flash devices on the Altera | 480 | This enables support for the flash devices on the Altera |
466 | Excalibur XA10 Development Board. If you are building a kernel | 481 | Excalibur XA10 Development Board. If you are building a kernel |
@@ -468,21 +483,21 @@ config MTD_EPXA10DB | |||
468 | 483 | ||
469 | config MTD_FORTUNET | 484 | config MTD_FORTUNET |
470 | tristate "CFI Flash device mapped on the FortuNet board" | 485 | tristate "CFI Flash device mapped on the FortuNet board" |
471 | depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET | 486 | depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET |
472 | help | 487 | help |
473 | This enables access to the Flash on the FortuNet board. If you | 488 | This enables access to the Flash on the FortuNet board. If you |
474 | have such a board, say 'Y'. | 489 | have such a board, say 'Y'. |
475 | 490 | ||
476 | config MTD_AUTCPU12 | 491 | config MTD_AUTCPU12 |
477 | tristate "NV-RAM mapping AUTCPU12 board" | 492 | tristate "NV-RAM mapping AUTCPU12 board" |
478 | depends on ARM && ARCH_AUTCPU12 | 493 | depends on ARCH_AUTCPU12 |
479 | help | 494 | help |
480 | This enables access to the NV-RAM on autronix autcpu12 board. | 495 | This enables access to the NV-RAM on autronix autcpu12 board. |
481 | If you have such a board, say 'Y'. | 496 | If you have such a board, say 'Y'. |
482 | 497 | ||
483 | config MTD_EDB7312 | 498 | config MTD_EDB7312 |
484 | tristate "CFI Flash device mapped on EDB7312" | 499 | tristate "CFI Flash device mapped on EDB7312" |
485 | depends on ARM && MTD_CFI | 500 | depends on ARCH_EDB7312 && MTD_CFI |
486 | help | 501 | help |
487 | This enables access to the CFI Flash on the Cogent EDB7312 board. | 502 | This enables access to the CFI Flash on the Cogent EDB7312 board. |
488 | If you have such a board, say 'Y' here. | 503 | If you have such a board, say 'Y' here. |
@@ -496,7 +511,7 @@ config MTD_IMPA7 | |||
496 | 511 | ||
497 | config MTD_CEIVA | 512 | config MTD_CEIVA |
498 | tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame" | 513 | tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame" |
499 | depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA | 514 | depends on MTD_JEDECPROBE && ARCH_CEIVA |
500 | help | 515 | help |
501 | This enables access to the flash chips on the Ceiva/Polaroid | 516 | This enables access to the flash chips on the Ceiva/Polaroid |
502 | PhotoMax Digital Picture Frame. | 517 | PhotoMax Digital Picture Frame. |
@@ -504,25 +519,31 @@ config MTD_CEIVA | |||
504 | 519 | ||
505 | config MTD_NOR_TOTO | 520 | config MTD_NOR_TOTO |
506 | tristate "NOR Flash device on TOTO board" | 521 | tristate "NOR Flash device on TOTO board" |
507 | depends on ARM && ARCH_OMAP && OMAP_TOTO | 522 | depends on ARCH_OMAP && OMAP_TOTO |
508 | help | 523 | help |
509 | This enables access to the NOR flash on the Texas Instruments | 524 | This enables access to the NOR flash on the Texas Instruments |
510 | TOTO board. | 525 | TOTO board. |
511 | 526 | ||
512 | config MTD_H720X | 527 | config MTD_H720X |
513 | tristate "Hynix evaluation board mappings" | 528 | tristate "Hynix evaluation board mappings" |
514 | depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 ) | 529 | depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 ) |
515 | help | 530 | help |
516 | This enables access to the flash chips on the Hynix evaluation boards. | 531 | This enables access to the flash chips on the Hynix evaluation boards. |
517 | If you have such a board, say 'Y'. | 532 | If you have such a board, say 'Y'. |
518 | 533 | ||
519 | config MTD_MPC1211 | 534 | config MTD_MPC1211 |
520 | tristate "CFI Flash device mapped on Interface MPC-1211" | 535 | tristate "CFI Flash device mapped on Interface MPC-1211" |
521 | depends on SUPERH && SH_MPC1211 && MTD_CFI | 536 | depends on SH_MPC1211 && MTD_CFI |
522 | help | 537 | help |
523 | This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02). | 538 | This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02). |
524 | If you have such a board, say 'Y'. | 539 | If you have such a board, say 'Y'. |
525 | 540 | ||
541 | config MTD_PQ2FADS | ||
542 | tristate "JEDEC flash SIMM mapped on PQ2FADS and 8272ADS boards" | ||
543 | depends on (ADS8272 || PQ2FADS) && MTD_PARTITIONS && MTD_JEDECPROBE && MTD_PHYSMAP && MTD_CFI_GEOMETRY && MTD_CFI_INTELEXT | ||
544 | help | ||
545 | This enables access to flash SIMM on PQ2FADS-like boards | ||
546 | |||
526 | config MTD_OMAP_NOR | 547 | config MTD_OMAP_NOR |
527 | tristate "TI OMAP board mappings" | 548 | tristate "TI OMAP board mappings" |
528 | depends on MTD_CFI && ARCH_OMAP | 549 | depends on MTD_CFI && ARCH_OMAP |