drivers/mtd/maps/Kconfig

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