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