blob: 94a693f4bea79979b97179e478e4c5e4d47ca3a9 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001# drivers/mtd/maps/Kconfig
Joern Engelb523b3b2005-09-18 11:46:45 +01002# $Id: Kconfig,v 1.59 2005/09/18 10:46:41 joern Exp $
Linus Torvalds1da177e2005-04-16 15:20:36 -07003
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
17 help
18 This provides a 'mapping' driver which allows the CFI probe and
19 command set driver code to communicate with flash chips which
20 are mapped physically into the CPU's memory. You will need to
21 configure the physical address and size of the flash chips on
22 your 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 "0x4000000"
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_SUN_UFLASH
64 tristate "Sun Microsystems userflash support"
65 depends on (SPARC32 || SPARC64) && MTD_CFI
66 help
67 This provides a 'mapping' driver which supports the way in
68 which user-programmable flash chips are connected on various
69 Sun Microsystems boardsets. This driver will require CFI support
70 in the kernel, so if you did not enable CFI previously, do that now.
71
72config MTD_PNC2000
73 tristate "CFI Flash device mapped on Photron PNC-2000"
74 depends on X86 && MTD_CFI && MTD_PARTITIONS
75 help
76 PNC-2000 is the name of Network Camera product from PHOTRON
77 Ltd. in Japan. It uses CFI-compliant flash.
78
79config MTD_SC520CDP
80 tristate "CFI Flash device mapped on AMD SC520 CDP"
81 depends on X86 && MTD_CFI
82 help
83 The SC520 CDP board has two banks of CFI-compliant chips and one
84 Dual-in-line JEDEC chip. This 'mapping' driver supports that
85 arrangement, implementing three MTD devices.
86
87config MTD_NETSC520
88 tristate "CFI Flash device mapped on AMD NetSc520"
89 depends on X86 && MTD_CFI && MTD_PARTITIONS
90 help
91 This enables access routines for the flash chips on the AMD NetSc520
92 demonstration board. If you have one of these boards and would like
93 to use the flash chips on it, say 'Y'.
94
95config MTD_TS5500
96 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
Sean Young01ac7422005-06-29 09:46:19 +000097 depends on ELAN
98 select MTD_PARTITIONS
99 select MTD_JEDECPROBE
100 select MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700101 help
102 This provides a driver for the on-board flash of the Technologic
Sean Younge27a9962005-06-16 09:49:33 +0100103 System's TS-5500 board. The 2MB flash is split into 3 partitions
Linus Torvalds1da177e2005-04-16 15:20:36 -0700104 which are accessed as separate MTD devices.
105
Sean Younge27a9962005-06-16 09:49:33 +0100106 mtd0 and mtd2 are the two BIOS drives, which use the resident
107 flash disk (RFD) flash translation layer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700108
109 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
110
111 Note that jumper 3 ("Write Enable Drive A") must be set
112 otherwise detection won't succeeed.
113
114config MTD_SBC_GXX
115 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
116 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
117 help
118 This provides a driver for the on-board flash of Arcom Control
119 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
120 By default the flash is split into 3 partitions which are accessed
121 as separate MTD devices. This board utilizes Intel StrataFlash.
122 More info at
123 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
124
Linus Torvalds1da177e2005-04-16 15:20:36 -0700125config MTD_LUBBOCK
126 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
127 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
128 help
129 This provides a driver for the on-board flash of the Intel
130 'Lubbock' XScale evaluation board.
131
Nico Pitrecbec19a2005-07-01 23:55:24 +0100132config MTD_MAINSTONE
133 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
134 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
135 select MTD_PARTITIONS
136 help
137 This provides a driver for the on-board flash of the Intel
138 'Mainstone PXA27x evaluation board.
139
Linus Torvalds1da177e2005-04-16 15:20:36 -0700140config MTD_OCTAGON
141 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
142 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
143 help
144 This provides a 'mapping' driver which supports the way in which
145 the flash chips are connected in the Octagon-5066 Single Board
146 Computer. More information on the board is available at
147 <http://www.octagonsystems.com/CPUpages/5066.html>.
148
149config MTD_VMAX
150 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
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 Tempustech VMAX SBC301 Single
155 Board Computer. More information on the board is available at
156 <http://www.tempustech.com/>.
157
158config MTD_SCx200_DOCFLASH
159 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
160 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
161 help
162 Enable support for a flash chip mapped using the DOCCS signal on a
163 National Semiconductor SCx200 processor.
164
165 If you don't know what to do here, say N.
166
167 If compiled as a module, it will be called scx200_docflash.
168
169config MTD_AMD76XROM
170 tristate "BIOS flash chip on AMD76x southbridge"
171 depends on X86 && MTD_JEDECPROBE
172 help
173 Support for treating the BIOS flash chip on AMD76x motherboards
174 as an MTD device - with this you can reprogram your BIOS.
175
176 BE VERY CAREFUL.
177
178config MTD_ICHXROM
179 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
180 depends on X86 && MTD_JEDECPROBE
181 help
182 Support for treating the BIOS flash chip on ICHX motherboards
183 as an MTD device - with this you can reprogram your BIOS.
184
185 BE VERY CAREFUL.
186
187config MTD_SCB2_FLASH
188 tristate "BIOS flash chip on Intel SCB2 boards"
189 depends on X86 && MTD_JEDECPROBE
190 help
191 Support for treating the BIOS flash chip on Intel SCB2 boards
192 as an MTD device - with this you can reprogram your BIOS.
193
194 BE VERY CAREFUL.
195
196config MTD_TSUNAMI
197 tristate "Flash chips on Tsunami TIG bus"
198 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
199 help
200 Support for the flash chip on Tsunami TIG bus.
201
202config MTD_LASAT
203 tristate "Flash chips on LASAT board"
204 depends on LASAT
205 help
206 Support for the flash chips on the Lasat 100 and 200 boards.
207
208config MTD_NETtel
209 tristate "CFI flash device on SnapGear/SecureEdge"
210 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
211 help
212 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
213
Pete Popov002fa302005-02-27 21:50:25 +0000214config MTD_ALCHEMY
215 tristate ' AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support'
Sean Young01ac7422005-06-29 09:46:19 +0000216 depends on SOC_AU1X00
Linus Torvalds1da177e2005-04-16 15:20:36 -0700217 help
Pete Popov002fa302005-02-27 21:50:25 +0000218 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
Linus Torvalds1da177e2005-04-16 15:20:36 -0700219
Joern Engelb523b3b2005-09-18 11:46:45 +0100220config MTD_MTX1
221 tristate "4G Systems MTX-1 Flash device"
222 depends on MIPS && MIPS_MTX1
223 help
224 Flash memory access on 4G Systems MTX-1 Board. If you have one of
225 these boards and would like to use the flash chips on it, say 'Y'.
226
Linus Torvalds1da177e2005-04-16 15:20:36 -0700227config MTD_DILNETPC
228 tristate "CFI Flash device mapped on DIL/Net PC"
229 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
230 help
231 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
232 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
233 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
234
235config MTD_DILNETPC_BOOTSIZE
236 hex "Size of DIL/Net PC flash boot partition"
237 depends on MTD_DILNETPC
238 default "0x80000"
239 help
240 The amount of space taken up by the kernel or Etherboot
241 on the DIL/Net PC flash chips.
242
243config MTD_L440GX
244 tristate "BIOS flash chip on Intel L440GX boards"
245 depends on X86 && MTD_JEDECPROBE
246 help
247 Support for treating the BIOS flash chip on Intel L440GX motherboards
248 as an MTD device - with this you can reprogram your BIOS.
249
250 BE VERY CAREFUL.
251
252config MTD_SBC8240
253 tristate "Flash device on SBC8240"
Sean Young01ac7422005-06-29 09:46:19 +0000254 depends on MTD_JEDECPROBE && 8260
Linus Torvalds1da177e2005-04-16 15:20:36 -0700255 help
256 Flash access on the SBC8240 board from Wind River. See
257 <http://www.windriver.com/products/sbc8240/>
258
259config MTD_TQM8XXL
260 tristate "CFI Flash device mapped on TQM8XXL"
Sean Young01ac7422005-06-29 09:46:19 +0000261 depends on MTD_CFI && TQM8xxL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700262 help
263 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
264 chips, currently uses AMD one. This 'mapping' driver supports
265 that arrangement, allowing the CFI probe and command set driver
266 code to communicate with the chips on the TQM8xxL board. More at
267 <http://www.denx.de/embedded-ppc-en.html>.
268
269config MTD_RPXLITE
270 tristate "CFI Flash device mapped on RPX Lite or CLLF"
Sean Young01ac7422005-06-29 09:46:19 +0000271 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700272 help
273 The RPXLite PowerPC board has CFI-compliant chips mapped in
274 a strange sparse mapping. This 'mapping' driver supports that
275 arrangement, allowing the CFI probe and command set driver code
276 to communicate with the chips on the RPXLite board. More at
277 <http://www.embeddedplanet.com/>.
278
279config MTD_MBX860
280 tristate "System flash on MBX860 board"
Sean Young01ac7422005-06-29 09:46:19 +0000281 depends on MTD_CFI && MBX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700282 help
283 This enables access routines for the flash chips on the Motorola
284 MBX860 board. If you have one of these boards and would like
285 to use the flash chips on it, say 'Y'.
286
287config MTD_DBOX2
288 tristate "CFI Flash device mapped on D-Box2"
Sean Young01ac7422005-06-29 09:46:19 +0000289 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700290 help
291 This enables access routines for the flash chips on the Nokia/Sagem
292 D-Box 2 board. If you have one of these boards and would like to use
293 the flash chips on it, say 'Y'.
294
295config MTD_CFI_FLAGADM
296 tristate "CFI Flash device mapping on FlagaDM"
Sean Young01ac7422005-06-29 09:46:19 +0000297 depends on 8xx && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700298 help
299 Mapping for the Flaga digital module. If you don't have one, ignore
300 this setting.
301
302config MTD_BEECH
303 tristate "CFI Flash device mapped on IBM 405LP Beech"
Sean Young01ac7422005-06-29 09:46:19 +0000304 depends on MTD_CFI && BEECH
Linus Torvalds1da177e2005-04-16 15:20:36 -0700305 help
306 This enables access routines for the flash chips on the IBM
307 405LP Beech board. If you have one of these boards and would like
308 to use the flash chips on it, say 'Y'.
309
310config MTD_ARCTIC
311 tristate "CFI Flash device mapped on IBM 405LP Arctic"
Sean Young01ac7422005-06-29 09:46:19 +0000312 depends on MTD_CFI && ARCTIC2
Linus Torvalds1da177e2005-04-16 15:20:36 -0700313 help
314 This enables access routines for the flash chips on the IBM 405LP
315 Arctic board. If you have one of these boards and would like to
316 use the flash chips on it, say 'Y'.
317
318config MTD_WALNUT
319 tristate "Flash device mapped on IBM 405GP Walnut"
Sean Young01ac7422005-06-29 09:46:19 +0000320 depends on MTD_JEDECPROBE && WALNUT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700321 help
322 This enables access routines for the flash chips on the IBM 405GP
323 Walnut board. If you have one of these boards and would like to
324 use the flash chips on it, say 'Y'.
325
326config MTD_EBONY
327 tristate "Flash devices mapped on IBM 440GP Ebony"
Sean Young01ac7422005-06-29 09:46:19 +0000328 depends on MTD_JEDECPROBE && EBONY
Linus Torvalds1da177e2005-04-16 15:20:36 -0700329 help
330 This enables access routines for the flash chips on the IBM 440GP
331 Ebony board. If you have one of these boards and would like to
332 use the flash chips on it, say 'Y'.
333
334config MTD_OCOTEA
335 tristate "Flash devices mapped on IBM 440GX Ocotea"
Sean Young01ac7422005-06-29 09:46:19 +0000336 depends on MTD_CFI && OCOTEA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700337 help
338 This enables access routines for the flash chips on the IBM 440GX
339 Ocotea board. If you have one of these boards and would like to
340 use the flash chips on it, say 'Y'.
341
342config MTD_REDWOOD
343 tristate "CFI Flash devices mapped on IBM Redwood"
Sean Young01ac7422005-06-29 09:46:19 +0000344 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700345 help
346 This enables access routines for the flash chips on the IBM
347 Redwood board. If you have one of these boards and would like to
348 use the flash chips on it, say 'Y'.
349
350config MTD_CSTM_MIPS_IXX
351 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
352 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
353 help
354 This provides a mapping driver for the Integrated Technology
355 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
356 Reference Board. It provides the necessary addressing, length,
357 buswidth, vpp code and addition setup of the flash device for
358 these boards. In addition, this mapping driver can be used for
359 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
360 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
361 using one partition. The start address can be offset from the
362 beginning of flash and the len can be less than the total flash
363 device size to allow a window into the flash. Both CFI and JEDEC
364 probes are called.
365
366config MTD_CSTM_MIPS_IXX_START
367 hex "Physical start address of flash mapping"
368 depends on MTD_CSTM_MIPS_IXX
369 default "0x8000000"
370 help
371 This is the physical memory location that the MTD driver will
372 use for the flash chips on your particular target board.
373 Refer to the memory map which should hopefully be in the
374 documentation for your board.
375
376config MTD_CSTM_MIPS_IXX_LEN
377 hex "Physical length of flash mapping"
378 depends on MTD_CSTM_MIPS_IXX
379 default "0x4000000"
380 help
381 This is the total length that the MTD driver will use for the
382 flash chips on your particular board. Refer to the memory
383 map which should hopefully be in the documentation for your
384 board.
385
386config MTD_CSTM_MIPS_IXX_BUSWIDTH
387 int "Bus width in octets"
388 depends on MTD_CSTM_MIPS_IXX
389 default "2"
390 help
391 This is the total bus width of the mapping of the flash chips
392 on your particular board.
393
394config MTD_OCELOT
395 tristate "Momenco Ocelot boot flash device"
396 depends on MIPS && MOMENCO_OCELOT
397 help
398 This enables access routines for the boot flash device and for the
399 NVRAM on the Momenco Ocelot board. If you have one of these boards
400 and would like access to either of these, say 'Y'.
401
402config MTD_SOLUTIONENGINE
403 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
404 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
405 help
406 This enables access to the flash chips on the Hitachi SolutionEngine and
407 similar boards. Say 'Y' if you are building a kernel for such a board.
408
409config MTD_ARM_INTEGRATOR
410 tristate "CFI Flash device mapped on ARM Integrator/P720T"
411 depends on ARM && MTD_CFI
412
413config MTD_CDB89712
414 tristate "Cirrus CDB89712 evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000415 depends on MTD_CFI && ARCH_CDB89712
Linus Torvalds1da177e2005-04-16 15:20:36 -0700416 help
417 This enables access to the flash or ROM chips on the CDB89712 board.
418 If you have such a board, say 'Y'.
419
420config MTD_SA1100
421 tristate "CFI Flash device mapped on StrongARM SA11x0"
Sean Young01ac7422005-06-29 09:46:19 +0000422 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700423 help
424 This enables access to the flash chips on most platforms based on
425 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
426 If you have such a board, say 'Y'.
427
428config MTD_IPAQ
429 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
Sean Young01ac7422005-06-29 09:46:19 +0000430 depends on IPAQ_HANDHELD && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700431 help
432 This provides a driver for the on-board flash of the iPAQ.
433
434config MTD_DC21285
435 tristate "CFI Flash device mapped on DC21285 Footbridge"
Sean Young01ac7422005-06-29 09:46:19 +0000436 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700437 help
438 This provides a driver for the flash accessed using Intel's
439 21285 bridge used with Intel's StrongARM processors. More info at
440 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
441
442config MTD_IQ80310
443 tristate "CFI Flash device mapped on the XScale IQ80310 board"
Sean Young01ac7422005-06-29 09:46:19 +0000444 depends on MTD_CFI && ARCH_IQ80310
Linus Torvalds1da177e2005-04-16 15:20:36 -0700445 help
446 This enables access routines for the flash chips on the Intel XScale
447 IQ80310 evaluation board. If you have one of these boards and would
448 like to use the flash chips on it, say 'Y'.
449
450config MTD_IXP4XX
451 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000452 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700453 help
454 This enables MTD access to flash devices on platforms based
455 on Intel's IXP4xx family of network processors such as the
456 IXDP425 and Coyote. If you have an IXP4xx based board and
457 would like to use the flash chips on it, say 'Y'.
458
459config MTD_IXP2000
460 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000461 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700462 help
463 This enables MTD access to flash devices on platforms based
464 on Intel's IXP2000 family of network processors such as the
465 IXDP425 and Coyote. If you have an IXP2000 based board and
466 would like to use the flash chips on it, say 'Y'.
467
468config MTD_EPXA10DB
469 tristate "CFI Flash device mapped on Epxa10db"
Sean Young01ac7422005-06-29 09:46:19 +0000470 depends on MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700471 help
472 This enables support for the flash devices on the Altera
473 Excalibur XA10 Development Board. If you are building a kernel
474 for on of these boards then you should say 'Y' otherwise say 'N'.
475
476config MTD_FORTUNET
477 tristate "CFI Flash device mapped on the FortuNet board"
Sean Young01ac7422005-06-29 09:46:19 +0000478 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700479 help
480 This enables access to the Flash on the FortuNet board. If you
481 have such a board, say 'Y'.
482
483config MTD_AUTCPU12
484 tristate "NV-RAM mapping AUTCPU12 board"
Sean Young01ac7422005-06-29 09:46:19 +0000485 depends on ARCH_AUTCPU12
Linus Torvalds1da177e2005-04-16 15:20:36 -0700486 help
487 This enables access to the NV-RAM on autronix autcpu12 board.
488 If you have such a board, say 'Y'.
489
490config MTD_EDB7312
491 tristate "CFI Flash device mapped on EDB7312"
Sean Young01ac7422005-06-29 09:46:19 +0000492 depends on ARCH_EDB7312 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700493 help
494 This enables access to the CFI Flash on the Cogent EDB7312 board.
495 If you have such a board, say 'Y' here.
496
497config MTD_IMPA7
498 tristate "JEDEC Flash device mapped on impA7"
499 depends on ARM && MTD_JEDECPROBE
500 help
501 This enables access to the NOR Flash on the impA7 board of
502 implementa GmbH. If you have such a board, say 'Y' here.
503
504config MTD_CEIVA
505 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
Sean Young01ac7422005-06-29 09:46:19 +0000506 depends on MTD_JEDECPROBE && ARCH_CEIVA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700507 help
508 This enables access to the flash chips on the Ceiva/Polaroid
509 PhotoMax Digital Picture Frame.
510 If you have such a device, say 'Y'.
511
512config MTD_NOR_TOTO
513 tristate "NOR Flash device on TOTO board"
Sean Young01ac7422005-06-29 09:46:19 +0000514 depends on ARCH_OMAP && OMAP_TOTO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700515 help
516 This enables access to the NOR flash on the Texas Instruments
517 TOTO board.
518
519config MTD_H720X
520 tristate "Hynix evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000521 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700522 help
523 This enables access to the flash chips on the Hynix evaluation boards.
524 If you have such a board, say 'Y'.
525
526config MTD_MPC1211
527 tristate "CFI Flash device mapped on Interface MPC-1211"
Sean Young01ac7422005-06-29 09:46:19 +0000528 depends on SH_MPC1211 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700529 help
530 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
531 If you have such a board, say 'Y'.
532
Todd Poynor9c517e62005-09-14 20:14:17 +0100533config MTD_PQ2FADS
534 tristate "JEDEC flash SIMM mapped on PQ2FADS and 8272ADS boards"
535 depends on (ADS8272 || PQ2FADS) && MTD_PARTITIONS && MTD_JEDECPROBE && MTD_PHYSMAP && MTD_CFI_GEOMETRY && MTD_CFI_INTELEXT
536 help
537 This enables access to flash SIMM on PQ2FADS-like boards
538
Todd Poynor10c96f22005-07-02 02:53:28 +0100539config MTD_OMAP_NOR
540 tristate "TI OMAP board mappings"
541 depends on MTD_CFI && ARCH_OMAP
542 help
543 This enables access to the NOR flash chips on TI OMAP-based
544 boards defining flash platform devices and flash platform data.
545 These boards include the Innovator, H2, H3, OSK, Perseus2, and
546 more. If you have such a board, say 'Y'.
547
Linus Torvalds1da177e2005-04-16 15:20:36 -0700548# This needs CFI or JEDEC, depending on the cards found.
549config MTD_PCI
550 tristate "PCI MTD driver"
551 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
552 help
553 Mapping for accessing flash devices on add-in cards like the Intel XScale
554 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
555 (please see the manual for the link settings).
556
557 If you are not sure, say N.
558
559config MTD_PCMCIA
560 tristate "PCMCIA MTD driver"
561 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
562 help
563 Map driver for accessing PCMCIA linear flash memory cards. These
564 cards are usually around 4-16MiB in size. This does not include
565 Compact Flash cards which are treated as IDE devices.
566
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700567config MTD_PCMCIA_ANONYMOUS
568 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
569 depends on MTD_PCMCIA
570 default N
571 help
572 If this option is enabled, PCMCIA cards which do not report
573 anything about themselves are assumed to be MTD cards.
574
575 If unsure, say N.
576
Linus Torvalds1da177e2005-04-16 15:20:36 -0700577config MTD_UCLINUX
578 tristate "Generic uClinux RAM/ROM filesystem support"
579 depends on MTD_PARTITIONS && !MMU
580 help
581 Map driver to support image based filesystems for uClinux.
582
583config MTD_WRSBC8260
584 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
585 depends on (SBC82xx || SBC8560)
586 select MTD_PARTITIONS
587 select MTD_MAP_BANK_WIDTH_4
588 select MTD_MAP_BANK_WIDTH_1
589 select MTD_CFI_I1
590 select MTD_CFI_I4
591 help
592 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
593 all three flash regions on CS0, CS1 and CS6 if they are configured
594 correctly by the boot loader.
595
596config MTD_DMV182
597 tristate "Map driver for Dy-4 SVME/DMV-182 board."
598 depends on DMV182
599 select MTD_PARTITIONS
600 select MTD_MAP_BANK_WIDTH_32
601 select MTD_CFI_I8
602 select MTD_CFI_AMDSTD
603 help
604 Map driver for Dy-4 SVME/DMV-182 board.
605
606config MTD_BAST
Ben Dooks76853592005-02-18 11:03:48 +0000607 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
608 depends on ARCH_BAST || MACH_VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700609 select MTD_PARTITIONS
610 select MTD_MAP_BANK_WIDTH_16
611 select MTD_JEDECPROBE
612 help
Ben Dooks76853592005-02-18 11:03:48 +0000613 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
614 Thorcom VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700615
616 Note, this driver *cannot* over-ride the WP link on the
617 board, or currently detect the state of the link.
618
619config MTD_BAST_MAXSIZE
620 int "Maximum size for BAST flash area (MiB)"
621 depends on MTD_BAST
622 default "4"
623
624config MTD_SHARP_SL
625 bool "ROM maped on Sharp SL Series"
626 depends on MTD && ARCH_PXA
627 help
628 This enables access to the flash chip on the Sharp SL Series of PDAs.
629
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000630config MTD_PLATRAM
Thomas Gleixner3c45e00a2005-03-18 02:07:24 +0000631 tristate "Map driver for platform device RAM (mtd-ram)"
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000632 depends on MTD
633 select MTD_RAM
634 help
635 Map driver for RAM areas described via the platform device
636 system.
637
638 This selection automatically selects the map_ram driver.
639
Linus Torvalds1da177e2005-04-16 15:20:36 -0700640endmenu
641