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