1menu "Mapping drivers for chip access" 2 depends on MTD!=n 3 depends on HAS_IOMEM 4 5config MTD_COMPLEX_MAPPINGS 6 bool "Support non-linear mappings of flash chips" 7 help 8 This causes the chip drivers to allow for complicated 9 paged mappings of flash chips. 10 11config MTD_PHYSMAP 12 tristate "Flash device in physical memory map" 13 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR 14 help 15 This provides a 'mapping' driver which allows the NOR Flash and 16 ROM driver code to communicate with chips which are mapped 17 physically into the CPU's memory. You will need to configure 18 the physical address and size of the flash chips on your 19 particular board as well as the bus width, either statically 20 with config options or at run-time. 21 22 To compile this driver as a module, choose M here: the 23 module will be called physmap. 24 25config MTD_PHYSMAP_COMPAT 26 bool "Physmap compat support" 27 depends on MTD_PHYSMAP 28 default n 29 help 30 Setup a simple mapping via the Kconfig options. Normally the 31 physmap configuration options are done via your board's 32 resource file. 33 34 If unsure, say N here. 35 36config MTD_PHYSMAP_START 37 hex "Physical start address of flash mapping" 38 depends on MTD_PHYSMAP_COMPAT 39 default "0x8000000" 40 help 41 This is the physical memory location at which the flash chips 42 are mapped on your particular target board. Refer to the 43 memory map which should hopefully be in the documentation for 44 your board. 45 46config MTD_PHYSMAP_LEN 47 hex "Physical length of flash mapping" 48 depends on MTD_PHYSMAP_COMPAT 49 default "0" 50 help 51 This is the total length of the mapping of the flash chips on 52 your particular board. If there is space, or aliases, in the 53 physical memory map between the chips, this could be larger 54 than the total amount of flash present. Refer to the memory 55 map which should hopefully be in the documentation for your 56 board. 57 58config MTD_PHYSMAP_BANKWIDTH 59 int "Bank width in octets" 60 depends on MTD_PHYSMAP_COMPAT 61 default "2" 62 help 63 This is the total width of the data bus of the flash devices 64 in octets. For example, if you have a data bus width of 32 65 bits, you would set the bus width octet value to 4. This is 66 used internally by the CFI drivers. 67 68config MTD_PHYSMAP_OF 69 bool "Memory device in physical memory map based on OF description" 70 depends on OF && MTD_PHYSMAP 71 help 72 This provides a 'mapping' driver which allows the NOR Flash, ROM 73 and RAM driver code to communicate with chips which are mapped 74 physically into the CPU's memory. The mapping description here is 75 taken from OF device tree. 76 77config MTD_PHYSMAP_VERSATILE 78 bool "ARM Versatile OF-based physical memory map handling" 79 depends on MTD_PHYSMAP_OF 80 depends on MFD_SYSCON 81 default y if (ARCH_INTEGRATOR || ARCH_VERSATILE || ARCH_REALVIEW) 82 help 83 This provides some extra DT physmap parsing for the ARM Versatile 84 platforms, basically to add a VPP (write protection) callback so 85 the flash can be taken out of write protection. 86 87config MTD_PHYSMAP_GEMINI 88 bool "Cortina Gemini OF-based physical memory map handling" 89 depends on MTD_PHYSMAP_OF 90 depends on MFD_SYSCON 91 default ARCH_GEMINI 92 help 93 This provides some extra DT physmap parsing for the Gemini 94 platforms, some detection and setting up parallel mode on the 95 external interface. 96 97config MTD_PHYSMAP_GPIO_ADDR 98 bool "GPIO-assisted Flash Chip Support" 99 depends on MTD_PHYSMAP 100 depends on GPIOLIB || COMPILE_TEST 101 depends on MTD_COMPLEX_MAPPINGS 102 help 103 Extend the physmap driver to allow flashes to be partially 104 physically addressed and assisted by GPIOs. 105 106config MTD_PMC_MSP_EVM 107 tristate "CFI Flash device mapped on PMC-Sierra MSP" 108 depends on PMC_MSP && MTD_CFI 109 help 110 This provides a 'mapping' driver which supports the way 111 in which user-programmable flash chips are connected on the 112 PMC-Sierra MSP eval/demo boards. 113 114choice 115 prompt "Maximum mappable memory available for flash IO" 116 depends on MTD_PMC_MSP_EVM 117 default MSP_FLASH_MAP_LIMIT_32M 118 119config MSP_FLASH_MAP_LIMIT_32M 120 bool "32M" 121 122endchoice 123 124config MSP_FLASH_MAP_LIMIT 125 hex 126 default "0x02000000" 127 depends on MSP_FLASH_MAP_LIMIT_32M 128 129config MTD_SUN_UFLASH 130 tristate "Sun Microsystems userflash support" 131 depends on SPARC && MTD_CFI && PCI 132 help 133 This provides a 'mapping' driver which supports the way in 134 which user-programmable flash chips are connected on various 135 Sun Microsystems boardsets. This driver will require CFI support 136 in the kernel, so if you did not enable CFI previously, do that now. 137 138config MTD_SC520CDP 139 tristate "CFI Flash device mapped on AMD SC520 CDP" 140 depends on (MELAN || COMPILE_TEST) && MTD_CFI 141 help 142 The SC520 CDP board has two banks of CFI-compliant chips and one 143 Dual-in-line JEDEC chip. This 'mapping' driver supports that 144 arrangement, implementing three MTD devices. 145 146config MTD_NETSC520 147 tristate "CFI Flash device mapped on AMD NetSc520" 148 depends on (MELAN || COMPILE_TEST) && MTD_CFI 149 help 150 This enables access routines for the flash chips on the AMD NetSc520 151 demonstration board. If you have one of these boards and would like 152 to use the flash chips on it, say 'Y'. 153 154config MTD_TS5500 155 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" 156 depends on TS5500 || COMPILE_TEST 157 select MTD_JEDECPROBE 158 select MTD_CFI_AMDSTD 159 help 160 This provides a driver for the on-board flash of the Technologic 161 System's TS-5500 board. The 2MB flash is split into 3 partitions 162 which are accessed as separate MTD devices. 163 164 mtd0 and mtd2 are the two BIOS drives, which use the resident 165 flash disk (RFD) flash translation layer. 166 167 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. 168 169 Note that jumper 3 ("Write Enable Drive A") must be set 170 otherwise detection won't succeed. 171 172config MTD_SBC_GXX 173 tristate "CFI Flash device mapped on Arcom SBC-GXx boards" 174 depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS 175 help 176 This provides a driver for the on-board flash of Arcom Control 177 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. 178 By default the flash is split into 3 partitions which are accessed 179 as separate MTD devices. This board utilizes Intel StrataFlash. 180 More info at 181 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>. 182 183config MTD_PXA2XX 184 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards" 185 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT 186 help 187 This provides a driver for the NOR flash attached to a PXA2xx chip. 188 189config MTD_SCx200_DOCFLASH 190 tristate "Flash device mapped with DOCCS on NatSemi SCx200" 191 depends on SCx200 && MTD_CFI 192 help 193 Enable support for a flash chip mapped using the DOCCS signal on a 194 National Semiconductor SCx200 processor. 195 196 If you don't know what to do here, say N. 197 198 If compiled as a module, it will be called scx200_docflash. 199 200config MTD_AMD76XROM 201 tristate "BIOS flash chip on AMD76x southbridge" 202 depends on X86 && MTD_JEDECPROBE 203 help 204 Support for treating the BIOS flash chip on AMD76x motherboards 205 as an MTD device - with this you can reprogram your BIOS. 206 207 BE VERY CAREFUL. 208 209config MTD_ICHXROM 210 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" 211 depends on X86 && MTD_JEDECPROBE 212 help 213 Support for treating the BIOS flash chip on ICHX motherboards 214 as an MTD device - with this you can reprogram your BIOS. 215 216 BE VERY CAREFUL. 217 218config MTD_ESB2ROM 219 tristate "BIOS flash chip on Intel ESB Controller Hub 2" 220 depends on X86 && MTD_JEDECPROBE && PCI 221 help 222 Support for treating the BIOS flash chip on ESB2 motherboards 223 as an MTD device - with this you can reprogram your BIOS. 224 225 BE VERY CAREFUL. 226 227config MTD_CK804XROM 228 tristate "BIOS flash chip on Nvidia CK804" 229 depends on X86 && MTD_JEDECPROBE && PCI 230 help 231 Support for treating the BIOS flash chip on nvidia motherboards 232 as an MTD device - with this you can reprogram your BIOS. 233 234 BE VERY CAREFUL. 235 236config MTD_SCB2_FLASH 237 tristate "BIOS flash chip on Intel SCB2 boards" 238 depends on X86 && MTD_JEDECPROBE && PCI 239 help 240 Support for treating the BIOS flash chip on Intel SCB2 boards 241 as an MTD device - with this you can reprogram your BIOS. 242 243 BE VERY CAREFUL. 244 245config MTD_TSUNAMI 246 tristate "Flash chips on Tsunami TIG bus" 247 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS 248 help 249 Support for the flash chip on Tsunami TIG bus. 250 251config MTD_NETtel 252 tristate "CFI flash device on SnapGear/SecureEdge" 253 depends on X86 && MTD_JEDECPROBE 254 help 255 Support for flash chips on NETtel/SecureEdge/SnapGear boards. 256 257config MTD_LANTIQ 258 tristate "Lantiq SoC NOR support" 259 depends on LANTIQ 260 help 261 Support for NOR flash attached to the Lantiq SoC's External Bus Unit. 262 263config MTD_L440GX 264 tristate "BIOS flash chip on Intel L440GX boards" 265 depends on X86 && MTD_JEDECPROBE 266 help 267 Support for treating the BIOS flash chip on Intel L440GX motherboards 268 as an MTD device - with this you can reprogram your BIOS. 269 270 BE VERY CAREFUL. 271 272config MTD_CFI_FLAGADM 273 tristate "CFI Flash device mapping on FlagaDM" 274 depends on PPC_8xx && MTD_CFI 275 help 276 Mapping for the Flaga digital module. If you don't have one, ignore 277 this setting. 278 279config MTD_SOLUTIONENGINE 280 tristate "CFI Flash device mapped on Hitachi SolutionEngine" 281 depends on SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS 282 help 283 This enables access to the flash chips on the Hitachi SolutionEngine and 284 similar boards. Say 'Y' if you are building a kernel for such a board. 285 286config MTD_SA1100 287 tristate "CFI Flash device mapped on StrongARM SA11x0" 288 depends on MTD_CFI && ARCH_SA1100 289 help 290 This enables access to the flash chips on most platforms based on 291 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. 292 If you have such a board, say 'Y'. 293 294config MTD_DC21285 295 tristate "CFI Flash device mapped on DC21285 Footbridge" 296 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS 297 help 298 This provides a driver for the flash accessed using Intel's 299 21285 bridge used with Intel's StrongARM processors. More info at 300 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. 301 302config MTD_IXP4XX 303 tristate "CFI Flash device mapped on Intel IXP4xx based systems" 304 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX 305 help 306 This enables MTD access to flash devices on platforms based 307 on Intel's IXP4xx family of network processors such as the 308 IXDP425 and Coyote. If you have an IXP4xx based board and 309 would like to use the flash chips on it, say 'Y'. 310 311config MTD_IMPA7 312 tristate "JEDEC Flash device mapped on impA7" 313 depends on ARM && MTD_JEDECPROBE 314 help 315 This enables access to the NOR Flash on the impA7 board of 316 implementa GmbH. If you have such a board, say 'Y' here. 317 318# This needs CFI or JEDEC, depending on the cards found. 319config MTD_PCI 320 tristate "PCI MTD driver" 321 depends on PCI && MTD_COMPLEX_MAPPINGS 322 help 323 Mapping for accessing flash devices on add-in cards like the Intel XScale 324 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode 325 (please see the manual for the link settings). 326 327 If you are not sure, say N. 328 329config MTD_PCMCIA 330 tristate "PCMCIA MTD driver" 331 depends on PCMCIA && MTD_COMPLEX_MAPPINGS 332 help 333 Map driver for accessing PCMCIA linear flash memory cards. These 334 cards are usually around 4-16MiB in size. This does not include 335 Compact Flash cards which are treated as IDE devices. 336 337config MTD_PCMCIA_ANONYMOUS 338 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards" 339 depends on MTD_PCMCIA 340 help 341 If this option is enabled, PCMCIA cards which do not report 342 anything about themselves are assumed to be MTD cards. 343 344 If unsure, say N. 345 346config MTD_UCLINUX 347 bool "Generic uClinux RAM/ROM filesystem support" 348 depends on (MTD_RAM=y || MTD_ROM=y) && (!MMU || COLDFIRE) 349 help 350 Map driver to support image based filesystems for uClinux. 351 352config MTD_INTEL_VR_NOR 353 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0" 354 depends on PCI 355 help 356 Map driver for a NOR flash bank located on the Expansion Bus of the 357 Intel Vermilion Range chipset. 358 359config MTD_RBTX4939 360 tristate "Map driver for RBTX4939 board" 361 depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS 362 help 363 Map driver for NOR flash chips on RBTX4939 board. 364 365config MTD_PLATRAM 366 tristate "Map driver for platform device RAM (mtd-ram)" 367 select MTD_RAM 368 help 369 Map driver for RAM areas described via the platform device 370 system. 371 372 This selection automatically selects the map_ram driver. 373 374config MTD_VMU 375 tristate "Map driver for Dreamcast VMU" 376 depends on MAPLE 377 help 378 This driver enables access to the Dreamcast Visual Memory Unit (VMU). 379 380 Most Dreamcast users will want to say Y here. 381 382 To build this as a module select M here, the module will be called 383 vmu-flash. 384 385config MTD_PISMO 386 tristate "MTD discovery driver for PISMO modules" 387 depends on I2C 388 depends on ARCH_VERSATILE 389 help 390 This driver allows for discovery of PISMO modules - see 391 <http://www.pismoworld.org/>. These are small modules containing 392 up to five memory devices (eg, SRAM, flash, DOC) described by an 393 I2C EEPROM. 394 395 This driver does not create any MTD maps itself; instead it 396 creates MTD physmap and MTD SRAM platform devices. If you 397 enable this option, you should consider enabling MTD_PHYSMAP 398 and/or MTD_PLATRAM according to the devices on your module. 399 400 When built as a module, it will be called pismo.ko 401 402endmenu 403