[deliverable/linux.git] / drivers / mtd / maps / Kconfig

menu "Mapping drivers for chip access"
	depends on MTD!=n
	depends on HAS_IOMEM

config 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 "Flash device in physical memory map"
	depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR
	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_COMPAT
	bool "Physmap compat support"
	depends on MTD_PHYSMAP
	default n
	help
	  Setup a simple mapping via the Kconfig options.  Normally the
	  physmap configuration options are done via your board's
	  resource file.

	  If unsure, say N here.

config MTD_PHYSMAP_START
	hex "Physical start address of flash mapping"
	depends on MTD_PHYSMAP_COMPAT
	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_COMPAT
	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.

config MTD_PHYSMAP_BANKWIDTH
	int "Bank width in octets"
	depends on MTD_PHYSMAP_COMPAT
	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.

config MTD_PHYSMAP_OF
	tristate "Memory device in physical memory map based on OF description"
	depends on OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM)
	help
	  This provides a 'mapping' driver which allows the NOR Flash, ROM
	  and RAM 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_PHYSMAP_OF_VERSATILE
	bool "Support ARM Versatile physmap OF"
	depends on MTD_PHYSMAP_OF
	depends on MFD_SYSCON
	default y if (ARCH_INTEGRATOR || ARCH_VERSATILE || REALVIEW_DT)
	help
	  This provides some extra DT physmap parsing for the ARM Versatile
	  platforms, basically to add a VPP (write protection) callback so
	  the flash can be taken out of write protection.

config MTD_PMC_MSP_EVM
	tristate "CFI Flash device mapped on PMC-Sierra MSP"
	depends on PMC_MSP && MTD_CFI
	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_32M

config MSP_FLASH_MAP_LIMIT_32M
	bool "32M"

endchoice

config MSP_FLASH_MAP_LIMIT
	hex
	default "0x02000000"
	depends on MSP_FLASH_MAP_LIMIT_32M

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 (MELAN || COMPILE_TEST) && 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 (MELAN || COMPILE_TEST) && MTD_CFI
	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 TS5500 || COMPILE_TEST
	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_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
	help
	  This provides a driver for the NOR flash attached to a PXA2xx chip.

config MTD_SCx200_DOCFLASH
	tristate "Flash device mapped with DOCCS on NatSemi SCx200"
	depends on SCx200 && 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.

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 && PCI
	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_JEDECPROBE
	help
	  Support for flash chips on NETtel/SecureEdge/SnapGear boards.

config MTD_LANTIQ
	tristate "Lantiq SoC NOR support"
	depends on LANTIQ
	help
	  Support for NOR flash attached to the Lantiq SoC's External Bus Unit.

config MTD_L440GX
	tristate "BIOS flash chip on Intel L440GX boards"
	depends on X86 && MTD_JEDECPROBE
	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_CFI_FLAGADM
	tristate "CFI Flash device mapping on FlagaDM"
	depends on PPC_8xx && MTD_CFI
	help
	  Mapping for the Flaga digital module. If you don't have one, ignore
	  this setting.

config MTD_SOLUTIONENGINE
	tristate "CFI Flash device mapped on Hitachi SolutionEngine"
	depends on SOLUTION_ENGINE && 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_SA1100
	tristate "CFI Flash device mapped on StrongARM SA11x0"
	depends on MTD_CFI && ARCH_SA1100
	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 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_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_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.

# This needs CFI or JEDEC, depending on the cards found.
config MTD_PCI
	tristate "PCI MTD driver"
	depends on 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 PCMCIA && MTD_COMPLEX_MAPPINGS
	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
	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_BFIN_ASYNC
	tristate "Blackfin BF533-STAMP Flash Chip Support"
	depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS
	default y
	help
	  Map driver which allows for simultaneous utilization of
	  ethernet and CFI parallel flash.

	  If compiled as a module, it will be called bfin-async-flash.

config MTD_GPIO_ADDR
	tristate "GPIO-assisted Flash Chip Support"
	depends on GPIOLIB || COMPILE_TEST
	depends on MTD_COMPLEX_MAPPINGS
	help
	  Map driver which allows flashes to be partially physically addressed
	  and assisted by GPIOs.

	  If compiled as a module, it will be called gpio-addr-flash.

