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_ALCHEMY 255 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support" 256 depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI 257 help 258 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards 259 260config MTD_DILNETPC 261 tristate "CFI Flash device mapped on DIL/Net PC" 262 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT && BROKEN 263 help 264 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP". 265 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm> 266 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm> 267 268config MTD_DILNETPC_BOOTSIZE 269 hex "Size of DIL/Net PC flash boot partition" 270 depends on MTD_DILNETPC 271 default "0x80000" 272 help 273 The amount of space taken up by the kernel or Etherboot 274 on the DIL/Net PC flash chips. 275 276config MTD_L440GX 277 tristate "BIOS flash chip on Intel L440GX boards" 278 depends on X86 && MTD_JEDECPROBE 279 help 280 Support for treating the BIOS flash chip on Intel L440GX motherboards 281 as an MTD device - with this you can reprogram your BIOS. 282 283 BE VERY CAREFUL. 284 285config MTD_TQM8XXL 286 tristate "CFI Flash device mapped on TQM8XXL" 287 depends on MTD_CFI && TQM8xxL 288 help 289 The TQM8xxL PowerPC board has up to two banks of CFI-compliant 290 chips, currently uses AMD one. This 'mapping' driver supports 291 that arrangement, allowing the CFI probe and command set driver 292 code to communicate with the chips on the TQM8xxL board. More at 293 <http://www.denx.de/embedded-ppc-en.html>. 294 295config MTD_RPXLITE 296 tristate "CFI Flash device mapped on RPX Lite or CLLF" 297 depends on MTD_CFI && (RPXCLASSIC || RPXLITE) 298 help 299 The RPXLite PowerPC board has CFI-compliant chips mapped in 300 a strange sparse mapping. This 'mapping' driver supports that 301 arrangement, allowing the CFI probe and command set driver code 302 to communicate with the chips on the RPXLite board. More at 303 <http://www.embeddedplanet.com/>. 304 305config MTD_MBX860 306 tristate "System flash on MBX860 board" 307 depends on MTD_CFI && MBX 308 help 309 This enables access routines for the flash chips on the Motorola 310 MBX860 board. If you have one of these boards and would like 311 to use the flash chips on it, say 'Y'. 312 313config MTD_DBOX2 314 tristate "CFI Flash device mapped on D-Box2" 315 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD 316 help 317 This enables access routines for the flash chips on the Nokia/Sagem 318 D-Box 2 board. If you have one of these boards and would like to use 319 the flash chips on it, say 'Y'. 320 321config MTD_CFI_FLAGADM 322 tristate "CFI Flash device mapping on FlagaDM" 323 depends on 8xx && MTD_CFI 324 help 325 Mapping for the Flaga digital module. If you don't have one, ignore 326 this setting. 327 328config MTD_REDWOOD 329 tristate "CFI Flash devices mapped on IBM Redwood" 330 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 ) 331 help 332 This enables access routines for the flash chips on the IBM 333 Redwood board. If you have one of these boards and would like to 334 use the flash chips on it, say 'Y'. 335 336config MTD_SOLUTIONENGINE 337 tristate "CFI Flash device mapped on Hitachi SolutionEngine" 338 depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS 339 help 340 This enables access to the flash chips on the Hitachi SolutionEngine and 341 similar boards. Say 'Y' if you are building a kernel for such a board. 342 343config MTD_ARM_INTEGRATOR 344 tristate "CFI Flash device mapped on ARM Integrator/P720T" 345 depends on ARM && MTD_CFI 346 347config MTD_CDB89712 348 tristate "Cirrus CDB89712 evaluation board mappings" 349 depends on MTD_CFI && ARCH_CDB89712 350 help 351 This enables access to the flash or ROM chips on the CDB89712 board. 352 If you have such a board, say 'Y'. 353 354config MTD_SA1100 355 tristate "CFI Flash device mapped on StrongARM SA11x0" 356 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS 357 help 358 This enables access to the flash chips on most platforms based on 359 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. 360 If you have such a board, say 'Y'. 361 362config MTD_IPAQ 363 tristate "CFI Flash device mapped on Compaq/HP iPAQ" 364 depends on IPAQ_HANDHELD && MTD_CFI 365 help 366 This provides a driver for the on-board flash of the iPAQ. 367 368config MTD_DC21285 369 tristate "CFI Flash device mapped on DC21285 Footbridge" 370 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS 371 help 372 This provides a driver for the flash accessed using Intel's 373 21285 bridge used with Intel's StrongARM processors. More info at 374 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. 375 376config MTD_IXP4XX 377 tristate "CFI Flash device mapped on Intel IXP4xx based systems" 378 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX 379 help 380 This enables MTD access to flash devices on platforms based 381 on Intel's IXP4xx family of network processors such as the 382 IXDP425 and Coyote. If you have an IXP4xx based board and 383 would like to use the flash chips on it, say 'Y'. 384 385config MTD_IXP2000 386 tristate "CFI Flash device mapped on Intel IXP2000 based systems" 387 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 388 help 389 This enables MTD access to flash devices on platforms based 390 on Intel's IXP2000 family of network processors. If you have an 391 IXP2000 based board and would like to use the flash chips on it, 392 say 'Y'. 393 394config MTD_FORTUNET 395 tristate "CFI Flash device mapped on the FortuNet board" 396 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET 397 help 398 This enables access to the Flash on the FortuNet board. If you 399 have such a board, say 'Y'. 400 401config MTD_AUTCPU12 402 tristate "NV-RAM mapping AUTCPU12 board" 403 depends on ARCH_AUTCPU12 404 help 405 This enables access to the NV-RAM on autronix autcpu12 board. 406 If you have such a board, say 'Y'. 407 408config MTD_EDB7312 409 tristate "CFI Flash device mapped on EDB7312" 410 depends on ARCH_EDB7312 && MTD_CFI 411 help 412 This enables access to the CFI Flash on the Cogent EDB7312 board. 413 If you have such a board, say 'Y' here. 414 415config MTD_IMPA7 416 tristate "JEDEC Flash device mapped on impA7" 417 depends on ARM && MTD_JEDECPROBE 418 help 419 This enables access to the NOR Flash on the impA7 board of 420 implementa GmbH. If you have such a board, say 'Y' here. 421 422config MTD_CEIVA 423 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame" 424 depends on MTD_JEDECPROBE && ARCH_CEIVA 425 help 426 This enables access to the flash chips on the Ceiva/Polaroid 427 PhotoMax Digital Picture Frame. 428 If you have such a device, say 'Y'. 429 430config MTD_H720X 431 tristate "Hynix evaluation board mappings" 432 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 ) 433 help 434 This enables access to the flash chips on the Hynix evaluation boards. 435 If you have such a board, say 'Y'. 436 437config MTD_OMAP_NOR 438 tristate "TI OMAP board mappings" 439 depends on MTD_CFI && ARCH_OMAP 440 help 441 This enables access to the NOR flash chips on TI OMAP-based 442 boards defining flash platform devices and flash platform data. 443 These boards include the Innovator, H2, H3, OSK, Perseus2, and 444 more. If you have such a board, say 'Y'. 445 446# This needs CFI or JEDEC, depending on the cards found. 447config MTD_PCI 448 tristate "PCI MTD driver" 449 depends on PCI && MTD_COMPLEX_MAPPINGS 450 help 451 Mapping for accessing flash devices on add-in cards like the Intel XScale 452 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode 453 (please see the manual for the link settings). 454 455 If you are not sure, say N. 456 457config MTD_PCMCIA 458 tristate "PCMCIA MTD driver" 459 depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN 460 help 461 Map driver for accessing PCMCIA linear flash memory cards. These 462 cards are usually around 4-16MiB in size. This does not include 463 Compact Flash cards which are treated as IDE devices. 464 465config MTD_PCMCIA_ANONYMOUS 466 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards" 467 depends on MTD_PCMCIA 468 help 469 If this option is enabled, PCMCIA cards which do not report 470 anything about themselves are assumed to be MTD cards. 471 472 If unsure, say N. 473 474config MTD_BFIN_ASYNC 475 tristate "Blackfin BF533-STAMP Flash Chip Support" 476 depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS 477 select MTD_PARTITIONS 478 default y 479 help 480 Map driver which allows for simultaneous utilization of 481 ethernet and CFI parallel flash. 482 483 If compiled as a module, it will be called bfin-async-flash. 484 485config MTD_GPIO_ADDR 486 tristate "GPIO-assisted Flash Chip Support" 487 depends on GENERIC_GPIO || GPIOLIB 488 depends on MTD_COMPLEX_MAPPINGS 489 select MTD_PARTITIONS 490 help 491 Map driver which allows flashes to be partially physically addressed 492 and assisted by GPIOs. 493 494 If compiled as a module, it will be called gpio-addr-flash. 495 496config MTD_UCLINUX 497 bool "Generic uClinux RAM/ROM filesystem support" 498 depends on MTD_PARTITIONS && MTD_RAM=y && !MMU 499 help 500 Map driver to support image based filesystems for uClinux. 501 502config MTD_WRSBC8260 503 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board" 504 depends on (SBC82xx || SBC8560) 505 select MTD_PARTITIONS 506 select MTD_MAP_BANK_WIDTH_4 507 select MTD_MAP_BANK_WIDTH_1 508 select MTD_CFI_I1 509 select MTD_CFI_I4 510 help 511 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives 512 all three flash regions on CS0, CS1 and CS6 if they are configured 513 correctly by the boot loader. 514 515config MTD_DMV182 516 tristate "Map driver for Dy-4 SVME/DMV-182 board." 517 depends on DMV182 518 select MTD_PARTITIONS 519 select MTD_MAP_BANK_WIDTH_32 520 select MTD_CFI_I8 521 select MTD_CFI_AMDSTD 522 help 523 Map driver for Dy-4 SVME/DMV-182 board. 524 525config MTD_INTEL_VR_NOR 526 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0" 527 depends on PCI 528 help 529 Map driver for a NOR flash bank located on the Expansion Bus of the 530 Intel Vermilion Range chipset. 531 532config MTD_RBTX4939 533 tristate "Map driver for RBTX4939 board" 534 depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS 535 help 536 Map driver for NOR flash chips on RBTX4939 board. 537 538config MTD_PLATRAM 539 tristate "Map driver for platform device RAM (mtd-ram)" 540 select MTD_RAM 541 help 542 Map driver for RAM areas described via the platform device 543 system. 544 545 This selection automatically selects the map_ram driver. 546 547config MTD_VMU 548 tristate "Map driver for Dreamcast VMU" 549 depends on MAPLE 550 help 551 This driver enables access to the Dreamcast Visual Memory Unit (VMU). 552 553 Most Dreamcast users will want to say Y here. 554 555 To build this as a module select M here, the module will be called 556 vmu-flash. 557 558endmenu 559