blob: 02c45e1e24eeb6de7ed7eb9d6e947d3e48faf7ea [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001# drivers/mtd/maps/Kconfig
Linus Torvalds1da177e2005-04-16 15:20:36 -07002
3menu "Mapping drivers for chip access"
4 depends on MTD!=n
5
6config MTD_COMPLEX_MAPPINGS
7 bool "Support non-linear mappings of flash chips"
Linus Torvalds1da177e2005-04-16 15:20:36 -07008 help
9 This causes the chip drivers to allow for complicated
10 paged mappings of flash chips.
11
12config MTD_PHYSMAP
13 tristate "CFI Flash device in physical memory map"
Takashi YOSHII79b9cd52006-08-15 07:26:32 -050014 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
Linus Torvalds1da177e2005-04-16 15:20:36 -070015 help
Takashi YOSHII79b9cd52006-08-15 07:26:32 -050016 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070021 with config options or at run-time.
22
Mike Frysinger41bdf962008-04-18 13:44:10 -070023 To compile this driver as a module, choose M here: the
24 module will be called physmap.
25
Linus Torvalds1da177e2005-04-16 15:20:36 -070026config MTD_PHYSMAP_START
27 hex "Physical start address of flash mapping"
28 depends on MTD_PHYSMAP
29 default "0x8000000"
30 help
31 This is the physical memory location at which the flash chips
32 are mapped on your particular target board. Refer to the
33 memory map which should hopefully be in the documentation for
34 your board.
35 Ignore this option if you use run-time physmap configuration
36 (i.e., run-time calling physmap_configure()).
37
38config MTD_PHYSMAP_LEN
39 hex "Physical length of flash mapping"
40 depends on MTD_PHYSMAP
Lennert Buytenhek73566ed2006-05-07 17:16:36 +010041 default "0"
Linus Torvalds1da177e2005-04-16 15:20:36 -070042 help
43 This is the total length of the mapping of the flash chips on
44 your particular board. If there is space, or aliases, in the
45 physical memory map between the chips, this could be larger
46 than the total amount of flash present. Refer to the memory
47 map which should hopefully be in the documentation for your
48 board.
49 Ignore this option if you use run-time physmap configuration
50 (i.e., run-time calling physmap_configure()).
51
52config MTD_PHYSMAP_BANKWIDTH
53 int "Bank width in octets"
54 depends on MTD_PHYSMAP
55 default "2"
56 help
57 This is the total width of the data bus of the flash devices
58 in octets. For example, if you have a data bus width of 32
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020059 bits, you would set the bus width octet value to 4. This is
Linus Torvalds1da177e2005-04-16 15:20:36 -070060 used internally by the CFI drivers.
61 Ignore this option if you use run-time physmap configuration
62 (i.e., run-time calling physmap_configure()).
63
Vitaly Woola2c2fe42006-12-06 13:17:49 +030064config MTD_PHYSMAP_OF
Matt LaPlantea982ac02007-05-09 07:35:06 +020065 tristate "Flash device in physical memory map based on OF description"
Vitaly Woola2c2fe42006-12-06 13:17:49 +030066 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
67 help
68 This provides a 'mapping' driver which allows the NOR Flash and
69 ROM driver code to communicate with chips which are mapped
70 physically into the CPU's memory. The mapping description here is
71 taken from OF device tree.
72
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080073config MTD_PMC_MSP_EVM
74 tristate "CFI Flash device mapped on PMC-Sierra MSP"
75 depends on PMC_MSP && MTD_CFI
76 select MTD_PARTITIONS
77 help
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020078 This provides a 'mapping' driver which supports the way
79 in which user-programmable flash chips are connected on the
80 PMC-Sierra MSP eval/demo boards.
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080081
82choice
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020083 prompt "Maximum mappable memory available for flash IO"
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080084 depends on MTD_PMC_MSP_EVM
85 default MSP_FLASH_MAP_LIMIT_32M
86
87config MSP_FLASH_MAP_LIMIT_32M
88 bool "32M"
89
90endchoice
91
92config MSP_FLASH_MAP_LIMIT
93 hex
94 default "0x02000000"
95 depends on MSP_FLASH_MAP_LIMIT_32M
96
97config MTD_PMC_MSP_RAMROOT
98 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
99 depends on PMC_MSP_EMBEDDED_ROOTFS && \
100 (MTD_BLOCK || MTD_BLOCK_RO) && \
101 MTD_RAM
102 help
103 This provides support for the embedded root file system
104 on PMC MSP devices. This memory is mapped as a MTD block device.
105
Linus Torvalds1da177e2005-04-16 15:20:36 -0700106config MTD_SUN_UFLASH
107 tristate "Sun Microsystems userflash support"
Al Viroe0e5de02007-07-26 17:33:09 +0100108 depends on SPARC && MTD_CFI && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000110 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 Torvalds1da177e2005-04-16 15:20:36 -0700113 in the kernel, so if you did not enable CFI previously, do that now.
114
Linus Torvalds1da177e2005-04-16 15:20:36 -0700115config MTD_SC520CDP
116 tristate "CFI Flash device mapped on AMD SC520 CDP"
Daniel Drakefbbc21c2006-04-29 11:41:44 +0100117 depends on X86 && MTD_CFI && MTD_CONCAT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700118 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
123config 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 Gleixner69f34c92005-11-07 11:15:40 +0000128 demonstration board. If you have one of these boards and would like
Linus Torvalds1da177e2005-04-16 15:20:36 -0700129 to use the flash chips on it, say 'Y'.
130
131config MTD_TS5500
132 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
Sean Youngef63d002005-11-09 00:12:50 +0000133 depends on X86
Sean Young01ac7422005-06-29 09:46:19 +0000134 select MTD_PARTITIONS
135 select MTD_JEDECPROBE
136 select MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700137 help
138 This provides a driver for the on-board flash of the Technologic
Sean Younge27a9962005-06-16 09:49:33 +0100139 System's TS-5500 board. The 2MB flash is split into 3 partitions
Linus Torvalds1da177e2005-04-16 15:20:36 -0700140 which are accessed as separate MTD devices.
141
Sean Younge27a9962005-06-16 09:49:33 +0100142 mtd0 and mtd2 are the two BIOS drives, which use the resident
143 flash disk (RFD) flash translation layer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700144
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ábor4992a9e2006-05-12 17:35:02 +0100148 otherwise detection won't succeed.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700149
150config 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 Poynore644f7d2005-11-07 21:47:48 +0000161config MTD_PXA2XX
162 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
163 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
Nico Pitrecbec19a2005-07-01 23:55:24 +0100164 select MTD_PARTITIONS
165 help
Todd Poynore644f7d2005-11-07 21:47:48 +0000166 This provides a driver for the NOR flash attached to a PXA2xx chip.
Nico Pitrecbec19a2005-07-01 23:55:24 +0100167
Linus Torvalds1da177e2005-04-16 15:20:36 -0700168config 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
175 <http://www.octagonsystems.com/CPUpages/5066.html>.
176
177config 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
186config 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
197config 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
206config 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 Glendenning29175772006-10-20 14:41:04 -0700215config MTD_ESB2ROM
216 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
Randy Dunlapdffbc422006-12-04 15:03:00 -0800217 depends on X86 && MTD_JEDECPROBE && PCI
Lew Glendenning29175772006-10-20 14:41:04 -0700218 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 Olsen90afffc2006-11-06 16:33:57 -0700224config MTD_CK804XROM
225 tristate "BIOS flash chip on Nvidia CK804"
akpm@osdl.org862c93b2007-01-25 15:15:17 -0800226 depends on X86 && MTD_JEDECPROBE && PCI
Dave Olsen90afffc2006-11-06 16:33:57 -0700227 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 Torvalds1da177e2005-04-16 15:20:36 -0700233config 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
242config 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 Torvalds1da177e2005-04-16 15:20:36 -0700248config 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
Pete Popov002fa302005-02-27 21:50:25 +0000254config MTD_ALCHEMY
Roman Zippele55a3e82006-06-08 22:12:49 -0700255 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
Ralf Baechle873b6a22007-03-10 23:10:50 +0000256 depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700257 help
Pete Popov002fa302005-02-27 21:50:25 +0000258 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
Linus Torvalds1da177e2005-04-16 15:20:36 -0700259
Joern Engelb523b3b2005-09-18 11:46:45 +0100260config MTD_MTX1
261 tristate "4G Systems MTX-1 Flash device"
Ralf Baechle873b6a22007-03-10 23:10:50 +0000262 depends on MIPS_MTX1 && MTD_CFI
Joern Engelb523b3b2005-09-18 11:46:45 +0100263 help
264 Flash memory access on 4G Systems MTX-1 Board. If you have one of
265 these boards and would like to use the flash chips on it, say 'Y'.
266
Linus Torvalds1da177e2005-04-16 15:20:36 -0700267config MTD_DILNETPC
268 tristate "CFI Flash device mapped on DIL/Net PC"
269 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
270 help
271 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
272 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
273 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
274
275config MTD_DILNETPC_BOOTSIZE
276 hex "Size of DIL/Net PC flash boot partition"
277 depends on MTD_DILNETPC
278 default "0x80000"
279 help
280 The amount of space taken up by the kernel or Etherboot
281 on the DIL/Net PC flash chips.
282
283config MTD_L440GX
284 tristate "BIOS flash chip on Intel L440GX boards"
285 depends on X86 && MTD_JEDECPROBE
286 help
287 Support for treating the BIOS flash chip on Intel L440GX motherboards
288 as an MTD device - with this you can reprogram your BIOS.
289
290 BE VERY CAREFUL.
291
292config MTD_SBC8240
293 tristate "Flash device on SBC8240"
Sean Young01ac7422005-06-29 09:46:19 +0000294 depends on MTD_JEDECPROBE && 8260
Linus Torvalds1da177e2005-04-16 15:20:36 -0700295 help
296 Flash access on the SBC8240 board from Wind River. See
297 <http://www.windriver.com/products/sbc8240/>
298
299config MTD_TQM8XXL
300 tristate "CFI Flash device mapped on TQM8XXL"
Sean Young01ac7422005-06-29 09:46:19 +0000301 depends on MTD_CFI && TQM8xxL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700302 help
303 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
304 chips, currently uses AMD one. This 'mapping' driver supports
305 that arrangement, allowing the CFI probe and command set driver
306 code to communicate with the chips on the TQM8xxL board. More at
307 <http://www.denx.de/embedded-ppc-en.html>.
308
309config MTD_RPXLITE
310 tristate "CFI Flash device mapped on RPX Lite or CLLF"
Sean Young01ac7422005-06-29 09:46:19 +0000311 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700312 help
313 The RPXLite PowerPC board has CFI-compliant chips mapped in
314 a strange sparse mapping. This 'mapping' driver supports that
315 arrangement, allowing the CFI probe and command set driver code
316 to communicate with the chips on the RPXLite board. More at
317 <http://www.embeddedplanet.com/>.
318
319config MTD_MBX860
320 tristate "System flash on MBX860 board"
Sean Young01ac7422005-06-29 09:46:19 +0000321 depends on MTD_CFI && MBX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700322 help
323 This enables access routines for the flash chips on the Motorola
324 MBX860 board. If you have one of these boards and would like
325 to use the flash chips on it, say 'Y'.
326
327config MTD_DBOX2
328 tristate "CFI Flash device mapped on D-Box2"
Sean Young01ac7422005-06-29 09:46:19 +0000329 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700330 help
331 This enables access routines for the flash chips on the Nokia/Sagem
332 D-Box 2 board. If you have one of these boards and would like to use
333 the flash chips on it, say 'Y'.
334
335config MTD_CFI_FLAGADM
336 tristate "CFI Flash device mapping on FlagaDM"
Sean Young01ac7422005-06-29 09:46:19 +0000337 depends on 8xx && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700338 help
339 Mapping for the Flaga digital module. If you don't have one, ignore
340 this setting.
341
Linus Torvalds1da177e2005-04-16 15:20:36 -0700342config MTD_WALNUT
343 tristate "Flash device mapped on IBM 405GP Walnut"
Josh Boyer3feb0ff2007-08-22 14:30:47 -0500344 depends on MTD_JEDECPROBE && WALNUT && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700345 help
346 This enables access routines for the flash chips on the IBM 405GP
347 Walnut board. If you have one of these boards and would like to
348 use the flash chips on it, say 'Y'.
349
350config MTD_EBONY
351 tristate "Flash devices mapped on IBM 440GP Ebony"
David Gibson0d279d42007-07-30 15:55:02 +1000352 depends on MTD_JEDECPROBE && EBONY && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700353 help
354 This enables access routines for the flash chips on the IBM 440GP
355 Ebony board. If you have one of these boards and would like to
356 use the flash chips on it, say 'Y'.
357
358config MTD_OCOTEA
359 tristate "Flash devices mapped on IBM 440GX Ocotea"
Josh Boyer3feb0ff2007-08-22 14:30:47 -0500360 depends on MTD_CFI && OCOTEA && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700361 help
362 This enables access routines for the flash chips on the IBM 440GX
363 Ocotea board. If you have one of these boards and would like to
364 use the flash chips on it, say 'Y'.
365
366config MTD_REDWOOD
367 tristate "CFI Flash devices mapped on IBM Redwood"
Sean Young01ac7422005-06-29 09:46:19 +0000368 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700369 help
370 This enables access routines for the flash chips on the IBM
371 Redwood board. If you have one of these boards and would like to
372 use the flash chips on it, say 'Y'.
373
Linus Torvalds1da177e2005-04-16 15:20:36 -0700374config MTD_SOLUTIONENGINE
375 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
376 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
377 help
378 This enables access to the flash chips on the Hitachi SolutionEngine and
379 similar boards. Say 'Y' if you are building a kernel for such a board.
380
381config MTD_ARM_INTEGRATOR
382 tristate "CFI Flash device mapped on ARM Integrator/P720T"
383 depends on ARM && MTD_CFI
384
385config MTD_CDB89712
386 tristate "Cirrus CDB89712 evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000387 depends on MTD_CFI && ARCH_CDB89712
Linus Torvalds1da177e2005-04-16 15:20:36 -0700388 help
389 This enables access to the flash or ROM chips on the CDB89712 board.
390 If you have such a board, say 'Y'.
391
392config MTD_SA1100
393 tristate "CFI Flash device mapped on StrongARM SA11x0"
Sean Young01ac7422005-06-29 09:46:19 +0000394 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700395 help
396 This enables access to the flash chips on most platforms based on
397 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
398 If you have such a board, say 'Y'.
399
400config MTD_IPAQ
401 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
Sean Young01ac7422005-06-29 09:46:19 +0000402 depends on IPAQ_HANDHELD && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700403 help
404 This provides a driver for the on-board flash of the iPAQ.
405
406config MTD_DC21285
407 tristate "CFI Flash device mapped on DC21285 Footbridge"
Sean Young01ac7422005-06-29 09:46:19 +0000408 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700409 help
410 This provides a driver for the flash accessed using Intel's
411 21285 bridge used with Intel's StrongARM processors. More info at
412 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
413
Linus Torvalds1da177e2005-04-16 15:20:36 -0700414config MTD_IXP4XX
415 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000416 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700417 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000418 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700419 on Intel's IXP4xx family of network processors such as the
420 IXDP425 and Coyote. If you have an IXP4xx based board and
421 would like to use the flash chips on it, say 'Y'.
422
423config MTD_IXP2000
424 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000425 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700426 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000427 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700428 on Intel's IXP2000 family of network processors such as the
429 IXDP425 and Coyote. If you have an IXP2000 based board and
430 would like to use the flash chips on it, say 'Y'.
431
Linus Torvalds1da177e2005-04-16 15:20:36 -0700432config MTD_FORTUNET
433 tristate "CFI Flash device mapped on the FortuNet board"
Sean Young01ac7422005-06-29 09:46:19 +0000434 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700435 help
436 This enables access to the Flash on the FortuNet board. If you
437 have such a board, say 'Y'.
438
439config MTD_AUTCPU12
440 tristate "NV-RAM mapping AUTCPU12 board"
Sean Young01ac7422005-06-29 09:46:19 +0000441 depends on ARCH_AUTCPU12
Linus Torvalds1da177e2005-04-16 15:20:36 -0700442 help
443 This enables access to the NV-RAM on autronix autcpu12 board.
444 If you have such a board, say 'Y'.
445
446config MTD_EDB7312
447 tristate "CFI Flash device mapped on EDB7312"
Sean Young01ac7422005-06-29 09:46:19 +0000448 depends on ARCH_EDB7312 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700449 help
450 This enables access to the CFI Flash on the Cogent EDB7312 board.
451 If you have such a board, say 'Y' here.
452
453config MTD_IMPA7
454 tristate "JEDEC Flash device mapped on impA7"
455 depends on ARM && MTD_JEDECPROBE
456 help
457 This enables access to the NOR Flash on the impA7 board of
458 implementa GmbH. If you have such a board, say 'Y' here.
459
460config MTD_CEIVA
461 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
Sean Young01ac7422005-06-29 09:46:19 +0000462 depends on MTD_JEDECPROBE && ARCH_CEIVA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700463 help
464 This enables access to the flash chips on the Ceiva/Polaroid
465 PhotoMax Digital Picture Frame.
466 If you have such a device, say 'Y'.
467
468config MTD_NOR_TOTO
469 tristate "NOR Flash device on TOTO board"
Sean Young01ac7422005-06-29 09:46:19 +0000470 depends on ARCH_OMAP && OMAP_TOTO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700471 help
472 This enables access to the NOR flash on the Texas Instruments
473 TOTO board.
474
475config MTD_H720X
476 tristate "Hynix evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000477 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700478 help
479 This enables access to the flash chips on the Hynix evaluation boards.
480 If you have such a board, say 'Y'.
481
482config MTD_MPC1211
483 tristate "CFI Flash device mapped on Interface MPC-1211"
Sean Young01ac7422005-06-29 09:46:19 +0000484 depends on SH_MPC1211 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700485 help
486 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
487 If you have such a board, say 'Y'.
488
Todd Poynor10c96f22005-07-02 02:53:28 +0100489config MTD_OMAP_NOR
490 tristate "TI OMAP board mappings"
491 depends on MTD_CFI && ARCH_OMAP
492 help
493 This enables access to the NOR flash chips on TI OMAP-based
494 boards defining flash platform devices and flash platform data.
495 These boards include the Innovator, H2, H3, OSK, Perseus2, and
496 more. If you have such a board, say 'Y'.
497
Linus Torvalds1da177e2005-04-16 15:20:36 -0700498# This needs CFI or JEDEC, depending on the cards found.
499config MTD_PCI
500 tristate "PCI MTD driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500501 depends on PCI && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700502 help
503 Mapping for accessing flash devices on add-in cards like the Intel XScale
504 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
505 (please see the manual for the link settings).
506
507 If you are not sure, say N.
508
509config MTD_PCMCIA
510 tristate "PCMCIA MTD driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500511 depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
Linus Torvalds1da177e2005-04-16 15:20:36 -0700512 help
513 Map driver for accessing PCMCIA linear flash memory cards. These
514 cards are usually around 4-16MiB in size. This does not include
515 Compact Flash cards which are treated as IDE devices.
516
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700517config MTD_PCMCIA_ANONYMOUS
518 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
519 depends on MTD_PCMCIA
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700520 help
521 If this option is enabled, PCMCIA cards which do not report
522 anything about themselves are assumed to be MTD cards.
523
524 If unsure, say N.
525
Mike Frysinger2e3c22f2008-05-19 18:32:24 +0800526config MTD_BFIN_ASYNC
527 tristate "Blackfin BF533-STAMP Flash Chip Support"
528 depends on BFIN533_STAMP && MTD_CFI
529 select MTD_PARTITIONS
530 default y
531 help
532 Map driver which allows for simultaneous utilization of
533 ethernet and CFI parallel flash.
534
535 If compiled as a module, it will be called bfin-async-flash.
536
Linus Torvalds1da177e2005-04-16 15:20:36 -0700537config MTD_UCLINUX
538 tristate "Generic uClinux RAM/ROM filesystem support"
539 depends on MTD_PARTITIONS && !MMU
540 help
541 Map driver to support image based filesystems for uClinux.
542
543config MTD_WRSBC8260
544 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
545 depends on (SBC82xx || SBC8560)
546 select MTD_PARTITIONS
547 select MTD_MAP_BANK_WIDTH_4
548 select MTD_MAP_BANK_WIDTH_1
549 select MTD_CFI_I1
550 select MTD_CFI_I4
551 help
552 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
553 all three flash regions on CS0, CS1 and CS6 if they are configured
554 correctly by the boot loader.
555
556config MTD_DMV182
557 tristate "Map driver for Dy-4 SVME/DMV-182 board."
558 depends on DMV182
559 select MTD_PARTITIONS
560 select MTD_MAP_BANK_WIDTH_32
561 select MTD_CFI_I8
562 select MTD_CFI_AMDSTD
563 help
564 Map driver for Dy-4 SVME/DMV-182 board.
565
566config MTD_BAST
Ben Dooks76853592005-02-18 11:03:48 +0000567 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
568 depends on ARCH_BAST || MACH_VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700569 select MTD_PARTITIONS
570 select MTD_MAP_BANK_WIDTH_16
571 select MTD_JEDECPROBE
572 help
Ben Dooks76853592005-02-18 11:03:48 +0000573 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
574 Thorcom VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700575
576 Note, this driver *cannot* over-ride the WP link on the
577 board, or currently detect the state of the link.
578
579config MTD_BAST_MAXSIZE
580 int "Maximum size for BAST flash area (MiB)"
581 depends on MTD_BAST
582 default "4"
583
584config MTD_SHARP_SL
Stanislav Brabec73061e42007-11-19 22:33:02 +0100585 tristate "ROM mapped on Sharp SL Series"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500586 depends on ARCH_PXA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700587 help
588 This enables access to the flash chip on the Sharp SL Series of PDAs.
589
David Woodhouse0bac5112007-09-23 18:51:25 +0100590config MTD_INTEL_VR_NOR
591 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
592 depends on PCI
593 help
594 Map driver for a NOR flash bank located on the Expansion Bus of the
595 Intel Vermilion Range chipset.
596
Ben Dooks99f2a8a2005-01-24 00:37:04 +0000597config MTD_PLATRAM
Thomas Gleixner3c45e002005-03-18 02:07:24 +0000598 tristate "Map driver for platform device RAM (mtd-ram)"
Ben Dooks99f2a8a2005-01-24 00:37:04 +0000599 select MTD_RAM
600 help
601 Map driver for RAM areas described via the platform device
602 system.
603
604 This selection automatically selects the map_ram driver.
605
Linus Torvalds1da177e2005-04-16 15:20:36 -0700606endmenu
607