ia64/linux-2.6.18-xen.hg

view drivers/mtd/maps/Kconfig @ 897:329ea0ccb344

balloon: try harder to balloon up under memory pressure.

Currently if the balloon driver is unable to increase the guest's
reservation it assumes the failure was due to reaching its full
allocation, gives up on the ballooning operation and records the limit
it reached as the "hard limit". The driver will not try again until
the target is set again (even to the same value).

However it is possible that ballooning has in fact failed due to
memory pressure in the host and therefore it is desirable to keep
attempting to reach the target in case memory becomes available. The
most likely scenario is that some guests are ballooning down while
others are ballooning up and therefore there is temporary memory
pressure while things stabilise. You would not expect a well behaved
toolstack to ask a domain to balloon to more than its allocation nor
would you expect it to deliberately over-commit memory by setting
balloon targets which exceed the total host memory.

This patch drops the concept of a hard limit and causes the balloon
driver to retry increasing the reservation on a timer in the same
manner as when decreasing the reservation.

Also if we partially succeed in increasing the reservation
(i.e. receive less pages than we asked for) then we may as well keep
those pages rather than returning them to Xen.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
author Keir Fraser <keir.fraser@citrix.com>
date Fri Jun 05 14:01:20 2009 +0100 (2009-06-05)
parents 831230e53067
children
line source
1 # drivers/mtd/maps/Kconfig
2 # $Id: Kconfig,v 1.61 2005/11/07 11:14:26 gleixner Exp $
4 menu "Mapping drivers for chip access"
5 depends on MTD!=n
7 config MTD_COMPLEX_MAPPINGS
8 bool "Support non-linear mappings of flash chips"
9 depends on MTD
10 help
11 This causes the chip drivers to allow for complicated
12 paged mappings of flash chips.
14 config MTD_PHYSMAP
15 tristate "CFI Flash device in physical memory map"
16 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
17 help
18 This provides a 'mapping' driver which allows the NOR Flash and
19 ROM driver code to communicate with chips which are mapped
20 physically into the CPU's memory. You will need to configure
21 the physical address and size of the flash chips on your
22 particular board as well as the bus width, either statically
23 with config options or at run-time.
25 config MTD_PHYSMAP_START
26 hex "Physical start address of flash mapping"
27 depends on MTD_PHYSMAP
28 default "0x8000000"
29 help
30 This is the physical memory location at which the flash chips
31 are mapped on your particular target board. Refer to the
32 memory map which should hopefully be in the documentation for
33 your board.
34 Ignore this option if you use run-time physmap configuration
35 (i.e., run-time calling physmap_configure()).
37 config MTD_PHYSMAP_LEN
38 hex "Physical length of flash mapping"
39 depends on MTD_PHYSMAP
40 default "0"
41 help
42 This is the total length of the mapping of the flash chips on
43 your particular board. If there is space, or aliases, in the
44 physical memory map between the chips, this could be larger
45 than the total amount of flash present. Refer to the memory
46 map which should hopefully be in the documentation for your
47 board.
48 Ignore this option if you use run-time physmap configuration
49 (i.e., run-time calling physmap_configure()).
51 config MTD_PHYSMAP_BANKWIDTH
52 int "Bank width in octets"
53 depends on MTD_PHYSMAP
54 default "2"
55 help
56 This is the total width of the data bus of the flash devices
57 in octets. For example, if you have a data bus width of 32
58 bits, you would set the bus width octect value to 4. This is
59 used internally by the CFI drivers.
60 Ignore this option if you use run-time physmap configuration
61 (i.e., run-time calling physmap_configure()).
63 config MTD_SUN_UFLASH
64 tristate "Sun Microsystems userflash support"
65 depends on SPARC && MTD_CFI
66 help
67 This provides a 'mapping' driver which supports the way in
68 which user-programmable flash chips are connected on various
69 Sun Microsystems boardsets. This driver will require CFI support
70 in the kernel, so if you did not enable CFI previously, do that now.
72 config MTD_PNC2000
73 tristate "CFI Flash device mapped on Photron PNC-2000"
74 depends on X86 && MTD_CFI && MTD_PARTITIONS
75 help
76 PNC-2000 is the name of Network Camera product from PHOTRON
77 Ltd. in Japan. It uses CFI-compliant flash.
79 config MTD_SC520CDP
80 tristate "CFI Flash device mapped on AMD SC520 CDP"
81 depends on X86 && MTD_CFI && MTD_CONCAT
82 help
83 The SC520 CDP board has two banks of CFI-compliant chips and one
84 Dual-in-line JEDEC chip. This 'mapping' driver supports that
85 arrangement, implementing three MTD devices.
87 config MTD_NETSC520
88 tristate "CFI Flash device mapped on AMD NetSc520"
89 depends on X86 && MTD_CFI && MTD_PARTITIONS
90 help
91 This enables access routines for the flash chips on the AMD NetSc520
92 demonstration board. If you have one of these boards and would like
93 to use the flash chips on it, say 'Y'.
95 config MTD_TS5500
96 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
97 depends on X86
98 select MTD_PARTITIONS
99 select MTD_JEDECPROBE
100 select MTD_CFI_AMDSTD
101 help
102 This provides a driver for the on-board flash of the Technologic
103 System's TS-5500 board. The 2MB flash is split into 3 partitions
104 which are accessed as separate MTD devices.
106 mtd0 and mtd2 are the two BIOS drives, which use the resident
107 flash disk (RFD) flash translation layer.
109 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
111 Note that jumper 3 ("Write Enable Drive A") must be set
112 otherwise detection won't succeed.
114 config MTD_SBC_GXX
115 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
116 depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
117 help
118 This provides a driver for the on-board flash of Arcom Control
119 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
120 By default the flash is split into 3 partitions which are accessed
121 as separate MTD devices. This board utilizes Intel StrataFlash.
122 More info at
123 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
125 config MTD_LUBBOCK
126 tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"
127 depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS
128 help
129 This provides a driver for the on-board flash of the Intel
130 'Lubbock' XScale evaluation board.
132 config MTD_MAINSTONE
133 tristate "CFI Flash device mapped on Intel Mainstone XScale eval board"
134 depends on MACH_MAINSTONE && MTD_CFI_INTELEXT
135 select MTD_PARTITIONS
136 help
137 This provides a driver for the on-board flash of the Intel
138 'Mainstone PXA27x evaluation board.
140 config MTD_OCTAGON
141 tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
142 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
143 help
144 This provides a 'mapping' driver which supports the way in which
145 the flash chips are connected in the Octagon-5066 Single Board
146 Computer. More information on the board is available at
147 <http://www.octagonsystems.com/CPUpages/5066.html>.
149 config MTD_VMAX
150 tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
151 depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
152 help
153 This provides a 'mapping' driver which supports the way in which
154 the flash chips are connected in the Tempustech VMAX SBC301 Single
155 Board Computer. More information on the board is available at
156 <http://www.tempustech.com/>.
158 config MTD_SCx200_DOCFLASH
159 tristate "Flash device mapped with DOCCS on NatSemi SCx200"
160 depends on SCx200 && MTD_CFI && MTD_PARTITIONS
161 help
162 Enable support for a flash chip mapped using the DOCCS signal on a
163 National Semiconductor SCx200 processor.
165 If you don't know what to do here, say N.
167 If compiled as a module, it will be called scx200_docflash.
169 config MTD_AMD76XROM
170 tristate "BIOS flash chip on AMD76x southbridge"
171 depends on X86 && MTD_JEDECPROBE
172 help
173 Support for treating the BIOS flash chip on AMD76x motherboards
174 as an MTD device - with this you can reprogram your BIOS.
176 BE VERY CAREFUL.
178 config MTD_ICHXROM
179 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
180 depends on X86 && MTD_JEDECPROBE
181 help
182 Support for treating the BIOS flash chip on ICHX motherboards
183 as an MTD device - with this you can reprogram your BIOS.
185 BE VERY CAREFUL.
187 config MTD_SCB2_FLASH
188 tristate "BIOS flash chip on Intel SCB2 boards"
189 depends on X86 && MTD_JEDECPROBE
190 help
191 Support for treating the BIOS flash chip on Intel SCB2 boards
192 as an MTD device - with this you can reprogram your BIOS.
194 BE VERY CAREFUL.
196 config MTD_TSUNAMI
197 tristate "Flash chips on Tsunami TIG bus"
198 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
199 help
200 Support for the flash chip on Tsunami TIG bus.
202 config MTD_LASAT
203 tristate "LASAT flash device"
204 depends on LASAT && MTD_CFI
205 help
206 Support for the flash chips on the Lasat 100 and 200 boards.
208 config MTD_NETtel
209 tristate "CFI flash device on SnapGear/SecureEdge"
210 depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
211 help
212 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
214 config MTD_ALCHEMY
215 tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
216 depends on SOC_AU1X00
217 help
218 Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
220 config MTD_MTX1
221 tristate "4G Systems MTX-1 Flash device"
222 depends on MIPS && MIPS_MTX1
223 help
224 Flash memory access on 4G Systems MTX-1 Board. If you have one of
225 these boards and would like to use the flash chips on it, say 'Y'.
227 config MTD_DILNETPC
228 tristate "CFI Flash device mapped on DIL/Net PC"
229 depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
230 help
231 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
232 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
233 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
235 config MTD_DILNETPC_BOOTSIZE
236 hex "Size of DIL/Net PC flash boot partition"
237 depends on MTD_DILNETPC
238 default "0x80000"
239 help
240 The amount of space taken up by the kernel or Etherboot
241 on the DIL/Net PC flash chips.
243 config MTD_L440GX
244 tristate "BIOS flash chip on Intel L440GX boards"
245 depends on X86 && MTD_JEDECPROBE
246 help
247 Support for treating the BIOS flash chip on Intel L440GX motherboards
248 as an MTD device - with this you can reprogram your BIOS.
250 BE VERY CAREFUL.
252 config MTD_SBC8240
253 tristate "Flash device on SBC8240"
254 depends on MTD_JEDECPROBE && 8260
255 help
256 Flash access on the SBC8240 board from Wind River. See
257 <http://www.windriver.com/products/sbc8240/>
259 config MTD_TQM8XXL
260 tristate "CFI Flash device mapped on TQM8XXL"
261 depends on MTD_CFI && TQM8xxL
262 help
263 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
264 chips, currently uses AMD one. This 'mapping' driver supports
265 that arrangement, allowing the CFI probe and command set driver
266 code to communicate with the chips on the TQM8xxL board. More at
267 <http://www.denx.de/embedded-ppc-en.html>.
269 config MTD_RPXLITE
270 tristate "CFI Flash device mapped on RPX Lite or CLLF"
271 depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
272 help
273 The RPXLite PowerPC board has CFI-compliant chips mapped in
274 a strange sparse mapping. This 'mapping' driver supports that
275 arrangement, allowing the CFI probe and command set driver code
276 to communicate with the chips on the RPXLite board. More at
277 <http://www.embeddedplanet.com/>.
279 config MTD_MBX860
280 tristate "System flash on MBX860 board"
281 depends on MTD_CFI && MBX
282 help
283 This enables access routines for the flash chips on the Motorola
284 MBX860 board. If you have one of these boards and would like
285 to use the flash chips on it, say 'Y'.
287 config MTD_DBOX2
288 tristate "CFI Flash device mapped on D-Box2"
289 depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
290 help
291 This enables access routines for the flash chips on the Nokia/Sagem
292 D-Box 2 board. If you have one of these boards and would like to use
293 the flash chips on it, say 'Y'.
295 config MTD_CFI_FLAGADM
296 tristate "CFI Flash device mapping on FlagaDM"
297 depends on 8xx && MTD_CFI
298 help
299 Mapping for the Flaga digital module. If you don't have one, ignore
300 this setting.
302 config MTD_BEECH
303 tristate "CFI Flash device mapped on IBM 405LP Beech"
304 depends on MTD_CFI && BEECH
305 help
306 This enables access routines for the flash chips on the IBM
307 405LP Beech board. If you have one of these boards and would like
308 to use the flash chips on it, say 'Y'.
310 config MTD_ARCTIC
311 tristate "CFI Flash device mapped on IBM 405LP Arctic"
312 depends on MTD_CFI && ARCTIC2
313 help
314 This enables access routines for the flash chips on the IBM 405LP
315 Arctic board. If you have one of these boards and would like to
316 use the flash chips on it, say 'Y'.
318 config MTD_WALNUT
319 tristate "Flash device mapped on IBM 405GP Walnut"
320 depends on MTD_JEDECPROBE && WALNUT
321 help
322 This enables access routines for the flash chips on the IBM 405GP
323 Walnut board. If you have one of these boards and would like to
324 use the flash chips on it, say 'Y'.
326 config MTD_EBONY
327 tristate "Flash devices mapped on IBM 440GP Ebony"
328 depends on MTD_JEDECPROBE && EBONY
329 help
330 This enables access routines for the flash chips on the IBM 440GP
331 Ebony board. If you have one of these boards and would like to
332 use the flash chips on it, say 'Y'.
334 config MTD_OCOTEA
335 tristate "Flash devices mapped on IBM 440GX Ocotea"
336 depends on MTD_CFI && OCOTEA
337 help
338 This enables access routines for the flash chips on the IBM 440GX
339 Ocotea board. If you have one of these boards and would like to
340 use the flash chips on it, say 'Y'.
342 config MTD_REDWOOD
343 tristate "CFI Flash devices mapped on IBM Redwood"
344 depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
345 help
346 This enables access routines for the flash chips on the IBM
347 Redwood board. If you have one of these boards and would like to
348 use the flash chips on it, say 'Y'.
350 config MTD_TQM834x
351 tristate "Flash device mapped on TQ Components TQM834x Boards"
352 depends on MTD_CFI && TQM834x
353 help
354 This enables access routines for the flash chips on the
355 TQ Components TQM834x boards. If you have one of these boards
356 and would like to use the flash chips on it, say 'Y'.
358 config MTD_CSTM_MIPS_IXX
359 tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"
360 depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS
361 help
362 This provides a mapping driver for the Integrated Technology
363 Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR
364 Reference Board. It provides the necessary addressing, length,
365 buswidth, vpp code and addition setup of the flash device for
366 these boards. In addition, this mapping driver can be used for
367 other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/
368 LEN/BUSWIDTH parameters. This mapping will provide one mtd device
369 using one partition. The start address can be offset from the
370 beginning of flash and the len can be less than the total flash
371 device size to allow a window into the flash. Both CFI and JEDEC
372 probes are called.
374 config MTD_CSTM_MIPS_IXX_START
375 hex "Physical start address of flash mapping"
376 depends on MTD_CSTM_MIPS_IXX
377 default "0x8000000"
378 help
379 This is the physical memory location that the MTD driver will
380 use for the flash chips on your particular target board.
381 Refer to the memory map which should hopefully be in the
382 documentation for your board.
384 config MTD_CSTM_MIPS_IXX_LEN
385 hex "Physical length of flash mapping"
386 depends on MTD_CSTM_MIPS_IXX
387 default "0x4000000"
388 help
389 This is the total length that the MTD driver will use for the
390 flash chips on your particular board. Refer to the memory
391 map which should hopefully be in the documentation for your
392 board.
394 config MTD_CSTM_MIPS_IXX_BUSWIDTH
395 int "Bus width in octets"
396 depends on MTD_CSTM_MIPS_IXX
397 default "2"
398 help
399 This is the total bus width of the mapping of the flash chips
400 on your particular board.
402 config MTD_OCELOT
403 tristate "Momenco Ocelot boot flash device"
404 depends on MIPS && MOMENCO_OCELOT
405 help
406 This enables access routines for the boot flash device and for the
407 NVRAM on the Momenco Ocelot board. If you have one of these boards
408 and would like access to either of these, say 'Y'.
410 config MTD_SOLUTIONENGINE
411 tristate "CFI Flash device mapped on Hitachi SolutionEngine"
412 depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS
413 help
414 This enables access to the flash chips on the Hitachi SolutionEngine and
415 similar boards. Say 'Y' if you are building a kernel for such a board.
417 config MTD_ARM_INTEGRATOR
418 tristate "CFI Flash device mapped on ARM Integrator/P720T"
419 depends on ARM && MTD_CFI
421 config MTD_CDB89712
422 tristate "Cirrus CDB89712 evaluation board mappings"
423 depends on MTD_CFI && ARCH_CDB89712
424 help
425 This enables access to the flash or ROM chips on the CDB89712 board.
426 If you have such a board, say 'Y'.
428 config MTD_SA1100
429 tristate "CFI Flash device mapped on StrongARM SA11x0"
430 depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
431 help
432 This enables access to the flash chips on most platforms based on
433 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
434 If you have such a board, say 'Y'.
436 config MTD_IPAQ
437 tristate "CFI Flash device mapped on Compaq/HP iPAQ"
438 depends on IPAQ_HANDHELD && MTD_CFI
439 help
440 This provides a driver for the on-board flash of the iPAQ.
442 config MTD_DC21285
443 tristate "CFI Flash device mapped on DC21285 Footbridge"
444 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
445 help
446 This provides a driver for the flash accessed using Intel's
447 21285 bridge used with Intel's StrongARM processors. More info at
448 <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
450 config MTD_IQ80310
451 tristate "CFI Flash device mapped on the XScale IQ80310 board"
452 depends on MTD_CFI && ARCH_IQ80310
453 help
454 This enables access routines for the flash chips on the Intel XScale
455 IQ80310 evaluation board. If you have one of these boards and would
456 like to use the flash chips on it, say 'Y'.
458 config MTD_IXP4XX
459 tristate "CFI Flash device mapped on Intel IXP4xx based systems"
460 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
461 help
462 This enables MTD access to flash devices on platforms based
463 on Intel's IXP4xx family of network processors such as the
464 IXDP425 and Coyote. If you have an IXP4xx based board and
465 would like to use the flash chips on it, say 'Y'.
467 config MTD_IXP2000
468 tristate "CFI Flash device mapped on Intel IXP2000 based systems"
469 depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
470 help
471 This enables MTD access to flash devices on platforms based
472 on Intel's IXP2000 family of network processors such as the
473 IXDP425 and Coyote. If you have an IXP2000 based board and
474 would like to use the flash chips on it, say 'Y'.
476 config MTD_FORTUNET
477 tristate "CFI Flash device mapped on the FortuNet board"
478 depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
479 help
480 This enables access to the Flash on the FortuNet board. If you
481 have such a board, say 'Y'.
483 config MTD_AUTCPU12
484 tristate "NV-RAM mapping AUTCPU12 board"
485 depends on ARCH_AUTCPU12
486 help
487 This enables access to the NV-RAM on autronix autcpu12 board.
488 If you have such a board, say 'Y'.
490 config MTD_EDB7312
491 tristate "CFI Flash device mapped on EDB7312"
492 depends on ARCH_EDB7312 && MTD_CFI
493 help
494 This enables access to the CFI Flash on the Cogent EDB7312 board.
495 If you have such a board, say 'Y' here.
497 config MTD_IMPA7
498 tristate "JEDEC Flash device mapped on impA7"
499 depends on ARM && MTD_JEDECPROBE
500 help
501 This enables access to the NOR Flash on the impA7 board of
502 implementa GmbH. If you have such a board, say 'Y' here.
504 config MTD_CEIVA
505 tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
506 depends on MTD_JEDECPROBE && ARCH_CEIVA
507 help
508 This enables access to the flash chips on the Ceiva/Polaroid
509 PhotoMax Digital Picture Frame.
510 If you have such a device, say 'Y'.
512 config MTD_NOR_TOTO
513 tristate "NOR Flash device on TOTO board"
514 depends on ARCH_OMAP && OMAP_TOTO
515 help
516 This enables access to the NOR flash on the Texas Instruments
517 TOTO board.
519 config MTD_H720X
520 tristate "Hynix evaluation board mappings"
521 depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
522 help
523 This enables access to the flash chips on the Hynix evaluation boards.
524 If you have such a board, say 'Y'.
526 config MTD_MPC1211
527 tristate "CFI Flash device mapped on Interface MPC-1211"
528 depends on SH_MPC1211 && MTD_CFI
529 help
530 This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).
531 If you have such a board, say 'Y'.
533 config MTD_OMAP_NOR
534 tristate "TI OMAP board mappings"
535 depends on MTD_CFI && ARCH_OMAP
536 help
537 This enables access to the NOR flash chips on TI OMAP-based
538 boards defining flash platform devices and flash platform data.
539 These boards include the Innovator, H2, H3, OSK, Perseus2, and
540 more. If you have such a board, say 'Y'.
542 # This needs CFI or JEDEC, depending on the cards found.
543 config MTD_PCI
544 tristate "PCI MTD driver"
545 depends on MTD && PCI && MTD_COMPLEX_MAPPINGS
546 help
547 Mapping for accessing flash devices on add-in cards like the Intel XScale
548 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
549 (please see the manual for the link settings).
551 If you are not sure, say N.
553 config MTD_PCMCIA
554 tristate "PCMCIA MTD driver"
555 depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
556 help
557 Map driver for accessing PCMCIA linear flash memory cards. These
558 cards are usually around 4-16MiB in size. This does not include
559 Compact Flash cards which are treated as IDE devices.
561 config MTD_PCMCIA_ANONYMOUS
562 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
563 depends on MTD_PCMCIA
564 help
565 If this option is enabled, PCMCIA cards which do not report
566 anything about themselves are assumed to be MTD cards.
568 If unsure, say N.
570 config MTD_UCLINUX
571 tristate "Generic uClinux RAM/ROM filesystem support"
572 depends on MTD_PARTITIONS && !MMU
573 help
574 Map driver to support image based filesystems for uClinux.
576 config MTD_WRSBC8260
577 tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
578 depends on (SBC82xx || SBC8560)
579 select MTD_PARTITIONS
580 select MTD_MAP_BANK_WIDTH_4
581 select MTD_MAP_BANK_WIDTH_1
582 select MTD_CFI_I1
583 select MTD_CFI_I4
584 help
585 Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
586 all three flash regions on CS0, CS1 and CS6 if they are configured
587 correctly by the boot loader.
589 config MTD_DMV182
590 tristate "Map driver for Dy-4 SVME/DMV-182 board."
591 depends on DMV182
592 select MTD_PARTITIONS
593 select MTD_MAP_BANK_WIDTH_32
594 select MTD_CFI_I8
595 select MTD_CFI_AMDSTD
596 help
597 Map driver for Dy-4 SVME/DMV-182 board.
599 config MTD_BAST
600 tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"
601 depends on ARCH_BAST || MACH_VR1000
602 select MTD_PARTITIONS
603 select MTD_MAP_BANK_WIDTH_16
604 select MTD_JEDECPROBE
605 help
606 Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the
607 Thorcom VR1000
609 Note, this driver *cannot* over-ride the WP link on the
610 board, or currently detect the state of the link.
612 config MTD_BAST_MAXSIZE
613 int "Maximum size for BAST flash area (MiB)"
614 depends on MTD_BAST
615 default "4"
617 config MTD_SHARP_SL
618 bool "ROM maped on Sharp SL Series"
619 depends on MTD && ARCH_PXA
620 help
621 This enables access to the flash chip on the Sharp SL Series of PDAs.
623 config MTD_PLATRAM
624 tristate "Map driver for platform device RAM (mtd-ram)"
625 depends on MTD
626 select MTD_RAM
627 help
628 Map driver for RAM areas described via the platform device
629 system.
631 This selection automatically selects the map_ram driver.
633 endmenu