# drivers/mtd/maps/Kconfigmenu "Mapping drivers for chip access"	depends on MTD!=nconfig MTD_COMPLEX_MAPPINGS	bool "Support non-linear mappings of flash chips"	help	  This causes the chip drivers to allow for complicated	  paged mappings of flash chips.config MTD_PHYSMAP	tristate "CFI Flash device in physical memory map"	depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM	help	  This provides a 'mapping' driver which allows the NOR Flash and	  ROM driver code to communicate with 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, either statically	  with config options or at run-time.	  To compile this driver as a module, choose M here: the	  module will be called physmap.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.	  Ignore this option if you use run-time physmap configuration	  (i.e., run-time calling physmap_configure()).config MTD_PHYSMAP_LEN	hex "Physical length of flash mapping"	depends on MTD_PHYSMAP	default "0"	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.	  Ignore this option if you use run-time physmap configuration	  (i.e., run-time calling physmap_configure()).config MTD_PHYSMAP_BANKWIDTH	int "Bank 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 octet value to 4. This is	  used internally by the CFI drivers.	  Ignore this option if you use run-time physmap configuration	  (i.e., run-time calling physmap_configure()).config MTD_PHYSMAP_OF	tristate "Flash device in physical memory map based on OF description"	depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)	help	  This provides a 'mapping' driver which allows the NOR Flash and	  ROM driver code to communicate with chips which are mapped	  physically into the CPU's memory. The mapping description here is	  taken from OF device tree.config MTD_PMC_MSP_EVM	tristate "CFI Flash device mapped on PMC-Sierra MSP"	depends on PMC_MSP && MTD_CFI	select MTD_PARTITIONS	help	  This provides a 'mapping' driver which supports the way	  in which user-programmable flash chips are connected on the	  PMC-Sierra MSP eval/demo boards.choice	prompt "Maximum mappable memory available for flash IO"	depends on MTD_PMC_MSP_EVM	default MSP_FLASH_MAP_LIMIT_32Mconfig MSP_FLASH_MAP_LIMIT_32M	bool "32M"endchoiceconfig MSP_FLASH_MAP_LIMIT	hex	default "0x02000000"	depends on MSP_FLASH_MAP_LIMIT_32Mconfig MTD_PMC_MSP_RAMROOT	tristate "Embedded RAM block device for root on PMC-Sierra MSP"	depends on PMC_MSP_EMBEDDED_ROOTFS && \			(MTD_BLOCK || MTD_BLOCK_RO) && \			MTD_RAM	help	  This provides support for the embedded root file system          on PMC MSP devices.  This memory is mapped as a MTD block device.config MTD_SUN_UFLASH	tristate "Sun Microsystems userflash support"	depends on SPARC && MTD_CFI && PCI	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_SC520CDP	tristate "CFI Flash device mapped on AMD SC520 CDP"	depends on X86 && MTD_CFI && MTD_CONCAT	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_TS5500	tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"	depends on X86	select MTD_PARTITIONS	select MTD_JEDECPROBE	select MTD_CFI_AMDSTD	help	  This provides a driver for the on-board flash of the Technologic	  System's TS-5500 board. The 2MB flash is split into 3 partitions	  which are accessed as separate MTD devices.	  mtd0 and mtd2 are the two BIOS drives, which use the resident	  flash disk (RFD) flash translation layer.	  mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.	  Note that jumper 3 ("Write Enable Drive A") must be set	  otherwise detection won't succeed.config MTD_SBC_GXX	tristate "CFI Flash device mapped on Arcom SBC-GXx boards"	depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS	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/SBC_GX1.htm>.config MTD_PXA2XX	tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"	depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT	select MTD_PARTITIONS	help	  This provides a driver for the NOR flash attached to a PXA2xx chip.config MTD_OCTAGON	tristate "JEDEC Flash device mapped on Octagon 5066 SBC"	depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS	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/CPUpages/5066.html>.config MTD_VMAX	tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"	depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS	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/>.config MTD_SCx200_DOCFLASH	tristate "Flash device mapped with DOCCS on NatSemi SCx200"	depends on SCx200 && MTD_CFI && MTD_PARTITIONS	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.config MTD_AMD76XROM	tristate "BIOS flash chip on AMD76x southbridge"	depends on X86 && MTD_JEDECPROBE	help	  Support for treating the BIOS flash chip on AMD76x motherboards	  as an MTD device - with this you can reprogram your BIOS.	  BE VERY CAREFUL.config MTD_ICHXROM	tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"	depends on X86 && MTD_JEDECPROBE	help	  Support for treating the BIOS flash chip on ICHX motherboards	  as an MTD device - with this you can reprogram your BIOS.	  BE VERY CAREFUL.config MTD_ESB2ROM        tristate "BIOS flash chip on Intel ESB Controller Hub 2"        depends on X86 && MTD_JEDECPROBE && PCI        help          Support for treating the BIOS flash chip on ESB2 motherboards          as an MTD device - with this you can reprogram your BIOS.          BE VERY CAREFUL.config MTD_CK804XROM	tristate "BIOS flash chip on Nvidia CK804"	depends on X86 && MTD_JEDECPROBE && PCI	help	  Support for treating the BIOS flash chip on nvidia motherboards	  as an MTD device - with this you can reprogram your BIOS.	  BE VERY CAREFUL.config MTD_SCB2_FLASH	tristate "BIOS flash chip on Intel SCB2 boards"	depends on X86 && MTD_JEDECPROBE	help	  Support for treating the BIOS flash chip on Intel SCB2 boards	  as an MTD device - with this you can reprogram your BIOS.	  BE VERY CAREFUL.config MTD_TSUNAMI	tristate "Flash chips on Tsunami TIG bus"	depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS	help	  Support for the flash chip on Tsunami TIG bus.config MTD_NETtel	tristate "CFI flash device on SnapGear/SecureEdge"	depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE	help	  Support for flash chips on NETtel/SecureEdge/SnapGear boards.config MTD_ALCHEMY	tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"	depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI	help	  Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boardsconfig MTD_DILNETPC	tristate "CFI Flash device mapped on DIL/Net PC"	depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT	help	  MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".	  For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm> 	  and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>config MTD_DILNETPC_BOOTSIZE	hex "Size of DIL/Net PC flash boot partition"	depends on MTD_DILNETPC	default "0x80000"	help	  The amount of space taken up by the kernel or Etherboot	  on the DIL/Net PC flash chips.config MTD_L440GX