blob: 5e651721ddb93206b27f36ca6d3c6951364b5341 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001# drivers/mtd/maps/Kconfig
Thomas Gleixner69f34c92005-11-07 11:15:40 +00002# $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner 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"
Takashi YOSHII79b9cd52006-08-15 07:26:32 -050016 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
Linus Torvalds1da177e2005-04-16 15:20:36 -070017 help
Takashi YOSHII79b9cd52006-08-15 07:26:32 -050018 This provides a 'mapping' driver which allows the NOR Flash and
19 ROM driver code to communicate with chips which are mapped
20 physically into the CPU's memory. You will need to configure
21 the physical address and size of the flash chips on your
22 particular board as well as the bus width, either statically
Linus Torvalds1da177e2005-04-16 15:20:36 -070023 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
Lennert Buytenhek73566ed2006-05-07 17:16:36 +010040 default "0"
Linus Torvalds1da177e2005-04-16 15:20:36 -070041 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
Vitaly Woola2c2fe42006-12-06 13:17:49 +030063config MTD_PHYSMAP_OF
64 tristate "Flash device in physical memory map based on OF descirption"
65 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
66 help
67 This provides a 'mapping' driver which allows the NOR Flash and
68 ROM driver code to communicate with chips which are mapped
69 physically into the CPU's memory. The mapping description here is
70 taken from OF device tree.
71
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080072config MTD_PMC_MSP_EVM
73 tristate "CFI Flash device mapped on PMC-Sierra MSP"
74 depends on PMC_MSP && MTD_CFI
75 select MTD_PARTITIONS
76 help
77 This provides a 'mapping' driver which support the way
78 in which user-programmable flash chips are connected on the
79 PMC-Sierra MSP eval/demo boards
80
81choice
82 prompt "Maximum mappable memory avialable for flash IO"
83 depends on MTD_PMC_MSP_EVM
84 default MSP_FLASH_MAP_LIMIT_32M
85
86config MSP_FLASH_MAP_LIMIT_32M
87 bool "32M"
88
89endchoice
90
91config MSP_FLASH_MAP_LIMIT
92 hex
93 default "0x02000000"
94 depends on MSP_FLASH_MAP_LIMIT_32M
95
96config MTD_PMC_MSP_RAMROOT
97 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
98 depends on PMC_MSP_EMBEDDED_ROOTFS && \
99 (MTD_BLOCK || MTD_BLOCK_RO) && \
100 MTD_RAM
101 help
102 This provides support for the embedded root file system
103 on PMC MSP devices. This memory is mapped as a MTD block device.
104
Linus Torvalds1da177e2005-04-16 15:20:36 -0700105config MTD_SUN_UFLASH
106 tristate "Sun Microsystems userflash support"
Adrian Bunk0b57ee92005-12-22 21:03:47 -0800107 depends on SPARC && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700108 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000109 This provides a 'mapping' driver which supports the way in
110 which user-programmable flash chips are connected on various
111 Sun Microsystems boardsets. This driver will require CFI support
Linus Torvalds1da177e2005-04-16 15:20:36 -0700112 in the kernel, so if you did not enable CFI previously, do that now.
113
114config MTD_PNC2000
115 tristate "CFI Flash device mapped on Photron PNC-2000"
116 depends on X86 && MTD_CFI && MTD_PARTITIONS
117 help
118 PNC-2000 is the name of Network Camera product from PHOTRON
119 Ltd. in Japan. It uses CFI-compliant flash.
120
121config MTD_SC520CDP
122 tristate "CFI Flash device mapped on AMD SC520 CDP"
Daniel Drakefbbc21c2006-04-29 11:41:44 +0100123 depends on X86 && MTD_CFI && MTD_CONCAT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700124 help
125 The SC520 CDP board has two banks of CFI-compliant chips and one
126 Dual-in-line JEDEC chip. This 'mapping' driver supports that
127 arrangement, implementing three MTD devices.
128
129config MTD_NETSC520
130 tristate "CFI Flash device mapped on AMD NetSc520"
131 depends on X86 && MTD_CFI && MTD_PARTITIONS
132 help
133 This enables access routines for the flash chips on the AMD NetSc520
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000134 demonstration board. If you have one of these boards and would like
Linus Torvalds1da177e2005-04-16 15:20:36 -0700135 to use the flash chips on it, say 'Y'.
136
137config MTD_TS5500
138 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
Sean Youngef63d002005-11-09 00:12:50 +0000139 depends on X86
Sean Young01ac7422005-06-29 09:46:19 +0000140 select MTD_PARTITIONS
141 select MTD_JEDECPROBE
142 select MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700143 help
144 This provides a driver for the on-board flash of the Technologic
Sean Younge27a9962005-06-16 09:49:33 +0100145 System's TS-5500 board. The 2MB flash is split into 3 partitions
Linus Torvalds1da177e2005-04-16 15:20:36 -0700146 which are accessed as separate MTD devices.
147
Sean Younge27a9962005-06-16 09:49:33 +0100148 mtd0 and mtd2 are the two BIOS drives, which use the resident
149 flash disk (RFD) flash translation layer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700150
151 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
152
153 Note that jumper 3 ("Write Enable Drive A") must be set
Egry Gábor4992a9e2006-05-12 17:35:02 +0100154 otherwise detection won't succeed.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700155
156config MTD_SBC_GXX
157 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
158 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
159 help
160 This provides a driver for the on-board flash of Arcom Control
161 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
162 By default the flash is split into 3 partitions which are accessed
163 as separate MTD devices. This board utilizes Intel StrataFlash.
164 More info at
165 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
166
Linus Torvalds1da177e2005-04-16 15:20:36 -0700167config MTD_LUBBOCK
168 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
169 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
170 help
171 This provides a driver for the on-board flash of the Intel
172 'Lubbock' XScale evaluation board.
173
Nico Pitrecbec19a2005-07-01 23:55:24 +0100174config MTD_MAINSTONE
175 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
176 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
177 select MTD_PARTITIONS
178 help
179 This provides a driver for the on-board flash of the Intel
180 'Mainstone PXA27x evaluation board.
181
Linus Torvalds1da177e2005-04-16 15:20:36 -0700182config MTD_OCTAGON
183 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
184 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
185 help
186 This provides a 'mapping' driver which supports the way in which
187 the flash chips are connected in the Octagon-5066 Single Board
188 Computer. More information on the board is available at
189 <http://www.octagonsystems.com/CPUpages/5066.html>.
190
191config MTD_VMAX
192 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
193 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
194 help
195 This provides a 'mapping' driver which supports the way in which
196 the flash chips are connected in the Tempustech VMAX SBC301 Single
197 Board Computer. More information on the board is available at
198 <http://www.tempustech.com/>.
199
200config MTD_SCx200_DOCFLASH
201 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
202 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
203 help
204 Enable support for a flash chip mapped using the DOCCS signal on a
205 National Semiconductor SCx200 processor.
206
207 If you don't know what to do here, say N.
208
209 If compiled as a module, it will be called scx200_docflash.
210
211config MTD_AMD76XROM
212 tristate "BIOS flash chip on AMD76x southbridge"
213 depends on X86 && MTD_JEDECPROBE
214 help
215 Support for treating the BIOS flash chip on AMD76x motherboards
216 as an MTD device - with this you can reprogram your BIOS.
217
218 BE VERY CAREFUL.
219
220config MTD_ICHXROM
221 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
222 depends on X86 && MTD_JEDECPROBE
223 help
224 Support for treating the BIOS flash chip on ICHX motherboards
225 as an MTD device - with this you can reprogram your BIOS.
226
227 BE VERY CAREFUL.
228
Lew Glendenning29175772006-10-20 14:41:04 -0700229config MTD_ESB2ROM
230 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
Randy Dunlapdffbc422006-12-04 15:03:00 -0800231 depends on X86 && MTD_JEDECPROBE && PCI
Lew Glendenning29175772006-10-20 14:41:04 -0700232 help
233 Support for treating the BIOS flash chip on ESB2 motherboards
234 as an MTD device - with this you can reprogram your BIOS.
235
236 BE VERY CAREFUL.
237
Dave Olsen90afffc2006-11-06 16:33:57 -0700238config MTD_CK804XROM
239 tristate "BIOS flash chip on Nvidia CK804"
akpm@osdl.org862c93b2007-01-25 15:15:17 -0800240 depends on X86 && MTD_JEDECPROBE && PCI
Dave Olsen90afffc2006-11-06 16:33:57 -0700241 help
242 Support for treating the BIOS flash chip on nvidia motherboards
243 as an MTD device - with this you can reprogram your BIOS.
244
245 BE VERY CAREFUL.
246
Linus Torvalds1da177e2005-04-16 15:20:36 -0700247config MTD_SCB2_FLASH
248 tristate "BIOS flash chip on Intel SCB2 boards"
249 depends on X86 && MTD_JEDECPROBE
250 help
251 Support for treating the BIOS flash chip on Intel SCB2 boards
252 as an MTD device - with this you can reprogram your BIOS.
253
254 BE VERY CAREFUL.
255
256config MTD_TSUNAMI
257 tristate "Flash chips on Tsunami TIG bus"
258 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
259 help
260 Support for the flash chip on Tsunami TIG bus.
261
262config MTD_LASAT
Martin Michlmayrceb31db2006-03-20 04:40:46 +0000263 tristate "LASAT flash device"
264 depends on LASAT && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700265 help
266 Support for the flash chips on the Lasat 100 and 200 boards.
267
268config MTD_NETtel
269 tristate "CFI flash device on SnapGear/SecureEdge"
270 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
271 help
272 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
273
Pete Popov002fa302005-02-27 21:50:25 +0000274config MTD_ALCHEMY
Roman Zippele55a3e82006-06-08 22:12:49 -0700275 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
Sean Young01ac7422005-06-29 09:46:19 +0000276 depends on SOC_AU1X00
Linus Torvalds1da177e2005-04-16 15:20:36 -0700277 help
Pete Popov002fa302005-02-27 21:50:25 +0000278 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
Linus Torvalds1da177e2005-04-16 15:20:36 -0700279
Joern Engelb523b3b2005-09-18 11:46:45 +0100280config MTD_MTX1
281 tristate "4G Systems MTX-1 Flash device"
282 depends on MIPS && MIPS_MTX1
283 help
284 Flash memory access on 4G Systems MTX-1 Board. If you have one of
285 these boards and would like to use the flash chips on it, say 'Y'.
286
Linus Torvalds1da177e2005-04-16 15:20:36 -0700287config MTD_DILNETPC
288 tristate "CFI Flash device mapped on DIL/Net PC"
289 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
290 help
291 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
292 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
293 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
294
295config MTD_DILNETPC_BOOTSIZE
296 hex "Size of DIL/Net PC flash boot partition"
297 depends on MTD_DILNETPC
298 default "0x80000"
299 help
300 The amount of space taken up by the kernel or Etherboot
301 on the DIL/Net PC flash chips.
302
303config MTD_L440GX
304 tristate "BIOS flash chip on Intel L440GX boards"
305 depends on X86 && MTD_JEDECPROBE
306 help
307 Support for treating the BIOS flash chip on Intel L440GX motherboards
308 as an MTD device - with this you can reprogram your BIOS.
309
310 BE VERY CAREFUL.
311
312config MTD_SBC8240
313 tristate "Flash device on SBC8240"
Sean Young01ac7422005-06-29 09:46:19 +0000314 depends on MTD_JEDECPROBE && 8260
Linus Torvalds1da177e2005-04-16 15:20:36 -0700315 help
316 Flash access on the SBC8240 board from Wind River. See
317 <http://www.windriver.com/products/sbc8240/>
318
319config MTD_TQM8XXL
320 tristate "CFI Flash device mapped on TQM8XXL"
Sean Young01ac7422005-06-29 09:46:19 +0000321 depends on MTD_CFI && TQM8xxL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700322 help
323 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
324 chips, currently uses AMD one. This 'mapping' driver supports
325 that arrangement, allowing the CFI probe and command set driver
326 code to communicate with the chips on the TQM8xxL board. More at
327 <http://www.denx.de/embedded-ppc-en.html>.
328
329config MTD_RPXLITE
330 tristate "CFI Flash device mapped on RPX Lite or CLLF"
Sean Young01ac7422005-06-29 09:46:19 +0000331 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700332 help
333 The RPXLite PowerPC board has CFI-compliant chips mapped in
334 a strange sparse mapping. This 'mapping' driver supports that
335 arrangement, allowing the CFI probe and command set driver code
336 to communicate with the chips on the RPXLite board. More at
337 <http://www.embeddedplanet.com/>.
338
339config MTD_MBX860
340 tristate "System flash on MBX860 board"
Sean Young01ac7422005-06-29 09:46:19 +0000341 depends on MTD_CFI && MBX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700342 help
343 This enables access routines for the flash chips on the Motorola
344 MBX860 board. If you have one of these boards and would like
345 to use the flash chips on it, say 'Y'.
346
347config MTD_DBOX2
348 tristate "CFI Flash device mapped on D-Box2"
Sean Young01ac7422005-06-29 09:46:19 +0000349 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700350 help
351 This enables access routines for the flash chips on the Nokia/Sagem
352 D-Box 2 board. If you have one of these boards and would like to use
353 the flash chips on it, say 'Y'.
354
355config MTD_CFI_FLAGADM
356 tristate "CFI Flash device mapping on FlagaDM"
Sean Young01ac7422005-06-29 09:46:19 +0000357 depends on 8xx && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700358 help
359 Mapping for the Flaga digital module. If you don't have one, ignore
360 this setting.
361
362config MTD_BEECH
363 tristate "CFI Flash device mapped on IBM 405LP Beech"
Sean Young01ac7422005-06-29 09:46:19 +0000364 depends on MTD_CFI && BEECH
Linus Torvalds1da177e2005-04-16 15:20:36 -0700365 help
366 This enables access routines for the flash chips on the IBM
367 405LP Beech board. If you have one of these boards and would like
368 to use the flash chips on it, say 'Y'.
369
370config MTD_ARCTIC
371 tristate "CFI Flash device mapped on IBM 405LP Arctic"
Sean Young01ac7422005-06-29 09:46:19 +0000372 depends on MTD_CFI && ARCTIC2
Linus Torvalds1da177e2005-04-16 15:20:36 -0700373 help
374 This enables access routines for the flash chips on the IBM 405LP
375 Arctic board. If you have one of these boards and would like to
376 use the flash chips on it, say 'Y'.
377
378config MTD_WALNUT
379 tristate "Flash device mapped on IBM 405GP Walnut"
Sean Young01ac7422005-06-29 09:46:19 +0000380 depends on MTD_JEDECPROBE && WALNUT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700381 help
382 This enables access routines for the flash chips on the IBM 405GP
383 Walnut board. If you have one of these boards and would like to
384 use the flash chips on it, say 'Y'.
385
386config MTD_EBONY
387 tristate "Flash devices mapped on IBM 440GP Ebony"
Sean Young01ac7422005-06-29 09:46:19 +0000388 depends on MTD_JEDECPROBE && EBONY
Linus Torvalds1da177e2005-04-16 15:20:36 -0700389 help
390 This enables access routines for the flash chips on the IBM 440GP
391 Ebony board. If you have one of these boards and would like to
392 use the flash chips on it, say 'Y'.
393
394config MTD_OCOTEA
395 tristate "Flash devices mapped on IBM 440GX Ocotea"
Sean Young01ac7422005-06-29 09:46:19 +0000396 depends on MTD_CFI && OCOTEA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700397 help
398 This enables access routines for the flash chips on the IBM 440GX
399 Ocotea board. If you have one of these boards and would like to
400 use the flash chips on it, say 'Y'.
401
402config MTD_REDWOOD
403 tristate "CFI Flash devices mapped on IBM Redwood"
Sean Young01ac7422005-06-29 09:46:19 +0000404 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700405 help
406 This enables access routines for the flash chips on the IBM
407 Redwood board. If you have one of these boards and would like to
408 use the flash chips on it, say 'Y'.
409
Marian Balakowiczbe30c102005-11-07 08:33:38 +0000410config MTD_TQM834x
411 tristate "Flash device mapped on TQ Components TQM834x Boards"
412 depends on MTD_CFI && TQM834x
413 help
414 This enables access routines for the flash chips on the
415 TQ Components TQM834x boards. If you have one of these boards
416 and would like to use the flash chips on it, say 'Y'.
417
Linus Torvalds1da177e2005-04-16 15:20:36 -0700418config MTD_OCELOT
419 tristate "Momenco Ocelot boot flash device"
420 depends on MIPS && MOMENCO_OCELOT
421 help
422 This enables access routines for the boot flash device and for the
423 NVRAM on the Momenco Ocelot board. If you have one of these boards
424 and would like access to either of these, say 'Y'.
425
426config MTD_SOLUTIONENGINE
427 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
428 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
429 help
430 This enables access to the flash chips on the Hitachi SolutionEngine and
431 similar boards. Say 'Y' if you are building a kernel for such a board.
432
433config MTD_ARM_INTEGRATOR
434 tristate "CFI Flash device mapped on ARM Integrator/P720T"
435 depends on ARM && MTD_CFI
436
437config MTD_CDB89712
438 tristate "Cirrus CDB89712 evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000439 depends on MTD_CFI && ARCH_CDB89712
Linus Torvalds1da177e2005-04-16 15:20:36 -0700440 help
441 This enables access to the flash or ROM chips on the CDB89712 board.
442 If you have such a board, say 'Y'.
443
444config MTD_SA1100
445 tristate "CFI Flash device mapped on StrongARM SA11x0"
Sean Young01ac7422005-06-29 09:46:19 +0000446 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700447 help
448 This enables access to the flash chips on most platforms based on
449 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
450 If you have such a board, say 'Y'.
451
452config MTD_IPAQ
453 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
Sean Young01ac7422005-06-29 09:46:19 +0000454 depends on IPAQ_HANDHELD && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700455 help
456 This provides a driver for the on-board flash of the iPAQ.
457
458config MTD_DC21285
459 tristate "CFI Flash device mapped on DC21285 Footbridge"
Sean Young01ac7422005-06-29 09:46:19 +0000460 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700461 help
462 This provides a driver for the flash accessed using Intel's
463 21285 bridge used with Intel's StrongARM processors. More info at
464 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
465
Linus Torvalds1da177e2005-04-16 15:20:36 -0700466config MTD_IXP4XX
467 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000468 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700469 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000470 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700471 on Intel's IXP4xx family of network processors such as the
472 IXDP425 and Coyote. If you have an IXP4xx based board and
473 would like to use the flash chips on it, say 'Y'.
474
475config MTD_IXP2000
476 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000477 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700478 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000479 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700480 on Intel's IXP2000 family of network processors such as the
481 IXDP425 and Coyote. If you have an IXP2000 based board and
482 would like to use the flash chips on it, say 'Y'.
483
Linus Torvalds1da177e2005-04-16 15:20:36 -0700484config MTD_FORTUNET
485 tristate "CFI Flash device mapped on the FortuNet board"
Sean Young01ac7422005-06-29 09:46:19 +0000486 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700487 help
488 This enables access to the Flash on the FortuNet board. If you
489 have such a board, say 'Y'.
490
491config MTD_AUTCPU12
492 tristate "NV-RAM mapping AUTCPU12 board"
Sean Young01ac7422005-06-29 09:46:19 +0000493 depends on ARCH_AUTCPU12
Linus Torvalds1da177e2005-04-16 15:20:36 -0700494 help
495 This enables access to the NV-RAM on autronix autcpu12 board.
496 If you have such a board, say 'Y'.
497
498config MTD_EDB7312
499 tristate "CFI Flash device mapped on EDB7312"
Sean Young01ac7422005-06-29 09:46:19 +0000500 depends on ARCH_EDB7312 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700501 help
502 This enables access to the CFI Flash on the Cogent EDB7312 board.
503 If you have such a board, say 'Y' here.
504
505config MTD_IMPA7
506 tristate "JEDEC Flash device mapped on impA7"
507 depends on ARM && MTD_JEDECPROBE
508 help
509 This enables access to the NOR Flash on the impA7 board of
510 implementa GmbH. If you have such a board, say 'Y' here.
511
512config MTD_CEIVA
513 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
Sean Young01ac7422005-06-29 09:46:19 +0000514 depends on MTD_JEDECPROBE && ARCH_CEIVA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700515 help
516 This enables access to the flash chips on the Ceiva/Polaroid
517 PhotoMax Digital Picture Frame.
518 If you have such a device, say 'Y'.
519
520config MTD_NOR_TOTO
521 tristate "NOR Flash device on TOTO board"
Sean Young01ac7422005-06-29 09:46:19 +0000522 depends on ARCH_OMAP && OMAP_TOTO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700523 help
524 This enables access to the NOR flash on the Texas Instruments
525 TOTO board.
526
527config MTD_H720X
528 tristate "Hynix evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000529 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700530 help
531 This enables access to the flash chips on the Hynix evaluation boards.
532 If you have such a board, say 'Y'.
533
534config MTD_MPC1211
535 tristate "CFI Flash device mapped on Interface MPC-1211"
Sean Young01ac7422005-06-29 09:46:19 +0000536 depends on SH_MPC1211 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700537 help
538 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
539 If you have such a board, say 'Y'.
540
Todd Poynor10c96f22005-07-02 02:53:28 +0100541config MTD_OMAP_NOR
542 tristate "TI OMAP board mappings"
543 depends on MTD_CFI && ARCH_OMAP
544 help
545 This enables access to the NOR flash chips on TI OMAP-based
546 boards defining flash platform devices and flash platform data.
547 These boards include the Innovator, H2, H3, OSK, Perseus2, and
548 more. If you have such a board, say 'Y'.
549
Linus Torvalds1da177e2005-04-16 15:20:36 -0700550# This needs CFI or JEDEC, depending on the cards found.
551config MTD_PCI
552 tristate "PCI MTD driver"
553 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
554 help
555 Mapping for accessing flash devices on add-in cards like the Intel XScale
556 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
557 (please see the manual for the link settings).
558
559 If you are not sure, say N.
560
561config MTD_PCMCIA
562 tristate "PCMCIA MTD driver"
563 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
564 help
565 Map driver for accessing PCMCIA linear flash memory cards. These
566 cards are usually around 4-16MiB in size. This does not include
567 Compact Flash cards which are treated as IDE devices.
568
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700569config MTD_PCMCIA_ANONYMOUS
570 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
571 depends on MTD_PCMCIA
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700572 help
573 If this option is enabled, PCMCIA cards which do not report
574 anything about themselves are assumed to be MTD cards.
575
576 If unsure, say N.
577
Linus Torvalds1da177e2005-04-16 15:20:36 -0700578config MTD_UCLINUX
579 tristate "Generic uClinux RAM/ROM filesystem support"
580 depends on MTD_PARTITIONS && !MMU
581 help
582 Map driver to support image based filesystems for uClinux.
583
584config MTD_WRSBC8260
585 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
586 depends on (SBC82xx || SBC8560)
587 select MTD_PARTITIONS
588 select MTD_MAP_BANK_WIDTH_4
589 select MTD_MAP_BANK_WIDTH_1
590 select MTD_CFI_I1
591 select MTD_CFI_I4
592 help
593 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
594 all three flash regions on CS0, CS1 and CS6 if they are configured
595 correctly by the boot loader.
596
597config MTD_DMV182
598 tristate "Map driver for Dy-4 SVME/DMV-182 board."
599 depends on DMV182
600 select MTD_PARTITIONS
601 select MTD_MAP_BANK_WIDTH_32
602 select MTD_CFI_I8
603 select MTD_CFI_AMDSTD
604 help
605 Map driver for Dy-4 SVME/DMV-182 board.
606
607config MTD_BAST
Ben Dooks76853592005-02-18 11:03:48 +0000608 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
609 depends on ARCH_BAST || MACH_VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700610 select MTD_PARTITIONS
611 select MTD_MAP_BANK_WIDTH_16
612 select MTD_JEDECPROBE
613 help
Ben Dooks76853592005-02-18 11:03:48 +0000614 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
615 Thorcom VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700616
617 Note, this driver *cannot* over-ride the WP link on the
618 board, or currently detect the state of the link.
619
620config MTD_BAST_MAXSIZE
621 int "Maximum size for BAST flash area (MiB)"
622 depends on MTD_BAST
623 default "4"
624
625config MTD_SHARP_SL
Matt LaPlante3cb2fcc2006-11-30 05:22:59 +0100626 bool "ROM mapped on Sharp SL Series"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700627 depends on MTD && ARCH_PXA
628 help
629 This enables access to the flash chip on the Sharp SL Series of PDAs.
630
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000631config MTD_PLATRAM
Thomas Gleixner3c45e00a2005-03-18 02:07:24 +0000632 tristate "Map driver for platform device RAM (mtd-ram)"
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000633 depends on MTD
634 select MTD_RAM
635 help
636 Map driver for RAM areas described via the platform device
637 system.
638
639 This selection automatically selects the map_ram driver.
640
Linus Torvalds1da177e2005-04-16 15:20:36 -0700641endmenu
642