[linux-2.6-block.git] / drivers / mtd / devices / Kconfig

# drivers/mtd/maps/Kconfig
# $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $

menu "Self-contained MTD device drivers"
	depends on MTD!=n

config MTD_PMC551
	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
	depends on PCI
	---help---
	  This provides a MTD device driver for the Ramix PMC551 RAM PCI card
	  from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
	  These devices come in memory configurations from 32M - 1G.  If you
	  have one, you probably want to enable this.

	  If this driver is compiled as a module you get the ability to select
	  the size of the aperture window pointing into the devices memory.
	  What this means is that if you have a 1G card, normally the kernel
	  will use a 1G memory map as its view of the device.  As a module,
	  you can select a 1M window into the memory and the driver will
	  "slide" the window around the PMC551's memory.  This was
	  particularly useful on the 2.2 kernels on PPC architectures as there
	  was limited kernel space to deal with.

config MTD_PMC551_BUGFIX
	bool "PMC551 256M DRAM Bugfix"
	depends on MTD_PMC551
	help
	  Some of Ramix's PMC551 boards with 256M configurations have invalid
	  column and row mux values.  This option will fix them, but will
	  break other memory configurations.  If unsure say N.

config MTD_PMC551_DEBUG
	bool "PMC551 Debugging"
	depends on MTD_PMC551
	help
	  This option makes the PMC551 more verbose during its operation and
	  is only really useful if you are developing on this driver or
	  suspect a possible hardware or driver bug.  If unsure say N.

config MTD_MS02NV
	tristate "DEC MS02-NV NVRAM module support"
	depends on MACH_DECSTATION
	help
	  This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
	  backed-up NVRAM module.  The module was originally meant as an NFS
	  accelerator.  Say Y here if you have a DECstation 5000/2x0 or a
	  DECsystem 5900 equipped with such a module.

	  If you want to compile this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/kbuild/modules.txt>.
	  The module will be called ms02-nv.ko.

config MTD_DATAFLASH
	tristate "Support for AT45xxx DataFlash"
	depends on SPI_MASTER && EXPERIMENTAL
	help
	  This enables access to AT45xxx DataFlash chips, using SPI.
	  Sometimes DataFlash chips are packaged inside MMC-format
	  cards; at this writing, the MMC stack won't handle those.

config MTD_DATAFLASH26
	tristate "AT91RM9200 DataFlash AT26xxx"
	depends on MTD && ARCH_AT91RM9200 && AT91_SPI
	help
	  This enables access to the DataFlash chip (AT26xxx) on an
	  AT91RM9200-based board.
	  If you have such a board and such a DataFlash, say 'Y'.

config MTD_M25P80
	tristate "Support for M25 SPI Flash"
	depends on SPI_MASTER && EXPERIMENTAL
	help
	  This enables access to ST M25P80 and similar SPI flash chips,
	  used for program and data storage.  Set up your spi devices
	  with the right board-specific platform data.

config MTD_SLRAM
	tristate "Uncached system RAM"
	help
	  If your CPU cannot cache all of the physical memory in your machine,
	  you can still use it for storage or swap by using this driver to
	  present it to the system as a Memory Technology Device.

config MTD_PHRAM
	tristate "Physical system RAM"
	help
	  This is a re-implementation of the slram driver above.

	  Use this driver to access physical memory that the kernel proper
	  doesn't have access to, memory beyond the mem=xxx limit, nvram,
	  memory on the video card, etc...