config MTD_UCLINUX
	bool "Generic uClinux RAM/ROM filesystem support"
	depends on (MTD_RAM=y || MTD_ROM=y) && (!MMU || COLDFIRE)
	help
	  Map driver to support image based filesystems for uClinux.

config MTD_INTEL_VR_NOR
	tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
	depends on PCI
	help
	  Map driver for a NOR flash bank located on the Expansion Bus of the
	  Intel Vermilion Range chipset.

config MTD_RBTX4939
	tristate "Map driver for RBTX4939 board"
	depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS
	help
	  Map driver for NOR flash chips on RBTX4939 board.

config MTD_PLATRAM
	tristate "Map driver for platform device RAM (mtd-ram)"
	select MTD_RAM
	help
	  Map driver for RAM areas described via the platform device
	  system.

	  This selection automatically selects the map_ram driver.

config MTD_VMU
	tristate "Map driver for Dreamcast VMU"
	depends on MAPLE
	help
	  This driver enables access to the Dreamcast Visual Memory Unit (VMU).

	  Most Dreamcast users will want to say Y here.

	  To build this as a module select M here, the module will be called
	  vmu-flash.

config MTD_PISMO
	tristate "MTD discovery driver for PISMO modules"
	depends on I2C
	depends on ARCH_VERSATILE
	help
	  This driver allows for discovery of PISMO modules - see
	  <http://www.pismoworld.org/>.  These are small modules containing
	  up to five memory devices (eg, SRAM, flash, DOC) described by an
	  I2C EEPROM.

	  This driver does not create any MTD maps itself; instead it
	  creates MTD physmap and MTD SRAM platform devices.  If you
	  enable this option, you should consider enabling MTD_PHYSMAP
	  and/or MTD_PLATRAM according to the devices on your module.

	  When built as a module, it will be called pismo.ko

config MTD_LATCH_ADDR
        tristate "Latch-assisted Flash Chip Support"
        depends on MTD_COMPLEX_MAPPINGS
        help
          Map driver which allows flashes to be partially physically addressed
          and have the upper address lines set by a board specific code.

          If compiled as a module, it will be called latch-addr-flash.

endmenu
Commit	Line	Data
1da177e4 LT	1	menu "Mapping drivers for chip access"
1da177e4 LT	2	depends on MTD!=n
9310da0b	3	depends on HAS_IOMEM
1da177e4 LT	4
	5	config MTD_COMPLEX_MAPPINGS
	6	bool "Support non-linear mappings of flash chips"
1da177e4 LT	7	help
	8	This causes the chip drivers to allow for complicated
	9	paged mappings of flash chips.
	10
	11	config MTD_PHYSMAP
d8140830 AK	12	tristate "Flash device in physical memory map"
d8140830 AK	13	depends on MTD_CFI \|\| MTD_JEDECPROBE \|\| MTD_ROM \|\| MTD_LPDDR
1da177e4	14	help
79b9cd58 TY	15	This provides a 'mapping' driver which allows the NOR Flash and
	16	ROM driver code to communicate with chips which are mapped
	17	physically into the CPU's memory. You will need to configure
	18	the physical address and size of the flash chips on your
	19	particular board as well as the bus width, either statically
1da177e4 LT	20	with config options or at run-time.
1da177e4 LT	21
41bdf960 MF	22	To compile this driver as a module, choose M here: the
	23	module will be called physmap.
	24
dcb3e137 MF	25	config MTD_PHYSMAP_COMPAT
	26	bool "Physmap compat support"
	27	depends on MTD_PHYSMAP
	28	default n
	29	help
	30	Setup a simple mapping via the Kconfig options. Normally the
	31	physmap configuration options are done via your board's
	32	resource file.
	33
	34	If unsure, say N here.
	35
1da177e4 LT	36	config MTD_PHYSMAP_START
1da177e4 LT	37	hex "Physical start address of flash mapping"
dcb3e137	38	depends on MTD_PHYSMAP_COMPAT
1da177e4 LT	39	default "0x8000000"
	40	help
	41	This is the physical memory location at which the flash chips
	42	are mapped on your particular target board. Refer to the
	43	memory map which should hopefully be in the documentation for
	44	your board.
1da177e4 LT	45
	46	config MTD_PHYSMAP_LEN
	47	hex "Physical length of flash mapping"
