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 description"
  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_WALNUT
 362         tristate "Flash device mapped on IBM 405GP Walnut"
 363         depends on MTD_JEDECPROBE && WALNUT
 364         help
 365           This enables access routines for the flash chips on the IBM 405GP
 366           Walnut board. If you have one of these boards and would like to
 367           use the flash chips on it, say 'Y'.
 368
 369 config MTD_EBONY
 370         tristate "Flash devices mapped on IBM 440GP Ebony"
 371         depends on MTD_JEDECPROBE && EBONY
 372         help
 373           This enables access routines for the flash chips on the IBM 440GP
 374           Ebony 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_OCOTEA
 378         tristate "Flash devices mapped on IBM 440GX Ocotea"
 379         depends on MTD_CFI && OCOTEA
 380         help
 381           This enables access routines for the flash chips on the IBM 440GX
 382           Ocotea 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_REDWOOD
 386         tristate "CFI Flash devices mapped on IBM Redwood"
 387         depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
 388         help
 389           This enables access routines for the flash chips on the IBM
 390           Redwood 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_TQM834x
 394         tristate "Flash device mapped on TQ Components TQM834x Boards"
 395         depends on MTD_CFI && TQM834x
 396         help
 397           This enables access routines for the flash chips on the
 398           TQ Components TQM834x boards. If you have one of these boards
 399           and would like to use the flash chips on it, say 'Y'.
 400
 401 config MTD_OCELOT
 402         tristate "Momenco Ocelot boot flash device"
 403         depends on MOMENCO_OCELOT
 404         help
 405           This enables access routines for the boot flash device and for the
 406           NVRAM on the Momenco Ocelot board. If you have one of these boards
 407           and would like access to either of these, say 'Y'.
 408
 409 config MTD_SOLUTIONENGINE
 410         tristate "CFI Flash device mapped on Hitachi SolutionEngine"
 411         depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
 412         help
 413           This enables access to the flash chips on the Hitachi SolutionEngine and
 414           similar boards. Say 'Y' if you are building a kernel for such a board.
 415
 416 config MTD_ARM_INTEGRATOR
 417         tristate "CFI Flash device mapped on ARM Integrator/P720T"
 418         depends on ARM && MTD_CFI
 419
 420 config MTD_CDB89712
 421         tristate "Cirrus CDB89712 evaluation board mappings"
 422         depends on MTD_CFI && ARCH_CDB89712
 423         help
 424           This enables access to the flash or ROM chips on the CDB89712 board.
 425           If you have such a board, say 'Y'.
 426
 427 config MTD_SA1100
 428         tristate "CFI Flash device mapped on StrongARM SA11x0"
 429         depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
 430         help
 431           This enables access to the flash chips on most platforms based on
 432           the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
 433           If you have such a board, say 'Y'.
 434
 435 config MTD_IPAQ
 436         tristate "CFI Flash device mapped on Compaq/HP iPAQ"
 437         depends on IPAQ_HANDHELD && MTD_CFI
 438         help
 439           This provides a driver for the on-board flash of the iPAQ.
 440
 441 config MTD_DC21285
 442         tristate "CFI Flash device mapped on DC21285 Footbridge"
 443         depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
 444         help
 445           This provides a driver for the flash accessed using Intel's
 446           21285 bridge used with Intel's StrongARM processors. More info at
 447           <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
 448
 449 config MTD_IXP4XX
 450         tristate "CFI Flash device mapped on Intel IXP4xx based systems"
 451         depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
 452         help
 453           This enables MTD access to flash devices on platforms based
 454           on Intel's IXP4xx family of network processors such as the
 455           IXDP425 and Coyote. If you have an IXP4xx based board and
 456           would like to use the flash chips on it, say 'Y'.
 457
 458 config MTD_IXP2000
 459         tristate "CFI Flash device mapped on Intel IXP2000 based systems"
 460         depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
 461         help
 462           This enables MTD access to flash devices on platforms based
 463           on Intel's IXP2000 family of network processors such as the
 464           IXDP425 and Coyote. If you have an IXP2000 based board and
 465           would like to use the flash chips on it, say 'Y'.
 466
 467 config MTD_FORTUNET
 468         tristate "CFI Flash device mapped on the FortuNet board"
 469         depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
 470         help
 471           This enables access to the Flash on the FortuNet board.  If you
 472           have such a board, say 'Y'.
 473
 474 config MTD_AUTCPU12
 475         tristate "NV-RAM mapping AUTCPU12 board"
 476         depends on ARCH_AUTCPU12
 477         help
 478           This enables access to the NV-RAM on autronix autcpu12 board.
 479           If you have such a board, say 'Y'.
 480
 481 config MTD_EDB7312
 482         tristate "CFI Flash device mapped on EDB7312"
 483         depends on ARCH_EDB7312 && MTD_CFI
 484         help
 485           This enables access to the CFI Flash on the Cogent EDB7312 board.
 486           If you have such a board, say 'Y' here.
 487
 488 config MTD_IMPA7
 489         tristate "JEDEC Flash device mapped on impA7"
 490         depends on ARM && MTD_JEDECPROBE
 491         help
 492           This enables access to the NOR Flash on the impA7 board of
 493           implementa GmbH. If you have such a board, say 'Y' here.
 494
 495 config MTD_CEIVA
 496         tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
 497         depends on MTD_JEDECPROBE && ARCH_CEIVA
 498         help
 499           This enables access to the flash chips on the Ceiva/Polaroid
 500           PhotoMax Digital Picture Frame.
 501           If you have such a device, say 'Y'.
 502
 503 config MTD_NOR_TOTO
 504         tristate "NOR Flash device on TOTO board"
 505         depends on ARCH_OMAP && OMAP_TOTO
 506         help
 507           This enables access to the NOR flash on the Texas Instruments
 508           TOTO board.
 509
 510 config MTD_H720X
 511         tristate "Hynix evaluation board mappings"
 512         depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
 513         help
 514           This enables access to the flash chips on the Hynix evaluation boards.
 515           If you have such a board, say 'Y'.
 516
 517 config MTD_MPC1211
 518         tristate "CFI Flash device mapped on Interface MPC-1211"
 519         depends on SH_MPC1211 && MTD_CFI
 520         help
 521           This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
 522           If you have such a board, say 'Y'.
 523
 524 config MTD_OMAP_NOR
 525         tristate "TI OMAP board mappings"
 526         depends on MTD_CFI && ARCH_OMAP
 527         help
 528           This enables access to the NOR flash chips on TI OMAP-based
 529           boards defining flash platform devices and flash platform data.
 530           These boards include the Innovator, H2, H3, OSK, Perseus2, and
 531           more.  If you have such a board, say 'Y'.
 532
 533 # This needs CFI or JEDEC, depending on the cards found.
 534 config MTD_PCI
 535         tristate "PCI MTD driver"
 536         depends on PCI && MTD_COMPLEX_MAPPINGS
 537         help
 538           Mapping for accessing flash devices on add-in cards like the Intel XScale
 539           IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
 540           (please see the manual for the link settings).
 541
 542           If you are not sure, say N.
 543
 544 config MTD_PCMCIA
 545         tristate "PCMCIA MTD driver"
 546         depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
 547         help
 548           Map driver for accessing PCMCIA linear flash memory cards. These
 549           cards are usually around 4-16MiB in size. This does not include
 550           Compact Flash cards which are treated as IDE devices.
 551
 552 config MTD_PCMCIA_ANONYMOUS
 553         bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
 554         depends on MTD_PCMCIA
 555         help
 556           If this option is enabled, PCMCIA cards which do not report
 557           anything about themselves are assumed to be MTD cards.
 558
 559           If unsure, say N.
 560
 561 config MTD_UCLINUX
 562         tristate "Generic uClinux RAM/ROM filesystem support"
 563         depends on MTD_PARTITIONS && !MMU
 564         help
 565           Map driver to support image based filesystems for uClinux.
 566
 567 config MTD_WRSBC8260
 568         tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
 569         depends on (SBC82xx || SBC8560)
 570         select MTD_PARTITIONS
 571         select MTD_MAP_BANK_WIDTH_4
 572         select MTD_MAP_BANK_WIDTH_1
 573         select MTD_CFI_I1
 574         select MTD_CFI_I4
 575         help
 576           Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
 577           all three flash regions on CS0, CS1 and CS6 if they are configured
 578           correctly by the boot loader.
 579
 580 config MTD_DMV182
 581         tristate "Map driver for Dy-4 SVME/DMV-182 board."
 582         depends on DMV182
 583         select MTD_PARTITIONS
 584         select MTD_MAP_BANK_WIDTH_32
 585         select MTD_CFI_I8
 586         select MTD_CFI_AMDSTD
 587         help
 588           Map driver for Dy-4 SVME/DMV-182 board.
 589
 590 config MTD_BAST
 591         tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
 592         depends on ARCH_BAST || MACH_VR1000
 593         select MTD_PARTITIONS
 594         select MTD_MAP_BANK_WIDTH_16
 595         select MTD_JEDECPROBE
 596         help
 597           Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
 598           Thorcom VR1000
 599
 600           Note, this driver *cannot* over-ride the WP link on the
 601           board, or currently detect the state of the link.
 602
 603 config MTD_BAST_MAXSIZE
 604         int "Maximum size for BAST flash area (MiB)"
 605         depends on MTD_BAST
 606         default "4"
 607
 608 config MTD_SHARP_SL
 609         bool "ROM mapped on Sharp SL Series"
 610         depends on ARCH_PXA
 611         help
 612           This enables access to the flash chip on the Sharp SL Series of PDAs.
 613
 614 config MTD_PLATRAM
 615         tristate "Map driver for platform device RAM (mtd-ram)"
 616         select MTD_RAM
 617         help
 618           Map driver for RAM areas described via the platform device
 619           system.
 620
 621           This selection automatically selects the map_ram driver.
 622
 623 endmenu
 624