blob: df8e00bba07b2726f71fbf02b6b1d27ff0cf396a [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001# drivers/mtd/maps/Kconfig
Linus Torvalds1da177e2005-04-16 15:20:36 -07002
3menu "Mapping drivers for chip access"
4 depends on MTD!=n
5
6config MTD_COMPLEX_MAPPINGS
7 bool "Support non-linear mappings of flash chips"
Linus Torvalds1da177e2005-04-16 15:20:36 -07008 help
9 This causes the chip drivers to allow for complicated
10 paged mappings of flash chips.
11
12config MTD_PHYSMAP
13 tristate "CFI Flash device in physical memory map"
Takashi YOSHII79b9cd52006-08-15 07:26:32 -050014 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
Linus Torvalds1da177e2005-04-16 15:20:36 -070015 help
Takashi YOSHII79b9cd52006-08-15 07:26:32 -050016 This provides a 'mapping' driver which allows the NOR Flash and
17 ROM driver code to communicate with chips which are mapped
18 physically into the CPU's memory. You will need to configure
19 the physical address and size of the flash chips on your
20 particular board as well as the bus width, either statically
Linus Torvalds1da177e2005-04-16 15:20:36 -070021 with config options or at run-time.
22
Mike Frysinger41bdf962008-04-18 13:44:10 -070023 To compile this driver as a module, choose M here: the
24 module will be called physmap.
25
Linus Torvalds1da177e2005-04-16 15:20:36 -070026config MTD_PHYSMAP_START
27 hex "Physical start address of flash mapping"
28 depends on MTD_PHYSMAP
29 default "0x8000000"
30 help
31 This is the physical memory location at which the flash chips
32 are mapped on your particular target board. Refer to the
33 memory map which should hopefully be in the documentation for
34 your board.
35 Ignore this option if you use run-time physmap configuration
36 (i.e., run-time calling physmap_configure()).
37
38config MTD_PHYSMAP_LEN
39 hex "Physical length of flash mapping"
40 depends on MTD_PHYSMAP
Lennert Buytenhek73566ed2006-05-07 17:16:36 +010041 default "0"
Linus Torvalds1da177e2005-04-16 15:20:36 -070042 help
43 This is the total length of the mapping of the flash chips on
44 your particular board. If there is space, or aliases, in the
45 physical memory map between the chips, this could be larger
46 than the total amount of flash present. Refer to the memory
47 map which should hopefully be in the documentation for your
48 board.
49 Ignore this option if you use run-time physmap configuration
50 (i.e., run-time calling physmap_configure()).
51
52config MTD_PHYSMAP_BANKWIDTH
53 int "Bank width in octets"
54 depends on MTD_PHYSMAP
55 default "2"
56 help
57 This is the total width of the data bus of the flash devices
58 in octets. For example, if you have a data bus width of 32
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020059 bits, you would set the bus width octet value to 4. This is
Linus Torvalds1da177e2005-04-16 15:20:36 -070060 used internally by the CFI drivers.
61 Ignore this option if you use run-time physmap configuration
62 (i.e., run-time calling physmap_configure()).
63
Vitaly Woola2c2fe42006-12-06 13:17:49 +030064config MTD_PHYSMAP_OF
Matt LaPlantea982ac02007-05-09 07:35:06 +020065 tristate "Flash device in physical memory map based on OF description"
Vitaly Woola2c2fe42006-12-06 13:17:49 +030066 depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
67 help
68 This provides a 'mapping' driver which allows the NOR Flash and
69 ROM driver code to communicate with chips which are mapped
70 physically into the CPU's memory. The mapping description here is
71 taken from OF device tree.
72
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080073config MTD_PMC_MSP_EVM
74 tristate "CFI Flash device mapped on PMC-Sierra MSP"
75 depends on PMC_MSP && MTD_CFI
76 select MTD_PARTITIONS
77 help
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020078 This provides a 'mapping' driver which supports the way
79 in which user-programmable flash chips are connected on the
80 PMC-Sierra MSP eval/demo boards.
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080081
82choice
Matt LaPlante01dd2fb2007-10-20 01:34:40 +020083 prompt "Maximum mappable memory available for flash IO"
Marc St-Jean68aa0fa2007-03-26 21:45:41 -080084 depends on MTD_PMC_MSP_EVM
85 default MSP_FLASH_MAP_LIMIT_32M
86
87config MSP_FLASH_MAP_LIMIT_32M
88 bool "32M"
89
90endchoice
91
92config MSP_FLASH_MAP_LIMIT
93 hex
94 default "0x02000000"
95 depends on MSP_FLASH_MAP_LIMIT_32M
96
97config MTD_PMC_MSP_RAMROOT
98 tristate "Embedded RAM block device for root on PMC-Sierra MSP"
99 depends on PMC_MSP_EMBEDDED_ROOTFS && \
100 (MTD_BLOCK || MTD_BLOCK_RO) && \
101 MTD_RAM
102 help
103 This provides support for the embedded root file system
104 on PMC MSP devices. This memory is mapped as a MTD block device.
105
Linus Torvalds1da177e2005-04-16 15:20:36 -0700106config MTD_SUN_UFLASH
107 tristate "Sun Microsystems userflash support"
Al Viroe0e5de02007-07-26 17:33:09 +0100108 depends on SPARC && MTD_CFI && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000110 This provides a 'mapping' driver which supports the way in
111 which user-programmable flash chips are connected on various
112 Sun Microsystems boardsets. This driver will require CFI support
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 in the kernel, so if you did not enable CFI previously, do that now.
114
Linus Torvalds1da177e2005-04-16 15:20:36 -0700115config MTD_SC520CDP
116 tristate "CFI Flash device mapped on AMD SC520 CDP"
Daniel Drakefbbc21c2006-04-29 11:41:44 +0100117 depends on X86 && MTD_CFI && MTD_CONCAT
Linus Torvalds1da177e2005-04-16 15:20:36 -0700118 help
119 The SC520 CDP board has two banks of CFI-compliant chips and one
120 Dual-in-line JEDEC chip. This 'mapping' driver supports that
121 arrangement, implementing three MTD devices.
122
123config MTD_NETSC520
124 tristate "CFI Flash device mapped on AMD NetSc520"
125 depends on X86 && MTD_CFI && MTD_PARTITIONS
126 help
127 This enables access routines for the flash chips on the AMD NetSc520
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000128 demonstration board. If you have one of these boards and would like
Linus Torvalds1da177e2005-04-16 15:20:36 -0700129 to use the flash chips on it, say 'Y'.
130
131config MTD_TS5500
132 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
Sean Youngef63d002005-11-09 00:12:50 +0000133 depends on X86
Sean Young01ac7422005-06-29 09:46:19 +0000134 select MTD_PARTITIONS
135 select MTD_JEDECPROBE
136 select MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700137 help
138 This provides a driver for the on-board flash of the Technologic
Sean Younge27a9962005-06-16 09:49:33 +0100139 System's TS-5500 board. The 2MB flash is split into 3 partitions
Linus Torvalds1da177e2005-04-16 15:20:36 -0700140 which are accessed as separate MTD devices.
141
Sean Younge27a9962005-06-16 09:49:33 +0100142 mtd0 and mtd2 are the two BIOS drives, which use the resident
143 flash disk (RFD) flash translation layer.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700144
145 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
146
147 Note that jumper 3 ("Write Enable Drive A") must be set
Egry Gábor4992a9e2006-05-12 17:35:02 +0100148 otherwise detection won't succeed.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700149
150config MTD_SBC_GXX
151 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
152 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
153 help
154 This provides a driver for the on-board flash of Arcom Control
155 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
156 By default the flash is split into 3 partitions which are accessed
157 as separate MTD devices. This board utilizes Intel StrataFlash.
158 More info at
159 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
160
Todd Poynore644f7d2005-11-07 21:47:48 +0000161config MTD_PXA2XX
162 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
163 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
Nico Pitrecbec19a2005-07-01 23:55:24 +0100164 select MTD_PARTITIONS
165 help
Todd Poynore644f7d2005-11-07 21:47:48 +0000166 This provides a driver for the NOR flash attached to a PXA2xx chip.
Nico Pitrecbec19a2005-07-01 23:55:24 +0100167
Linus Torvalds1da177e2005-04-16 15:20:36 -0700168config MTD_OCTAGON
169 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
170 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
171 help
172 This provides a 'mapping' driver which supports the way in which
173 the flash chips are connected in the Octagon-5066 Single Board
174 Computer. More information on the board is available at
175 <http://www.octagonsystems.com/CPUpages/5066.html>.
176
177config MTD_VMAX
178 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
179 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
180 help
181 This provides a 'mapping' driver which supports the way in which
182 the flash chips are connected in the Tempustech VMAX SBC301 Single
183 Board Computer. More information on the board is available at
184 <http://www.tempustech.com/>.
185
186config MTD_SCx200_DOCFLASH
187 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
188 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
189 help
190 Enable support for a flash chip mapped using the DOCCS signal on a
191 National Semiconductor SCx200 processor.
192
193 If you don't know what to do here, say N.
194
195 If compiled as a module, it will be called scx200_docflash.
196
197config MTD_AMD76XROM
198 tristate "BIOS flash chip on AMD76x southbridge"
199 depends on X86 && MTD_JEDECPROBE
200 help
201 Support for treating the BIOS flash chip on AMD76x motherboards
202 as an MTD device - with this you can reprogram your BIOS.
203
204 BE VERY CAREFUL.
205
206config MTD_ICHXROM
207 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
208 depends on X86 && MTD_JEDECPROBE
209 help
210 Support for treating the BIOS flash chip on ICHX motherboards
211 as an MTD device - with this you can reprogram your BIOS.
212
213 BE VERY CAREFUL.
214
Lew Glendenning29175772006-10-20 14:41:04 -0700215config MTD_ESB2ROM
216 tristate "BIOS flash chip on Intel ESB Controller Hub 2"
Randy Dunlapdffbc422006-12-04 15:03:00 -0800217 depends on X86 && MTD_JEDECPROBE && PCI
Lew Glendenning29175772006-10-20 14:41:04 -0700218 help
219 Support for treating the BIOS flash chip on ESB2 motherboards
220 as an MTD device - with this you can reprogram your BIOS.
221
222 BE VERY CAREFUL.
223
Dave Olsen90afffc2006-11-06 16:33:57 -0700224config MTD_CK804XROM
225 tristate "BIOS flash chip on Nvidia CK804"
akpm@osdl.org862c93b2007-01-25 15:15:17 -0800226 depends on X86 && MTD_JEDECPROBE && PCI
Dave Olsen90afffc2006-11-06 16:33:57 -0700227 help
228 Support for treating the BIOS flash chip on nvidia motherboards
229 as an MTD device - with this you can reprogram your BIOS.
230
231 BE VERY CAREFUL.
232
Linus Torvalds1da177e2005-04-16 15:20:36 -0700233config MTD_SCB2_FLASH
234 tristate "BIOS flash chip on Intel SCB2 boards"
235 depends on X86 && MTD_JEDECPROBE
236 help
237 Support for treating the BIOS flash chip on Intel SCB2 boards
238 as an MTD device - with this you can reprogram your BIOS.
239
240 BE VERY CAREFUL.
241
242config MTD_TSUNAMI
243 tristate "Flash chips on Tsunami TIG bus"
244 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
245 help
246 Support for the flash chip on Tsunami TIG bus.
247
Linus Torvalds1da177e2005-04-16 15:20:36 -0700248config MTD_NETtel
249 tristate "CFI flash device on SnapGear/SecureEdge"
250 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
251 help
252 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
253
Pete Popov002fa302005-02-27 21:50:25 +0000254config MTD_ALCHEMY
Roman Zippele55a3e82006-06-08 22:12:49 -0700255 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
Ralf Baechle873b6a22007-03-10 23:10:50 +0000256 depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700257 help
Pete Popov002fa302005-02-27 21:50:25 +0000258 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
Linus Torvalds1da177e2005-04-16 15:20:36 -0700259
260config MTD_DILNETPC
261 tristate "CFI Flash device mapped on DIL/Net PC"
262 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
263 help
264 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
265 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
266 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
267
268config MTD_DILNETPC_BOOTSIZE
269 hex "Size of DIL/Net PC flash boot partition"
270 depends on MTD_DILNETPC
271 default "0x80000"
272 help
273 The amount of space taken up by the kernel or Etherboot
274 on the DIL/Net PC flash chips.
275
276config MTD_L440GX
277 tristate "BIOS flash chip on Intel L440GX boards"
278 depends on X86 && MTD_JEDECPROBE
279 help
280 Support for treating the BIOS flash chip on Intel L440GX motherboards
281 as an MTD device - with this you can reprogram your BIOS.
282
283 BE VERY CAREFUL.
284
285config MTD_SBC8240
286 tristate "Flash device on SBC8240"
Sean Young01ac7422005-06-29 09:46:19 +0000287 depends on MTD_JEDECPROBE && 8260
Linus Torvalds1da177e2005-04-16 15:20:36 -0700288 help
289 Flash access on the SBC8240 board from Wind River. See
290 <http://www.windriver.com/products/sbc8240/>
291
292config MTD_TQM8XXL
293 tristate "CFI Flash device mapped on TQM8XXL"
Sean Young01ac7422005-06-29 09:46:19 +0000294 depends on MTD_CFI && TQM8xxL
Linus Torvalds1da177e2005-04-16 15:20:36 -0700295 help
296 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
297 chips, currently uses AMD one. This 'mapping' driver supports
298 that arrangement, allowing the CFI probe and command set driver
299 code to communicate with the chips on the TQM8xxL board. More at
300 <http://www.denx.de/embedded-ppc-en.html>.
301
302config MTD_RPXLITE
303 tristate "CFI Flash device mapped on RPX Lite or CLLF"
Sean Young01ac7422005-06-29 09:46:19 +0000304 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700305 help
306 The RPXLite PowerPC board has CFI-compliant chips mapped in
307 a strange sparse mapping. This 'mapping' driver supports that
308 arrangement, allowing the CFI probe and command set driver code
309 to communicate with the chips on the RPXLite board. More at
310 <http://www.embeddedplanet.com/>.
311
312config MTD_MBX860
313 tristate "System flash on MBX860 board"
Sean Young01ac7422005-06-29 09:46:19 +0000314 depends on MTD_CFI && MBX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700315 help
316 This enables access routines for the flash chips on the Motorola
317 MBX860 board. If you have one of these boards and would like
318 to use the flash chips on it, say 'Y'.
319
320config MTD_DBOX2
321 tristate "CFI Flash device mapped on D-Box2"
Sean Young01ac7422005-06-29 09:46:19 +0000322 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700323 help
324 This enables access routines for the flash chips on the Nokia/Sagem
325 D-Box 2 board. If you have one of these boards and would like to use
326 the flash chips on it, say 'Y'.
327
328config MTD_CFI_FLAGADM
329 tristate "CFI Flash device mapping on FlagaDM"
Sean Young01ac7422005-06-29 09:46:19 +0000330 depends on 8xx && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700331 help
332 Mapping for the Flaga digital module. If you don't have one, ignore
333 this setting.
334
Linus Torvalds1da177e2005-04-16 15:20:36 -0700335config MTD_WALNUT
336 tristate "Flash device mapped on IBM 405GP Walnut"
Josh Boyer3feb0ff2007-08-22 14:30:47 -0500337 depends on MTD_JEDECPROBE && WALNUT && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700338 help
339 This enables access routines for the flash chips on the IBM 405GP
340 Walnut board. If you have one of these boards and would like to
341 use the flash chips on it, say 'Y'.
342
343config MTD_EBONY
344 tristate "Flash devices mapped on IBM 440GP Ebony"
David Gibson0d279d42007-07-30 15:55:02 +1000345 depends on MTD_JEDECPROBE && EBONY && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700346 help
347 This enables access routines for the flash chips on the IBM 440GP
348 Ebony board. If you have one of these boards and would like to
349 use the flash chips on it, say 'Y'.
350
351config MTD_OCOTEA
352 tristate "Flash devices mapped on IBM 440GX Ocotea"
Josh Boyer3feb0ff2007-08-22 14:30:47 -0500353 depends on MTD_CFI && OCOTEA && !PPC_MERGE
Linus Torvalds1da177e2005-04-16 15:20:36 -0700354 help
355 This enables access routines for the flash chips on the IBM 440GX
356 Ocotea board. If you have one of these boards and would like to
357 use the flash chips on it, say 'Y'.
358
359config MTD_REDWOOD
360 tristate "CFI Flash devices mapped on IBM Redwood"
Sean Young01ac7422005-06-29 09:46:19 +0000361 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700362 help
363 This enables access routines for the flash chips on the IBM
364 Redwood board. If you have one of these boards and would like to
365 use the flash chips on it, say 'Y'.
366
Linus Torvalds1da177e2005-04-16 15:20:36 -0700367config MTD_SOLUTIONENGINE
368 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
Paul Mundte35e2832008-04-25 14:27:08 +0900369 depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700370 help
371 This enables access to the flash chips on the Hitachi SolutionEngine and
372 similar boards. Say 'Y' if you are building a kernel for such a board.
373
374config MTD_ARM_INTEGRATOR
375 tristate "CFI Flash device mapped on ARM Integrator/P720T"
376 depends on ARM && MTD_CFI
377
378config MTD_CDB89712
379 tristate "Cirrus CDB89712 evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000380 depends on MTD_CFI && ARCH_CDB89712
Linus Torvalds1da177e2005-04-16 15:20:36 -0700381 help
382 This enables access to the flash or ROM chips on the CDB89712 board.
383 If you have such a board, say 'Y'.
384
385config MTD_SA1100
386 tristate "CFI Flash device mapped on StrongARM SA11x0"
Sean Young01ac7422005-06-29 09:46:19 +0000387 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700388 help
389 This enables access to the flash chips on most platforms based on
390 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
391 If you have such a board, say 'Y'.
392
393config MTD_IPAQ
394 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
Sean Young01ac7422005-06-29 09:46:19 +0000395 depends on IPAQ_HANDHELD && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700396 help
397 This provides a driver for the on-board flash of the iPAQ.
398
399config MTD_DC21285
400 tristate "CFI Flash device mapped on DC21285 Footbridge"
Sean Young01ac7422005-06-29 09:46:19 +0000401 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700402 help
403 This provides a driver for the flash accessed using Intel's
404 21285 bridge used with Intel's StrongARM processors. More info at
405 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
406
Linus Torvalds1da177e2005-04-16 15:20:36 -0700407config MTD_IXP4XX
408 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000409 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700410 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000411 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700412 on Intel's IXP4xx family of network processors such as the
413 IXDP425 and Coyote. If you have an IXP4xx based board and
414 would like to use the flash chips on it, say 'Y'.
415
416config MTD_IXP2000
417 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
Sean Young01ac7422005-06-29 09:46:19 +0000418 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700419 help
Thomas Gleixner69f34c92005-11-07 11:15:40 +0000420 This enables MTD access to flash devices on platforms based
Linus Torvalds1da177e2005-04-16 15:20:36 -0700421 on Intel's IXP2000 family of network processors such as the
422 IXDP425 and Coyote. If you have an IXP2000 based board and
423 would like to use the flash chips on it, say 'Y'.
424
Linus Torvalds1da177e2005-04-16 15:20:36 -0700425config MTD_FORTUNET
426 tristate "CFI Flash device mapped on the FortuNet board"
Sean Young01ac7422005-06-29 09:46:19 +0000427 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
Linus Torvalds1da177e2005-04-16 15:20:36 -0700428 help
429 This enables access to the Flash on the FortuNet board. If you
430 have such a board, say 'Y'.
431
432config MTD_AUTCPU12
433 tristate "NV-RAM mapping AUTCPU12 board"
Sean Young01ac7422005-06-29 09:46:19 +0000434 depends on ARCH_AUTCPU12
Linus Torvalds1da177e2005-04-16 15:20:36 -0700435 help
436 This enables access to the NV-RAM on autronix autcpu12 board.
437 If you have such a board, say 'Y'.
438
439config MTD_EDB7312
440 tristate "CFI Flash device mapped on EDB7312"
Sean Young01ac7422005-06-29 09:46:19 +0000441 depends on ARCH_EDB7312 && MTD_CFI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700442 help
443 This enables access to the CFI Flash on the Cogent EDB7312 board.
444 If you have such a board, say 'Y' here.
445
446config MTD_IMPA7
447 tristate "JEDEC Flash device mapped on impA7"
448 depends on ARM && MTD_JEDECPROBE
449 help
450 This enables access to the NOR Flash on the impA7 board of
451 implementa GmbH. If you have such a board, say 'Y' here.
452
453config MTD_CEIVA
454 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
Sean Young01ac7422005-06-29 09:46:19 +0000455 depends on MTD_JEDECPROBE && ARCH_CEIVA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700456 help
457 This enables access to the flash chips on the Ceiva/Polaroid
458 PhotoMax Digital Picture Frame.
459 If you have such a device, say 'Y'.
460
461config MTD_NOR_TOTO
462 tristate "NOR Flash device on TOTO board"
Sean Young01ac7422005-06-29 09:46:19 +0000463 depends on ARCH_OMAP && OMAP_TOTO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700464 help
465 This enables access to the NOR flash on the Texas Instruments
466 TOTO board.
467
468config MTD_H720X
469 tristate "Hynix evaluation board mappings"
Sean Young01ac7422005-06-29 09:46:19 +0000470 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
Linus Torvalds1da177e2005-04-16 15:20:36 -0700471 help
472 This enables access to the flash chips on the Hynix evaluation boards.
473 If you have such a board, say 'Y'.
474
Todd Poynor10c96f22005-07-02 02:53:28 +0100475config MTD_OMAP_NOR
476 tristate "TI OMAP board mappings"
477 depends on MTD_CFI && ARCH_OMAP
478 help
479 This enables access to the NOR flash chips on TI OMAP-based
480 boards defining flash platform devices and flash platform data.
481 These boards include the Innovator, H2, H3, OSK, Perseus2, and
482 more. If you have such a board, say 'Y'.
483
Linus Torvalds1da177e2005-04-16 15:20:36 -0700484# This needs CFI or JEDEC, depending on the cards found.
485config MTD_PCI
486 tristate "PCI MTD driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500487 depends on PCI && MTD_COMPLEX_MAPPINGS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700488 help
489 Mapping for accessing flash devices on add-in cards like the Intel XScale
490 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
491 (please see the manual for the link settings).
492
493 If you are not sure, say N.
494
495config MTD_PCMCIA
496 tristate "PCMCIA MTD driver"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500497 depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
Linus Torvalds1da177e2005-04-16 15:20:36 -0700498 help
499 Map driver for accessing PCMCIA linear flash memory cards. These
500 cards are usually around 4-16MiB in size. This does not include
501 Compact Flash cards which are treated as IDE devices.
502
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700503config MTD_PCMCIA_ANONYMOUS
504 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
505 depends on MTD_PCMCIA
Dominik Brodowski11d28a32005-06-27 16:28:32 -0700506 help
507 If this option is enabled, PCMCIA cards which do not report
508 anything about themselves are assumed to be MTD cards.
509
510 If unsure, say N.
511
Mike Frysinger2e3c22f2008-05-19 18:32:24 +0800512config MTD_BFIN_ASYNC
513 tristate "Blackfin BF533-STAMP Flash Chip Support"
514 depends on BFIN533_STAMP && MTD_CFI
515 select MTD_PARTITIONS
516 default y
517 help
518 Map driver which allows for simultaneous utilization of
519 ethernet and CFI parallel flash.
520
521 If compiled as a module, it will be called bfin-async-flash.
522
Linus Torvalds1da177e2005-04-16 15:20:36 -0700523config MTD_UCLINUX
524 tristate "Generic uClinux RAM/ROM filesystem support"
525 depends on MTD_PARTITIONS && !MMU
526 help
527 Map driver to support image based filesystems for uClinux.
528
529config MTD_WRSBC8260
530 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
531 depends on (SBC82xx || SBC8560)
532 select MTD_PARTITIONS
533 select MTD_MAP_BANK_WIDTH_4
534 select MTD_MAP_BANK_WIDTH_1
535 select MTD_CFI_I1
536 select MTD_CFI_I4
537 help
538 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
539 all three flash regions on CS0, CS1 and CS6 if they are configured
540 correctly by the boot loader.
541
542config MTD_DMV182
543 tristate "Map driver for Dy-4 SVME/DMV-182 board."
544 depends on DMV182
545 select MTD_PARTITIONS
546 select MTD_MAP_BANK_WIDTH_32
547 select MTD_CFI_I8
548 select MTD_CFI_AMDSTD
549 help
550 Map driver for Dy-4 SVME/DMV-182 board.
551
Linus Torvalds1da177e2005-04-16 15:20:36 -0700552config MTD_SHARP_SL
Stanislav Brabec73061e42007-11-19 22:33:02 +0100553 tristate "ROM mapped on Sharp SL Series"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500554 depends on ARCH_PXA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700555 help
556 This enables access to the flash chip on the Sharp SL Series of PDAs.
557
David Woodhouse0bac5112007-09-23 18:51:25 +0100558config MTD_INTEL_VR_NOR
559 tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
560 depends on PCI
561 help
562 Map driver for a NOR flash bank located on the Expansion Bus of the
563 Intel Vermilion Range chipset.
564
Ben Dooks99f2a8a2005-01-24 00:37:04 +0000565config MTD_PLATRAM
Thomas Gleixner3c45e002005-03-18 02:07:24 +0000566 tristate "Map driver for platform device RAM (mtd-ram)"
Ben Dooks99f2a8a2005-01-24 00:37:04 +0000567 select MTD_RAM
568 help
569 Map driver for RAM areas described via the platform device
570 system.
571
572 This selection automatically selects the map_ram driver.
573
Linus Torvalds1da177e2005-04-16 15:20:36 -0700574endmenu
575