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