blob: 17bc87a43ff415d151125673b1cda275c4d7b28d [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
Mike Frysinger41bdf962008-04-18 13:44:10 -070024 To compile this driver as a module, choose M here: the
25 module will be called physmap.
26
Linus Torvalds1da177e2005-04-16 15:20:36 -070027config MTD_PHYSMAP_START
28 hex "Physical start address of flash mapping"
29 depends on MTD_PHYSMAP
30 default "0x8000000"
31 help
32 This is the physical memory location at which the flash chips
33 are mapped on your particular target board. Refer to the
34 memory map which should hopefully be in the documentation for
35 your board.
36 Ignore this option if you use run-time physmap configuration
37 (i.e., run-time calling physmap_configure()).
38
39config MTD_PHYSMAP_LEN
40 hex "Physical length of flash mapping"
41 depends on MTD_PHYSMAP
Lennert Buytenhek73566ed2006-05-07 17:16:36 +010042 default "0"
Linus Torvalds1da177e2005-04-16 15:20:36 -070043 help
44 This is the total length of the mapping of the flash chips on
45 your particular board. If there is space, or aliases, in the
46 physical memory map between the chips, this could be larger
47 than the total amount of flash present. Refer to the memory
48 map which should hopefully be in the documentation for your
49 board.
50 Ignore this option if you use run-time physmap configuration
51 (i.e., run-time calling physmap_configure()).
52
53config MTD_PHYSMAP_BANKWIDTH
54 int "Bank width in octets"
55 depends on MTD_PHYSMAP
56 default "2"
57 help
58 This is the total width of the data bus of the flash devices
59 in octets. For example, if you have a data bus width of 32
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020060 bits, you would set the bus width octet value to 4. This is
Linus Torvalds1da177e2005-04-16 15:20:36 -070061 used internally by the CFI drivers.
62 Ignore this option if you use run-time physmap configuration
63 (i.e., run-time calling physmap_configure()).
64
Vitaly Woola2c2fe42006-12-06 13:17:49 +030065config MTD_PHYSMAP_OF
Matt LaPlantea982ac02007-05-09 07:35:06 +020066 tristate "Flash device in physical memory map based on OF description"
Vitaly Woola2c2fe42006-12-06 13:17:49 +030067 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
68 help
69 This provides a 'mapping' driver which allows the NOR Flash and
70 ROM driver code to communicate with chips which are mapped
71 physically into the CPU's memory. The mapping description here is
72 taken from OF device tree.
73
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080074config MTD_PMC_MSP_EVM
75 tristate "CFI Flash device mapped on PMC-Sierra MSP"
76 depends on PMC_MSP && MTD_CFI
77 select MTD_PARTITIONS
78 help
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020079 This provides a 'mapping' driver which supports the way
80 in which user-programmable flash chips are connected on the
81 PMC-Sierra MSP eval/demo boards.
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080082
83choice
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020084 prompt "Maximum mappable memory available for flash IO"
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080085 depends on MTD_PMC_MSP_EVM
86 default MSP_FLASH_MAP_LIMIT_32M
87
88config MSP_FLASH_MAP_LIMIT_32M
89 bool "32M"
90
91endchoice
92
93config MSP_FLASH_MAP_LIMIT
94 hex
95 default "0x02000000"
96 depends on MSP_FLASH_MAP_LIMIT_32M
97
98config MTD_PMC_MSP_RAMROOT
99 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
100 depends on PMC_MSP_EMBEDDED_ROOTFS && \
101 (MTD_BLOCK || MTD_BLOCK_RO) && \
102 MTD_RAM
103 help
104 This provides support for the embedded root file system
105 on PMC MSP devices. This memory is mapped as a MTD block device.
106
Linus Torvalds1da177e2005-04-16 15:20:36 -0700107config MTD_SUN_UFLASH
108 tristate "Sun Microsystems userflash support"
Al Viroe0e5de02007-07-26 17:33:09 +0100109 depends on SPARC && MTD_CFI && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700110 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000111 This provides a 'mapping' driver which supports the way in
112 which user-programmable flash chips are connected on various
113 Sun Microsystems boardsets. This driver will require CFI support
Linus Torvalds1da177e2005-04-16 15:20:36 -0700114 in the kernel, so if you did not enable CFI previously, do that now.
115
Linus Torvalds1da177e2005-04-16 15:20:36 -0700116config MTD_SC520CDP
117 tristate "CFI Flash device mapped on AMD SC520 CDP"
Daniel Drakefbbc21c2006-04-29 11:41:44 +0100118 depends on X86 && MTD_CFI && MTD_CONCAT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700119 help
120 The SC520 CDP board has two banks of CFI-compliant chips and one
121 Dual-in-line JEDEC chip. This 'mapping' driver supports that
122 arrangement, implementing three MTD devices.
123
124config MTD_NETSC520
125 tristate "CFI Flash device mapped on AMD NetSc520"
126 depends on X86 && MTD_CFI && MTD_PARTITIONS
127 help
128 This enables access routines for the flash chips on the AMD NetSc520
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000129 demonstration board. If you have one of these boards and would like
Linus Torvalds1da177e2005-04-16 15:20:36 -0700130 to use the flash chips on it, say 'Y'.
131
132config MTD_TS5500
133 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
Sean Youngef63d002005-11-09 00:12:50 +0000134 depends on X86
Sean Young01ac7422005-06-29 09:46:19 +0000135 select MTD_PARTITIONS
136 select MTD_JEDECPROBE
137 select MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700138 help
139 This provides a driver for the on-board flash of the Technologic
Sean Younge27a9962005-06-16 09:49:33 +0100140 System's TS-5500 board. The 2MB flash is split into 3 partitions
Linus Torvalds1da177e2005-04-16 15:20:36 -0700141 which are accessed as separate MTD devices.
142
Sean Younge27a9962005-06-16 09:49:33 +0100143 mtd0 and mtd2 are the two BIOS drives, which use the resident
144 flash disk (RFD) flash translation layer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700145
146 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
147
148 Note that jumper 3 ("Write Enable Drive A") must be set
Egry Gábor4992a9e2006-05-12 17:35:02 +0100149 otherwise detection won't succeed.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700150
151config MTD_SBC_GXX
152 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
153 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
154 help
155 This provides a driver for the on-board flash of Arcom Control
156 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
157 By default the flash is split into 3 partitions which are accessed
158 as separate MTD devices. This board utilizes Intel StrataFlash.
159 More info at
160 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
161
Todd Poynore644f7d2005-11-07 21:47:48 +0000162config MTD_PXA2XX
163 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
164 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
Nico Pitrecbec19a2005-07-01 23:55:24 +0100165 select MTD_PARTITIONS
166 help
Todd Poynore644f7d2005-11-07 21:47:48 +0000167 This provides a driver for the NOR flash attached to a PXA2xx chip.
Nico Pitrecbec19a2005-07-01 23:55:24 +0100168
Linus Torvalds1da177e2005-04-16 15:20:36 -0700169config MTD_OCTAGON
170 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
171 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
172 help
173 This provides a 'mapping' driver which supports the way in which
174 the flash chips are connected in the Octagon-5066 Single Board
175 Computer. More information on the board is available at
176 <http://www.octagonsystems.com/CPUpages/5066.html>.
177
178config MTD_VMAX
179 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
180 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
181 help
182 This provides a 'mapping' driver which supports the way in which
183 the flash chips are connected in the Tempustech VMAX SBC301 Single
184 Board Computer. More information on the board is available at
185 <http://www.tempustech.com/>.
186
187config MTD_SCx200_DOCFLASH
188 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
189 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
190 help
191 Enable support for a flash chip mapped using the DOCCS signal on a
192 National Semiconductor SCx200 processor.
193
194 If you don't know what to do here, say N.
195
196 If compiled as a module, it will be called scx200_docflash.
197
198config MTD_AMD76XROM
199 tristate "BIOS flash chip on AMD76x southbridge"
200 depends on X86 && MTD_JEDECPROBE
201 help
202 Support for treating the BIOS flash chip on AMD76x motherboards
203 as an MTD device - with this you can reprogram your BIOS.
204
205 BE VERY CAREFUL.
206
207config MTD_ICHXROM
208 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
209 depends on X86 && MTD_JEDECPROBE
210 help
211 Support for treating the BIOS flash chip on ICHX motherboards
212 as an MTD device - with this you can reprogram your BIOS.
213
214 BE VERY CAREFUL.
215
Lew Glendenning29175772006-10-20 14:41:04 -0700216config MTD_ESB2ROM
217 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
Randy Dunlapdffbc422006-12-04 15:03:00 -0800218 depends on X86 && MTD_JEDECPROBE && PCI
Lew Glendenning29175772006-10-20 14:41:04 -0700219 help
220 Support for treating the BIOS flash chip on ESB2 motherboards
221 as an MTD device - with this you can reprogram your BIOS.
222
223 BE VERY CAREFUL.
224
Dave Olsen90afffc2006-11-06 16:33:57 -0700225config MTD_CK804XROM
226 tristate "BIOS flash chip on Nvidia CK804"
akpm@osdl.org862c93b2007-01-25 15:15:17 -0800227 depends on X86 && MTD_JEDECPROBE && PCI
Dave Olsen90afffc2006-11-06 16:33:57 -0700228 help
229 Support for treating the BIOS flash chip on nvidia motherboards
230 as an MTD device - with this you can reprogram your BIOS.
231
232 BE VERY CAREFUL.
233
Linus Torvalds1da177e2005-04-16 15:20:36 -0700234config MTD_SCB2_FLASH
235 tristate "BIOS flash chip on Intel SCB2 boards"
236 depends on X86 && MTD_JEDECPROBE
237 help
238 Support for treating the BIOS flash chip on Intel SCB2 boards
239 as an MTD device - with this you can reprogram your BIOS.
240
241 BE VERY CAREFUL.
242
243config MTD_TSUNAMI
244 tristate "Flash chips on Tsunami TIG bus"
245 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
246 help
247 Support for the flash chip on Tsunami TIG bus.
248
Linus Torvalds1da177e2005-04-16 15:20:36 -0700249config MTD_NETtel
250 tristate "CFI flash device on SnapGear/SecureEdge"
251 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
252 help
253 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
254
Pete Popov002fa302005-02-27 21:50:25 +0000255config MTD_ALCHEMY
Roman Zippele55a3e82006-06-08 22:12:49 -0700256 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
Ralf Baechle873b6a22007-03-10 23:10:50 +0000257 depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700258 help
Pete Popov002fa302005-02-27 21:50:25 +0000259 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
Linus Torvalds1da177e2005-04-16 15:20:36 -0700260
Joern Engelb523b3b2005-09-18 11:46:45 +0100261config MTD_MTX1
262 tristate "4G Systems MTX-1 Flash device"
Ralf Baechle873b6a22007-03-10 23:10:50 +0000263 depends on MIPS_MTX1 && MTD_CFI
Joern Engelb523b3b2005-09-18 11:46:45 +0100264 help
265 Flash memory access on 4G Systems MTX-1 Board. If you have one of
266 these boards and would like to use the flash chips on it, say 'Y'.
267
Linus Torvalds1da177e2005-04-16 15:20:36 -0700268config MTD_DILNETPC
269 tristate "CFI Flash device mapped on DIL/Net PC"
270 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
271 help
272 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
273 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
274 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
275
276config MTD_DILNETPC_BOOTSIZE
277 hex "Size of DIL/Net PC flash boot partition"
278 depends on MTD_DILNETPC
279 default "0x80000"
280 help
281 The amount of space taken up by the kernel or Etherboot
282 on the DIL/Net PC flash chips.
283
284config MTD_L440GX
285 tristate "BIOS flash chip on Intel L440GX boards"
286 depends on X86 && MTD_JEDECPROBE
287 help
288 Support for treating the BIOS flash chip on Intel L440GX motherboards
289 as an MTD device - with this you can reprogram your BIOS.
290
291 BE VERY CAREFUL.
292
293config MTD_SBC8240
294 tristate "Flash device on SBC8240"
Sean Young01ac7422005-06-29 09:46:19 +0000295 depends on MTD_JEDECPROBE && 8260
Linus Torvalds1da177e2005-04-16 15:20:36 -0700296 help
297 Flash access on the SBC8240 board from Wind River. See
298 <http://www.windriver.com/products/sbc8240/>
299
300config MTD_TQM8XXL
301 tristate "CFI Flash device mapped on TQM8XXL"
Sean Young01ac7422005-06-29 09:46:19 +0000302 depends on MTD_CFI && TQM8xxL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700303 help
304 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
305 chips, currently uses AMD one. This 'mapping' driver supports
306 that arrangement, allowing the CFI probe and command set driver
307 code to communicate with the chips on the TQM8xxL board. More at
308 <http://www.denx.de/embedded-ppc-en.html>.
309
310config MTD_RPXLITE
311 tristate "CFI Flash device mapped on RPX Lite or CLLF"
Sean Young01ac7422005-06-29 09:46:19 +0000312 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700313 help
314 The RPXLite PowerPC board has CFI-compliant chips mapped in
315 a strange sparse mapping. This 'mapping' driver supports that
316 arrangement, allowing the CFI probe and command set driver code
317 to communicate with the chips on the RPXLite board. More at
318 <http://www.embeddedplanet.com/>.
319
320config MTD_MBX860
321 tristate "System flash on MBX860 board"
Sean Young01ac7422005-06-29 09:46:19 +0000322 depends on MTD_CFI && MBX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700323 help
324 This enables access routines for the flash chips on the Motorola
325 MBX860 board. If you have one of these boards and would like
326 to use the flash chips on it, say 'Y'.
327
328config MTD_DBOX2
329 tristate "CFI Flash device mapped on D-Box2"
Sean Young01ac7422005-06-29 09:46:19 +0000330 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700331 help
332 This enables access routines for the flash chips on the Nokia/Sagem
333 D-Box 2 board. If you have one of these boards and would like to use
334 the flash chips on it, say 'Y'.
335
336config MTD_CFI_FLAGADM
337 tristate "CFI Flash device mapping on FlagaDM"
Sean Young01ac7422005-06-29 09:46:19 +0000338 depends on 8xx && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700339 help
340 Mapping for the Flaga digital module. If you don't have one, ignore
341 this setting.
342
Linus Torvalds1da177e2005-04-16 15:20:36 -0700343config MTD_WALNUT
344 tristate "Flash device mapped on IBM 405GP Walnut"
Josh Boyer3feb0ff2007-08-22 14:30:47 -0500345 depends on MTD_JEDECPROBE && WALNUT && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700346 help
347 This enables access routines for the flash chips on the IBM 405GP
348 Walnut board. If you have one of these boards and would like to
349 use the flash chips on it, say 'Y'.
350
351config MTD_EBONY
352 tristate "Flash devices mapped on IBM 440GP Ebony"
David Gibson0d279d42007-07-30 15:55:02 +1000353 depends on MTD_JEDECPROBE && EBONY && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700354 help
355 This enables access routines for the flash chips on the IBM 440GP
356 Ebony board. If you have one of these boards and would like to
357 use the flash chips on it, say 'Y'.
358
359config MTD_OCOTEA
360 tristate "Flash devices mapped on IBM 440GX Ocotea"
Josh Boyer3feb0ff2007-08-22 14:30:47 -0500361 depends on MTD_CFI && OCOTEA && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700362 help
363 This enables access routines for the flash chips on the IBM 440GX
364 Ocotea board. If you have one of these boards and would like to
365 use the flash chips on it, say 'Y'.
366
367config MTD_REDWOOD
368 tristate "CFI Flash devices mapped on IBM Redwood"
Sean Young01ac7422005-06-29 09:46:19 +0000369 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700370 help
371 This enables access routines for the flash chips on the IBM
372 Redwood board. If you have one of these boards and would like to
373 use the flash chips on it, say 'Y'.
374
Linus Torvalds1da177e2005-04-16 15:20:36 -0700375config MTD_SOLUTIONENGINE
376 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
Paul Mundte35e2832008-04-25 14:27:08 +0900377 depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700378 help
379 This enables access to the flash chips on the Hitachi SolutionEngine and
380 similar boards. Say 'Y' if you are building a kernel for such a board.
381
382config MTD_ARM_INTEGRATOR
383 tristate "CFI Flash device mapped on ARM Integrator/P720T"
384 depends on ARM && MTD_CFI
385
386config MTD_CDB89712
387 tristate "Cirrus CDB89712 evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000388 depends on MTD_CFI && ARCH_CDB89712
Linus Torvalds1da177e2005-04-16 15:20:36 -0700389 help
390 This enables access to the flash or ROM chips on the CDB89712 board.
391 If you have such a board, say 'Y'.
392
393config MTD_SA1100
394 tristate "CFI Flash device mapped on StrongARM SA11x0"
Sean Young01ac7422005-06-29 09:46:19 +0000395 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700396 help
397 This enables access to the flash chips on most platforms based on
398 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
399 If you have such a board, say 'Y'.
400
401config MTD_IPAQ
402 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
Sean Young01ac7422005-06-29 09:46:19 +0000403 depends on IPAQ_HANDHELD && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700404 help
405 This provides a driver for the on-board flash of the iPAQ.
406
407config MTD_DC21285
408 tristate "CFI Flash device mapped on DC21285 Footbridge"
Sean Young01ac7422005-06-29 09:46:19 +0000409 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700410 help
411 This provides a driver for the flash accessed using Intel's
412 21285 bridge used with Intel's StrongARM processors. More info at
413 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
414
Linus Torvalds1da177e2005-04-16 15:20:36 -0700415config MTD_IXP4XX
416 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000417 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700418 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000419 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700420 on Intel's IXP4xx family of network processors such as the
421 IXDP425 and Coyote. If you have an IXP4xx based board and
422 would like to use the flash chips on it, say 'Y'.
423
424config MTD_IXP2000
425 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000426 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700427 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000428 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700429 on Intel's IXP2000 family of network processors such as the
430 IXDP425 and Coyote. If you have an IXP2000 based board and
431 would like to use the flash chips on it, say 'Y'.
432
Linus Torvalds1da177e2005-04-16 15:20:36 -0700433config MTD_FORTUNET
434 tristate "CFI Flash device mapped on the FortuNet board"
Sean Young01ac7422005-06-29 09:46:19 +0000435 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700436 help
437 This enables access to the Flash on the FortuNet board. If you
438 have such a board, say 'Y'.
439
440config MTD_AUTCPU12
441 tristate "NV-RAM mapping AUTCPU12 board"
Sean Young01ac7422005-06-29 09:46:19 +0000442 depends on ARCH_AUTCPU12
Linus Torvalds1da177e2005-04-16 15:20:36 -0700443 help
444 This enables access to the NV-RAM on autronix autcpu12 board.
445 If you have such a board, say 'Y'.
446
447config MTD_EDB7312
448 tristate "CFI Flash device mapped on EDB7312"
Sean Young01ac7422005-06-29 09:46:19 +0000449 depends on ARCH_EDB7312 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700450 help
451 This enables access to the CFI Flash on the Cogent EDB7312 board.
452 If you have such a board, say 'Y' here.
453
454config MTD_IMPA7
455 tristate "JEDEC Flash device mapped on impA7"
456 depends on ARM && MTD_JEDECPROBE
457 help
458 This enables access to the NOR Flash on the impA7 board of
459 implementa GmbH. If you have such a board, say 'Y' here.
460
461config MTD_CEIVA
462 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
Sean Young01ac7422005-06-29 09:46:19 +0000463 depends on MTD_JEDECPROBE && ARCH_CEIVA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700464 help
465 This enables access to the flash chips on the Ceiva/Polaroid
466 PhotoMax Digital Picture Frame.
467 If you have such a device, say 'Y'.
468
469config MTD_NOR_TOTO
470 tristate "NOR Flash device on TOTO board"
Sean Young01ac7422005-06-29 09:46:19 +0000471 depends on ARCH_OMAP && OMAP_TOTO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700472 help
473 This enables access to the NOR flash on the Texas Instruments
474 TOTO board.
475
476config MTD_H720X
477 tristate "Hynix evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000478 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700479 help
480 This enables access to the flash chips on the Hynix evaluation boards.
481 If you have such a board, say 'Y'.
482
Todd Poynor10c96f22005-07-02 02:53:28 +0100483config MTD_OMAP_NOR
484 tristate "TI OMAP board mappings"
485 depends on MTD_CFI && ARCH_OMAP
486 help
487 This enables access to the NOR flash chips on TI OMAP-based
488 boards defining flash platform devices and flash platform data.
489 These boards include the Innovator, H2, H3, OSK, Perseus2, and
490 more. If you have such a board, say 'Y'.
491
Linus Torvalds1da177e2005-04-16 15:20:36 -0700492# This needs CFI or JEDEC, depending on the cards found.
493config MTD_PCI
494 tristate "PCI MTD driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500495 depends on PCI && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700496 help
497 Mapping for accessing flash devices on add-in cards like the Intel XScale
498 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
499 (please see the manual for the link settings).
500
501 If you are not sure, say N.
502
503config MTD_PCMCIA
504 tristate "PCMCIA MTD driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500505 depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
Linus Torvalds1da177e2005-04-16 15:20:36 -0700506 help
507 Map driver for accessing PCMCIA linear flash memory cards. These
508 cards are usually around 4-16MiB in size. This does not include
509 Compact Flash cards which are treated as IDE devices.
510
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700511config MTD_PCMCIA_ANONYMOUS
512 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
513 depends on MTD_PCMCIA
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700514 help
515 If this option is enabled, PCMCIA cards which do not report
516 anything about themselves are assumed to be MTD cards.
517
518 If unsure, say N.
519
Linus Torvalds1da177e2005-04-16 15:20:36 -0700520config MTD_UCLINUX
521 tristate "Generic uClinux RAM/ROM filesystem support"
522 depends on MTD_PARTITIONS && !MMU
523 help
524 Map driver to support image based filesystems for uClinux.
525
526config MTD_WRSBC8260
527 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
528 depends on (SBC82xx || SBC8560)
529 select MTD_PARTITIONS
530 select MTD_MAP_BANK_WIDTH_4
531 select MTD_MAP_BANK_WIDTH_1
532 select MTD_CFI_I1
533 select MTD_CFI_I4
534 help
535 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
536 all three flash regions on CS0, CS1 and CS6 if they are configured
537 correctly by the boot loader.
538
539config MTD_DMV182
540 tristate "Map driver for Dy-4 SVME/DMV-182 board."
541 depends on DMV182
542 select MTD_PARTITIONS
543 select MTD_MAP_BANK_WIDTH_32
544 select MTD_CFI_I8
545 select MTD_CFI_AMDSTD
546 help
547 Map driver for Dy-4 SVME/DMV-182 board.
548
549config MTD_BAST
Ben Dooks76853592005-02-18 11:03:48 +0000550 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
551 depends on ARCH_BAST || MACH_VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700552 select MTD_PARTITIONS
553 select MTD_MAP_BANK_WIDTH_16
554 select MTD_JEDECPROBE
555 help
Ben Dooks76853592005-02-18 11:03:48 +0000556 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
557 Thorcom VR1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700558
559 Note, this driver *cannot* over-ride the WP link on the
560 board, or currently detect the state of the link.
561
562config MTD_BAST_MAXSIZE
563 int "Maximum size for BAST flash area (MiB)"
564 depends on MTD_BAST
565 default "4"
566
567config MTD_SHARP_SL
Stanislav Brabec73061e42007-11-19 22:33:02 +0100568 tristate "ROM mapped on Sharp SL Series"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500569 depends on ARCH_PXA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700570 help
571 This enables access to the flash chip on the Sharp SL Series of PDAs.
572
David Woodhouse0bac5112007-09-23 18:51:25 +0100573config MTD_INTEL_VR_NOR
574 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
575 depends on PCI
576 help
577 Map driver for a NOR flash bank located on the Expansion Bus of the
578 Intel Vermilion Range chipset.
579
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000580config MTD_PLATRAM
Thomas Gleixner3c45e00a2005-03-18 02:07:24 +0000581 tristate "Map driver for platform device RAM (mtd-ram)"
Ben Dooks99f2a8aea2005-01-24 00:37:04 +0000582 select MTD_RAM
583 help
584 Map driver for RAM areas described via the platform device
585 system.
586
587 This selection automatically selects the map_ram driver.
588
Linus Torvalds1da177e2005-04-16 15:20:36 -0700589endmenu
590