dcb3e137	48	depends on MTD_PHYSMAP_COMPAT
73566edf	49	default "0"
1da177e4 LT	50	help
	51	This is the total length of the mapping of the flash chips on
	52	your particular board. If there is space, or aliases, in the
	53	physical memory map between the chips, this could be larger
	54	than the total amount of flash present. Refer to the memory
	55	map which should hopefully be in the documentation for your
	56	board.
1da177e4 LT	57
	58	config MTD_PHYSMAP_BANKWIDTH
	59	int "Bank width in octets"
dcb3e137	60	depends on MTD_PHYSMAP_COMPAT
1da177e4 LT	61	default "2"
	62	help
	63	This is the total width of the data bus of the flash devices
	64	in octets. For example, if you have a data bus width of 32
01dd2fbf	65	bits, you would set the bus width octet value to 4. This is
1da177e4	66	used internally by the CFI drivers.
1da177e4	67
a2c2fe4b	68	config MTD_PHYSMAP_OF
670b46aa PDM	69	tristate "Memory device in physical memory map based on OF description"
670b46aa PDM	70	depends on OF && (MTD_CFI \|\| MTD_JEDECPROBE \|\| MTD_ROM \|\| MTD_RAM)
a2c2fe4b	71	help
670b46aa PDM	72	This provides a 'mapping' driver which allows the NOR Flash, ROM
670b46aa PDM	73	and RAM driver code to communicate with chips which are mapped
a2c2fe4b VW	74	physically into the CPU's memory. The mapping description here is
	75	taken from OF device tree.
	76
b0afd44b LW	77	config MTD_PHYSMAP_OF_VERSATILE
	78	bool "Support ARM Versatile physmap OF"
	79	depends on MTD_PHYSMAP_OF
	80	depends on MFD_SYSCON
	81	default y if (ARCH_INTEGRATOR \|\| ARCH_VERSATILE \|\| REALVIEW_DT)
	82	help
	83	This provides some extra DT physmap parsing for the ARM Versatile
	84	platforms, basically to add a VPP (write protection) callback so
	85	the flash can be taken out of write protection.
	86
68aa0fa8 MSJ	87	config MTD_PMC_MSP_EVM
	88	tristate "CFI Flash device mapped on PMC-Sierra MSP"
	89	depends on PMC_MSP && MTD_CFI
68aa0fa8	90	help
01dd2fbf ML	91	This provides a 'mapping' driver which supports the way
	92	in which user-programmable flash chips are connected on the
	93	PMC-Sierra MSP eval/demo boards.
68aa0fa8 MSJ	94
68aa0fa8 MSJ	95	choice
01dd2fbf	96	prompt "Maximum mappable memory available for flash IO"
68aa0fa8 MSJ	97	depends on MTD_PMC_MSP_EVM
	98	default MSP_FLASH_MAP_LIMIT_32M
	99
	100	config MSP_FLASH_MAP_LIMIT_32M
	101	bool "32M"
	102
	103	endchoice
	104
	105	config MSP_FLASH_MAP_LIMIT
	106	hex
	107	default "0x02000000"
	108	depends on MSP_FLASH_MAP_LIMIT_32M
	109
1da177e4 LT	110	config MTD_SUN_UFLASH
1da177e4 LT	111	tristate "Sun Microsystems userflash support"
e0e5de00	112	depends on SPARC && MTD_CFI && PCI
1da177e4	113	help
69f34c98 TG	114	This provides a 'mapping' driver which supports the way in
	115	which user-programmable flash chips are connected on various
	116	Sun Microsystems boardsets. This driver will require CFI support
1da177e4 LT	117	in the kernel, so if you did not enable CFI previously, do that now.
1da177e4 LT	118
1da177e4 LT	119	config MTD_SC520CDP
1da177e4 LT	120	tristate "CFI Flash device mapped on AMD SC520 CDP"
3579ad41	121	depends on (MELAN \|\| COMPILE_TEST) && MTD_CFI
1da177e4 LT	122	help
	123	The SC520 CDP board has two banks of CFI-compliant chips and one
	124	Dual-in-line JEDEC chip. This 'mapping' driver supports that
	125	arrangement, implementing three MTD devices.
	126
	127	config MTD_NETSC520
	128	tristate "CFI Flash device mapped on AMD NetSc520"
