drivers/mtd/maps/Kconfig

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