Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | menu "Mapping drivers for chip access" |
| 2 | depends on MTD!=n |
| 3 | |
| 4 | config MTD_COMPLEX_MAPPINGS |
| 5 | bool "Support non-linear mappings of flash chips" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 6 | help |
| 7 | This causes the chip drivers to allow for complicated |
| 8 | paged mappings of flash chips. |
| 9 | |
| 10 | config MTD_PHYSMAP |
Alexey Korolev | d814083 | 2008-12-16 18:22:39 +0000 | [diff] [blame] | 11 | tristate "Flash device in physical memory map" |
| 12 | depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 13 | help |
Takashi YOSHII | 79b9cd5 | 2006-08-15 07:26:32 -0500 | [diff] [blame] | 14 | This provides a 'mapping' driver which allows the NOR Flash and |
| 15 | ROM driver code to communicate with chips which are mapped |
| 16 | physically into the CPU's memory. You will need to configure |
| 17 | the physical address and size of the flash chips on your |
| 18 | particular board as well as the bus width, either statically |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 19 | with config options or at run-time. |
| 20 | |
Mike Frysinger | 41bdf96 | 2008-04-18 13:44:10 -0700 | [diff] [blame] | 21 | To compile this driver as a module, choose M here: the |
| 22 | module will be called physmap. |
| 23 | |
Mike Frysinger | dcb3e13 | 2008-12-01 14:23:40 -0800 | [diff] [blame] | 24 | config MTD_PHYSMAP_COMPAT |
| 25 | bool "Physmap compat support" |
| 26 | depends on MTD_PHYSMAP |
| 27 | default n |
| 28 | help |
| 29 | Setup a simple mapping via the Kconfig options. Normally the |
| 30 | physmap configuration options are done via your board's |
| 31 | resource file. |
| 32 | |
| 33 | If unsure, say N here. |
| 34 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 35 | config MTD_PHYSMAP_START |
| 36 | hex "Physical start address of flash mapping" |
Mike Frysinger | dcb3e13 | 2008-12-01 14:23:40 -0800 | [diff] [blame] | 37 | depends on MTD_PHYSMAP_COMPAT |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 38 | default "0x8000000" |
| 39 | help |
| 40 | This is the physical memory location at which the flash chips |
| 41 | are mapped on your particular target board. Refer to the |
| 42 | memory map which should hopefully be in the documentation for |
| 43 | your board. |
| 44 | Ignore this option if you use run-time physmap configuration |
| 45 | (i.e., run-time calling physmap_configure()). |
| 46 | |
| 47 | config MTD_PHYSMAP_LEN |
| 48 | hex "Physical length of flash mapping" |
Mike Frysinger | dcb3e13 | 2008-12-01 14:23:40 -0800 | [diff] [blame] | 49 | depends on MTD_PHYSMAP_COMPAT |
Lennert Buytenhek | 73566ed | 2006-05-07 17:16:36 +0100 | [diff] [blame] | 50 | default "0" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 51 | help |
| 52 | This is the total length of the mapping of the flash chips on |
| 53 | your particular board. If there is space, or aliases, in the |
| 54 | physical memory map between the chips, this could be larger |
| 55 | than the total amount of flash present. Refer to the memory |
| 56 | map which should hopefully be in the documentation for your |
| 57 | board. |
| 58 | Ignore this option if you use run-time physmap configuration |
| 59 | (i.e., run-time calling physmap_configure()). |
| 60 | |
| 61 | config MTD_PHYSMAP_BANKWIDTH |
| 62 | int "Bank width in octets" |
Mike Frysinger | dcb3e13 | 2008-12-01 14:23:40 -0800 | [diff] [blame] | 63 | depends on MTD_PHYSMAP_COMPAT |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 64 | default "2" |
| 65 | help |
| 66 | This is the total width of the data bus of the flash devices |
| 67 | in octets. For example, if you have a data bus width of 32 |
Matt LaPlante | 01dd2fb | 2007-10-20 01:34:40 +0200 | [diff] [blame] | 68 | bits, you would set the bus width octet value to 4. This is |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 69 | used internally by the CFI drivers. |
| 70 | Ignore this option if you use run-time physmap configuration |
| 71 | (i.e., run-time calling physmap_configure()). |
| 72 | |
Vitaly Wool | a2c2fe4 | 2006-12-06 13:17:49 +0300 | [diff] [blame] | 73 | config MTD_PHYSMAP_OF |
Matt LaPlante | a982ac0 | 2007-05-09 07:35:06 +0200 | [diff] [blame] | 74 | tristate "Flash device in physical memory map based on OF description" |
John Williams | c2a32f0 | 2009-08-25 19:19:54 +1000 | [diff] [blame] | 75 | depends on (MICROBLAZE || PPC_OF) && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM) |
Vitaly Wool | a2c2fe4 | 2006-12-06 13:17:49 +0300 | [diff] [blame] | 76 | help |
| 77 | This provides a 'mapping' driver which allows the NOR Flash and |
| 78 | ROM driver code to communicate with chips which are mapped |
| 79 | physically into the CPU's memory. The mapping description here is |
| 80 | taken from OF device tree. |
| 81 | |
Marc St-Jean | 68aa0fa | 2007-03-26 21:45:41 -0800 | [diff] [blame] | 82 | config MTD_PMC_MSP_EVM |
| 83 | tristate "CFI Flash device mapped on PMC-Sierra MSP" |
| 84 | depends on PMC_MSP && MTD_CFI |
| 85 | select MTD_PARTITIONS |
| 86 | help |
Matt LaPlante | 01dd2fb | 2007-10-20 01:34:40 +0200 | [diff] [blame] | 87 | This provides a 'mapping' driver which supports the way |
| 88 | in which user-programmable flash chips are connected on the |
| 89 | PMC-Sierra MSP eval/demo boards. |
Marc St-Jean | 68aa0fa | 2007-03-26 21:45:41 -0800 | [diff] [blame] | 90 | |
| 91 | choice |
Matt LaPlante | 01dd2fb | 2007-10-20 01:34:40 +0200 | [diff] [blame] | 92 | prompt "Maximum mappable memory available for flash IO" |
Marc St-Jean | 68aa0fa | 2007-03-26 21:45:41 -0800 | [diff] [blame] | 93 | depends on MTD_PMC_MSP_EVM |
| 94 | default MSP_FLASH_MAP_LIMIT_32M |
| 95 | |
| 96 | config MSP_FLASH_MAP_LIMIT_32M |
| 97 | bool "32M" |
| 98 | |
| 99 | endchoice |
| 100 | |
| 101 | config MSP_FLASH_MAP_LIMIT |
| 102 | hex |
| 103 | default "0x02000000" |
| 104 | depends on MSP_FLASH_MAP_LIMIT_32M |
| 105 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 106 | config MTD_SUN_UFLASH |
| 107 | tristate "Sun Microsystems userflash support" |
Al Viro | e0e5de0 | 2007-07-26 17:33:09 +0100 | [diff] [blame] | 108 | depends on SPARC && MTD_CFI && PCI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 109 | help |
Thomas Gleixner | 69f34c9 | 2005-11-07 11:15:40 +0000 | [diff] [blame] | 110 | This provides a 'mapping' driver which supports the way in |
| 111 | which user-programmable flash chips are connected on various |
| 112 | Sun Microsystems boardsets. This driver will require CFI support |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 113 | in the kernel, so if you did not enable CFI previously, do that now. |
| 114 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 115 | config MTD_SC520CDP |
| 116 | tristate "CFI Flash device mapped on AMD SC520 CDP" |
Daniel Drake | fbbc21c | 2006-04-29 11:41:44 +0100 | [diff] [blame] | 117 | depends on X86 && MTD_CFI && MTD_CONCAT |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 118 | help |
| 119 | The SC520 CDP board has two banks of CFI-compliant chips and one |
| 120 | Dual-in-line JEDEC chip. This 'mapping' driver supports that |
| 121 | arrangement, implementing three MTD devices. |
| 122 | |
| 123 | config MTD_NETSC520 |
| 124 | tristate "CFI Flash device mapped on AMD NetSc520" |
| 125 | depends on X86 && MTD_CFI && MTD_PARTITIONS |
| 126 | help |
| 127 | This enables access routines for the flash chips on the AMD NetSc520 |
Thomas Gleixner | 69f34c9 | 2005-11-07 11:15:40 +0000 | [diff] [blame] | 128 | demonstration board. If you have one of these boards and would like |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 129 | to use the flash chips on it, say 'Y'. |
| 130 | |
| 131 | config MTD_TS5500 |
| 132 | tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" |
Sean Young | ef63d00 | 2005-11-09 00:12:50 +0000 | [diff] [blame] | 133 | depends on X86 |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 134 | select MTD_PARTITIONS |
| 135 | select MTD_JEDECPROBE |
| 136 | select MTD_CFI_AMDSTD |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 137 | help |
| 138 | This provides a driver for the on-board flash of the Technologic |
Sean Young | e27a996 | 2005-06-16 09:49:33 +0100 | [diff] [blame] | 139 | System's TS-5500 board. The 2MB flash is split into 3 partitions |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 140 | which are accessed as separate MTD devices. |
| 141 | |
Sean Young | e27a996 | 2005-06-16 09:49:33 +0100 | [diff] [blame] | 142 | mtd0 and mtd2 are the two BIOS drives, which use the resident |
| 143 | flash disk (RFD) flash translation layer. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 144 | |
| 145 | mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. |
| 146 | |
| 147 | Note that jumper 3 ("Write Enable Drive A") must be set |
Egry Gábor | 4992a9e | 2006-05-12 17:35:02 +0100 | [diff] [blame] | 148 | otherwise detection won't succeed. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 149 | |
| 150 | config MTD_SBC_GXX |
| 151 | tristate "CFI Flash device mapped on Arcom SBC-GXx boards" |
| 152 | depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS |
| 153 | help |
| 154 | This provides a driver for the on-board flash of Arcom Control |
| 155 | Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. |
| 156 | By default the flash is split into 3 partitions which are accessed |
| 157 | as separate MTD devices. This board utilizes Intel StrataFlash. |
| 158 | More info at |
| 159 | <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>. |
| 160 | |
Todd Poynor | e644f7d | 2005-11-07 21:47:48 +0000 | [diff] [blame] | 161 | config MTD_PXA2XX |
| 162 | tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards" |
| 163 | depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT |
Nico Pitre | cbec19a | 2005-07-01 23:55:24 +0100 | [diff] [blame] | 164 | select MTD_PARTITIONS |
| 165 | help |
Todd Poynor | e644f7d | 2005-11-07 21:47:48 +0000 | [diff] [blame] | 166 | This provides a driver for the NOR flash attached to a PXA2xx chip. |
Nico Pitre | cbec19a | 2005-07-01 23:55:24 +0100 | [diff] [blame] | 167 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 168 | config MTD_OCTAGON |
| 169 | tristate "JEDEC Flash device mapped on Octagon 5066 SBC" |
| 170 | depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS |
| 171 | help |
| 172 | This provides a 'mapping' driver which supports the way in which |
| 173 | the flash chips are connected in the Octagon-5066 Single Board |
| 174 | Computer. More information on the board is available at |
Justin P. Mattock | 631dd1a | 2010-10-18 11:03:14 +0200 | [diff] [blame^] | 175 | <http://www.octagonsystems.com/products/5066.aspx>. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 176 | |
| 177 | config MTD_VMAX |
| 178 | tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301" |
| 179 | depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS |
| 180 | help |
| 181 | This provides a 'mapping' driver which supports the way in which |
| 182 | the flash chips are connected in the Tempustech VMAX SBC301 Single |
| 183 | Board Computer. More information on the board is available at |
| 184 | <http://www.tempustech.com/>. |
| 185 | |
| 186 | config MTD_SCx200_DOCFLASH |
| 187 | tristate "Flash device mapped with DOCCS on NatSemi SCx200" |
| 188 | depends on SCx200 && MTD_CFI && MTD_PARTITIONS |
| 189 | help |
| 190 | Enable support for a flash chip mapped using the DOCCS signal on a |
| 191 | National Semiconductor SCx200 processor. |
| 192 | |
| 193 | If you don't know what to do here, say N. |
| 194 | |
| 195 | If compiled as a module, it will be called scx200_docflash. |
| 196 | |
| 197 | config MTD_AMD76XROM |
| 198 | tristate "BIOS flash chip on AMD76x southbridge" |
| 199 | depends on X86 && MTD_JEDECPROBE |
| 200 | help |
| 201 | Support for treating the BIOS flash chip on AMD76x motherboards |
| 202 | as an MTD device - with this you can reprogram your BIOS. |
| 203 | |
| 204 | BE VERY CAREFUL. |
| 205 | |
| 206 | config MTD_ICHXROM |
| 207 | tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" |
| 208 | depends on X86 && MTD_JEDECPROBE |
| 209 | help |
| 210 | Support for treating the BIOS flash chip on ICHX motherboards |
| 211 | as an MTD device - with this you can reprogram your BIOS. |
| 212 | |
| 213 | BE VERY CAREFUL. |
| 214 | |
Lew Glendenning | 2917577 | 2006-10-20 14:41:04 -0700 | [diff] [blame] | 215 | config MTD_ESB2ROM |
| 216 | tristate "BIOS flash chip on Intel ESB Controller Hub 2" |
Randy Dunlap | dffbc42 | 2006-12-04 15:03:00 -0800 | [diff] [blame] | 217 | depends on X86 && MTD_JEDECPROBE && PCI |
Lew Glendenning | 2917577 | 2006-10-20 14:41:04 -0700 | [diff] [blame] | 218 | help |
| 219 | Support for treating the BIOS flash chip on ESB2 motherboards |
| 220 | as an MTD device - with this you can reprogram your BIOS. |
| 221 | |
| 222 | BE VERY CAREFUL. |
| 223 | |
Dave Olsen | 90afffc | 2006-11-06 16:33:57 -0700 | [diff] [blame] | 224 | config MTD_CK804XROM |
| 225 | tristate "BIOS flash chip on Nvidia CK804" |
akpm@osdl.org | 862c93b | 2007-01-25 15:15:17 -0800 | [diff] [blame] | 226 | depends on X86 && MTD_JEDECPROBE && PCI |
Dave Olsen | 90afffc | 2006-11-06 16:33:57 -0700 | [diff] [blame] | 227 | help |
| 228 | Support for treating the BIOS flash chip on nvidia motherboards |
| 229 | as an MTD device - with this you can reprogram your BIOS. |
| 230 | |
| 231 | BE VERY CAREFUL. |
| 232 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 233 | config MTD_SCB2_FLASH |
| 234 | tristate "BIOS flash chip on Intel SCB2 boards" |
| 235 | depends on X86 && MTD_JEDECPROBE |
| 236 | help |
| 237 | Support for treating the BIOS flash chip on Intel SCB2 boards |
| 238 | as an MTD device - with this you can reprogram your BIOS. |
| 239 | |
| 240 | BE VERY CAREFUL. |
| 241 | |
| 242 | config MTD_TSUNAMI |
| 243 | tristate "Flash chips on Tsunami TIG bus" |
| 244 | depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS |
| 245 | help |
| 246 | Support for the flash chip on Tsunami TIG bus. |
| 247 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 248 | config MTD_NETtel |
| 249 | tristate "CFI flash device on SnapGear/SecureEdge" |
| 250 | depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE |
| 251 | help |
| 252 | Support for flash chips on NETtel/SecureEdge/SnapGear boards. |
| 253 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 254 | config MTD_DILNETPC |
| 255 | tristate "CFI Flash device mapped on DIL/Net PC" |
David Woodhouse | 8d42b52 | 2009-05-29 13:57:13 +0100 | [diff] [blame] | 256 | depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT && BROKEN |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | |
| 262 | config 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 | |
| 270 | config 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 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 279 | config MTD_TQM8XXL |
| 280 | tristate "CFI Flash device mapped on TQM8XXL" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 281 | depends on MTD_CFI && TQM8xxL |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 282 | help |
| 283 | The TQM8xxL PowerPC board has up to two banks of CFI-compliant |
| 284 | chips, currently uses AMD one. This 'mapping' driver supports |
| 285 | that arrangement, allowing the CFI probe and command set driver |
| 286 | code to communicate with the chips on the TQM8xxL board. More at |
Justin P. Mattock | 631dd1a | 2010-10-18 11:03:14 +0200 | [diff] [blame^] | 287 | <http://www.denx.de/wiki/PPCEmbedded/>. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 288 | |
| 289 | config MTD_RPXLITE |
| 290 | tristate "CFI Flash device mapped on RPX Lite or CLLF" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 291 | depends on MTD_CFI && (RPXCLASSIC || RPXLITE) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 292 | help |
| 293 | The RPXLite PowerPC board has CFI-compliant chips mapped in |
| 294 | a strange sparse mapping. This 'mapping' driver supports that |
| 295 | arrangement, allowing the CFI probe and command set driver code |
| 296 | to communicate with the chips on the RPXLite board. More at |
| 297 | <http://www.embeddedplanet.com/>. |
| 298 | |
| 299 | config MTD_MBX860 |
| 300 | tristate "System flash on MBX860 board" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 301 | depends on MTD_CFI && MBX |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 302 | help |
| 303 | This enables access routines for the flash chips on the Motorola |
| 304 | MBX860 board. If you have one of these boards and would like |
| 305 | to use the flash chips on it, say 'Y'. |
| 306 | |
| 307 | config MTD_DBOX2 |
| 308 | tristate "CFI Flash device mapped on D-Box2" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 309 | depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 310 | help |
| 311 | This enables access routines for the flash chips on the Nokia/Sagem |
| 312 | D-Box 2 board. If you have one of these boards and would like to use |
| 313 | the flash chips on it, say 'Y'. |
| 314 | |
| 315 | config MTD_CFI_FLAGADM |
| 316 | tristate "CFI Flash device mapping on FlagaDM" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 317 | depends on 8xx && MTD_CFI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 318 | help |
| 319 | Mapping for the Flaga digital module. If you don't have one, ignore |
| 320 | this setting. |
| 321 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 322 | config MTD_SOLUTIONENGINE |
| 323 | tristate "CFI Flash device mapped on Hitachi SolutionEngine" |
Paul Mundt | e35e283 | 2008-04-25 14:27:08 +0900 | [diff] [blame] | 324 | depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 325 | help |
| 326 | This enables access to the flash chips on the Hitachi SolutionEngine and |
| 327 | similar boards. Say 'Y' if you are building a kernel for such a board. |
| 328 | |
| 329 | config MTD_ARM_INTEGRATOR |
| 330 | tristate "CFI Flash device mapped on ARM Integrator/P720T" |
| 331 | depends on ARM && MTD_CFI |
| 332 | |
| 333 | config MTD_CDB89712 |
| 334 | tristate "Cirrus CDB89712 evaluation board mappings" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 335 | depends on MTD_CFI && ARCH_CDB89712 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 336 | help |
| 337 | This enables access to the flash or ROM chips on the CDB89712 board. |
| 338 | If you have such a board, say 'Y'. |
| 339 | |
| 340 | config MTD_SA1100 |
| 341 | tristate "CFI Flash device mapped on StrongARM SA11x0" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 342 | depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 343 | help |
| 344 | This enables access to the flash chips on most platforms based on |
| 345 | the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. |
| 346 | If you have such a board, say 'Y'. |
| 347 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 348 | config MTD_DC21285 |
| 349 | tristate "CFI Flash device mapped on DC21285 Footbridge" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 350 | depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 351 | help |
| 352 | This provides a driver for the flash accessed using Intel's |
| 353 | 21285 bridge used with Intel's StrongARM processors. More info at |
| 354 | <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. |
| 355 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 356 | config MTD_IXP4XX |
| 357 | tristate "CFI Flash device mapped on Intel IXP4xx based systems" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 358 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 359 | help |
Thomas Gleixner | 69f34c9 | 2005-11-07 11:15:40 +0000 | [diff] [blame] | 360 | This enables MTD access to flash devices on platforms based |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 361 | on Intel's IXP4xx family of network processors such as the |
| 362 | IXDP425 and Coyote. If you have an IXP4xx based board and |
| 363 | would like to use the flash chips on it, say 'Y'. |
| 364 | |
| 365 | config MTD_IXP2000 |
| 366 | tristate "CFI Flash device mapped on Intel IXP2000 based systems" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 367 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 368 | help |
Thomas Gleixner | 69f34c9 | 2005-11-07 11:15:40 +0000 | [diff] [blame] | 369 | This enables MTD access to flash devices on platforms based |
Krzysztof Halasa | 86185af | 2009-11-15 19:14:07 +0100 | [diff] [blame] | 370 | on Intel's IXP2000 family of network processors. If you have an |
| 371 | IXP2000 based board and would like to use the flash chips on it, |
| 372 | say 'Y'. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 373 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 374 | config MTD_FORTUNET |
| 375 | tristate "CFI Flash device mapped on the FortuNet board" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 376 | depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 377 | help |
| 378 | This enables access to the Flash on the FortuNet board. If you |
| 379 | have such a board, say 'Y'. |
| 380 | |
| 381 | config MTD_AUTCPU12 |
| 382 | tristate "NV-RAM mapping AUTCPU12 board" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 383 | depends on ARCH_AUTCPU12 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 384 | help |
| 385 | This enables access to the NV-RAM on autronix autcpu12 board. |
| 386 | If you have such a board, say 'Y'. |
| 387 | |
| 388 | config MTD_EDB7312 |
| 389 | tristate "CFI Flash device mapped on EDB7312" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 390 | depends on ARCH_EDB7312 && MTD_CFI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 391 | help |
| 392 | This enables access to the CFI Flash on the Cogent EDB7312 board. |
| 393 | If you have such a board, say 'Y' here. |
| 394 | |
| 395 | config MTD_IMPA7 |
| 396 | tristate "JEDEC Flash device mapped on impA7" |
| 397 | depends on ARM && MTD_JEDECPROBE |
| 398 | help |
| 399 | This enables access to the NOR Flash on the impA7 board of |
| 400 | implementa GmbH. If you have such a board, say 'Y' here. |
| 401 | |
| 402 | config MTD_CEIVA |
| 403 | tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 404 | depends on MTD_JEDECPROBE && ARCH_CEIVA |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 405 | help |
| 406 | This enables access to the flash chips on the Ceiva/Polaroid |
| 407 | PhotoMax Digital Picture Frame. |
| 408 | If you have such a device, say 'Y'. |
| 409 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 410 | config MTD_H720X |
| 411 | tristate "Hynix evaluation board mappings" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 412 | depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 ) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 413 | help |
| 414 | This enables access to the flash chips on the Hynix evaluation boards. |
| 415 | If you have such a board, say 'Y'. |
| 416 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 417 | # This needs CFI or JEDEC, depending on the cards found. |
| 418 | config MTD_PCI |
| 419 | tristate "PCI MTD driver" |
Jan Engelhardt | ec98c68 | 2007-04-19 16:21:41 -0500 | [diff] [blame] | 420 | depends on PCI && MTD_COMPLEX_MAPPINGS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 421 | help |
| 422 | Mapping for accessing flash devices on add-in cards like the Intel XScale |
| 423 | IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode |
| 424 | (please see the manual for the link settings). |
| 425 | |
| 426 | If you are not sure, say N. |
| 427 | |
| 428 | config MTD_PCMCIA |
| 429 | tristate "PCMCIA MTD driver" |
Alexander Kurz | f6763c98 | 2010-05-13 11:59:59 +0200 | [diff] [blame] | 430 | depends on PCMCIA && MTD_COMPLEX_MAPPINGS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 431 | help |
| 432 | Map driver for accessing PCMCIA linear flash memory cards. These |
| 433 | cards are usually around 4-16MiB in size. This does not include |
| 434 | Compact Flash cards which are treated as IDE devices. |
| 435 | |
Dominik Brodowski | 11d28a3 | 2005-06-27 16:28:32 -0700 | [diff] [blame] | 436 | config MTD_PCMCIA_ANONYMOUS |
| 437 | bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards" |
| 438 | depends on MTD_PCMCIA |
Dominik Brodowski | 11d28a3 | 2005-06-27 16:28:32 -0700 | [diff] [blame] | 439 | help |
| 440 | If this option is enabled, PCMCIA cards which do not report |
| 441 | anything about themselves are assumed to be MTD cards. |
| 442 | |
| 443 | If unsure, say N. |
| 444 | |
Mike Frysinger | 2e3c22f | 2008-05-19 18:32:24 +0800 | [diff] [blame] | 445 | config MTD_BFIN_ASYNC |
| 446 | tristate "Blackfin BF533-STAMP Flash Chip Support" |
Mike Frysinger | ab00d68 | 2009-02-11 13:12:19 -0800 | [diff] [blame] | 447 | depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS |
Mike Frysinger | 2e3c22f | 2008-05-19 18:32:24 +0800 | [diff] [blame] | 448 | select MTD_PARTITIONS |
| 449 | default y |
| 450 | help |
| 451 | Map driver which allows for simultaneous utilization of |
| 452 | ethernet and CFI parallel flash. |
| 453 | |
| 454 | If compiled as a module, it will be called bfin-async-flash. |
| 455 | |
Mike Frysinger | d79c326 | 2009-05-20 12:04:09 -0400 | [diff] [blame] | 456 | config MTD_GPIO_ADDR |
| 457 | tristate "GPIO-assisted Flash Chip Support" |
Mike Frysinger | de19d02 | 2009-09-24 15:11:38 -0400 | [diff] [blame] | 458 | depends on GENERIC_GPIO || GPIOLIB |
Mike Frysinger | d79c326 | 2009-05-20 12:04:09 -0400 | [diff] [blame] | 459 | depends on MTD_COMPLEX_MAPPINGS |
| 460 | select MTD_PARTITIONS |
| 461 | help |
| 462 | Map driver which allows flashes to be partially physically addressed |
| 463 | and assisted by GPIOs. |
| 464 | |
| 465 | If compiled as a module, it will be called gpio-addr-flash. |
| 466 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 467 | config MTD_UCLINUX |
Mike Frysinger | 6ae392c | 2009-05-26 19:33:18 -0400 | [diff] [blame] | 468 | bool "Generic uClinux RAM/ROM filesystem support" |
Mike Frysinger | 1b533d2 | 2009-06-09 10:37:18 +0000 | [diff] [blame] | 469 | depends on MTD_PARTITIONS && MTD_RAM=y && !MMU |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 470 | help |
| 471 | Map driver to support image based filesystems for uClinux. |
| 472 | |
| 473 | config MTD_WRSBC8260 |
| 474 | tristate "Map driver for WindRiver PowerQUICC II MPC82xx board" |
| 475 | depends on (SBC82xx || SBC8560) |
| 476 | select MTD_PARTITIONS |
| 477 | select MTD_MAP_BANK_WIDTH_4 |
| 478 | select MTD_MAP_BANK_WIDTH_1 |
| 479 | select MTD_CFI_I1 |
| 480 | select MTD_CFI_I4 |
| 481 | help |
| 482 | Map driver for WindRiver PowerQUICC II MPC82xx board. Drives |
| 483 | all three flash regions on CS0, CS1 and CS6 if they are configured |
| 484 | correctly by the boot loader. |
| 485 | |
| 486 | config MTD_DMV182 |
| 487 | tristate "Map driver for Dy-4 SVME/DMV-182 board." |
| 488 | depends on DMV182 |
| 489 | select MTD_PARTITIONS |
| 490 | select MTD_MAP_BANK_WIDTH_32 |
| 491 | select MTD_CFI_I8 |
| 492 | select MTD_CFI_AMDSTD |
| 493 | help |
| 494 | Map driver for Dy-4 SVME/DMV-182 board. |
| 495 | |
David Woodhouse | 0bac511 | 2007-09-23 18:51:25 +0100 | [diff] [blame] | 496 | config MTD_INTEL_VR_NOR |
| 497 | tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0" |
| 498 | depends on PCI |
| 499 | help |
| 500 | Map driver for a NOR flash bank located on the Expansion Bus of the |
| 501 | Intel Vermilion Range chipset. |
| 502 | |
Atsushi Nemoto | 610f75e | 2009-03-04 12:01:34 -0800 | [diff] [blame] | 503 | config MTD_RBTX4939 |
| 504 | tristate "Map driver for RBTX4939 board" |
| 505 | depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS |
| 506 | help |
| 507 | Map driver for NOR flash chips on RBTX4939 board. |
| 508 | |
Ben Dooks | 99f2a8a | 2005-01-24 00:37:04 +0000 | [diff] [blame] | 509 | config MTD_PLATRAM |
Thomas Gleixner | 3c45e00 | 2005-03-18 02:07:24 +0000 | [diff] [blame] | 510 | tristate "Map driver for platform device RAM (mtd-ram)" |
Ben Dooks | 99f2a8a | 2005-01-24 00:37:04 +0000 | [diff] [blame] | 511 | select MTD_RAM |
| 512 | help |
| 513 | Map driver for RAM areas described via the platform device |
| 514 | system. |
| 515 | |
| 516 | This selection automatically selects the map_ram driver. |
| 517 | |
Adrian McMenamin | 47a7268 | 2009-03-04 00:31:04 +0000 | [diff] [blame] | 518 | config MTD_VMU |
| 519 | tristate "Map driver for Dreamcast VMU" |
| 520 | depends on MAPLE |
| 521 | help |
| 522 | This driver enables access to the Dreamcast Visual Memory Unit (VMU). |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 523 | |
Adrian McMenamin | 47a7268 | 2009-03-04 00:31:04 +0000 | [diff] [blame] | 524 | Most Dreamcast users will want to say Y here. |
| 525 | |
| 526 | To build this as a module select M here, the module will be called |
| 527 | vmu-flash. |
| 528 | |
Russell King - ARM Linux | f6a8c60 | 2009-11-29 15:23:51 +0000 | [diff] [blame] | 529 | config MTD_PISMO |
| 530 | tristate "MTD discovery driver for PISMO modules" |
| 531 | depends on I2C |
| 532 | depends on ARCH_VERSATILE |
| 533 | help |
| 534 | This driver allows for discovery of PISMO modules - see |
| 535 | <http://www.pismoworld.org/>. These are small modules containing |
| 536 | up to five memory devices (eg, SRAM, flash, DOC) described by an |
| 537 | I2C EEPROM. |
| 538 | |
| 539 | This driver does not create any MTD maps itself; instead it |
| 540 | creates MTD physmap and MTD SRAM platform devices. If you |
| 541 | enable this option, you should consider enabling MTD_PHYSMAP |
| 542 | and/or MTD_PLATRAM according to the devices on your module. |
| 543 | |
| 544 | When built as a module, it will be called pismo.ko |
| 545 | |
Adrian McMenamin | 47a7268 | 2009-03-04 00:31:04 +0000 | [diff] [blame] | 546 | endmenu |