1# drivers/mtd/maps/Kconfig 2# $Id: Kconfig,v 1.42 2005/01/05 16:59:50 dwmw2 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 11 This causes the chip drivers to allow for complicated 12 paged mappings of flash chips. 13 14config MTD_PHYSMAP 15 tristate "CFI Flash device in physical memory map" 16 depends on MTD_CFI 17 help 18 This provides a 'mapping' driver which allows the CFI probe and 19 command set driver code to communicate with flash chips which 20 are mapped physically into the CPU's memory. You will need to 21 configure the physical address and size of the flash chips on 22 your particular board as well as the bus width, either statically 23 with config options or at run-time. 24 25config MTD_PHYSMAP_START 26 hex "Physical start address of flash mapping" 27 depends on MTD_PHYSMAP 28 default "0x8000000" 29 help 30 This is the physical memory location at which the flash chips 31 are mapped on your particular target board. Refer to the 32 memory map which should hopefully be in the documentation for 33 your board. 34 Ignore this option if you use run-time physmap configuration 35 (i.e., run-time calling physmap_configure()). 36 37config MTD_PHYSMAP_LEN 38 hex "Physical length of flash mapping" 39 depends on MTD_PHYSMAP 40 default "0x4000000" 41 help 42 This is the total length of the mapping of the flash chips on 43 your particular board. If there is space, or aliases, in the 44 physical memory map between the chips, this could be larger 45 than the total amount of flash present. Refer to the memory 46 map which should hopefully be in the documentation for your 47 board. 48 Ignore this option if you use run-time physmap configuration 49 (i.e., run-time calling physmap_configure()). 50 51config MTD_PHYSMAP_BANKWIDTH 52 int "Bank width in octets" 53 depends on MTD_PHYSMAP 54 default "2" 55 help 56 This is the total width of the data bus of the flash devices 57 in octets. For example, if you have a data bus width of 32 58 bits, you would set the bus width octect value to 4. This is 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 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. 78 79config MTD_SC520CDP 80 tristate "CFI Flash device mapped on AMD SC520 CDP" 81 depends on X86 && MTD_CFI 82 help 83 The SC520 CDP board has two banks of CFI-compliant chips and one 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 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 X86 && MTD_JEDECPROBE && MTD_PARTITIONS 98 help 99 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 101 which are accessed as separate MTD devices. 102 103 mtd0 and mtd2 are the two BIOS drives. Unfortunately the BIOS 104 uses a proprietary flash translation layer from General Software, 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 109 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. 110 111 Note that jumper 3 ("Write Enable Drive A") must be set 112 otherwise detection won't succeeed. 113 114config MTD_SBC_GXX 115 tristate "CFI Flash device mapped on Arcom SBC-GXx boards" 116 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS 117 help 118 This provides a driver for the on-board flash of Arcom Control 119 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. 120 By default the flash is split into 3 partitions which are accessed 121 as separate MTD devices. This board utilizes Intel StrataFlash. 122 More info at 123 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>. 124 125config MTD_ELAN_104NC 126 tristate "CFI Flash device mapped on Arcom ELAN-104NC" 127 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS 128 help 129 This provides a driver for the on-board flash of the Arcom Control 130 System's ELAN-104NC development board. By default the flash 131 is split into 3 partitions which are accessed as separate MTD 132 devices. This board utilizes Intel StrataFlash. More info at 133 <http://www.arcomcontrols.com/products/icp/pc104/processors/ELAN104NC.htm>. 134 135config MTD_LUBBOCK 136 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board" 137 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS 138 help 139 This provides a driver for the on-board flash of the Intel 140 'Lubbock' XScale evaluation board. 141 142config MTD_OCTAGON 143 tristate "JEDEC Flash device mapped on Octagon 5066 SBC" 144 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS 145 help 146 This provides a 'mapping' driver which supports the way in which 147 the flash chips are connected in the Octagon-5066 Single Board 148 Computer. More information on the board is available at 149 <http://www.octagonsystems.com/CPUpages/5066.html>. 150 151config MTD_VMAX 152 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301" 153 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS 154 help 155 This provides a 'mapping' driver which supports the way in which 156 the flash chips are connected in the Tempustech VMAX SBC301 Single 157 Board Computer. More information on the board is available at 158 <http://www.tempustech.com/>. 159 160config MTD_SCx200_DOCFLASH 161 tristate "Flash device mapped with DOCCS on NatSemi SCx200" 162 depends on SCx200 && MTD_CFI && MTD_PARTITIONS 163 help 164 Enable support for a flash chip mapped using the DOCCS signal on a 165 National Semiconductor SCx200 processor. 166 167 If you don't know what to do here, say N. 168 169 If compiled as a module, it will be called scx200_docflash. 170 171config MTD_AMD76XROM 172 tristate "BIOS flash chip on AMD76x southbridge" 173 depends on X86 && MTD_JEDECPROBE 174 help 175 Support for treating the BIOS flash chip on AMD76x motherboards 176 as an MTD device - with this you can reprogram your BIOS. 177 178 BE VERY CAREFUL. 179 180config MTD_ICHXROM 181 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" 182 depends on X86 && MTD_JEDECPROBE 183 help 184 Support for treating the BIOS flash chip on ICHX motherboards 185 as an MTD device - with this you can reprogram your BIOS. 186 187 BE VERY CAREFUL. 188 189config MTD_SCB2_FLASH 190 tristate "BIOS flash chip on Intel SCB2 boards" 191 depends on X86 && MTD_JEDECPROBE 192 help 193 Support for treating the BIOS flash chip on Intel SCB2 boards 194 as an MTD device - with this you can reprogram your BIOS. 195 196 BE VERY CAREFUL. 197 198config MTD_TSUNAMI 199 tristate "Flash chips on Tsunami TIG bus" 200 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS 201 help 202 Support for the flash chip on Tsunami TIG bus. 203 204config MTD_LASAT 205 tristate "Flash chips on LASAT board" 206 depends on LASAT 207 help 208 Support for the flash chips on the Lasat 100 and 200 boards. 209 210config MTD_NETtel 211 tristate "CFI flash device on SnapGear/SecureEdge" 212 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE 213 help 214 Support for flash chips on NETtel/SecureEdge/SnapGear boards. 215 216config MTD_PB1XXX 217 tristate "Flash devices on Alchemy PB1xxx boards" 218 depends on MIPS && ( MIPS_PB1000 || MIPS_PB1100 || MIPS_PB1500 ) 219 help 220 Flash memory access on Alchemy Pb1000/Pb1100/Pb1500 boards 221 222config MTD_PB1XXX_BOOT 223 bool "PB1x00 boot flash device" 224 depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 ) 225 help 226 Use the first of the two 32MiB flash banks on Pb1100/Pb1500 board. 227 You can say 'Y' to both this and 'MTD_PB1XXX_USER' below, to use 228 both banks. 229 230config MTD_PB1XXX_USER 231 bool "PB1x00 user flash device" 232 depends on MTD_PB1XXX && ( MIPS_PB1100 || MIPS_PB1500 ) 233 default y if MTD_PB1XX_BOOT = n 234 help 235 Use the second of the two 32MiB flash banks on Pb1100/Pb1500 board. 236 You can say 'Y' to both this and 'MTD_PB1XXX_BOOT' above, to use 237 both banks. 238 239config MTD_PB1550 240 tristate "Flash devices on Alchemy PB1550 board" 241 depends on MIPS && MIPS_PB1550 242 help 243 Flash memory access on Alchemy Pb1550 board 244 245config MTD_PB1550_BOOT 246 bool "PB1550 boot flash device" 247 depends on MTD_PB1550 248 help 249 Use the first of the two 64MiB flash banks on Pb1550 board. 250 You can say 'Y' to both this and 'MTD_PB1550_USER' below, to use 251 both banks. 252 253config MTD_PB1550_USER 254 bool "PB1550 user flash device" 255 depends on MTD_PB1550 256 default y if MTD_PB1550_BOOT = n 257 help 258 Use the second of the two 64MiB flash banks on Pb1550 board. 259 You can say 'Y' to both this and 'MTD_PB1550_BOOT' above, to use 260 both banks. 261 262config MTD_DB1550 263 tristate "Flash devices on Alchemy DB1550 board" 264 depends on MIPS && MIPS_DB1550 265 help 266 Flash memory access on Alchemy Db1550 board 267 268config MTD_DB1550_BOOT 269 bool "DB1550 boot flash device" 270 depends on MTD_DB1550 271 help 272 Use the first of the two 64MiB flash banks on Db1550 board. 273 You can say 'Y' to both this and 'MTD_DB1550_USER' below, to use 274 both banks. 275 276config MTD_DB1550_USER 277 bool "DB1550 user flash device" 278 depends on MTD_DB1550 279 default y if MTD_DB1550_BOOT = n 280 help 281 Use the second of the two 64MiB flash banks on Db1550 board. 282 You can say 'Y' to both this and 'MTD_DB1550_BOOT' above, to use 283 both banks. 284 285config MTD_DILNETPC 286 tristate "CFI Flash device mapped on DIL/Net PC" 287 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT 288 help 289 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP". 290 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm> 291 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm> 292 293config MTD_DILNETPC_BOOTSIZE 294 hex "Size of DIL/Net PC flash boot partition" 295 depends on MTD_DILNETPC 296 default "0x80000" 297 help 298 The amount of space taken up by the kernel or Etherboot 299 on the DIL/Net PC flash chips. 300 301config MTD_L440GX 302 tristate "BIOS flash chip on Intel L440GX boards" 303 depends on X86 && MTD_JEDECPROBE 304 help 305 Support for treating the BIOS flash chip on Intel L440GX motherboards 306 as an MTD device - with this you can reprogram your BIOS. 307 308 BE VERY CAREFUL. 309 310config MTD_SBC8240 311 tristate "Flash device on SBC8240" 312 depends on PPC32 && MTD_JEDECPROBE && 6xx && 8260 313 help 314 Flash access on the SBC8240 board from Wind River. See 315 <http://www.windriver.com/products/sbc8240/> 316 317config MTD_TQM8XXL 318 tristate "CFI Flash device mapped on TQM8XXL" 319 depends on MTD_CFI && PPC32 && 8xx && TQM8xxL 320 help 321 The TQM8xxL PowerPC board has up to two banks of CFI-compliant 322 chips, currently uses AMD one. This 'mapping' driver supports 323 that arrangement, allowing the CFI probe and command set driver 324 code to communicate with the chips on the TQM8xxL board. More at 325 <http://www.denx.de/embedded-ppc-en.html>. 326 327config MTD_RPXLITE 328 tristate "CFI Flash device mapped on RPX Lite or CLLF" 329 depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE) 330 help 331 The RPXLite PowerPC board has CFI-compliant chips mapped in 332 a strange sparse mapping. This 'mapping' driver supports that 333 arrangement, allowing the CFI probe and command set driver code 334 to communicate with the chips on the RPXLite board. More at 335 <http://www.embeddedplanet.com/>. 336 337config MTD_MBX860 338 tristate "System flash on MBX860 board" 339 depends on MTD_CFI && PPC32 && 8xx && MBX 340 help 341 This enables access routines for the flash chips on the Motorola 342 MBX860 board. If you have one of these boards and would like 343 to use the flash chips on it, say 'Y'. 344 345config MTD_DBOX2 346 tristate "CFI Flash device mapped on D-Box2" 347 depends on PPC32 && 8xx && DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD 348 help 349 This enables access routines for the flash chips on the Nokia/Sagem 350 D-Box 2 board. If you have one of these boards and would like to use 351 the flash chips on it, say 'Y'. 352 353config MTD_CFI_FLAGADM 354 tristate "CFI Flash device mapping on FlagaDM" 355 depends on PPC32 && 8xx && MTD_CFI 356 help 357 Mapping for the Flaga digital module. If you don't have one, ignore 358 this setting. 359 360config MTD_BEECH 361 tristate "CFI Flash device mapped on IBM 405LP Beech" 362 depends on MTD_CFI && PPC32 && 40x && BEECH 363 help 364 This enables access routines for the flash chips on the IBM 365 405LP Beech board. If you have one of these boards and would like 366 to use the flash chips on it, say 'Y'. 367 368config MTD_ARCTIC 369 tristate "CFI Flash device mapped on IBM 405LP Arctic" 370 depends on MTD_CFI && PPC32 && 40x && ARCTIC2 371 help 372 This enables access routines for the flash chips on the IBM 405LP 373 Arctic board. If you have one of these boards and would like to 374 use the flash chips on it, say 'Y'. 375 376config MTD_WALNUT 377 tristate "Flash device mapped on IBM 405GP Walnut" 378 depends on MTD_JEDECPROBE && PPC32 && 40x && WALNUT 379 help 380 This enables access routines for the flash chips on the IBM 405GP 381 Walnut board. If you have one of these boards and would like to 382 use the flash chips on it, say 'Y'. 383 384config MTD_EBONY 385 tristate "Flash devices mapped on IBM 440GP Ebony" 386 depends on MTD_JEDECPROBE && PPC32 && 44x && EBONY 387 help 388 This enables access routines for the flash chips on the IBM 440GP 389 Ebony board. If you have one of these boards and would like to 390 use the flash chips on it, say 'Y'. 391 392config MTD_OCOTEA 393 tristate "Flash devices mapped on IBM 440GX Ocotea" 394 depends on MTD_CFI && PPC32 && 44x && OCOTEA 395 help 396 This enables access routines for the flash chips on the IBM 440GX 397 Ocotea board. If you have one of these boards and would like to 398 use the flash chips on it, say 'Y'. 399 400config MTD_REDWOOD 401 tristate "CFI Flash devices mapped on IBM Redwood" 402 depends on MTD_CFI && PPC32 && 4xx && 40x && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 ) 403 help 404 This enables access routines for the flash chips on the IBM 405 Redwood board. If you have one of these boards and would like to 406 use the flash chips on it, say 'Y'. 407 408config MTD_CSTM_MIPS_IXX 409 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board" 410 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS 411 help 412 This provides a mapping driver for the Integrated Technology 413 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR 414 Reference Board. It provides the necessary addressing, length, 415 buswidth, vpp code and addition setup of the flash device for 416 these boards. In addition, this mapping driver can be used for 417 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/ 418 LEN/BUSWIDTH parameters. This mapping will provide one mtd device 419 using one partition. The start address can be offset from the 420 beginning of flash and the len can be less than the total flash 421 device size to allow a window into the flash. Both CFI and JEDEC 422 probes are called. 423 424config MTD_CSTM_MIPS_IXX_START 425 hex "Physical start address of flash mapping" 426 depends on MTD_CSTM_MIPS_IXX 427 default "0x8000000" 428 help 429 This is the physical memory location that the MTD driver will 430 use for the flash chips on your particular target board. 431 Refer to the memory map which should hopefully be in the 432 documentation for your board. 433 434config MTD_CSTM_MIPS_IXX_LEN 435 hex "Physical length of flash mapping" 436 depends on MTD_CSTM_MIPS_IXX 437 default "0x4000000" 438 help 439 This is the total length that the MTD driver will use for the 440 flash chips on your particular board. Refer to the memory 441 map which should hopefully be in the documentation for your 442 board. 443 444config MTD_CSTM_MIPS_IXX_BUSWIDTH 445 int "Bus width in octets" 446 depends on MTD_CSTM_MIPS_IXX 447 default "2" 448 help 449 This is the total bus width of the mapping of the flash chips 450 on your particular board. 451 452config MTD_OCELOT 453 tristate "Momenco Ocelot boot flash device" 454 depends on MIPS && MOMENCO_OCELOT 455 help 456 This enables access routines for the boot flash device and for the 457 NVRAM on the Momenco Ocelot board. If you have one of these boards 458 and would like access to either of these, say 'Y'. 459 460config MTD_SOLUTIONENGINE 461 tristate "CFI Flash device mapped on Hitachi SolutionEngine" 462 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS 463 help 464 This enables access to the flash chips on the Hitachi SolutionEngine and 465 similar boards. Say 'Y' if you are building a kernel for such a board. 466 467config MTD_ARM_INTEGRATOR 468 tristate "CFI Flash device mapped on ARM Integrator/P720T" 469 depends on ARM && MTD_CFI 470 471config MTD_CDB89712 472 tristate "Cirrus CDB89712 evaluation board mappings" 473 depends on ARM && MTD_CFI && ARCH_CDB89712 474 help 475 This enables access to the flash or ROM chips on the CDB89712 board. 476 If you have such a board, say 'Y'. 477 478config MTD_SA1100 479 tristate "CFI Flash device mapped on StrongARM SA11x0" 480 depends on ARM && MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS 481 help 482 This enables access to the flash chips on most platforms based on 483 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. 484 If you have such a board, say 'Y'. 485 486config MTD_IPAQ 487 tristate "CFI Flash device mapped on Compaq/HP iPAQ" 488 depends on ARM && IPAQ_HANDHELD && MTD_CFI 489 help 490 This provides a driver for the on-board flash of the iPAQ. 491 492config MTD_DC21285 493 tristate "CFI Flash device mapped on DC21285 Footbridge" 494 depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS 495 help 496 This provides a driver for the flash accessed using Intel's 497 21285 bridge used with Intel's StrongARM processors. More info at 498 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. 499 500config MTD_IQ80310 501 tristate "CFI Flash device mapped on the XScale IQ80310 board" 502 depends on ARM && MTD_CFI && ARCH_IQ80310 503 help 504 This enables access routines for the flash chips on the Intel XScale 505 IQ80310 evaluation board. If you have one of these boards and would 506 like to use the flash chips on it, say 'Y'. 507 508config MTD_IXP4XX 509 tristate "CFI Flash device mapped on Intel IXP4xx based systems" 510 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX 511 help 512 This enables MTD access to flash devices on platforms based 513 on Intel's IXP4xx family of network processors such as the 514 IXDP425 and Coyote. If you have an IXP4xx based board and 515 would like to use the flash chips on it, say 'Y'. 516 517config MTD_IXP2000 518 tristate "CFI Flash device mapped on Intel IXP2000 based systems" 519 depends on ARM && MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 520 help 521 This enables MTD access to flash devices on platforms based 522 on Intel's IXP2000 family of network processors such as the 523 IXDP425 and Coyote. If you have an IXP2000 based board and 524 would like to use the flash chips on it, say 'Y'. 525 526config MTD_EPXA10DB 527 tristate "CFI Flash device mapped on Epxa10db" 528 depends on ARM && MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT 529 help 530 This enables support for the flash devices on the Altera 531 Excalibur XA10 Development Board. If you are building a kernel 532 for on of these boards then you should say 'Y' otherwise say 'N'. 533 534config MTD_FORTUNET 535 tristate "CFI Flash device mapped on the FortuNet board" 536 depends on ARM && MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET 537 help 538 This enables access to the Flash on the FortuNet board. If you 539 have such a board, say 'Y'. 540 541config MTD_AUTCPU12 542 tristate "NV-RAM mapping AUTCPU12 board" 543 depends on ARM && ARCH_AUTCPU12 544 help 545 This enables access to the NV-RAM on autronix autcpu12 board. 546 If you have such a board, say 'Y'. 547 548config MTD_EDB7312 549 tristate "CFI Flash device mapped on EDB7312" 550 depends on ARM && MTD_CFI 551 help 552 This enables access to the CFI Flash on the Cogent EDB7312 board. 553 If you have such a board, say 'Y' here. 554 555config MTD_IMPA7 556 tristate "JEDEC Flash device mapped on impA7" 557 depends on ARM && MTD_JEDECPROBE 558 help 559 This enables access to the NOR Flash on the impA7 board of 560 implementa GmbH. If you have such a board, say 'Y' here. 561 562config MTD_CEIVA 563 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame" 564 depends on ARM && MTD_JEDECPROBE && ARCH_CEIVA 565 help 566 This enables access to the flash chips on the Ceiva/Polaroid 567 PhotoMax Digital Picture Frame. 568 If you have such a device, say 'Y'. 569 570config MTD_NOR_TOTO 571 tristate "NOR Flash device on TOTO board" 572 depends on ARM && ARCH_OMAP && OMAP_TOTO 573 help 574 This enables access to the NOR flash on the Texas Instruments 575 TOTO board. 576 577config MTD_H720X 578 tristate "Hynix evaluation board mappings" 579 depends on ARM && MTD_CFI && ( ARCH_H7201 || ARCH_H7202 ) 580 help 581 This enables access to the flash chips on the Hynix evaluation boards. 582 If you have such a board, say 'Y'. 583 584config MTD_MPC1211 585 tristate "CFI Flash device mapped on Interface MPC-1211" 586 depends on SUPERH && SH_MPC1211 && MTD_CFI 587 help 588 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02). 589 If you have such a board, say 'Y'. 590 591# This needs CFI or JEDEC, depending on the cards found. 592config MTD_PCI 593 tristate "PCI MTD driver" 594 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS 595 help 596 Mapping for accessing flash devices on add-in cards like the Intel XScale 597 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode 598 (please see the manual for the link settings). 599 600 If you are not sure, say N. 601 602config MTD_PCMCIA 603 tristate "PCMCIA MTD driver" 604 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN 605 help 606 Map driver for accessing PCMCIA linear flash memory cards. These 607 cards are usually around 4-16MiB in size. This does not include 608 Compact Flash cards which are treated as IDE devices. 609 610config MTD_UCLINUX 611 tristate "Generic uClinux RAM/ROM filesystem support" 612 depends on MTD_PARTITIONS && !MMU 613 help 614 Map driver to support image based filesystems for uClinux. 615 616config MTD_WRSBC8260 617 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board" 618 depends on (SBC82xx || SBC8560) 619 select MTD_PARTITIONS 620 select MTD_MAP_BANK_WIDTH_4 621 select MTD_MAP_BANK_WIDTH_1 622 select MTD_CFI_I1 623 select MTD_CFI_I4 624 help 625 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives 626 all three flash regions on CS0, CS1 and CS6 if they are configured 627 correctly by the boot loader. 628 629config MTD_DMV182 630 tristate "Map driver for Dy-4 SVME/DMV-182 board." 631 depends on DMV182 632 select MTD_PARTITIONS 633 select MTD_MAP_BANK_WIDTH_32 634 select MTD_CFI_I8 635 select MTD_CFI_AMDSTD 636 help 637 Map driver for Dy-4 SVME/DMV-182 board. 638 639config MTD_BAST 640 tristate "Map driver for Simtec BAST (EB2410ITX)" 641 depends on ARCH_BAST 642 select MTD_PARTITIONS 643 select MTD_MAP_BANK_WIDTH_16 644 select MTD_JEDECPROBE 645 help 646 Map driver for NOR flash on the Simtec BAST (EB2410ITX). 647 648 Note, this driver *cannot* over-ride the WP link on the 649 board, or currently detect the state of the link. 650 651config MTD_BAST_MAXSIZE 652 int "Maximum size for BAST flash area (MiB)" 653 depends on MTD_BAST 654 default "4" 655 656config MTD_SHARP_SL 657 bool "ROM maped on Sharp SL Series" 658 depends on MTD && ARCH_PXA 659 help 660 This enables access to the flash chip on the Sharp SL Series of PDAs. 661 662endmenu 663 664