# drivers/mtd/maps/Kconfig# $Id: Kconfig,v 1.6 2003/04/20 08:38:01 gleixner Exp $menu "Mapping drivers for chip access"	depends on MTD!=nconfig MTD_PHYSMAP	tristate "CFI Flash device in physical memory map"	depends on MTD_CFI	help	  This provides a 'mapping' driver which allows the CFI probe and	  command set driver code to communicate with flash chips which	  are mapped physically into the CPU's memory. You will need to	  configure the physical address and size of the flash chips on	  your particular board as well as the bus width.config MTD_PHYSMAP_START	hex "Physical start address of flash mapping"	depends on MTD_PHYSMAP	default "0x8000000"	help	  This is the physical memory location at which the flash chips	  are mapped on your particular target board. Refer to the	  memory map which should hopefully be in the documentation for	  your board.config MTD_PHYSMAP_LEN	hex "Physical length of flash mapping"	depends on MTD_PHYSMAP	default "0x4000000"	help	  This is the total length of the mapping of the flash chips on	  your particular board. If there is space, or aliases, in the	  physical memory map between the chips, this could be larger	  than the total amount of flash present. Refer to the memory	  map which should hopefully be in the documentation for your	  board.config MTD_PHYSMAP_BUSWIDTH	int "Bus width in octets"	depends on MTD_PHYSMAP	default "2"	help	  This is the total width of the data bus of the flash devices	  in octets. For example, if you have a data bus width of 32	  bits, you would set the bus width octect value to 4. This is	  used internally by the CFI drivers.config MTD_SUN_UFLASH	tristate "Sun Microsystems userflash support"	depends on (SPARC32 || SPARC64) && MTD_CFI	help	  This provides a 'mapping' driver which supports the way in 	  which user-programmable flash chips are connected on various 	  Sun Microsystems boardsets.  This driver will require CFI support 	  in the kernel, so if you did not enable CFI previously, do that now.config MTD_PNC2000	tristate "CFI Flash device mapped on Photron PNC-2000"	depends on X86 && MTD_CFI && MTD_PARTITIONS	help	  PNC-2000 is the name of Network Camera product from PHOTRON	  Ltd. in Japan. It uses CFI-compliant flash.config MTD_SC520CDP	tristate "CFI Flash device mapped on AMD SC520 CDP"	depends on X86 && MTD_CFI	help	  The SC520 CDP board has two banks of CFI-compliant chips and one	  Dual-in-line JEDEC chip. This 'mapping' driver supports that	  arrangement, implementing three MTD devices.config MTD_NETSC520	tristate "CFI Flash device mapped on AMD NetSc520"	depends on X86 && MTD_CFI && MTD_PARTITIONS	help	  This enables access routines for the flash chips on the AMD NetSc520	  demonstration board. If you have one of these boards and would like 	  to use the flash chips on it, say 'Y'.config MTD_SBC_GXX	tristate "CFI Flash device mapped on Arcom SBC-GXx boards"	depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS	help	  This provides a driver for the on-board flash of Arcom Control	  Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.	  By default the flash is split into 3 partitions which are accessed	  as separate MTD devices. This board utilizes Intel StrataFlash.	  More info at	  <http://www.arcomcontrols.com/products/icp/pc104/processors/>.config MTD_ELAN_104NC	tristate "CFI Flash device mapped on Arcom ELAN-104NC"	depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS	help	  This provides a driver for the on-board flash of the Arcom Control	  System's ELAN-104NC development board. By default the flash	  is split into 3 partitions which are accessed as separate MTD	  devices. This board utilizes Intel StrataFlash. More info at	  <http://www.arcomcontrols.com/products/icp/pc104/processors/>.config MTD_LUBBOCK	tristate "CFI Flash device mapped on Intel Lubbock XScale eval board"	depends on ARCH_LUBBOCK && MTD_CFI_INTELEXT && MTD_PARTITIONS	help	  This provides a driver for the on-board flash of the Intel	  'Lubbock' XScale evaluation board.config MTD_MIXMEM	tristate "JEDEC Flash device mapped on Mixcom piggyback card"	depends on X86 && MTD_JEDEC	help	  This supports the paging arrangement for access to flash chips	  on the MixCOM piggyback card, allowing the flash chip drivers	  to get on with their job of driving the flash chips without	  having to know about the paging. If you have one of these boards,	  you probably want to enable this mapping driver. More info is at	  <http://www.itc.hu/>.config MTD_OCTAGON	tristate "JEDEC Flash device mapped on Octagon 5066 SBC"	depends on X86 && MTD_JEDEC	help	  This provides a 'mapping' driver which supports the way in which	  the flash chips are connected in the Octagon-5066 Single Board	  Computer. More information on the board is available at	  <http://www.octagonsystems.com/Products/5066/5066.html>.config MTD_VMAX	tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"	depends on X86 && MTD_JEDEC	help	  This provides a 'mapping' driver which supports the way in which	  the flash chips are connected in the Tempustech VMAX SBC301 Single	  Board Computer. More information on the board is available at	  <http://www.tempustech.com/tt301.htm>.config MTD_SCx200_DOCFLASH	tristate "Flash device mapped with DOCCS on NatSemi SCx200"	depends on X86 && MTD_CFI	help	  Enable support for a flash chip mapped using the DOCCS signal on a	  National Semiconductor SCx200 processor.	  If you don't know what to do here, say N.	  If compiled as a module, it will be called scx200_docflash.o.config MTD_L440GX	tristate "BIOS flash chip on Intel L440GX boards"	depends on X86 && MTD_JEDEC	help	  Support for treating the BIOS flash chip on Intel L440GX motherboards	  as an MTD device - with this you can reprogram your BIOS.	  BE VERY CAREFUL.config MTD_TQM8XXL	tristate "CFI Flash device mapped on TQM8XXL"	depends on MTD_CFI && PPC32 && 8xx && TQM8xxL	help	  The TQM8xxL PowerPC board has up to two banks of CFI-compliant	  chips, currently uses AMD one. This 'mapping' driver supports	  that arrangement, allowing the CFI probe and command set driver	  code to communicate with the chips on the TQM8xxL board. More at	  <http://www.denx.de/embedded-ppc-en.html>.config MTD_RPXLITE	tristate "CFI Flash device mapped on RPX Lite or CLLF"	depends on MTD_CFI && PPC32 && 8xx && (RPXCLASSIC || RPXLITE)	help	  The RPXLite PowerPC board has CFI-compliant chips mapped in	  a strange sparse mapping. This 'mapping' driver supports that	  arrangement, allowing the CFI probe and command set driver code	  to communicate with the chips on the RPXLite board. More at	  <http://www.embeddedplanet.com/rpx_lite_specification_sheet.htm>.config MTD_MBX860	tristate "System flash on MBX860 board"	depends on MTD_CFI && PPC32 && 8xx && MBX860	help	  This enables access routines for the flash chips on the Motorola	  MBX860 board. If you have one of these boards and would like	  to use the flash chips on it, say 'Y'.config MTD_DBOX2	tristate "CFI Flash device mapped on D-Box2"	depends on PPC32 && 8xx && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD	help	  This enables access routines for the flash chips on the Nokia/Sagem	  D-Box 2 board. If you have one of these boards and would like to use	  the flash chips on it, say 'Y'.config MTD_CFI_FLAGADM	tristate "CFI Flash device mapping on FlagaDM"	depends on PPC32 && 8xx && MTD_CFI	help	  Mapping for the Flaga digital module. If you don磘 have one, ignore	  this setting.config MTD_BEECH	tristate "CFI Flash device mapped on IBM 405LP Beech"	depends on MTD_CFI && PPC32 && 40x && BEECH	help	  This enables access routines for the flash chips on the IBM	  405LP Beech board. If you have one of these boards and would like	  to use the flash chips on it, say 'Y'.config MTD_ARCTIC	tristate "CFI Flash device mapped on IBM 405LP Arctic"	depends on MTD_CFI && PPC32 && 40x && ARCTIC2	help	  This enables access routines for the flash chips on the IBM 405LP	  Arctic board. If you have one of these boards and would like to	  use the flash chips on it, say 'Y'.config MTD_EBONY	tristate "CFI Flash device mapped on IBM 440GP Ebony"	depends on MTD_CFI && PPC32 && 440 && 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_CSTM_MIPS_IXX	tristate "Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board"	depends on MIPS && MTD_CFI && MTD_JEDEC && MTD_PARTITIONS	help	  This provides a mapping driver for the Integrated Tecnology	  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_NORA	tristate "CFI Flash device mapped on Nora"	depends on ARM && MTD_CFI	help	  If you had to ask, you don't have one. Say 'N'.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 ARM && 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 ARM && 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_DC21285	tristate "CFI Flash device mapped on DC21285 Footbridge"	depends on ARM && MTD_CFI && ARCH_FOOTBRIDGE	help	  This provides a driver for the flash accessed using Intel's	  21285 bridge used with Intel's StrongARM processors. More info at	  <http://developer.intel.com/design/bridge/quicklist/dsc-21285.htm>.config MTD_IQ80310	tristate "CFI Flash device mapped on the XScale IQ80310 board"	depends on ARM && 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_EPXA10DB	tristate "CFI Flash device mapped on Epxa10db"	depends on ARM && 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 ARM && 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 ARM && 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 ARM && 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 ARM && 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_H720X	tristate "Hynix evaluation board mappings"	depends on ARM && 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'.# This needs CFI or JEDEC, depending on the cards found.config MTD_PCI	tristate "PCI MTD driver"	depends on MTD && PCI	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	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_UCLINUX	tristate "Generic uClinux RAM/ROM filesystem support"	depends on MTD_PARTITIONS	help	  Map driver to support image based filesystems for uClinux.endmenu