Walnut board. If you have one of these boards and would like to	  use the flash chips on it, say 'Y'.config MTD_EBONY	tristate "Flash devices mapped on IBM 440GP Ebony"	depends on MTD_JEDECPROBE && EBONY	help	  This enables access routines for the flash chips on the IBM 440GP	  Ebony board. If you have one of these boards and would like to	  use the flash chips on it, say 'Y'.config MTD_OCOTEA	tristate "Flash devices mapped on IBM 440GX Ocotea"	depends on MTD_CFI && OCOTEA	help	  This enables access routines for the flash chips on the IBM 440GX	  Ocotea board. If you have one of these boards and would like to	  use the flash chips on it, say 'Y'.config MTD_REDWOOD	tristate "CFI Flash devices mapped on IBM Redwood"	depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )	help	  This enables access routines for the flash chips on the IBM	  Redwood board. If you have one of these boards and would like to	  use the flash chips on it, say 'Y'.config MTD_TQM834x	tristate "Flash device mapped on TQ Components TQM834x Boards"	depends on MTD_CFI && TQM834x	help	  This enables access routines for the flash chips on the	  TQ Components TQM834x boards. If you have one of these boards	  and would like to use the flash chips on it, say 'Y'.config MTD_CSTM_MIPS_IXX	tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"	depends on MIPS && MTD_CFI && MTD_JEDECPROBE && MTD_PARTITIONS	help	  This provides a mapping driver for the Integrated Technology	  Express, Inc (ITE) QED-4N-S01B eval board and the Globespan IVR	  Reference Board. It provides the necessary addressing, length,	  buswidth, vpp code and addition setup of the flash device for	  these boards. In addition, this mapping driver can be used for	  other boards via setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/	  LEN/BUSWIDTH parameters. This mapping will provide one mtd device	  using one partition. The start address can be offset from the	  beginning of flash and the len can be less than the total flash	  device size to allow a window into the flash. Both CFI and JEDEC	  probes are called.config MTD_CSTM_MIPS_IXX_START	hex "Physical start address of flash mapping"	depends on MTD_CSTM_MIPS_IXX	default "0x8000000"	help	  This is the physical memory location that the MTD driver will	  use for the flash chips on your particular target board.	  Refer to the memory map which should hopefully be in the	  documentation for your board.config MTD_CSTM_MIPS_IXX_LEN	hex "Physical length of flash mapping"	depends on MTD_CSTM_MIPS_IXX	default "0x4000000"	help	  This is the total length that the MTD driver will use for the	  flash chips on your particular board.  Refer to the memory	  map which should hopefully be in the documentation for your	  board.config MTD_CSTM_MIPS_IXX_BUSWIDTH	int "Bus width in octets"	depends on MTD_CSTM_MIPS_IXX	default "2"	help	  This is the total bus width of the mapping of the flash chips	  on your particular board.config MTD_OCELOT	tristate "Momenco Ocelot boot flash device"	depends on MIPS && MOMENCO_OCELOT	help	  This enables access routines for the boot flash device and for the	  NVRAM on the Momenco Ocelot board. If you have one of these boards	  and would like access to either of these, say 'Y'.config MTD_SOLUTIONENGINE	tristate "CFI Flash device mapped on Hitachi SolutionEngine"	depends on SUPERH && MTD_CFI && MTD_REDBOOT_PARTS	help	  This enables access to the flash chips on the Hitachi SolutionEngine and	  similar boards. Say 'Y' if you are building a kernel for such a board.config MTD_ARM_INTEGRATOR	tristate "CFI Flash device mapped on ARM Integrator/P720T"	depends on ARM && MTD_CFIconfig MTD_CDB89712	tristate "Cirrus CDB89712 evaluation board mappings"	depends on MTD_CFI && ARCH_CDB89712	help	  This enables access to the flash or ROM chips on the CDB89712 board.	  If you have such a board, say 'Y'.config MTD_SA1100	tristate "CFI Flash device mapped on StrongARM SA11x0"	depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS	help	  This enables access to the flash chips on most platforms based on	  the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.	  If you have such a board, say 'Y'.config MTD_IPAQ	tristate "CFI Flash device mapped on Compaq/HP iPAQ"	depends on IPAQ_HANDHELD && MTD_CFI	help	  This provides a driver for the on-board flash of the iPAQ.config MTD_DC21285	tristate "CFI Flash device mapped on DC21285 Footbridge"	depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS	help	  This provides a driver for the flash accessed using Intel's	  21285 bridge used with Intel's StrongARM processors. More info at	  <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.config MTD_IQ80310	tristate "CFI Flash device mapped on the XScale IQ80310 board"	depends on MTD_CFI && ARCH_IQ80310	help	  This enables access routines for the flash chips on the Intel XScale	  IQ80310 evaluation board. If you have one of these boards and would	  like to use the flash chips on it, say 'Y'.config MTD_IXP4XX	tristate "CFI Flash device mapped on Intel IXP4xx based systems"	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX	help	  This enables MTD access to flash devices on platforms based	  on Intel's IXP4xx family of network processors such as the	  IXDP425 and Coyote. If you have an IXP4xx based board and	  would like to use the flash chips on it, say 'Y'.config MTD_IXP2000	tristate "CFI Flash device mapped on Intel IXP2000 based systems"	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000	help	  This enables MTD access to flash devices on platforms based	  on Intel's IXP2000 family of network processors such as the	  IXDP425 and Coyote. If you have an IXP2000 based board and	  would like to use the flash chips on it, say 'Y'.config MTD_EPXA10DB	tristate "CFI Flash device mapped on Epxa10db"	depends on MTD_CFI && MTD_PARTITIONS && ARCH_CAMELOT	help	  This enables support for the flash devices on the Altera	  Excalibur XA10 Development Board. If you are building a kernel	  for on of these boards then you should say 'Y' otherwise say 'N'.config MTD_FORTUNET	tristate "CFI Flash device mapped on the FortuNet board"	depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET	help	  This enables access to the Flash on the FortuNet board.  If you	  have such a board, say 'Y'.config MTD_AUTCPU12	tristate "NV-RAM mapping AUTCPU12 board"	depends on ARCH_AUTCPU12	help	  This enables access to the NV-RAM on autronix autcpu12 board.	  If you have such a board, say 'Y'.config MTD_EDB7312	tristate "CFI Flash device mapped on EDB7312"	depends on ARCH_EDB7312 && MTD_CFI	help	  This enables access to the CFI Flash on the Cogent EDB7312 board.	  If you have such a board, say 'Y' here.config MTD_IMPA7	tristate "JEDEC Flash device mapped on impA7"	depends on ARM && MTD_JEDECPROBE	help	  This enables access to the NOR Flash on the impA7 board of	  implementa GmbH. If you have such a board, say 'Y' here.config MTD_CEIVA	tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"	depends on MTD_JEDECPROBE && ARCH_CEIVA	help	  This enables access to the flash chips on the Ceiva/Polaroid	  PhotoMax Digital Picture Frame.	  If you have such a device, say 'Y'.config MTD_NOR_TOTO	tristate "NOR Flash device on TOTO board"	depends on ARCH_OMAP && OMAP_TOTO	help	  This enables access to the NOR flash on the Texas Instruments	  TOTO board.config MTD_H720X	tristate "Hynix evaluation board mappings"	depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )	help	  This enables access to the flash chips on the Hynix evaluation boards.	  If you have such a board, say 'Y'.config MTD_MPC1211	tristate "CFI Flash device mapped on Interface MPC-1211"	depends on SH_MPC1211 && MTD_CFI	help	  This enables access to the flash chips on the Interface MPC-1211(CTP/PCI/MPC-SH02).	  If you have such a board, say 'Y'.config MTD_OMAP_NOR	tristate "TI OMAP board mappings"	depends on MTD_CFI && ARCH_OMAP	help	  This enables access to the NOR flash chips on TI OMAP-based	  boards defining flash platform devices and flash platform data.	  These boards include the Innovator, H2, H3, OSK, Perseus2, and	  more.  If you have such a board, say 'Y'.# This needs CFI or JEDEC, depending on the cards found.config MTD_PCI	tristate "PCI MTD driver"	depends on MTD && PCI && MTD_COMPLEX_MAPPINGS	help	  Mapping for accessing flash devices on add-in cards like the Intel XScale	  IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode	  (please see the manual for the link settings).	  If you are not sure, say N.config MTD_PCMCIA	tristate "PCMCIA MTD driver"	depends on MTD && PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN	help	  Map driver for accessing PCMCIA linear flash memory cards. These	  cards are usually around 4-16MiB in size. This does not include	  Compact Flash cards which are treated as IDE devices.config MTD_PCMCIA_ANONYMOUS	bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"	depends on MTD_PCMCIA	default N	help	  If this option is enabled, PCMCIA cards which do not report	  anything about themselves are assumed to be MTD cards.	  If unsure, say N.config MTD_UCLINUX	tristate "Generic uClinux RAM/ROM filesystem support"	depends on MTD_PARTITIONS && !MMU	help	  Map driver to support image based filesystems for uClinux.config MTD_WRSBC8260	tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"	depends on (SBC82xx || SBC8560)	select MTD_PARTITIONS	select MTD_MAP_BANK_WIDTH_4	select MTD_MAP_BANK_WIDTH_1	select MTD_CFI_I1	select MTD_CFI_I4	help	  Map driver for WindRiver PowerQUICC II MPC82xx board. Drives	  all three flash regions on CS0, CS1 and CS6 if they are configured	  correctly by the boot loader.config MTD_DMV182        tristate "Map driver for Dy-4 SVME/DMV-182 board."        depends on DMV182        select MTD_PARTITIONS	select MTD_MAP_BANK_WIDTH_32	select MTD_CFI_I8	select MTD_CFI_AMDSTD        help          Map driver for Dy-4 SVME/DMV-182 board.config MTD_BAST	tristate "Map driver for Simtec BAST (EB2410ITX) or Thorcom VR1000"	depends on ARCH_BAST || MACH_VR1000	select MTD_PARTITIONS	select MTD_MAP_BANK_WIDTH_16	select MTD_JEDECPROBE	help	  Map driver for NOR flash on the Simtec BAST (EB2410ITX), or the	  Thorcom VR1000	  Note, this driver *cannot* over-ride the WP link on the	  board, or currently detect the state of the link.config MTD_BAST_MAXSIZE	int "Maximum size for BAST flash area (MiB)"	depends on MTD_BAST	default "4"config MTD_SHARP_SL	bool "ROM maped on Sharp SL Series"	depends on MTD && ARCH_PXA	help	  This enables access to the flash chip on the Sharp SL Series of PDAs.config MTD_PLATRAM	tristate "Map driver for platform device RAM (mtd-ram)"	depends on MTD	select MTD_RAM	help	  Map driver for RAM areas described via the platform device	  system.	  This selection automatically selects the map_ram driver.endmenu