3579ad41	129	depends on (MELAN \|\| COMPILE_TEST) && MTD_CFI
1da177e4 LT	130	help
1da177e4 LT	131	This enables access routines for the flash chips on the AMD NetSc520
69f34c98	132	demonstration board. If you have one of these boards and would like
1da177e4 LT	133	to use the flash chips on it, say 'Y'.
	134
	135	config MTD_TS5500
	136	tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
f4f6a0be	137	depends on TS5500 \|\| COMPILE_TEST
01ac742d SY	138	select MTD_JEDECPROBE
01ac742d SY	139	select MTD_CFI_AMDSTD
1da177e4 LT	140	help
1da177e4 LT	141	This provides a driver for the on-board flash of the Technologic
e27a9960	142	System's TS-5500 board. The 2MB flash is split into 3 partitions
1da177e4 LT	143	which are accessed as separate MTD devices.
1da177e4 LT	144
e27a9960 SY	145	mtd0 and mtd2 are the two BIOS drives, which use the resident
e27a9960 SY	146	flash disk (RFD) flash translation layer.
1da177e4 LT	147
	148	mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
	149
	150	Note that jumper 3 ("Write Enable Drive A") must be set
4992a9e8	151	otherwise detection won't succeed.
1da177e4 LT	152
	153	config MTD_SBC_GXX
	154	tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
6a8a98b2	155	depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS
1da177e4 LT	156	help
	157	This provides a driver for the on-board flash of Arcom Control
	158	Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
	159	By default the flash is split into 3 partitions which are accessed
	160	as separate MTD devices. This board utilizes Intel StrataFlash.
	161	More info at
	162	<http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
	163
e644f7d6 TP	164	config MTD_PXA2XX
	165	tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
	166	depends on (PXA25x \|\| PXA27x) && MTD_CFI_INTELEXT
cbec19ae	167	help
e644f7d6	168	This provides a driver for the NOR flash attached to a PXA2xx chip.
cbec19ae	169
1da177e4 LT	170	config MTD_SCx200_DOCFLASH
1da177e4 LT	171	tristate "Flash device mapped with DOCCS on NatSemi SCx200"
f6c11c18	172	depends on SCx200 && MTD_CFI
1da177e4 LT	173	help
	174	Enable support for a flash chip mapped using the DOCCS signal on a
	175	National Semiconductor SCx200 processor.
	176
	177	If you don't know what to do here, say N.
	178
	179	If compiled as a module, it will be called scx200_docflash.
	180
	181	config MTD_AMD76XROM
	182	tristate "BIOS flash chip on AMD76x southbridge"
	183	depends on X86 && MTD_JEDECPROBE
	184	help
	185	Support for treating the BIOS flash chip on AMD76x motherboards
	186	as an MTD device - with this you can reprogram your BIOS.
	187
	188	BE VERY CAREFUL.
	189
	190	config MTD_ICHXROM
	191	tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
	192	depends on X86 && MTD_JEDECPROBE
	193	help
	194	Support for treating the BIOS flash chip on ICHX motherboards
	195	as an MTD device - with this you can reprogram your BIOS.
	196
	197	BE VERY CAREFUL.
	198
29175778 LG	199	config MTD_ESB2ROM
29175778 LG	200	tristate "BIOS flash chip on Intel ESB Controller Hub 2"
dffbc42b	201	depends on X86 && MTD_JEDECPROBE && PCI
29175778 LG	202	help
	203	Support for treating the BIOS flash chip on ESB2 motherboards
	204	as an MTD device - with this you can reprogram your BIOS.
	205
	206	BE VERY CAREFUL.
	207
90afffc8 DO	208	config MTD_CK804XROM
90afffc8 DO	209	tristate "BIOS flash chip on Nvidia CK804"
862c93b9	210	depends on X86 && MTD_JEDECPROBE && PCI
90afffc8 DO	211	help
	212	Support for treating the BIOS flash chip on nvidia motherboards
	213	as an MTD device - with this you can reprogram your BIOS.
	214
	215	BE VERY CAREFUL.
	216
