blob: bbf0553bdb2e67890a83387d30a2810f6bda5c93 [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
Linus Torvalds1da177e2005-04-16 15:20:36 -070072config MTD_SUN_UFLASH
73 tristate "Sun Microsystems userflash support"
Adrian Bunk0b57ee92005-12-22 21:03:47 -080074 depends on SPARC && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -070075 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +000076 This provides a 'mapping' driver which supports the way in
77 which user-programmable flash chips are connected on various
78 Sun Microsystems boardsets. This driver will require CFI support
Linus Torvalds1da177e2005-04-16 15:20:36 -070079 in the kernel, so if you did not enable CFI previously, do that now.
80
81config MTD_PNC2000
82 tristate "CFI Flash device mapped on Photron PNC-2000"
83 depends on X86 && MTD_CFI && MTD_PARTITIONS
84 help
85 PNC-2000 is the name of Network Camera product from PHOTRON
86 Ltd. in Japan. It uses CFI-compliant flash.
87
88config MTD_SC520CDP
89 tristate "CFI Flash device mapped on AMD SC520 CDP"
Daniel Drakefbbc21c2006-04-29 11:41:44 +010090 depends on X86 && MTD_CFI && MTD_CONCAT
Linus Torvalds1da177e2005-04-16 15:20:36 -070091 help
92 The SC520 CDP board has two banks of CFI-compliant chips and one
93 Dual-in-line JEDEC chip. This 'mapping' driver supports that
94 arrangement, implementing three MTD devices.
95
96config MTD_NETSC520
97 tristate "CFI Flash device mapped on AMD NetSc520"
98 depends on X86 && MTD_CFI && MTD_PARTITIONS
99 help
100 This enables access routines for the flash chips on the AMD NetSc520
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000101 demonstration board. If you have one of these boards and would like
Linus Torvalds1da177e2005-04-16 15:20:36 -0700102 to use the flash chips on it, say 'Y'.
103
104config MTD_TS5500
105 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
Sean Youngef63d002005-11-09 00:12:50 +0000106 depends on X86
Sean Young01ac7422005-06-29 09:46:19 +0000107 select MTD_PARTITIONS
108 select MTD_JEDECPROBE
109 select MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700110 help
111 This provides a driver for the on-board flash of the Technologic
Sean Younge27a9962005-06-16 09:49:33 +0100112 System's TS-5500 board. The 2MB flash is split into 3 partitions
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 which are accessed as separate MTD devices.
114
Sean Younge27a9962005-06-16 09:49:33 +0100115 mtd0 and mtd2 are the two BIOS drives, which use the resident
116 flash disk (RFD) flash translation layer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700117
118 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
119
120 Note that jumper 3 ("Write Enable Drive A") must be set
Egry Gábor4992a9e2006-05-12 17:35:02 +0100121 otherwise detection won't succeed.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700122
123config MTD_SBC_GXX
124 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
125 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
126 help
127 This provides a driver for the on-board flash of Arcom Control
128 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
129 By default the flash is split into 3 partitions which are accessed
130 as separate MTD devices. This board utilizes Intel StrataFlash.
131 More info at
132 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
133
Linus Torvalds1da177e2005-04-16 15:20:36 -0700134config MTD_LUBBOCK
135 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
136 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
137 help
138 This provides a driver for the on-board flash of the Intel
139 'Lubbock' XScale evaluation board.
140
Nico Pitrecbec19a2005-07-01 23:55:24 +0100141config MTD_MAINSTONE
142 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
143 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
144 select MTD_PARTITIONS
145 help
146 This provides a driver for the on-board flash of the Intel
147 'Mainstone PXA27x evaluation board.
148
Linus Torvalds1da177e2005-04-16 15:20:36 -0700149config MTD_OCTAGON
150 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
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 Octagon-5066 Single Board
155 Computer. More information on the board is available at
156 <http://www.octagonsystems.com/CPUpages/5066.html>.
157
158config MTD_VMAX
159 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
160 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
161 help
162 This provides a 'mapping' driver which supports the way in which
163 the flash chips are connected in the Tempustech VMAX SBC301 Single
164 Board Computer. More information on the board is available at
165 <http://www.tempustech.com/>.
166
167config MTD_SCx200_DOCFLASH
168 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
169 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
170 help
171 Enable support for a flash chip mapped using the DOCCS signal on a
172 National Semiconductor SCx200 processor.
173
174 If you don't know what to do here, say N.
175
176 If compiled as a module, it will be called scx200_docflash.
177
178config MTD_AMD76XROM
179 tristate "BIOS flash chip on AMD76x southbridge"
180 depends on X86 && MTD_JEDECPROBE
181 help
182 Support for treating the BIOS flash chip on AMD76x motherboards
183 as an MTD device - with this you can reprogram your BIOS.
184
185 BE VERY CAREFUL.
186
187config MTD_ICHXROM
188 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
189 depends on X86 && MTD_JEDECPROBE
190 help
191 Support for treating the BIOS flash chip on ICHX motherboards
192 as an MTD device - with this you can reprogram your BIOS.
193
194 BE VERY CAREFUL.
195
Lew Glendenning29175772006-10-20 14:41:04 -0700196config MTD_ESB2ROM
197 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
Randy Dunlapdffbc422006-12-04 15:03:00 -0800198 depends on X86 && MTD_JEDECPROBE && PCI
Lew Glendenning29175772006-10-20 14:41:04 -0700199 help
200 Support for treating the BIOS flash chip on ESB2 motherboards
201 as an MTD device - with this you can reprogram your BIOS.
202
203 BE VERY CAREFUL.
204
Dave Olsen90afffc2006-11-06 16:33:57 -0700205config MTD_CK804XROM
206 tristate "BIOS flash chip on Nvidia CK804"
akpm@osdl.org862c93b2007-01-25 15:15:17 -0800207 depends on X86 && MTD_JEDECPROBE && PCI
Dave Olsen90afffc2006-11-06 16:33:57 -0700208 help
209 Support for treating the BIOS flash chip on nvidia motherboards
210 as an MTD device - with this you can reprogram your BIOS.
211
212 BE VERY CAREFUL.
213
Linus Torvalds1da177e2005-04-16 15:20:36 -0700214config MTD_SCB2_FLASH
215 tristate "BIOS flash chip on Intel SCB2 boards"
216 depends on X86 && MTD_JEDECPROBE
217 help
218 Support for treating the BIOS flash chip on Intel SCB2 boards
219 as an MTD device - with this you can reprogram your BIOS.
220
221 BE VERY CAREFUL.
222
223config MTD_TSUNAMI
224 tristate "Flash chips on Tsunami TIG bus"
225 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
226 help
227 Support for the flash chip on Tsunami TIG bus.
228
229config MTD_LASAT
Martin Michlmayrceb31db2006-03-20 04:40:46 +0000230 tristate "LASAT flash device"
231 depends on LASAT && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700232 help
233 Support for the flash chips on the Lasat 100 and 200 boards.
234
235config MTD_NETtel
236 tristate "CFI flash device on SnapGear/SecureEdge"
237 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
238 help
239 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
240
Pete Popov002fa302005-02-27 21:50:25 +0000241config MTD_ALCHEMY
Roman Zippele55a3e82006-06-08 22:12:49 -0700242 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
Sean Young01ac7422005-06-29 09:46:19 +0000243 depends on SOC_AU1X00
Linus Torvalds1da177e2005-04-16 15:20:36 -0700244 help
Pete Popov002fa302005-02-27 21:50:25 +0000245 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
Linus Torvalds1da177e2005-04-16 15:20:36 -0700246
Joern Engelb523b3b2005-09-18 11:46:45 +0100247config MTD_MTX1
248 tristate "4G Systems MTX-1 Flash device"
249 depends on MIPS && MIPS_MTX1
250 help
251 Flash memory access on 4G Systems MTX-1 Board. If you have one of
252 these boards and would like to use the flash chips on it, say 'Y'.
253
Linus Torvalds1da177e2005-04-16 15:20:36 -0700254config MTD_DILNETPC
255 tristate "CFI Flash device mapped on DIL/Net PC"
256 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
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
262config 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
270config 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
279config MTD_SBC8240
280 tristate "Flash device on SBC8240"
Sean Young01ac7422005-06-29 09:46:19 +0000281 depends on MTD_JEDECPROBE && 8260
Linus Torvalds1da177e2005-04-16 15:20:36 -0700282 help
283 Flash access on the SBC8240 board from Wind River. See
284 <http://www.windriver.com/products/sbc8240/>
285
286config MTD_TQM8XXL
287 tristate "CFI Flash device mapped on TQM8XXL"
Sean Young01ac7422005-06-29 09:46:19 +0000288 depends on MTD_CFI && TQM8xxL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700289 help
290 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
291 chips, currently uses AMD one. This 'mapping' driver supports
292 that arrangement, allowing the CFI probe and command set driver
293 code to communicate with the chips on the TQM8xxL board. More at
294 <http://www.denx.de/embedded-ppc-en.html>.
295
296config MTD_RPXLITE
297 tristate "CFI Flash device mapped on RPX Lite or CLLF"
Sean Young01ac7422005-06-29 09:46:19 +0000298 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700299 help
300 The RPXLite PowerPC board has CFI-compliant chips mapped in
301 a strange sparse mapping. This 'mapping' driver supports that
302 arrangement, allowing the CFI probe and command set driver code
303 to communicate with the chips on the RPXLite board. More at
304 <http://www.embeddedplanet.com/>.
305
306config MTD_MBX860
307 tristate "System flash on MBX860 board"
Sean Young01ac7422005-06-29 09:46:19 +0000308 depends on MTD_CFI && MBX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700309 help
310 This enables access routines for the flash chips on the Motorola
311 MBX860 board. If you have one of these boards and would like
312 to use the flash chips on it, say 'Y'.
313
314config MTD_DBOX2
315 tristate "CFI Flash device mapped on D-Box2"
Sean Young01ac7422005-06-29 09:46:19 +0000316 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700317 help
318 This enables access routines for the flash chips on the Nokia/Sagem
319 D-Box 2 board. If you have one of these boards and would like to use
320 the flash chips on it, say 'Y'.
321
322config MTD_CFI_FLAGADM
323 tristate "CFI Flash device mapping on FlagaDM"
Sean Young01ac7422005-06-29 09:46:19 +0000324 depends on 8xx && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700325 help
326 Mapping for the Flaga digital module. If you don't have one, ignore
327 this setting.
328
329config MTD_BEECH
330 tristate "CFI Flash device mapped on IBM 405LP Beech"
Sean Young01ac7422005-06-29 09:46:19 +0000331 depends on MTD_CFI && BEECH
Linus Torvalds1da177e2005-04-16 15:20:36 -0700332 help
333 This enables access routines for the flash chips on the IBM
334 405LP Beech board. If you have one of these boards and would like
335 to use the flash chips on it, say 'Y'.
336
337config MTD_ARCTIC
338 tristate "CFI Flash device mapped on IBM 405LP Arctic"
Sean Young01ac7422005-06-29 09:46:19 +0000339 depends on MTD_CFI && ARCTIC2
Linus Torvalds1da177e2005-04-16 15:20:36 -0700340 help
341 This enables access routines for the flash chips on the IBM 405LP
342 Arctic board. If you have one of these boards and would like to
343 use the flash chips on it, say 'Y'.
344
345config MTD_WALNUT
346 tristate "Flash device mapped on IBM 405GP Walnut"
Sean Young01ac7422005-06-29 09:46:19 +0000347 depends on MTD_JEDECPROBE && WALNUT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700348 help
349 This enables access routines for the flash chips on the IBM 405GP
350 Walnut board. If you have one of these boards and would like to
351 use the flash chips on it, say 'Y'.
352
353config MTD_EBONY
354 tristate "Flash devices mapped on IBM 440GP Ebony"
Sean Young01ac7422005-06-29 09:46:19 +0000355 depends on MTD_JEDECPROBE && EBONY
Linus Torvalds1da177e2005-04-16 15:20:36 -0700356 help
357 This enables access routines for the flash chips on the IBM 440GP
358 Ebony board. If you have one of these boards and would like to
359 use the flash chips on it, say 'Y'.
360
361config MTD_OCOTEA
362 tristate "Flash devices mapped on IBM 440GX Ocotea"
Sean Young01ac7422005-06-29 09:46:19 +0000363 depends on MTD_CFI && OCOTEA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700364 help
365 This enables access routines for the flash chips on the IBM 440GX
366 Ocotea board. If you have one of these boards and would like to
367 use the flash chips on it, say 'Y'.
368
369config MTD_REDWOOD
370 tristate "CFI Flash devices mapped on IBM Redwood"
Sean Young01ac7422005-06-29 09:46:19 +0000371 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700372 help
373 This enables access routines for the flash chips on the IBM
374 Redwood board. If you have one of these boards and would like to
375 use the flash chips on it, say 'Y'.
376
Marian Balakowiczbe30c102005-11-07 08:33:38 +0000377config MTD_TQM834x
378 tristate "Flash device mapped on TQ Components TQM834x Boards"
379 depends on MTD_CFI && TQM834x
380 help
381 This enables access routines for the flash chips on the
382 TQ Components TQM834x boards. If you have one of these boards
383 and would like to use the flash chips on it, say 'Y'.
384
Linus Torvalds1da177e2005-04-16 15:20:36 -0700385config MTD_OCELOT
386 tristate "Momenco Ocelot boot flash device"
387 depends on MIPS && MOMENCO_OCELOT
388 help
389 This enables access routines for the boot flash device and for the
390 NVRAM on the Momenco Ocelot board. If you have one of these boards
391 and would like access to either of these, say 'Y'.
392
393config MTD_SOLUTIONENGINE
394 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
395 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
396 help
397 This enables access to the flash chips on the Hitachi SolutionEngine and
398 similar boards. Say 'Y' if you are building a kernel for such a board.
399
400config MTD_ARM_INTEGRATOR
401 tristate "CFI Flash device mapped on ARM Integrator/P720T"
402 depends on ARM && MTD_CFI
403
404config MTD_CDB89712
405 tristate "Cirrus CDB89712 evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000406 depends on MTD_CFI && ARCH_CDB89712
Linus Torvalds1da177e2005-04-16 15:20:36 -0700407 help
408 This enables access to the flash or ROM chips on the CDB89712 board.
409 If you have such a board, say 'Y'.
410
411config MTD_SA1100
412 tristate "CFI Flash device mapped on StrongARM SA11x0"
Sean Young01ac7422005-06-29 09:46:19 +0000413 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700414 help
415 This enables access to the flash chips on most platforms based on
416 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
417 If you have such a board, say 'Y'.
418
419config MTD_IPAQ
420 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
Sean Young01ac7422005-06-29 09:46:19 +0000421 depends on IPAQ_HANDHELD && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700422 help
423 This provides a driver for the on-board flash of the iPAQ.
424
425config MTD_DC21285
426 tristate "CFI Flash device mapped on DC21285 Footbridge"
Sean Young01ac7422005-06-29 09:46:19 +0000427 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700428 help
429 This provides a driver for the flash accessed using Intel's
430 21285 bridge used with Intel's StrongARM processors. More info at
431 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
432
Linus Torvalds1da177e2005-04-16 15:20:36 -0700433config MTD_IXP4XX
434 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000435 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700436 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000437 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700438 on Intel's IXP4xx family of network processors such as the
439 IXDP425 and Coyote. If you have an IXP4xx based board and
440 would like to use the flash chips on it, say 'Y'.
441
442config MTD_IXP2000
443 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000444 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700445 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000446 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700447 on Intel's IXP2000 family of network processors such as the
448 IXDP425 and Coyote. If you have an IXP2000 based board and
449 would like to use the flash chips on it, say 'Y'.
450
Linus Torvalds1da177e2005-04-16 15:20:36 -0700451config MTD_FORTUNET
452 tristate "CFI Flash device mapped on the FortuNet board"
Sean Young01ac7422005-06-29 09:46:19 +0000453 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700454 help
455 This enables access to the Flash on the FortuNet board. If you
456 have such a board, say 'Y'.
457
458config MTD_AUTCPU12
459 tristate "NV-RAM mapping AUTCPU12 board"
Sean Young01ac7422005-06-29 09:46:19 +0000460 depends on ARCH_AUTCPU12
Linus Torvalds1da177e2005-04-16 15:20:36 -0700461 help
462 This enables access to the NV-RAM on autronix autcpu12 board.
463 If you have such a board, say 'Y'.
464
465config MTD_EDB7312
466 tristate "CFI Flash device mapped on EDB7312"
Sean Young01ac7422005-06-29 09:46:19 +0000467 depends on ARCH_EDB7312 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700468 help
469 This enables access to the CFI Flash on the Cogent EDB7312 board.
470 If you have such a board, say 'Y' here.
471
472config MTD_IMPA7
473 tristate "JEDEC Flash device mapped on impA7"
474 depends on ARM && MTD_JEDECPROBE
475 help
476 This enables access to the NOR Flash on the impA7 board of
477 implementa GmbH. If you have such a board, say 'Y' here.
478
479config MTD_CEIVA
480 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
Sean Young01ac7422005-06-29 09:46:19 +0000481 depends on MTD_JEDECPROBE && ARCH_CEIVA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700482 help
483 This enables access to the flash chips on the Ceiva/Polaroid
484 PhotoMax Digital Picture Frame.
485 If you have such a device, say 'Y'.
486
487config MTD_NOR_TOTO
488 tristate "NOR Flash device on TOTO board"
Sean Young01ac7422005-06-29 09:46:19 +0000489 depends on ARCH_OMAP && OMAP_TOTO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700490 help
491 This enables access to the NOR flash on the Texas Instruments
492 TOTO board.
493
494config MTD_H720X
495 tristate "Hynix evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000496 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700497 help
498 This enables access to the flash chips on the Hynix evaluation boards.
499 If you have such a board, say 'Y'.
500
501config MTD_MPC1211
502 tristate "CFI Flash device mapped on Interface MPC-1211"
Sean Young01ac7422005-06-29 09:46:19 +0000503 depends on SH_MPC1211 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700504 help
505 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
506 If you have such a board, say 'Y'.
507
Todd Poynor10c96f22005-07-02 02:53:28 +0100508config MTD_OMAP_NOR
509 tristate "TI OMAP board mappings"
510 depends on MTD_CFI && ARCH_OMAP
511 help
512 This enables access to the NOR flash chips on TI OMAP-based
513 boards defining flash platform devices and flash platform data.
514 These boards include the Innovator, H2, H3, OSK, Perseus2, and
515 more. If you have such a board, say 'Y'.
516
Linus Torvalds1da177e2005-04-16 15:20:36 -0700517# This needs CFI or JEDEC, depending on the cards found.
518config MTD_PCI
519 tristate "PCI MTD driver"
520 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
521 help
522 Mapping for accessing flash devices on add-in cards like the Intel XScale
523 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
524 (please see the manual for the link settings).
525
526 If you are not sure, say N.
527
528config MTD_PCMCIA
529 tristate "PCMCIA MTD driver"
530 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
531 help
532 Map driver for accessing PCMCIA linear flash memory cards. These
533 cards are usually around 4-16MiB in size. This does not include
534 Compact Flash cards which are treated as IDE devices.
535
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700536config MTD_PCMCIA_ANONYMOUS
537 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
538 depends on MTD_PCMCIA
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700539 help
540 If this option is enabled, PCMCIA cards which do not report
541 anything about themselves are assumed to be MTD cards.
542
543 If unsure, say N.
544
Linus Torvalds1da177e2005-04-16 15:20:36 -0700545config MTD_UCLINUX
546 tristate "Generic uClinux RAM/ROM filesystem support"
547 depends on MTD_PARTITIONS && !MMU
548 help
549 Map driver to support image based filesystems for uClinux.
550
551config MTD_WRSBC8260
552 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
553 depends on (SBC82xx || SBC8560)
554 select MTD_PARTITIONS
555 select MTD_MAP_BANK_WIDTH_4
556 select MTD_MAP_BANK_WIDTH_1
557 select MTD_CFI_I1
558 select MTD_CFI_I4
559 help
560 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
561 all three flash regions on CS0, CS1 and CS6 if they are configured
562 correctly by the boot loader.
563
564config MTD_DMV182
565 tristate "Map driver for Dy-4 SVME/DMV-182 board."
566 depends on DMV182
567 select MTD_PARTITIONS
568 select MTD_MAP_BANK_WIDTH_32
569 select MTD_CFI_I8
570 select MTD_CFI_AMDSTD
571 help
572 Map driver for Dy-4 SVME/DMV-182 board.
573
574config MTD_BAST
Ben Dooks76853592005-02-18 11:03:48 +0000575 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
576 depends on ARCH_BAST || MACH_VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700577 select MTD_PARTITIONS
578 select MTD_MAP_BANK_WIDTH_16
579 select MTD_JEDECPROBE
580 help
Ben Dooks76853592005-02-18 11:03:48 +0000581 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
582 Thorcom VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700583
584 Note, this driver *cannot* over-ride the WP link on the
585 board, or currently detect the state of the link.
586
587config MTD_BAST_MAXSIZE
588 int "Maximum size for BAST flash area (MiB)"
589 depends on MTD_BAST
590 default "4"
591
592config MTD_SHARP_SL
Matt LaPlante3cb2fcc2006-11-30 05:22:59 +0100593 bool "ROM mapped on Sharp SL Series"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700594 depends on MTD && ARCH_PXA
595 help
596 This enables access to the flash chip on the Sharp SL Series of PDAs.
597
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000598config MTD_PLATRAM
Thomas Gleixner3c45e00a2005-03-18 02:07:24 +0000599 tristate "Map driver for platform device RAM (mtd-ram)"
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000600 depends on MTD
601 select MTD_RAM
602 help
603 Map driver for RAM areas described via the platform device
604 system.
605
606 This selection automatically selects the map_ram driver.
607
Linus Torvalds1da177e2005-04-16 15:20:36 -0700608endmenu
609