config MTD_LART
	tristate "28F160xx flash driver for LART"
	depends on SA1100_LART
	help
	  This enables the flash driver for LART. Please note that you do
	  not need any mapping/chip driver for LART. This one does it all
	  for you, so go disable all of those if you enabled some of them (:

config MTD_MTDRAM
	tristate "Test driver using RAM"
	help
	  This enables a test MTD device driver which uses vmalloc() to
	  provide storage.  You probably want to say 'N' unless you're
	  testing stuff.

config MTDRAM_TOTAL_SIZE
	int "MTDRAM device size in KiB"
	depends on MTD_MTDRAM
	default "4096"
	help
	  This allows you to configure the total size of the MTD device
	  emulated by the MTDRAM driver.  If the MTDRAM driver is built
	  as a module, it is also possible to specify this as a parameter when
	  loading the module.

config MTDRAM_ERASE_SIZE
	int "MTDRAM erase block size in KiB"
	depends on MTD_MTDRAM
	default "128"
	help
	  This allows you to configure the size of the erase blocks in the
	  device emulated by the MTDRAM driver.  If the MTDRAM driver is built
	  as a module, it is also possible to specify this as a parameter when
	  loading the module.

#If not a module (I don't want to test it as a module)
config MTDRAM_ABS_POS
	hex "SRAM Hexadecimal Absolute position or 0"
	depends on MTD_MTDRAM=y
	default "0"
	help
	  If you have system RAM accessible by the CPU but not used by Linux
	  in normal operation, you can give the physical address at which the
	  available RAM starts, and the MTDRAM driver will use it instead of
	  allocating space from Linux's available memory. Otherwise, leave
	  this set to zero. Most people will want to leave this as zero.

config MTD_BLOCK2MTD
	tristate "MTD using block device"
	depends on BLOCK
	help
	  This driver allows a block device to appear as an MTD. It would
	  generally be used in the following cases:

	  Using Compact Flash as an MTD, these usually present themselves to
	  the system as an ATA drive.
	  Testing MTD users (eg JFFS2) on large media and media that might
	  be removed during a write (using the floppy drive).

comment "Disk-On-Chip Device Drivers"

config MTD_DOC2000
	tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
	select MTD_DOCPROBE
	select MTD_NAND_IDS
	---help---
	  This provides an MTD device driver for the M-Systems DiskOnChip
	  2000 and Millennium devices.  Originally designed for the DiskOnChip
	  2000, it also now includes support for the DiskOnChip Millennium.
	  If you have problems with this driver and the DiskOnChip Millennium,
	  you may wish to try the alternative Millennium driver below. To use
	  the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
	  in the <file:drivers/mtd/devices/docprobe.c> source code.

	  If you use this device, you probably also want to enable the NFTL
	  'NAND Flash Translation Layer' option below, which is used to
	  emulate a block device by using a kind of file system on the flash
	  chips.

	  NOTE: This driver is deprecated and will probably be removed soon.
	  Please try the new DiskOnChip driver under "NAND Flash Device
	  Drivers".

config MTD_DOC2001
	tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
	select MTD_DOCPROBE
	select MTD_NAND_IDS
	---help---
	  This provides an alternative MTD device driver for the M-Systems
	  DiskOnChip Millennium devices.  Use this if you have problems with
	  the combined DiskOnChip 2000 and Millennium driver above.  To get
	  the DiskOnChip probe code to load and use this driver instead of
	  the other one, you will need to undefine DOC_SINGLE_DRIVER near
	  the beginning of <file:drivers/mtd/devices/docprobe.c>.

	  If you use this device, you probably also want to enable the NFTL
	  'NAND Flash Translation Layer' option below, which is used to
	  emulate a block device by using a kind of file system on the flash
	  chips.

	  NOTE: This driver is deprecated and will probably be removed soon.
	  Please try the new DiskOnChip driver under "NAND Flash Device
	  Drivers".

config MTD_DOC2001PLUS
	tristate "M-Systems Disk-On-Chip Millennium Plus"
	select MTD_DOCPROBE
	select MTD_NAND_IDS
	---help---
	  This provides an MTD device driver for the M-Systems DiskOnChip
	  Millennium Plus devices.

	  If you use this device, you probably also want to enable the INFTL
	  'Inverse NAND Flash Translation Layer' option below, which is used
	  to emulate a block device by using a kind of file system on the
	  flash chips.

	  NOTE: This driver will soon be replaced by the new DiskOnChip driver
	  under "NAND Flash Device Drivers" (currently that driver does not
	  support all Millennium Plus devices).

config MTD_DOCPROBE
	tristate
	select MTD_DOCECC

config MTD_DOCECC
	tristate

config MTD_DOCPROBE_ADVANCED
	bool "Advanced detection options for DiskOnChip"
	depends on MTD_DOCPROBE
	help
	  This option allows you to specify nonstandard address at which to
	  probe for a DiskOnChip, or to change the detection options.  You
	  are unlikely to need any of this unless you are using LinuxBIOS.
	  Say 'N'.

config MTD_DOCPROBE_ADDRESS
	hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
	depends on MTD_DOCPROBE
	default "0x0000" if MTD_DOCPROBE_ADVANCED
	default "0" if !MTD_DOCPROBE_ADVANCED
	---help---
	  By default, the probe for DiskOnChip devices will look for a
	  DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
	  This option allows you to specify a single address at which to probe
	  for the device, which is useful if you have other devices in that
	  range which get upset when they are probed.

	  (Note that on PowerPC, the normal probe will only check at
	  0xE4000000.)

	  Normally, you should leave this set to zero, to allow the probe at
	  the normal addresses.

config MTD_DOCPROBE_HIGH
	bool "Probe high addresses"
	depends on MTD_DOCPROBE_ADVANCED
	help
	  By default, the probe for DiskOnChip devices will look for a
	  DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
	  This option changes to make it probe between 0xFFFC8000 and
	  0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
	  useful to you.  Say 'N'.

config MTD_DOCPROBE_55AA
	bool "Probe for 0x55 0xAA BIOS Extension Signature"
	depends on MTD_DOCPROBE_ADVANCED
	help
	  Check for the 0x55 0xAA signature of a DiskOnChip, and do not
	  continue with probing if it is absent.  The signature will always be
	  present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
	  Only if you have overwritten the first block of a DiskOnChip
	  Millennium will it be absent.  Enable this option if you are using
	  LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
	  you have managed to wipe the first block.

endmenu
Commit	Line	Data
1da177e4	1	# drivers/mtd/maps/Kconfig
e5580fbe	2	# $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $
1da177e4 LT	3
	4	menu "Self-contained MTD device drivers"
	5	depends on MTD!=n
	6
	7	config MTD_PMC551
	8	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
ec98c681	9	depends on PCI
1da177e4 LT	10	---help---
	11	This provides a MTD device driver for the Ramix PMC551 RAM PCI card
	12	from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
	13	These devices come in memory configurations from 32M - 1G. If you
	14	have one, you probably want to enable this.
	15
	16	If this driver is compiled as a module you get the ability to select
	17	the size of the aperture window pointing into the devices memory.
	18	What this means is that if you have a 1G card, normally the kernel
	19	will use a 1G memory map as its view of the device. As a module,
	20	you can select a 1M window into the memory and the driver will
	21	"slide" the window around the PMC551's memory. This was
	22	particularly useful on the 2.2 kernels on PPC architectures as there
	23	was limited kernel space to deal with.
	24
	25	config MTD_PMC551_BUGFIX
	26	bool "PMC551 256M DRAM Bugfix"
	27	depends on MTD_PMC551
	28	help
	29	Some of Ramix's PMC551 boards with 256M configurations have invalid
	30	column and row mux values. This option will fix them, but will
	31	break other memory configurations. If unsure say N.
	32
	33	config MTD_PMC551_DEBUG
	34	bool "PMC551 Debugging"
	35	depends on MTD_PMC551
	36	help
	37	This option makes the PMC551 more verbose during its operation and
	38	is only really useful if you are developing on this driver or
	39	suspect a possible hardware or driver bug. If unsure say N.
	40
	41	config MTD_MS02NV
	42	tristate "DEC MS02-NV NVRAM module support"
ec98c681	43	depends on MACH_DECSTATION
1da177e4 LT	44	help
	45	This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
	46	backed-up NVRAM module. The module was originally meant as an NFS
	47	accelerator. Say Y here if you have a DECstation 5000/2x0 or a
	48	DECsystem 5900 equipped with such a module.
	49
be21ce11 MM	50	If you want to compile this driver as a module ( = code which can be
be21ce11 MM	51	inserted in and removed from the running kernel whenever you want),
39f5fb30 AP	52	say M here and read <file:Documentation/kbuild/modules.txt>.
39f5fb30 AP	53	The module will be called ms02-nv.ko.
be21ce11	54
1d6432fe DB	55	config MTD_DATAFLASH
1d6432fe DB	56	tristate "Support for AT45xxx DataFlash"
ec98c681	57	depends on SPI_MASTER && EXPERIMENTAL
1d6432fe DB	58	help
	59	This enables access to AT45xxx DataFlash chips, using SPI.
	60	Sometimes DataFlash chips are packaged inside MMC-format
	61	cards; at this writing, the MMC stack won't handle those.
	62
340ea370 HJK	63	config MTD_DATAFLASH26
	64	tristate "AT91RM9200 DataFlash AT26xxx"
	65	depends on MTD && ARCH_AT91RM9200 && AT91_SPI
	66	help
	67	This enables access to the DataFlash chip (AT26xxx) on an
	68	AT91RM9200-based board.
	69	If you have such a board and such a DataFlash, say 'Y'.
	70
2f9f7628 ML	71	config MTD_M25P80
2f9f7628 ML	72	tristate "Support for M25 SPI Flash"
ec98c681	73	depends on SPI_MASTER && EXPERIMENTAL
2f9f7628 ML	74	help
	75	This enables access to ST M25P80 and similar SPI flash chips,
	76	used for program and data storage. Set up your spi devices
	77	with the right board-specific platform data.
	78
1da177e4 LT	79	config MTD_SLRAM
1da177e4 LT	80	tristate "Uncached system RAM"
1da177e4 LT	81	help
	82	If your CPU cannot cache all of the physical memory in your machine,
	83	you can still use it for storage or swap by using this driver to
	84	present it to the system as a Memory Technology Device.
	85
	86	config MTD_PHRAM
	87	tristate "Physical system RAM"
1da177e4 LT	88	help
	89	This is a re-implementation of the slram driver above.
	90
	91	Use this driver to access physical memory that the kernel proper
	92	doesn't have access to, memory beyond the mem=xxx limit, nvram,
	93	memory on the video card, etc...
	94
	95	config MTD_LART
	96	tristate "28F160xx flash driver for LART"
ec98c681	97	depends on SA1100_LART
1da177e4 LT	98	help
	99	This enables the flash driver for LART. Please note that you do
	100	not need any mapping/chip driver for LART. This one does it all
	101	for you, so go disable all of those if you enabled some of them (:
	102
	103	config MTD_MTDRAM
	104	tristate "Test driver using RAM"
1da177e4 LT	105	help
	106	This enables a test MTD device driver which uses vmalloc() to
	107	provide storage. You probably want to say 'N' unless you're
	108	testing stuff.
	109
	110	config MTDRAM_TOTAL_SIZE
	111	int "MTDRAM device size in KiB"
	112	depends on MTD_MTDRAM
	113	default "4096"
	114	help
	115	This allows you to configure the total size of the MTD device
	116	emulated by the MTDRAM driver. If the MTDRAM driver is built
	117	as a module, it is also possible to specify this as a parameter when
	118	loading the module.
	119
	120	config MTDRAM_ERASE_SIZE
	121	int "MTDRAM erase block size in KiB"
	122	depends on MTD_MTDRAM
	123	default "128"
	124	help
	125	This allows you to configure the size of the erase blocks in the
	126	device emulated by the MTDRAM driver. If the MTDRAM driver is built
	127	as a module, it is also possible to specify this as a parameter when
	128	loading the module.
	129
	130	#If not a module (I don't want to test it as a module)
	131	config MTDRAM_ABS_POS
	132	hex "SRAM Hexadecimal Absolute position or 0"
	133	depends on MTD_MTDRAM=y
	134	default "0"
	135	help
	136	If you have system RAM accessible by the CPU but not used by Linux
	137	in normal operation, you can give the physical address at which the
	138	available RAM starts, and the MTDRAM driver will use it instead of
e5580fbe	139	allocating space from Linux's available memory. Otherwise, leave
1da177e4 LT	140	this set to zero. Most people will want to leave this as zero.
1da177e4 LT	141
acc8dadc JE	142	config MTD_BLOCK2MTD
acc8dadc JE	143	tristate "MTD using block device"
ec98c681	144	depends on BLOCK
1da177e4 LT	145	help
	146	This driver allows a block device to appear as an MTD. It would
	147	generally be used in the following cases:
	148
	149	Using Compact Flash as an MTD, these usually present themselves to
	150	the system as an ATA drive.
	151	Testing MTD users (eg JFFS2) on large media and media that might
	152	be removed during a write (using the floppy drive).
	153
1da177e4 LT	154	comment "Disk-On-Chip Device Drivers"
	155
	156	config MTD_DOC2000
	157	tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
1da177e4 LT	158	select MTD_DOCPROBE
	159	select MTD_NAND_IDS
	160	---help---
	161	This provides an MTD device driver for the M-Systems DiskOnChip
	162	2000 and Millennium devices. Originally designed for the DiskOnChip
	163	2000, it also now includes support for the DiskOnChip Millennium.
	164	If you have problems with this driver and the DiskOnChip Millennium,
	165	you may wish to try the alternative Millennium driver below. To use
	166	the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
	167	in the <file:drivers/mtd/devices/docprobe.c> source code.
	168
	169	If you use this device, you probably also want to enable the NFTL
	170	'NAND Flash Translation Layer' option below, which is used to
	171	emulate a block device by using a kind of file system on the flash
	172	chips.
	173
	174	NOTE: This driver is deprecated and will probably be removed soon.
	175	Please try the new DiskOnChip driver under "NAND Flash Device
	176	Drivers".
	177
	178	config MTD_DOC2001
	179	tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
1da177e4 LT	180	select MTD_DOCPROBE
	181	select MTD_NAND_IDS
	182	---help---
e5580fbe	183	This provides an alternative MTD device driver for the M-Systems
1da177e4 LT	184	DiskOnChip Millennium devices. Use this if you have problems with
	185	the combined DiskOnChip 2000 and Millennium driver above. To get
	186	the DiskOnChip probe code to load and use this driver instead of
	187	the other one, you will need to undefine DOC_SINGLE_DRIVER near
	188	the beginning of <file:drivers/mtd/devices/docprobe.c>.
	189
	190	If you use this device, you probably also want to enable the NFTL
	191	'NAND Flash Translation Layer' option below, which is used to
	192	emulate a block device by using a kind of file system on the flash
	193	chips.
	194
	195	NOTE: This driver is deprecated and will probably be removed soon.
	196	Please try the new DiskOnChip driver under "NAND Flash Device
	197	Drivers".
	198
	199	config MTD_DOC2001PLUS
	200	tristate "M-Systems Disk-On-Chip Millennium Plus"
1da177e4 LT	201	select MTD_DOCPROBE
	202	select MTD_NAND_IDS
	203	---help---
	204	This provides an MTD device driver for the M-Systems DiskOnChip
	205	Millennium Plus devices.
	206
	207	If you use this device, you probably also want to enable the INFTL
	208	'Inverse NAND Flash Translation Layer' option below, which is used
e5580fbe	209	to emulate a block device by using a kind of file system on the
1da177e4 LT	210	flash chips.
	211
	212	NOTE: This driver will soon be replaced by the new DiskOnChip driver
	213	under "NAND Flash Device Drivers" (currently that driver does not
	214	support all Millennium Plus devices).
	215
	216	config MTD_DOCPROBE
	217	tristate
	218	select MTD_DOCECC
	219
	220	config MTD_DOCECC
	221	tristate
	222
	223	config MTD_DOCPROBE_ADVANCED
	224	bool "Advanced detection options for DiskOnChip"
	225	depends on MTD_DOCPROBE
	226	help
	227	This option allows you to specify nonstandard address at which to
	228	probe for a DiskOnChip, or to change the detection options. You
	229	are unlikely to need any of this unless you are using LinuxBIOS.
	230	Say 'N'.
	231
	232	config MTD_DOCPROBE_ADDRESS
	233	hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
	234	depends on MTD_DOCPROBE
	235	default "0x0000" if MTD_DOCPROBE_ADVANCED
	236	default "0" if !MTD_DOCPROBE_ADVANCED
	237	---help---
	238	By default, the probe for DiskOnChip devices will look for a
	239	DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
	240	This option allows you to specify a single address at which to probe
	241	for the device, which is useful if you have other devices in that
	242	range which get upset when they are probed.
	243
	244	(Note that on PowerPC, the normal probe will only check at
	245	0xE4000000.)
	246
	247	Normally, you should leave this set to zero, to allow the probe at
	248	the normal addresses.
	249
	250	config MTD_DOCPROBE_HIGH
	251	bool "Probe high addresses"
	252	depends on MTD_DOCPROBE_ADVANCED
	253	help
	254	By default, the probe for DiskOnChip devices will look for a
	255	DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
	256	This option changes to make it probe between 0xFFFC8000 and
	257	0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
	258	useful to you. Say 'N'.
	259
	260	config MTD_DOCPROBE_55AA
	261	bool "Probe for 0x55 0xAA BIOS Extension Signature"
	262	depends on MTD_DOCPROBE_ADVANCED
	263	help
	264	Check for the 0x55 0xAA signature of a DiskOnChip, and do not
	265	continue with probing if it is absent. The signature will always be
	266	present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
	267	Only if you have overwritten the first block of a DiskOnChip
	268	Millennium will it be absent. Enable this option if you are using
	269	LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
	270	you have managed to wipe the first block.
	271
	272	endmenu
	273