1da177e4 LT	217	config MTD_SCB2_FLASH
1da177e4 LT	218	tristate "BIOS flash chip on Intel SCB2 boards"
47d0505b	219	depends on X86 && MTD_JEDECPROBE && PCI
1da177e4 LT	220	help
	221	Support for treating the BIOS flash chip on Intel SCB2 boards
	222	as an MTD device - with this you can reprogram your BIOS.
	223
	224	BE VERY CAREFUL.
	225
	226	config MTD_TSUNAMI
	227	tristate "Flash chips on Tsunami TIG bus"
	228	depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
	229	help
	230	Support for the flash chip on Tsunami TIG bus.
	231
1da177e4 LT	232	config MTD_NETtel
1da177e4 LT	233	tristate "CFI flash device on SnapGear/SecureEdge"
6a8a98b2	234	depends on X86 && MTD_JEDECPROBE
1da177e4 LT	235	help
	236	Support for flash chips on NETtel/SecureEdge/SnapGear boards.
	237
3c544739 JC	238	config MTD_LANTIQ
	239	tristate "Lantiq SoC NOR support"
	240	depends on LANTIQ
3c544739 JC	241	help
	242	Support for NOR flash attached to the Lantiq SoC's External Bus Unit.
	243
1da177e4 LT	244	config MTD_L440GX
	245	tristate "BIOS flash chip on Intel L440GX boards"
	246	depends on X86 && MTD_JEDECPROBE
	247	help
	248	Support for treating the BIOS flash chip on Intel L440GX motherboards
	249	as an MTD device - with this you can reprogram your BIOS.
	250
	251	BE VERY CAREFUL.
	252
1da177e4 LT	253	config MTD_CFI_FLAGADM
1da177e4 LT	254	tristate "CFI Flash device mapping on FlagaDM"
318157ab	255	depends on PPC_8xx && MTD_CFI
1da177e4 LT	256	help
	257	Mapping for the Flaga digital module. If you don't have one, ignore
	258	this setting.
	259
1da177e4 LT	260	config MTD_SOLUTIONENGINE
1da177e4 LT	261	tristate "CFI Flash device mapped on Hitachi SolutionEngine"
7a6f4395	262	depends on SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
1da177e4 LT	263	help
	264	This enables access to the flash chips on the Hitachi SolutionEngine and
	265	similar boards. Say 'Y' if you are building a kernel for such a board.
	266
1da177e4 LT	267	config MTD_SA1100
1da177e4 LT	268	tristate "CFI Flash device mapped on StrongARM SA11x0"
2fe2e24e	269	depends on MTD_CFI && ARCH_SA1100
1da177e4 LT	270	help
	271	This enables access to the flash chips on most platforms based on
	272	the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
	273	If you have such a board, say 'Y'.
	274
1da177e4 LT	275	config MTD_DC21285
1da177e4 LT	276	tristate "CFI Flash device mapped on DC21285 Footbridge"
01ac742d	277	depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
1da177e4 LT	278	help
	279	This provides a driver for the flash accessed using Intel's
	280	21285 bridge used with Intel's StrongARM processors. More info at
	281	<http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
	282
1da177e4 LT	283	config MTD_IXP4XX
1da177e4 LT	284	tristate "CFI Flash device mapped on Intel IXP4xx based systems"
01ac742d	285	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
1da177e4	286	help
69f34c98	287	This enables MTD access to flash devices on platforms based
1da177e4 LT	288	on Intel's IXP4xx family of network processors such as the
	289	IXDP425 and Coyote. If you have an IXP4xx based board and
	290	would like to use the flash chips on it, say 'Y'.
	291
1da177e4 LT	292	config MTD_IMPA7
	293	tristate "JEDEC Flash device mapped on impA7"
	294	depends on ARM && MTD_JEDECPROBE
	295	help
	296	This enables access to the NOR Flash on the impA7 board of
	297	implementa GmbH. If you have such a board, say 'Y' here.
	298
1da177e4 LT	299	# This needs CFI or JEDEC, depending on the cards found.
	300	config MTD_PCI
	301	tristate "PCI MTD driver"
ec98c681	302	depends on PCI && MTD_COMPLEX_MAPPINGS
1da177e4 LT	303	help
	304	Mapping for accessing flash devices on add-in cards like the Intel XScale
	305	IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
	306	(please see the manual for the link settings).
	307
	308	If you are not sure, say N.
	309
	310	config MTD_PCMCIA
	311	tristate "PCMCIA MTD driver"
