Kconfig (be30c10fd8015a00c97c9b473263fe3c581389de) | Kconfig (69f34c98c1416eb74c55e38a21dbf3e294966514) |
---|---|
1# drivers/mtd/maps/Kconfig | 1# drivers/mtd/maps/Kconfig |
2# $Id: Kconfig,v 1.60 2005/11/07 08:33:35 gleixner Exp $ | 2# $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner Exp $ |
3 4menu "Mapping drivers for chip access" 5 depends on MTD!=n 6 7config MTD_COMPLEX_MAPPINGS 8 bool "Support non-linear mappings of flash chips" 9 depends on MTD 10 help --- 48 unchanged lines hidden (view full) --- 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 63config MTD_SUN_UFLASH 64 tristate "Sun Microsystems userflash support" 65 depends on (SPARC32 || SPARC64) && MTD_CFI 66 help | 3 4menu "Mapping drivers for chip access" 5 depends on MTD!=n 6 7config MTD_COMPLEX_MAPPINGS 8 bool "Support non-linear mappings of flash chips" 9 depends on MTD 10 help --- 48 unchanged lines hidden (view full) --- 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 63config 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 | 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 72config 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. --- 6 unchanged lines hidden (view full) --- 84 Dual-in-line JEDEC chip. This 'mapping' driver supports that 85 arrangement, implementing three MTD devices. 86 87config 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 | 70 in the kernel, so if you did not enable CFI previously, do that now. 71 72config 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. --- 6 unchanged lines hidden (view full) --- 84 Dual-in-line JEDEC chip. This 'mapping' driver supports that 85 arrangement, implementing three MTD devices. 86 87config 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 | 92 demonstration board. If you have one of these boards and would like |
93 to use the flash chips on it, say 'Y'. 94 95config MTD_TS5500 96 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" 97 depends on ELAN 98 select MTD_PARTITIONS 99 select MTD_JEDECPROBE 100 select MTD_CFI_AMDSTD --- 106 unchanged lines hidden (view full) --- 207 208config MTD_NETtel 209 tristate "CFI flash device on SnapGear/SecureEdge" 210 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE 211 help 212 Support for flash chips on NETtel/SecureEdge/SnapGear boards. 213 214config MTD_ALCHEMY | 93 to use the flash chips on it, say 'Y'. 94 95config MTD_TS5500 96 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" 97 depends on ELAN 98 select MTD_PARTITIONS 99 select MTD_JEDECPROBE 100 select MTD_CFI_AMDSTD --- 106 unchanged lines hidden (view full) --- 207 208config MTD_NETtel 209 tristate "CFI flash device on SnapGear/SecureEdge" 210 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE 211 help 212 Support for flash chips on NETtel/SecureEdge/SnapGear boards. 213 214config MTD_ALCHEMY |
215 tristate ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support' | 215 tristate ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support' |
216 depends on SOC_AU1X00 217 help 218 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards 219 220config MTD_MTX1 221 tristate "4G Systems MTX-1 Flash device" 222 depends on MIPS && MIPS_MTX1 223 help --- 148 unchanged lines hidden (view full) --- 372 probes are called. 373 374config MTD_CSTM_MIPS_IXX_START 375 hex "Physical start address of flash mapping" 376 depends on MTD_CSTM_MIPS_IXX 377 default "0x8000000" 378 help 379 This is the physical memory location that the MTD driver will | 216 depends on SOC_AU1X00 217 help 218 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards 219 220config MTD_MTX1 221 tristate "4G Systems MTX-1 Flash device" 222 depends on MIPS && MIPS_MTX1 223 help --- 148 unchanged lines hidden (view full) --- 372 probes are called. 373 374config MTD_CSTM_MIPS_IXX_START 375 hex "Physical start address of flash mapping" 376 depends on MTD_CSTM_MIPS_IXX 377 default "0x8000000" 378 help 379 This is the physical memory location that the MTD driver will |
380 use for the flash chips on your particular target board. 381 Refer to the memory map which should hopefully be in the | 380 use for the flash chips on your particular target board. 381 Refer to the memory map which should hopefully be in the |
382 documentation for your board. 383 384config MTD_CSTM_MIPS_IXX_LEN 385 hex "Physical length of flash mapping" 386 depends on MTD_CSTM_MIPS_IXX 387 default "0x4000000" 388 help | 382 documentation for your board. 383 384config MTD_CSTM_MIPS_IXX_LEN 385 hex "Physical length of flash mapping" 386 depends on MTD_CSTM_MIPS_IXX 387 default "0x4000000" 388 help |
389 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 |
390 flash chips on your particular board. Refer to the memory 391 map which should hopefully be in the documentation for your 392 board. 393 394config MTD_CSTM_MIPS_IXX_BUSWIDTH 395 int "Bus width in octets" 396 depends on MTD_CSTM_MIPS_IXX 397 default "2" --- 49 unchanged lines hidden (view full) --- 447 21285 bridge used with Intel's StrongARM processors. More info at 448 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. 449 450config MTD_IQ80310 451 tristate "CFI Flash device mapped on the XScale IQ80310 board" 452 depends on MTD_CFI && ARCH_IQ80310 453 help 454 This enables access routines for the flash chips on the Intel XScale | 390 flash chips on your particular board. Refer to the memory 391 map which should hopefully be in the documentation for your 392 board. 393 394config MTD_CSTM_MIPS_IXX_BUSWIDTH 395 int "Bus width in octets" 396 depends on MTD_CSTM_MIPS_IXX 397 default "2" --- 49 unchanged lines hidden (view full) --- 447 21285 bridge used with Intel's StrongARM processors. More info at 448 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. 449 450config MTD_IQ80310 451 tristate "CFI Flash device mapped on the XScale IQ80310 board" 452 depends on MTD_CFI && ARCH_IQ80310 453 help 454 This enables access routines for the flash chips on the Intel XScale |
455 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 |
456 like to use the flash chips on it, say 'Y'. 457 458config MTD_IXP4XX 459 tristate "CFI Flash device mapped on Intel IXP4xx based systems" 460 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX 461 help | 456 like to use the flash chips on it, say 'Y'. 457 458config MTD_IXP4XX 459 tristate "CFI Flash device mapped on Intel IXP4xx based systems" 460 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX 461 help |
462 This enables MTD access to flash devices on platforms based | 462 This enables MTD access to flash devices on platforms based |
463 on Intel's IXP4xx family of network processors such as the 464 IXDP425 and Coyote. If you have an IXP4xx based board and 465 would like to use the flash chips on it, say 'Y'. 466 467config MTD_IXP2000 468 tristate "CFI Flash device mapped on Intel IXP2000 based systems" 469 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 470 help | 463 on Intel's IXP4xx family of network processors such as the 464 IXDP425 and Coyote. If you have an IXP4xx based board and 465 would like to use the flash chips on it, say 'Y'. 466 467config MTD_IXP2000 468 tristate "CFI Flash device mapped on Intel IXP2000 based systems" 469 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 470 help |
471 This enables MTD access to flash devices on platforms based | 471 This enables MTD access to flash devices on platforms based |
472 on Intel's IXP2000 family of network processors such as the 473 IXDP425 and Coyote. If you have an IXP2000 based board and 474 would like to use the flash chips on it, say 'Y'. 475 476config MTD_EPXA10DB 477 tristate "CFI Flash device mapped on Epxa10db" 478 depends on MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT 479 help --- 170 unchanged lines hidden --- | 472 on Intel's IXP2000 family of network processors such as the 473 IXDP425 and Coyote. If you have an IXP2000 based board and 474 would like to use the flash chips on it, say 'Y'. 475 476config MTD_EPXA10DB 477 tristate "CFI Flash device mapped on Epxa10db" 478 depends on MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT 479 help --- 170 unchanged lines hidden --- |