blob: cc6c734424350e17de559c8551a470e70f7e5639 [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"
Linus Torvalds1da177e2005-04-16 15:20:36 -07009 help
10 This causes the chip drivers to allow for complicated
11 paged mappings of flash chips.
12
13config MTD_PHYSMAP
14 tristate "CFI Flash device in physical memory map"
Takashi YOSHII79b9cd52006-08-15 07:26:32 -050015 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
Linus Torvalds1da177e2005-04-16 15:20:36 -070016 help
Takashi YOSHII79b9cd52006-08-15 07:26:32 -050017 This provides a 'mapping' driver which allows the NOR Flash and
18 ROM driver code to communicate with chips which are mapped
19 physically into the CPU's memory. You will need to configure
20 the physical address and size of the flash chips on your
21 particular board as well as the bus width, either statically
Linus Torvalds1da177e2005-04-16 15:20:36 -070022 with config options or at run-time.
23
24config MTD_PHYSMAP_START
25 hex "Physical start address of flash mapping"
26 depends on MTD_PHYSMAP
27 default "0x8000000"
28 help
29 This is the physical memory location at which the flash chips
30 are mapped on your particular target board. Refer to the
31 memory map which should hopefully be in the documentation for
32 your board.
33 Ignore this option if you use run-time physmap configuration
34 (i.e., run-time calling physmap_configure()).
35
36config MTD_PHYSMAP_LEN
37 hex "Physical length of flash mapping"
38 depends on MTD_PHYSMAP
Lennert Buytenhek73566ed2006-05-07 17:16:36 +010039 default "0"
Linus Torvalds1da177e2005-04-16 15:20:36 -070040 help
41 This is the total length of the mapping of the flash chips on
42 your particular board. If there is space, or aliases, in the
43 physical memory map between the chips, this could be larger
44 than the total amount of flash present. Refer to the memory
45 map which should hopefully be in the documentation for your
46 board.
47 Ignore this option if you use run-time physmap configuration
48 (i.e., run-time calling physmap_configure()).
49
50config MTD_PHYSMAP_BANKWIDTH
51 int "Bank width in octets"
52 depends on MTD_PHYSMAP
53 default "2"
54 help
55 This is the total width of the data bus of the flash devices
56 in octets. For example, if you have a data bus width of 32
57 bits, you would set the bus width octect value to 4. This is
58 used internally by the CFI drivers.
59 Ignore this option if you use run-time physmap configuration
60 (i.e., run-time calling physmap_configure()).
61
Vitaly Woola2c2fe42006-12-06 13:17:49 +030062config MTD_PHYSMAP_OF
Matt LaPlantea982ac02007-05-09 07:35:06 +020063 tristate "Flash device in physical memory map based on OF description"
Vitaly Woola2c2fe42006-12-06 13:17:49 +030064 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
65 help
66 This provides a 'mapping' driver which allows the NOR Flash and
67 ROM driver code to communicate with chips which are mapped
68 physically into the CPU's memory. The mapping description here is
69 taken from OF device tree.
70
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080071config MTD_PMC_MSP_EVM
72 tristate "CFI Flash device mapped on PMC-Sierra MSP"
73 depends on PMC_MSP && MTD_CFI
74 select MTD_PARTITIONS
75 help
76 This provides a 'mapping' driver which support the way
77 in which user-programmable flash chips are connected on the
78 PMC-Sierra MSP eval/demo boards
79
80choice
81 prompt "Maximum mappable memory avialable for flash IO"
82 depends on MTD_PMC_MSP_EVM
83 default MSP_FLASH_MAP_LIMIT_32M
84
85config MSP_FLASH_MAP_LIMIT_32M
86 bool "32M"
87
88endchoice
89
90config MSP_FLASH_MAP_LIMIT
91 hex
92 default "0x02000000"
93 depends on MSP_FLASH_MAP_LIMIT_32M
94
95config MTD_PMC_MSP_RAMROOT
96 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
97 depends on PMC_MSP_EMBEDDED_ROOTFS && \
98 (MTD_BLOCK || MTD_BLOCK_RO) && \
99 MTD_RAM
100 help
101 This provides support for the embedded root file system
102 on PMC MSP devices. This memory is mapped as a MTD block device.
103
Linus Torvalds1da177e2005-04-16 15:20:36 -0700104config MTD_SUN_UFLASH
105 tristate "Sun Microsystems userflash support"
Al Viroe0e5de02007-07-26 17:33:09 +0100106 depends on SPARC && MTD_CFI && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700107 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000108 This provides a 'mapping' driver which supports the way in
109 which user-programmable flash chips are connected on various
110 Sun Microsystems boardsets. This driver will require CFI support
Linus Torvalds1da177e2005-04-16 15:20:36 -0700111 in the kernel, so if you did not enable CFI previously, do that now.
112
113config MTD_PNC2000
114 tristate "CFI Flash device mapped on Photron PNC-2000"
115 depends on X86 && MTD_CFI && MTD_PARTITIONS
116 help
117 PNC-2000 is the name of Network Camera product from PHOTRON
118 Ltd. in Japan. It uses CFI-compliant flash.
119
120config MTD_SC520CDP
121 tristate "CFI Flash device mapped on AMD SC520 CDP"
Daniel Drakefbbc21c2006-04-29 11:41:44 +0100122 depends on X86 && MTD_CFI && MTD_CONCAT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700123 help
124 The SC520 CDP board has two banks of CFI-compliant chips and one
125 Dual-in-line JEDEC chip. This 'mapping' driver supports that
126 arrangement, implementing three MTD devices.
127
128config MTD_NETSC520
129 tristate "CFI Flash device mapped on AMD NetSc520"
130 depends on X86 && MTD_CFI && MTD_PARTITIONS
131 help
132 This enables access routines for the flash chips on the AMD NetSc520
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000133 demonstration board. If you have one of these boards and would like
Linus Torvalds1da177e2005-04-16 15:20:36 -0700134 to use the flash chips on it, say 'Y'.
135
136config MTD_TS5500
137 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
Sean Youngef63d002005-11-09 00:12:50 +0000138 depends on X86
Sean Young01ac7422005-06-29 09:46:19 +0000139 select MTD_PARTITIONS
140 select MTD_JEDECPROBE
141 select MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700142 help
143 This provides a driver for the on-board flash of the Technologic
Sean Younge27a9962005-06-16 09:49:33 +0100144 System's TS-5500 board. The 2MB flash is split into 3 partitions
Linus Torvalds1da177e2005-04-16 15:20:36 -0700145 which are accessed as separate MTD devices.
146
Sean Younge27a9962005-06-16 09:49:33 +0100147 mtd0 and mtd2 are the two BIOS drives, which use the resident
148 flash disk (RFD) flash translation layer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700149
150 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
151
152 Note that jumper 3 ("Write Enable Drive A") must be set
Egry Gábor4992a9e2006-05-12 17:35:02 +0100153 otherwise detection won't succeed.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700154
155config MTD_SBC_GXX
156 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
157 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
158 help
159 This provides a driver for the on-board flash of Arcom Control
160 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
161 By default the flash is split into 3 partitions which are accessed
162 as separate MTD devices. This board utilizes Intel StrataFlash.
163 More info at
164 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
165
Linus Torvalds1da177e2005-04-16 15:20:36 -0700166config MTD_LUBBOCK
167 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
168 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
169 help
170 This provides a driver for the on-board flash of the Intel
171 'Lubbock' XScale evaluation board.
172
Nico Pitrecbec19a2005-07-01 23:55:24 +0100173config MTD_MAINSTONE
174 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
175 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
176 select MTD_PARTITIONS
177 help
178 This provides a driver for the on-board flash of the Intel
179 'Mainstone PXA27x evaluation board.
180
Linus Torvalds1da177e2005-04-16 15:20:36 -0700181config MTD_OCTAGON
182 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
183 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
184 help
185 This provides a 'mapping' driver which supports the way in which
186 the flash chips are connected in the Octagon-5066 Single Board
187 Computer. More information on the board is available at
188 <http://www.octagonsystems.com/CPUpages/5066.html>.
189
190config MTD_VMAX
191 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
192 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
193 help
194 This provides a 'mapping' driver which supports the way in which
195 the flash chips are connected in the Tempustech VMAX SBC301 Single
196 Board Computer. More information on the board is available at
197 <http://www.tempustech.com/>.
198
199config MTD_SCx200_DOCFLASH
200 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
201 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
202 help
203 Enable support for a flash chip mapped using the DOCCS signal on a
204 National Semiconductor SCx200 processor.
205
206 If you don't know what to do here, say N.
207
208 If compiled as a module, it will be called scx200_docflash.
209
210config MTD_AMD76XROM
211 tristate "BIOS flash chip on AMD76x southbridge"
212 depends on X86 && MTD_JEDECPROBE
213 help
214 Support for treating the BIOS flash chip on AMD76x motherboards
215 as an MTD device - with this you can reprogram your BIOS.
216
217 BE VERY CAREFUL.
218
219config MTD_ICHXROM
220 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
221 depends on X86 && MTD_JEDECPROBE
222 help
223 Support for treating the BIOS flash chip on ICHX motherboards
224 as an MTD device - with this you can reprogram your BIOS.
225
226 BE VERY CAREFUL.
227
Lew Glendenning29175772006-10-20 14:41:04 -0700228config MTD_ESB2ROM
229 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
Randy Dunlapdffbc422006-12-04 15:03:00 -0800230 depends on X86 && MTD_JEDECPROBE && PCI
Lew Glendenning29175772006-10-20 14:41:04 -0700231 help
232 Support for treating the BIOS flash chip on ESB2 motherboards
233 as an MTD device - with this you can reprogram your BIOS.
234
235 BE VERY CAREFUL.
236
Dave Olsen90afffc2006-11-06 16:33:57 -0700237config MTD_CK804XROM
238 tristate "BIOS flash chip on Nvidia CK804"
akpm@osdl.org862c93b2007-01-25 15:15:17 -0800239 depends on X86 && MTD_JEDECPROBE && PCI
Dave Olsen90afffc2006-11-06 16:33:57 -0700240 help
241 Support for treating the BIOS flash chip on nvidia motherboards
242 as an MTD device - with this you can reprogram your BIOS.
243
244 BE VERY CAREFUL.
245
Linus Torvalds1da177e2005-04-16 15:20:36 -0700246config MTD_SCB2_FLASH
247 tristate "BIOS flash chip on Intel SCB2 boards"
248 depends on X86 && MTD_JEDECPROBE
249 help
250 Support for treating the BIOS flash chip on Intel SCB2 boards
251 as an MTD device - with this you can reprogram your BIOS.
252
253 BE VERY CAREFUL.
254
255config MTD_TSUNAMI
256 tristate "Flash chips on Tsunami TIG bus"
257 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
258 help
259 Support for the flash chip on Tsunami TIG bus.
260
Linus Torvalds1da177e2005-04-16 15:20:36 -0700261config MTD_NETtel
262 tristate "CFI flash device on SnapGear/SecureEdge"
263 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
264 help
265 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
266
Pete Popov002fa302005-02-27 21:50:25 +0000267config MTD_ALCHEMY
Roman Zippele55a3e82006-06-08 22:12:49 -0700268 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
Ralf Baechle873b6a22007-03-10 23:10:50 +0000269 depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700270 help
Pete Popov002fa302005-02-27 21:50:25 +0000271 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
Linus Torvalds1da177e2005-04-16 15:20:36 -0700272
Joern Engelb523b3b2005-09-18 11:46:45 +0100273config MTD_MTX1
274 tristate "4G Systems MTX-1 Flash device"
Ralf Baechle873b6a22007-03-10 23:10:50 +0000275 depends on MIPS_MTX1 && MTD_CFI
Joern Engelb523b3b2005-09-18 11:46:45 +0100276 help
277 Flash memory access on 4G Systems MTX-1 Board. If you have one of
278 these boards and would like to use the flash chips on it, say 'Y'.
279
Linus Torvalds1da177e2005-04-16 15:20:36 -0700280config MTD_DILNETPC
281 tristate "CFI Flash device mapped on DIL/Net PC"
282 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
283 help
284 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
285 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
286 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
287
288config MTD_DILNETPC_BOOTSIZE
289 hex "Size of DIL/Net PC flash boot partition"
290 depends on MTD_DILNETPC
291 default "0x80000"
292 help
293 The amount of space taken up by the kernel or Etherboot
294 on the DIL/Net PC flash chips.
295
296config MTD_L440GX
297 tristate "BIOS flash chip on Intel L440GX boards"
298 depends on X86 && MTD_JEDECPROBE
299 help
300 Support for treating the BIOS flash chip on Intel L440GX motherboards
301 as an MTD device - with this you can reprogram your BIOS.
302
303 BE VERY CAREFUL.
304
305config MTD_SBC8240
306 tristate "Flash device on SBC8240"
Sean Young01ac7422005-06-29 09:46:19 +0000307 depends on MTD_JEDECPROBE && 8260
Linus Torvalds1da177e2005-04-16 15:20:36 -0700308 help
309 Flash access on the SBC8240 board from Wind River. See
310 <http://www.windriver.com/products/sbc8240/>
311
312config MTD_TQM8XXL
313 tristate "CFI Flash device mapped on TQM8XXL"
Sean Young01ac7422005-06-29 09:46:19 +0000314 depends on MTD_CFI && TQM8xxL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700315 help
316 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
317 chips, currently uses AMD one. This 'mapping' driver supports
318 that arrangement, allowing the CFI probe and command set driver
319 code to communicate with the chips on the TQM8xxL board. More at
320 <http://www.denx.de/embedded-ppc-en.html>.
321
322config MTD_RPXLITE
323 tristate "CFI Flash device mapped on RPX Lite or CLLF"
Sean Young01ac7422005-06-29 09:46:19 +0000324 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700325 help
326 The RPXLite PowerPC board has CFI-compliant chips mapped in
327 a strange sparse mapping. This 'mapping' driver supports that
328 arrangement, allowing the CFI probe and command set driver code
329 to communicate with the chips on the RPXLite board. More at
330 <http://www.embeddedplanet.com/>.
331
332config MTD_MBX860
333 tristate "System flash on MBX860 board"
Sean Young01ac7422005-06-29 09:46:19 +0000334 depends on MTD_CFI && MBX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700335 help
336 This enables access routines for the flash chips on the Motorola
337 MBX860 board. If you have one of these boards and would like
338 to use the flash chips on it, say 'Y'.
339
340config MTD_DBOX2
341 tristate "CFI Flash device mapped on D-Box2"
Sean Young01ac7422005-06-29 09:46:19 +0000342 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700343 help
344 This enables access routines for the flash chips on the Nokia/Sagem
345 D-Box 2 board. If you have one of these boards and would like to use
346 the flash chips on it, say 'Y'.
347
348config MTD_CFI_FLAGADM
349 tristate "CFI Flash device mapping on FlagaDM"
Sean Young01ac7422005-06-29 09:46:19 +0000350 depends on 8xx && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700351 help
352 Mapping for the Flaga digital module. If you don't have one, ignore
353 this setting.
354
Linus Torvalds1da177e2005-04-16 15:20:36 -0700355config MTD_WALNUT
356 tristate "Flash device mapped on IBM 405GP Walnut"
Sean Young01ac7422005-06-29 09:46:19 +0000357 depends on MTD_JEDECPROBE && WALNUT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700358 help
359 This enables access routines for the flash chips on the IBM 405GP
360 Walnut board. If you have one of these boards and would like to
361 use the flash chips on it, say 'Y'.
362
363config MTD_EBONY
364 tristate "Flash devices mapped on IBM 440GP Ebony"
Sean Young01ac7422005-06-29 09:46:19 +0000365 depends on MTD_JEDECPROBE && EBONY
Linus Torvalds1da177e2005-04-16 15:20:36 -0700366 help
367 This enables access routines for the flash chips on the IBM 440GP
368 Ebony board. If you have one of these boards and would like to
369 use the flash chips on it, say 'Y'.
370
371config MTD_OCOTEA
372 tristate "Flash devices mapped on IBM 440GX Ocotea"
Sean Young01ac7422005-06-29 09:46:19 +0000373 depends on MTD_CFI && OCOTEA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700374 help
375 This enables access routines for the flash chips on the IBM 440GX
376 Ocotea board. If you have one of these boards and would like to
377 use the flash chips on it, say 'Y'.
378
379config MTD_REDWOOD
380 tristate "CFI Flash devices mapped on IBM Redwood"
Sean Young01ac7422005-06-29 09:46:19 +0000381 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700382 help
383 This enables access routines for the flash chips on the IBM
384 Redwood board. If you have one of these boards and would like to
385 use the flash chips on it, say 'Y'.
386
Marian Balakowiczbe30c102005-11-07 08:33:38 +0000387config MTD_TQM834x
388 tristate "Flash device mapped on TQ Components TQM834x Boards"
389 depends on MTD_CFI && TQM834x
390 help
391 This enables access routines for the flash chips on the
392 TQ Components TQM834x boards. If you have one of these boards
393 and would like to use the flash chips on it, say 'Y'.
394
Linus Torvalds1da177e2005-04-16 15:20:36 -0700395config MTD_OCELOT
396 tristate "Momenco Ocelot boot flash device"
Ralf Baechle873b6a22007-03-10 23:10:50 +0000397 depends on MOMENCO_OCELOT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700398 help
399 This enables access routines for the boot flash device and for the
400 NVRAM on the Momenco Ocelot board. If you have one of these boards
401 and would like access to either of these, say 'Y'.
402
403config MTD_SOLUTIONENGINE
404 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
405 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
406 help
407 This enables access to the flash chips on the Hitachi SolutionEngine and
408 similar boards. Say 'Y' if you are building a kernel for such a board.
409
410config MTD_ARM_INTEGRATOR
411 tristate "CFI Flash device mapped on ARM Integrator/P720T"
412 depends on ARM && MTD_CFI
413
414config MTD_CDB89712
415 tristate "Cirrus CDB89712 evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000416 depends on MTD_CFI && ARCH_CDB89712
Linus Torvalds1da177e2005-04-16 15:20:36 -0700417 help
418 This enables access to the flash or ROM chips on the CDB89712 board.
419 If you have such a board, say 'Y'.
420
421config MTD_SA1100
422 tristate "CFI Flash device mapped on StrongARM SA11x0"
Sean Young01ac7422005-06-29 09:46:19 +0000423 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700424 help
425 This enables access to the flash chips on most platforms based on
426 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
427 If you have such a board, say 'Y'.
428
429config MTD_IPAQ
430 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
Sean Young01ac7422005-06-29 09:46:19 +0000431 depends on IPAQ_HANDHELD && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700432 help
433 This provides a driver for the on-board flash of the iPAQ.
434
435config MTD_DC21285
436 tristate "CFI Flash device mapped on DC21285 Footbridge"
Sean Young01ac7422005-06-29 09:46:19 +0000437 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700438 help
439 This provides a driver for the flash accessed using Intel's
440 21285 bridge used with Intel's StrongARM processors. More info at
441 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
442
Linus Torvalds1da177e2005-04-16 15:20:36 -0700443config MTD_IXP4XX
444 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000445 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700446 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000447 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700448 on Intel's IXP4xx family of network processors such as the
449 IXDP425 and Coyote. If you have an IXP4xx based board and
450 would like to use the flash chips on it, say 'Y'.
451
452config MTD_IXP2000
453 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000454 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700455 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000456 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700457 on Intel's IXP2000 family of network processors such as the
458 IXDP425 and Coyote. If you have an IXP2000 based board and
459 would like to use the flash chips on it, say 'Y'.
460
Linus Torvalds1da177e2005-04-16 15:20:36 -0700461config MTD_FORTUNET
462 tristate "CFI Flash device mapped on the FortuNet board"
Sean Young01ac7422005-06-29 09:46:19 +0000463 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700464 help
465 This enables access to the Flash on the FortuNet board. If you
466 have such a board, say 'Y'.
467
468config MTD_AUTCPU12
469 tristate "NV-RAM mapping AUTCPU12 board"
Sean Young01ac7422005-06-29 09:46:19 +0000470 depends on ARCH_AUTCPU12
Linus Torvalds1da177e2005-04-16 15:20:36 -0700471 help
472 This enables access to the NV-RAM on autronix autcpu12 board.
473 If you have such a board, say 'Y'.
474
475config MTD_EDB7312
476 tristate "CFI Flash device mapped on EDB7312"
Sean Young01ac7422005-06-29 09:46:19 +0000477 depends on ARCH_EDB7312 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700478 help
479 This enables access to the CFI Flash on the Cogent EDB7312 board.
480 If you have such a board, say 'Y' here.
481
482config MTD_IMPA7
483 tristate "JEDEC Flash device mapped on impA7"
484 depends on ARM && MTD_JEDECPROBE
485 help
486 This enables access to the NOR Flash on the impA7 board of
487 implementa GmbH. If you have such a board, say 'Y' here.
488
489config MTD_CEIVA
490 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
Sean Young01ac7422005-06-29 09:46:19 +0000491 depends on MTD_JEDECPROBE && ARCH_CEIVA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700492 help
493 This enables access to the flash chips on the Ceiva/Polaroid
494 PhotoMax Digital Picture Frame.
495 If you have such a device, say 'Y'.
496
497config MTD_NOR_TOTO
498 tristate "NOR Flash device on TOTO board"
Sean Young01ac7422005-06-29 09:46:19 +0000499 depends on ARCH_OMAP && OMAP_TOTO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700500 help
501 This enables access to the NOR flash on the Texas Instruments
502 TOTO board.
503
504config MTD_H720X
505 tristate "Hynix evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000506 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700507 help
508 This enables access to the flash chips on the Hynix evaluation boards.
509 If you have such a board, say 'Y'.
510
511config MTD_MPC1211
512 tristate "CFI Flash device mapped on Interface MPC-1211"
Sean Young01ac7422005-06-29 09:46:19 +0000513 depends on SH_MPC1211 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700514 help
515 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
516 If you have such a board, say 'Y'.
517
Todd Poynor10c96f22005-07-02 02:53:28 +0100518config MTD_OMAP_NOR
519 tristate "TI OMAP board mappings"
520 depends on MTD_CFI && ARCH_OMAP
521 help
522 This enables access to the NOR flash chips on TI OMAP-based
523 boards defining flash platform devices and flash platform data.
524 These boards include the Innovator, H2, H3, OSK, Perseus2, and
525 more. If you have such a board, say 'Y'.
526
Linus Torvalds1da177e2005-04-16 15:20:36 -0700527# This needs CFI or JEDEC, depending on the cards found.
528config MTD_PCI
529 tristate "PCI MTD driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500530 depends on PCI && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700531 help
532 Mapping for accessing flash devices on add-in cards like the Intel XScale
533 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
534 (please see the manual for the link settings).
535
536 If you are not sure, say N.
537
538config MTD_PCMCIA
539 tristate "PCMCIA MTD driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500540 depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
Linus Torvalds1da177e2005-04-16 15:20:36 -0700541 help
542 Map driver for accessing PCMCIA linear flash memory cards. These
543 cards are usually around 4-16MiB in size. This does not include
544 Compact Flash cards which are treated as IDE devices.
545
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700546config MTD_PCMCIA_ANONYMOUS
547 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
548 depends on MTD_PCMCIA
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700549 help
550 If this option is enabled, PCMCIA cards which do not report
551 anything about themselves are assumed to be MTD cards.
552
553 If unsure, say N.
554
Linus Torvalds1da177e2005-04-16 15:20:36 -0700555config MTD_UCLINUX
556 tristate "Generic uClinux RAM/ROM filesystem support"
557 depends on MTD_PARTITIONS && !MMU
558 help
559 Map driver to support image based filesystems for uClinux.
560
561config MTD_WRSBC8260
562 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
563 depends on (SBC82xx || SBC8560)
564 select MTD_PARTITIONS
565 select MTD_MAP_BANK_WIDTH_4
566 select MTD_MAP_BANK_WIDTH_1
567 select MTD_CFI_I1
568 select MTD_CFI_I4
569 help
570 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
571 all three flash regions on CS0, CS1 and CS6 if they are configured
572 correctly by the boot loader.
573
574config MTD_DMV182
575 tristate "Map driver for Dy-4 SVME/DMV-182 board."
576 depends on DMV182
577 select MTD_PARTITIONS
578 select MTD_MAP_BANK_WIDTH_32
579 select MTD_CFI_I8
580 select MTD_CFI_AMDSTD
581 help
582 Map driver for Dy-4 SVME/DMV-182 board.
583
584config MTD_BAST
Ben Dooks76853592005-02-18 11:03:48 +0000585 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
586 depends on ARCH_BAST || MACH_VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700587 select MTD_PARTITIONS
588 select MTD_MAP_BANK_WIDTH_16
589 select MTD_JEDECPROBE
590 help
Ben Dooks76853592005-02-18 11:03:48 +0000591 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
592 Thorcom VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700593
594 Note, this driver *cannot* over-ride the WP link on the
595 board, or currently detect the state of the link.
596
597config MTD_BAST_MAXSIZE
598 int "Maximum size for BAST flash area (MiB)"
599 depends on MTD_BAST
600 default "4"
601
602config MTD_SHARP_SL
Matt LaPlante3cb2fcc2006-11-30 05:22:59 +0100603 bool "ROM mapped on Sharp SL Series"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500604 depends on ARCH_PXA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700605 help
606 This enables access to the flash chip on the Sharp SL Series of PDAs.
607
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000608config MTD_PLATRAM
Thomas Gleixner3c45e00a2005-03-18 02:07:24 +0000609 tristate "Map driver for platform device RAM (mtd-ram)"
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000610 select MTD_RAM
611 help
612 Map driver for RAM areas described via the platform device
613 system.
614
615 This selection automatically selects the map_ram driver.
616
Linus Torvalds1da177e2005-04-16 15:20:36 -0700617endmenu
618