f6763c98	312	depends on PCMCIA && MTD_COMPLEX_MAPPINGS
1da177e4 LT	313	help
	314	Map driver for accessing PCMCIA linear flash memory cards. These
	315	cards are usually around 4-16MiB in size. This does not include
	316	Compact Flash cards which are treated as IDE devices.
	317
11d28a30 DB	318	config MTD_PCMCIA_ANONYMOUS
	319	bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
	320	depends on MTD_PCMCIA
11d28a30 DB	321	help
	322	If this option is enabled, PCMCIA cards which do not report
	323	anything about themselves are assumed to be MTD cards.
	324
	325	If unsure, say N.
	326
2e3c22f5 MF	327	config MTD_BFIN_ASYNC
2e3c22f5 MF	328	tristate "Blackfin BF533-STAMP Flash Chip Support"
ab00d682	329	depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS
2e3c22f5 MF	330	default y
	331	help
	332	Map driver which allows for simultaneous utilization of
	333	ethernet and CFI parallel flash.
	334
	335	If compiled as a module, it will be called bfin-async-flash.
	336
d79c326c MF	337	config MTD_GPIO_ADDR
d79c326c MF	338	tristate "GPIO-assisted Flash Chip Support"
f650ce24	339	depends on GPIOLIB \|\| COMPILE_TEST
d79c326c	340	depends on MTD_COMPLEX_MAPPINGS
d79c326c MF	341	help
	342	Map driver which allows flashes to be partially physically addressed
	343	and assisted by GPIOs.
	344
	345	If compiled as a module, it will be called gpio-addr-flash.
	346
1da177e4	347	config MTD_UCLINUX
6ae392cc	348	bool "Generic uClinux RAM/ROM filesystem support"
81f53ff8	349	depends on (MTD_RAM=y \|\| MTD_ROM=y) && (!MMU \|\| COLDFIRE)
1da177e4 LT	350	help
	351	Map driver to support image based filesystems for uClinux.
	352
0bac5111 DW	353	config MTD_INTEL_VR_NOR
	354	tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
	355	depends on PCI
	356	help
	357	Map driver for a NOR flash bank located on the Expansion Bus of the
	358	Intel Vermilion Range chipset.
	359
610f75e7 AN	360	config MTD_RBTX4939
	361	tristate "Map driver for RBTX4939 board"
	362	depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS
	363	help
	364	Map driver for NOR flash chips on RBTX4939 board.
	365
99f2a8ae	366	config MTD_PLATRAM
3c45e00a	367	tristate "Map driver for platform device RAM (mtd-ram)"
99f2a8ae BD	368	select MTD_RAM
	369	help
	370	Map driver for RAM areas described via the platform device
	371	system.
	372
	373	This selection automatically selects the map_ram driver.
	374
47a72688 AM	375	config MTD_VMU
	376	tristate "Map driver for Dreamcast VMU"
	377	depends on MAPLE
	378	help
	379	This driver enables access to the Dreamcast Visual Memory Unit (VMU).
	380
	381	Most Dreamcast users will want to say Y here.
1da177e4	382
47a72688 AM	383	To build this as a module select M here, the module will be called
	384	vmu-flash.
	385
f6a8c609 RKAL	386	config MTD_PISMO
	387	tristate "MTD discovery driver for PISMO modules"
	388	depends on I2C
	389	depends on ARCH_VERSATILE
	390	help
	391	This driver allows for discovery of PISMO modules - see
	392	<http://www.pismoworld.org/>. These are small modules containing
	393	up to five memory devices (eg, SRAM, flash, DOC) described by an
	394	I2C EEPROM.
	395
	396	This driver does not create any MTD maps itself; instead it
	397	creates MTD physmap and MTD SRAM platform devices. If you
	398	enable this option, you should consider enabling MTD_PHYSMAP
	399	and/or MTD_PLATRAM according to the devices on your module.
	400
	401	When built as a module, it will be called pismo.ko
	402
dcfb81d6 DG	403	config MTD_LATCH_ADDR
	404	tristate "Latch-assisted Flash Chip Support"
	405	depends on MTD_COMPLEX_MAPPINGS
	406	help
	407	Map driver which allows flashes to be partially physically addressed
	408	and have the upper address lines set by a board specific code.
	409
	410	If compiled as a module, it will be called latch-addr-flash.
	411
47a72688	412	endmenu