xref: /openbmc/linux/drivers/mtd/maps/Kconfig (revision 643d1f7f)
1# drivers/mtd/maps/Kconfig
2# $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner Exp $
3
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	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"
15	depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
16	help
17	  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
22	  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
39	default "0"
40	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 octet 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
62config MTD_PHYSMAP_OF
63	tristate "Flash device in physical memory map based on OF description"
64	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
71config 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 supports 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 available 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
104config MTD_SUN_UFLASH
105	tristate "Sun Microsystems userflash support"
106	depends on SPARC && MTD_CFI && PCI
107	help
108	  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
111	  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"
122	depends on X86 && MTD_CFI && MTD_CONCAT
123	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
133	  demonstration board. If you have one of these boards and would like
134	  to use the flash chips on it, say 'Y'.
135
136config MTD_TS5500
137	tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
138	depends on X86
139	select MTD_PARTITIONS
140	select MTD_JEDECPROBE
141	select MTD_CFI_AMDSTD
142	help
143	  This provides a driver for the on-board flash of the Technologic
144	  System's TS-5500 board. The 2MB flash is split into 3 partitions
145	  which are accessed as separate MTD devices.
146
147	  mtd0 and mtd2 are the two BIOS drives, which use the resident
148	  flash disk (RFD) flash translation layer.
149
150	  mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
151
152	  Note that jumper 3 ("Write Enable Drive A") must be set
153	  otherwise detection won't succeed.
154
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
166config MTD_PXA2XX
167	tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
168	depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
169	select MTD_PARTITIONS
170	help
171	  This provides a driver for the NOR flash attached to a PXA2xx chip.
172
173config MTD_OCTAGON
174	tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
175	depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
176	help
177	  This provides a 'mapping' driver which supports the way in which
178	  the flash chips are connected in the Octagon-5066 Single Board
179	  Computer. More information on the board is available at
180	  <http://www.octagonsystems.com/CPUpages/5066.html>.
181
182config MTD_VMAX
183	tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
184	depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
185	help
186	  This provides a 'mapping' driver which supports the way in which
187	  the flash chips are connected in the Tempustech VMAX SBC301 Single
188	  Board Computer. More information on the board is available at
189	  <http://www.tempustech.com/>.
190
191config MTD_SCx200_DOCFLASH
192	tristate "Flash device mapped with DOCCS on NatSemi SCx200"
193	depends on SCx200 && MTD_CFI && MTD_PARTITIONS
194	help
195	  Enable support for a flash chip mapped using the DOCCS signal on a
196	  National Semiconductor SCx200 processor.
197
198	  If you don't know what to do here, say N.
199
200	  If compiled as a module, it will be called scx200_docflash.
201
202config MTD_AMD76XROM
203	tristate "BIOS flash chip on AMD76x southbridge"
204	depends on X86 && MTD_JEDECPROBE
205	help
206	  Support for treating the BIOS flash chip on AMD76x motherboards
207	  as an MTD device - with this you can reprogram your BIOS.
208
209	  BE VERY CAREFUL.
210
211config MTD_ICHXROM
212	tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
213	depends on X86 && MTD_JEDECPROBE
214	help
215	  Support for treating the BIOS flash chip on ICHX motherboards
216	  as an MTD device - with this you can reprogram your BIOS.
217
218	  BE VERY CAREFUL.
219
220config MTD_ESB2ROM
221        tristate "BIOS flash chip on Intel ESB Controller Hub 2"
222        depends on X86 && MTD_JEDECPROBE && PCI
223        help
224          Support for treating the BIOS flash chip on ESB2 motherboards
225          as an MTD device - with this you can reprogram your BIOS.
226
227          BE VERY CAREFUL.
228
229config MTD_CK804XROM
230	tristate "BIOS flash chip on Nvidia CK804"
231	depends on X86 && MTD_JEDECPROBE && PCI
232	help
233	  Support for treating the BIOS flash chip on nvidia motherboards
234	  as an MTD device - with this you can reprogram your BIOS.
235
236	  BE VERY CAREFUL.
237
238config MTD_SCB2_FLASH
239	tristate "BIOS flash chip on Intel SCB2 boards"
240	depends on X86 && MTD_JEDECPROBE
241	help
242	  Support for treating the BIOS flash chip on Intel SCB2 boards
243	  as an MTD device - with this you can reprogram your BIOS.
244
245	  BE VERY CAREFUL.
246
247config MTD_TSUNAMI
248	tristate "Flash chips on Tsunami TIG bus"
249	depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
250	help
251	  Support for the flash chip on Tsunami TIG bus.
252
253config MTD_NETtel
254	tristate "CFI flash device on SnapGear/SecureEdge"
255	depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
256	help
257	  Support for flash chips on NETtel/SecureEdge/SnapGear boards.
258
259config MTD_ALCHEMY
260	tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
261	depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
262	help
263	  Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
264
265config MTD_MTX1
266	tristate "4G Systems MTX-1 Flash device"
267	depends on MIPS_MTX1 && MTD_CFI
268	help
269	  Flash memory access on 4G Systems MTX-1 Board. If you have one of
270	  these boards and would like to use the flash chips on it, say 'Y'.
271
272config MTD_DILNETPC
273	tristate "CFI Flash device mapped on DIL/Net PC"
274	depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
275	help
276	  MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
277	  For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
278 	  and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
279
280config MTD_DILNETPC_BOOTSIZE
281	hex "Size of DIL/Net PC flash boot partition"
282	depends on MTD_DILNETPC
283	default "0x80000"
284	help
285	  The amount of space taken up by the kernel or Etherboot
286	  on the DIL/Net PC flash chips.
287
288config MTD_L440GX
289	tristate "BIOS flash chip on Intel L440GX boards"
290	depends on X86 && MTD_JEDECPROBE
291	help
292	  Support for treating the BIOS flash chip on Intel L440GX motherboards
293	  as an MTD device - with this you can reprogram your BIOS.
294
295	  BE VERY CAREFUL.
296
297config MTD_SBC8240
298	tristate "Flash device on SBC8240"
299	depends on MTD_JEDECPROBE && 8260
300	help
301          Flash access on the SBC8240 board from Wind River.  See
302          <http://www.windriver.com/products/sbc8240/>
303
304config MTD_TQM8XXL
305	tristate "CFI Flash device mapped on TQM8XXL"
306	depends on MTD_CFI && TQM8xxL
307	help
308	  The TQM8xxL PowerPC board has up to two banks of CFI-compliant
309	  chips, currently uses AMD one. This 'mapping' driver supports
310	  that arrangement, allowing the CFI probe and command set driver
311	  code to communicate with the chips on the TQM8xxL board. More at
312	  <http://www.denx.de/embedded-ppc-en.html>.
313
314config MTD_RPXLITE
315	tristate "CFI Flash device mapped on RPX Lite or CLLF"
316	depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
317	help
318	  The RPXLite PowerPC board has CFI-compliant chips mapped in
319	  a strange sparse mapping. This 'mapping' driver supports that
320	  arrangement, allowing the CFI probe and command set driver code
321	  to communicate with the chips on the RPXLite board. More at
322	  <http://www.embeddedplanet.com/>.
323
324config MTD_MBX860
325	tristate "System flash on MBX860 board"
326	depends on MTD_CFI && MBX
327	help
328	  This enables access routines for the flash chips on the Motorola
329	  MBX860 board. If you have one of these boards and would like
330	  to use the flash chips on it, say 'Y'.
331
332config MTD_DBOX2
333	tristate "CFI Flash device mapped on D-Box2"
334	depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
335	help
336	  This enables access routines for the flash chips on the Nokia/Sagem
337	  D-Box 2 board. If you have one of these boards and would like to use
338	  the flash chips on it, say 'Y'.
339
340config MTD_CFI_FLAGADM
341	tristate "CFI Flash device mapping on FlagaDM"
342	depends on 8xx && MTD_CFI
343	help
344	  Mapping for the Flaga digital module. If you don't have one, ignore
345	  this setting.
346
347config MTD_WALNUT
348	tristate "Flash device mapped on IBM 405GP Walnut"
349	depends on MTD_JEDECPROBE && WALNUT && !PPC_MERGE
350	help
351	  This enables access routines for the flash chips on the IBM 405GP
352	  Walnut board. If you have one of these boards and would like to
353	  use the flash chips on it, say 'Y'.
354
355config MTD_EBONY
356	tristate "Flash devices mapped on IBM 440GP Ebony"
357	depends on MTD_JEDECPROBE && EBONY && !PPC_MERGE
358	help
359	  This enables access routines for the flash chips on the IBM 440GP
360	  Ebony board. If you have one of these boards and would like to
361	  use the flash chips on it, say 'Y'.
362
363config MTD_OCOTEA
364	tristate "Flash devices mapped on IBM 440GX Ocotea"
365	depends on MTD_CFI && OCOTEA && !PPC_MERGE
366	help
367	  This enables access routines for the flash chips on the IBM 440GX
368	  Ocotea board. If you have one of these boards and would like to
369	  use the flash chips on it, say 'Y'.
370
371config MTD_REDWOOD
372	tristate "CFI Flash devices mapped on IBM Redwood"
373	depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
374	help
375	  This enables access routines for the flash chips on the IBM
376	  Redwood board. If you have one of these boards and would like to
377	  use the flash chips on it, say 'Y'.
378
379config MTD_SOLUTIONENGINE
380	tristate "CFI Flash device mapped on Hitachi SolutionEngine"
381	depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
382	help
383	  This enables access to the flash chips on the Hitachi SolutionEngine and
384	  similar boards. Say 'Y' if you are building a kernel for such a board.
385
386config MTD_ARM_INTEGRATOR
387	tristate "CFI Flash device mapped on ARM Integrator/P720T"
388	depends on ARM && MTD_CFI
389
390config MTD_CDB89712
391	tristate "Cirrus CDB89712 evaluation board mappings"
392	depends on MTD_CFI && ARCH_CDB89712
393	help
394	  This enables access to the flash or ROM chips on the CDB89712 board.
395	  If you have such a board, say 'Y'.
396
397config MTD_SA1100
398	tristate "CFI Flash device mapped on StrongARM SA11x0"
399	depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
400	help
401	  This enables access to the flash chips on most platforms based on
402	  the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
403	  If you have such a board, say 'Y'.
404
405config MTD_IPAQ
406	tristate "CFI Flash device mapped on Compaq/HP iPAQ"
407	depends on IPAQ_HANDHELD && MTD_CFI
408	help
409	  This provides a driver for the on-board flash of the iPAQ.
410
411config MTD_DC21285
412	tristate "CFI Flash device mapped on DC21285 Footbridge"
413	depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
414	help
415	  This provides a driver for the flash accessed using Intel's
416	  21285 bridge used with Intel's StrongARM processors. More info at
417	  <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
418
419config MTD_IXP4XX
420	tristate "CFI Flash device mapped on Intel IXP4xx based systems"
421	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
422	help
423	  This enables MTD access to flash devices on platforms based
424	  on Intel's IXP4xx family of network processors such as the
425	  IXDP425 and Coyote. If you have an IXP4xx based board and
426	  would like to use the flash chips on it, say 'Y'.
427
428config MTD_IXP2000
429	tristate "CFI Flash device mapped on Intel IXP2000 based systems"
430	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
431	help
432	  This enables MTD access to flash devices on platforms based
433	  on Intel's IXP2000 family of network processors such as the
434	  IXDP425 and Coyote. If you have an IXP2000 based board and
435	  would like to use the flash chips on it, say 'Y'.
436
437config MTD_FORTUNET
438	tristate "CFI Flash device mapped on the FortuNet board"
439	depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
440	help
441	  This enables access to the Flash on the FortuNet board.  If you
442	  have such a board, say 'Y'.
443
444config MTD_AUTCPU12
445	tristate "NV-RAM mapping AUTCPU12 board"
446	depends on ARCH_AUTCPU12
447	help
448	  This enables access to the NV-RAM on autronix autcpu12 board.
449	  If you have such a board, say 'Y'.
450
451config MTD_EDB7312
452	tristate "CFI Flash device mapped on EDB7312"
453	depends on ARCH_EDB7312 && MTD_CFI
454	help
455	  This enables access to the CFI Flash on the Cogent EDB7312 board.
456	  If you have such a board, say 'Y' here.
457
458config MTD_IMPA7
459	tristate "JEDEC Flash device mapped on impA7"
460	depends on ARM && MTD_JEDECPROBE
461	help
462	  This enables access to the NOR Flash on the impA7 board of
463	  implementa GmbH. If you have such a board, say 'Y' here.
464
465config MTD_CEIVA
466	tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
467	depends on MTD_JEDECPROBE && ARCH_CEIVA
468	help
469	  This enables access to the flash chips on the Ceiva/Polaroid
470	  PhotoMax Digital Picture Frame.
471	  If you have such a device, say 'Y'.
472
473config MTD_NOR_TOTO
474	tristate "NOR Flash device on TOTO board"
475	depends on ARCH_OMAP && OMAP_TOTO
476	help
477	  This enables access to the NOR flash on the Texas Instruments
478	  TOTO board.
479
480config MTD_H720X
481	tristate "Hynix evaluation board mappings"
482	depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
483	help
484	  This enables access to the flash chips on the Hynix evaluation boards.
485	  If you have such a board, say 'Y'.
486
487config MTD_MPC1211
488	tristate "CFI Flash device mapped on Interface MPC-1211"
489	depends on SH_MPC1211 && MTD_CFI
490	help
491	  This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
492	  If you have such a board, say 'Y'.
493
494config MTD_OMAP_NOR
495	tristate "TI OMAP board mappings"
496	depends on MTD_CFI && ARCH_OMAP
497	help
498	  This enables access to the NOR flash chips on TI OMAP-based
499	  boards defining flash platform devices and flash platform data.
500	  These boards include the Innovator, H2, H3, OSK, Perseus2, and
501	  more.  If you have such a board, say 'Y'.
502
503# This needs CFI or JEDEC, depending on the cards found.
504config MTD_PCI
505	tristate "PCI MTD driver"
506	depends on PCI && MTD_COMPLEX_MAPPINGS
507	help
508	  Mapping for accessing flash devices on add-in cards like the Intel XScale
509	  IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
510	  (please see the manual for the link settings).
511
512	  If you are not sure, say N.
513
514config MTD_PCMCIA
515	tristate "PCMCIA MTD driver"
516	depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
517	help
518	  Map driver for accessing PCMCIA linear flash memory cards. These
519	  cards are usually around 4-16MiB in size. This does not include
520	  Compact Flash cards which are treated as IDE devices.
521
522config MTD_PCMCIA_ANONYMOUS
523	bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
524	depends on MTD_PCMCIA
525	help
526	  If this option is enabled, PCMCIA cards which do not report
527	  anything about themselves are assumed to be MTD cards.
528
529	  If unsure, say N.
530
531config MTD_UCLINUX
532	tristate "Generic uClinux RAM/ROM filesystem support"
533	depends on MTD_PARTITIONS && !MMU
534	help
535	  Map driver to support image based filesystems for uClinux.
536
537config MTD_WRSBC8260
538	tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
539	depends on (SBC82xx || SBC8560)
540	select MTD_PARTITIONS
541	select MTD_MAP_BANK_WIDTH_4
542	select MTD_MAP_BANK_WIDTH_1
543	select MTD_CFI_I1
544	select MTD_CFI_I4
545	help
546	  Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
547	  all three flash regions on CS0, CS1 and CS6 if they are configured
548	  correctly by the boot loader.
549
550config MTD_DMV182
551        tristate "Map driver for Dy-4 SVME/DMV-182 board."
552        depends on DMV182
553        select MTD_PARTITIONS
554	select MTD_MAP_BANK_WIDTH_32
555	select MTD_CFI_I8
556	select MTD_CFI_AMDSTD
557        help
558          Map driver for Dy-4 SVME/DMV-182 board.
559
560config MTD_BAST
561	tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
562	depends on ARCH_BAST || MACH_VR1000
563	select MTD_PARTITIONS
564	select MTD_MAP_BANK_WIDTH_16
565	select MTD_JEDECPROBE
566	help
567	  Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
568	  Thorcom VR1000
569
570	  Note, this driver *cannot* over-ride the WP link on the
571	  board, or currently detect the state of the link.
572
573config MTD_BAST_MAXSIZE
574	int "Maximum size for BAST flash area (MiB)"
575	depends on MTD_BAST
576	default "4"
577
578config MTD_SHARP_SL
579	bool "ROM mapped on Sharp SL Series"
580	depends on ARCH_PXA
581	help
582	  This enables access to the flash chip on the Sharp SL Series of PDAs.
583
584config MTD_INTEL_VR_NOR
585	tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
586	depends on PCI
587	help
588	  Map driver for a NOR flash bank located on the Expansion Bus of the
589	  Intel Vermilion Range chipset.
590
591config MTD_PLATRAM
592	tristate "Map driver for platform device RAM (mtd-ram)"
593	select MTD_RAM
594	help
595	  Map driver for RAM areas described via the platform device
596	  system.
597
598	  This selection automatically selects the map_ram driver.
599
600endmenu
601
602