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

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

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.

config MTD_DATAFLASH
	tristate "Support for AT45xxx DataFlash"
	depends on SPI_MASTER
	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_DATAFLASH_WRITE_VERIFY
	bool "Verify DataFlash page writes"
	depends on MTD_DATAFLASH
	help
	  This adds an extra check when data is written to the flash.
	  It may help if you are verifying chip setup (timings etc) on
	  your board.  There is a rare possibility that even though the
	  device thinks the write was successful, a bit could have been
	  flipped accidentally due to device wear or something else.

config MTD_DATAFLASH_OTP
	bool "DataFlash OTP support (Security Register)"
	depends on MTD_DATAFLASH
	select HAVE_MTD_OTP
	help
	  Newer DataFlash chips (revisions C and D) support 128 bytes of
	  one-time-programmable (OTP) data.  The first half may be written
	  (once) with up to 64 bytes of data, such as a serial number or
	  other key product data.  The second half is programmed with a
	  unique-to-each-chip bit pattern at the factory.

config MTD_M25P80
	tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
	depends on SPI_MASTER
	help
	  This enables access to most modern SPI flash chips, used for
	  program and data storage.   Series supported include Atmel AT26DF,
	  Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X.  Other chips
	  are supported as well.  See the driver source for the current list,
	  or to add other chips.

	  Note that the original DataFlash chips (AT45 series, not AT26DF),
	  need an entirely different driver.

	  Set up your spi devices with the right board-specific platform data,
	  if you want to specify device partitioning or to use a device which
	  doesn't support the JEDEC ID instruction.

config M25PXX_USE_FAST_READ
	bool "Use FAST_READ OPCode allowing SPI CLK >= 50MHz"
	depends on MTD_M25P80
	default y
	help
	  This option enables FAST_READ access supported by ST M25Pxx.

config MTD_SPEAR_SMI
	tristate "SPEAR MTD NOR Support through SMI controller"
	depends on PLAT_SPEAR
	default y
	help
	  This enable SNOR support on SPEAR platforms using SMI controller

config MTD_SST25L
	tristate "Support SST25L (non JEDEC) SPI Flash chips"
	depends on SPI_MASTER
	help
	  This enables access to the non JEDEC SST25L SPI flash chips, used
	  for program and data storage.

	  Set up your spi devices with the right board-specific platform data,
	  if you want to specify device partitioning.

config MTD_BCM47XXSFLASH
	tristate "R/O support for serial flash on BCMA bus"
	depends on BCMA_SFLASH
	help
	  BCMA bus can have various flash memories attached, they are
	  registered by bcma as platform devices. This enables driver for
	  serial flash memories (only read-only mode is implemented).

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)"
	depends on MTD_NAND
	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)"
	depends on MTD_NAND
	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"
	depends on MTD_NAND
	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_DOCG3
	tristate "M-Systems Disk-On-Chip G3"
	select BCH
	select BCH_CONST_PARAMS
	select BITREVERSE
	---help---
	  This provides an MTD device driver for the M-Systems DiskOnChip
	  G3 devices.

	  The driver provides access to G3 DiskOnChip, distributed by
	  M-Systems and now Sandisk. The support is very experimental,
	  and doesn't give access to any write operations.

if MTD_DOCG3
config BCH_CONST_M
	default 14
config BCH_CONST_T
	default 4
endif

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 "0x0"
	---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 LT	1	menu "Self-contained MTD device drivers"
1da177e4 LT	2	depends on MTD!=n
9310da0b	3	depends on HAS_IOMEM
1da177e4 LT	4
	5	config MTD_PMC551
	6	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
ec98c681	7	depends on PCI
1da177e4 LT	8	---help---
	9	This provides a MTD device driver for the Ramix PMC551 RAM PCI card
	10	from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
	11	These devices come in memory configurations from 32M - 1G. If you
	12	have one, you probably want to enable this.
	13
	14	If this driver is compiled as a module you get the ability to select
	15	the size of the aperture window pointing into the devices memory.
	16	What this means is that if you have a 1G card, normally the kernel
	17	will use a 1G memory map as its view of the device. As a module,
	18	you can select a 1M window into the memory and the driver will
	19	"slide" the window around the PMC551's memory. This was
	20	particularly useful on the 2.2 kernels on PPC architectures as there
	21	was limited kernel space to deal with.
	22
	23	config MTD_PMC551_BUGFIX
	24	bool "PMC551 256M DRAM Bugfix"
	25	depends on MTD_PMC551
	26	help
	27	Some of Ramix's PMC551 boards with 256M configurations have invalid
	28	column and row mux values. This option will fix them, but will
	29	break other memory configurations. If unsure say N.
	30
	31	config MTD_PMC551_DEBUG
	32	bool "PMC551 Debugging"
	33	depends on MTD_PMC551
	34	help
	35	This option makes the PMC551 more verbose during its operation and
	36	is only really useful if you are developing on this driver or
	37	suspect a possible hardware or driver bug. If unsure say N.
	38
	39	config MTD_MS02NV
	40	tristate "DEC MS02-NV NVRAM module support"
ec98c681	41	depends on MACH_DECSTATION
1da177e4 LT	42	help
	43	This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
	44	backed-up NVRAM module. The module was originally meant as an NFS
	45	accelerator. Say Y here if you have a DECstation 5000/2x0 or a
	46	DECsystem 5900 equipped with such a module.
	47
be21ce11 MM	48	If you want to compile this driver as a module ( = code which can be
be21ce11 MM	49	inserted in and removed from the running kernel whenever you want),
39f5fb30	50	say M here and read <file:Documentation/kbuild/modules.txt>.
4737f097	51	The module will be called ms02-nv.
be21ce11	52
1d6432fe DB	53	config MTD_DATAFLASH
1d6432fe DB	54	tristate "Support for AT45xxx DataFlash"
a11ed37c	55	depends on SPI_MASTER
1d6432fe DB	56	help
	57	This enables access to AT45xxx DataFlash chips, using SPI.
	58	Sometimes DataFlash chips are packaged inside MMC-format
	59	cards; at this writing, the MMC stack won't handle those.
	60
8c64038e DB	61	config MTD_DATAFLASH_WRITE_VERIFY
	62	bool "Verify DataFlash page writes"
	63	depends on MTD_DATAFLASH
	64	help
	65	This adds an extra check when data is written to the flash.
	66	It may help if you are verifying chip setup (timings etc) on
	67	your board. There is a rare possibility that even though the
	68	device thinks the write was successful, a bit could have been
	69	flipped accidentally due to device wear or something else.
	70
34a82443 DB	71	config MTD_DATAFLASH_OTP
	72	bool "DataFlash OTP support (Security Register)"
	73	depends on MTD_DATAFLASH
	74	select HAVE_MTD_OTP
	75	help
	76	Newer DataFlash chips (revisions C and D) support 128 bytes of
	77	one-time-programmable (OTP) data. The first half may be written
	78	(once) with up to 64 bytes of data, such as a serial number or
	79	other key product data. The second half is programmed with a
	80	unique-to-each-chip bit pattern at the factory.
	81
2f9f7628	82	config MTD_M25P80
fa0a8c71	83	tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
a11ed37c	84	depends on SPI_MASTER
2f9f7628	85	help
fa0a8c71 DB	86	This enables access to most modern SPI flash chips, used for
	87	program and data storage. Series supported include Atmel AT26DF,
	88	Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips
	89	are supported as well. See the driver source for the current list,
	90	or to add other chips.
	91
	92	Note that the original DataFlash chips (AT45 series, not AT26DF),
	93	need an entirely different driver.
	94
	95	Set up your spi devices with the right board-specific platform data,
	96	if you want to specify device partitioning or to use a device which
	97	doesn't support the JEDEC ID instruction.
2f9f7628	98
2230b76b	99	config M25PXX_USE_FAST_READ
b8c2d652	100	bool "Use FAST_READ OPCode allowing SPI CLK >= 50MHz"
2230b76b BW	101	depends on MTD_M25P80
	102	default y
	103	help
	104	This option enables FAST_READ access supported by ST M25Pxx.
	105
f18dbbb1 SH	106	config MTD_SPEAR_SMI
	107	tristate "SPEAR MTD NOR Support through SMI controller"
	108	depends on PLAT_SPEAR
	109	default y
	110	help
	111	This enable SNOR support on SPEAR platforms using SMI controller
	112
ec77e21b RM	113	config MTD_SST25L
	114	tristate "Support SST25L (non JEDEC) SPI Flash chips"
	115	depends on SPI_MASTER
	116	help
	117	This enables access to the non JEDEC SST25L SPI flash chips, used
	118	for program and data storage.
	119
	120	Set up your spi devices with the right board-specific platform data,
	121	if you want to specify device partitioning.
	122
5fe42d5b RM	123	config MTD_BCM47XXSFLASH
	124	tristate "R/O support for serial flash on BCMA bus"
	125	depends on BCMA_SFLASH
	126	help
	127	BCMA bus can have various flash memories attached, they are
	128	registered by bcma as platform devices. This enables driver for
	129	serial flash memories (only read-only mode is implemented).
	130
1da177e4 LT	131	config MTD_SLRAM
1da177e4 LT	132	tristate "Uncached system RAM"
1da177e4 LT	133	help
	134	If your CPU cannot cache all of the physical memory in your machine,
	135	you can still use it for storage or swap by using this driver to
	136	present it to the system as a Memory Technology Device.
	137
	138	config MTD_PHRAM
	139	tristate "Physical system RAM"
1da177e4 LT	140	help
	141	This is a re-implementation of the slram driver above.
	142
	143	Use this driver to access physical memory that the kernel proper
	144	doesn't have access to, memory beyond the mem=xxx limit, nvram,
	145	memory on the video card, etc...
	146
	147	config MTD_LART
	148	tristate "28F160xx flash driver for LART"
ec98c681	149	depends on SA1100_LART
1da177e4 LT	150	help
	151	This enables the flash driver for LART. Please note that you do
	152	not need any mapping/chip driver for LART. This one does it all
	153	for you, so go disable all of those if you enabled some of them (:
	154
	155	config MTD_MTDRAM
	156	tristate "Test driver using RAM"
1da177e4 LT	157	help
	158	This enables a test MTD device driver which uses vmalloc() to
	159	provide storage. You probably want to say 'N' unless you're
	160	testing stuff.
	161
	162	config MTDRAM_TOTAL_SIZE
	163	int "MTDRAM device size in KiB"
	164	depends on MTD_MTDRAM
	165	default "4096"
	166	help
	167	This allows you to configure the total size of the MTD device
	168	emulated by the MTDRAM driver. If the MTDRAM driver is built
	169	as a module, it is also possible to specify this as a parameter when
	170	loading the module.
	171
	172	config MTDRAM_ERASE_SIZE
	173	int "MTDRAM erase block size in KiB"
	174	depends on MTD_MTDRAM
	175	default "128"
	176	help
	177	This allows you to configure the size of the erase blocks in the
	178	device emulated by the MTDRAM driver. If the MTDRAM driver is built
	179	as a module, it is also possible to specify this as a parameter when
	180	loading the module.
	181
	182	#If not a module (I don't want to test it as a module)
	183	config MTDRAM_ABS_POS
	184	hex "SRAM Hexadecimal Absolute position or 0"
	185	depends on MTD_MTDRAM=y
	186	default "0"
	187	help
	188	If you have system RAM accessible by the CPU but not used by Linux
	189	in normal operation, you can give the physical address at which the
	190	available RAM starts, and the MTDRAM driver will use it instead of
e5580fbe	191	allocating space from Linux's available memory. Otherwise, leave
1da177e4 LT	192	this set to zero. Most people will want to leave this as zero.
1da177e4 LT	193
acc8dadc JE	194	config MTD_BLOCK2MTD
acc8dadc JE	195	tristate "MTD using block device"
ec98c681	196	depends on BLOCK
1da177e4 LT	197	help
	198	This driver allows a block device to appear as an MTD. It would
	199	generally be used in the following cases:
	200
	201	Using Compact Flash as an MTD, these usually present themselves to
	202	the system as an ATA drive.
	203	Testing MTD users (eg JFFS2) on large media and media that might
	204	be removed during a write (using the floppy drive).
	205
1da177e4 LT	206	comment "Disk-On-Chip Device Drivers"
	207
	208	config MTD_DOC2000
	209	tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
b60ef99c	210	depends on MTD_NAND
1da177e4 LT	211	select MTD_DOCPROBE
	212	select MTD_NAND_IDS
	213	---help---
	214	This provides an MTD device driver for the M-Systems DiskOnChip
	215	2000 and Millennium devices. Originally designed for the DiskOnChip
	216	2000, it also now includes support for the DiskOnChip Millennium.
	217	If you have problems with this driver and the DiskOnChip Millennium,
	218	you may wish to try the alternative Millennium driver below. To use
	219	the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
	220	in the <file:drivers/mtd/devices/docprobe.c> source code.
	221
	222	If you use this device, you probably also want to enable the NFTL
	223	'NAND Flash Translation Layer' option below, which is used to
	224	emulate a block device by using a kind of file system on the flash
	225	chips.
	226
	227	NOTE: This driver is deprecated and will probably be removed soon.
	228	Please try the new DiskOnChip driver under "NAND Flash Device
	229	Drivers".
	230
	231	config MTD_DOC2001
	232	tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
b60ef99c	233	depends on MTD_NAND
1da177e4 LT	234	select MTD_DOCPROBE
	235	select MTD_NAND_IDS
	236	---help---
e5580fbe	237	This provides an alternative MTD device driver for the M-Systems
1da177e4 LT	238	DiskOnChip Millennium devices. Use this if you have problems with
	239	the combined DiskOnChip 2000 and Millennium driver above. To get
	240	the DiskOnChip probe code to load and use this driver instead of
	241	the other one, you will need to undefine DOC_SINGLE_DRIVER near
	242	the beginning of <file:drivers/mtd/devices/docprobe.c>.
	243
	244	If you use this device, you probably also want to enable the NFTL
	245	'NAND Flash Translation Layer' option below, which is used to
	246	emulate a block device by using a kind of file system on the flash
	247	chips.
	248
	249	NOTE: This driver is deprecated and will probably be removed soon.
	250	Please try the new DiskOnChip driver under "NAND Flash Device
	251	Drivers".
	252
	253	config MTD_DOC2001PLUS
	254	tristate "M-Systems Disk-On-Chip Millennium Plus"
b60ef99c	255	depends on MTD_NAND
1da177e4 LT	256	select MTD_DOCPROBE
	257	select MTD_NAND_IDS
	258	---help---
	259	This provides an MTD device driver for the M-Systems DiskOnChip
	260	Millennium Plus devices.
	261
	262	If you use this device, you probably also want to enable the INFTL
	263	'Inverse NAND Flash Translation Layer' option below, which is used
e5580fbe	264	to emulate a block device by using a kind of file system on the
1da177e4 LT	265	flash chips.
	266
	267	NOTE: This driver will soon be replaced by the new DiskOnChip driver
	268	under "NAND Flash Device Drivers" (currently that driver does not
	269	support all Millennium Plus devices).
	270
efa2ca73 RJ	271	config MTD_DOCG3
efa2ca73 RJ	272	tristate "M-Systems Disk-On-Chip G3"
d13d19ec RJ	273	select BCH
d13d19ec RJ	274	select BCH_CONST_PARAMS
bf65aaa6	275	select BITREVERSE
efa2ca73 RJ	276	---help---
	277	This provides an MTD device driver for the M-Systems DiskOnChip
	278	G3 devices.
	279
	280	The driver provides access to G3 DiskOnChip, distributed by
	281	M-Systems and now Sandisk. The support is very experimental,
	282	and doesn't give access to any write operations.
	283
d13d19ec RJ	284	if MTD_DOCG3
	285	config BCH_CONST_M
	286	default 14
	287	config BCH_CONST_T
	288	default 4
	289	endif
	290
1da177e4 LT	291	config MTD_DOCPROBE
	292	tristate
	293	select MTD_DOCECC
	294
	295	config MTD_DOCECC
	296	tristate
	297
	298	config MTD_DOCPROBE_ADVANCED
	299	bool "Advanced detection options for DiskOnChip"
	300	depends on MTD_DOCPROBE
	301	help
	302	This option allows you to specify nonstandard address at which to
	303	probe for a DiskOnChip, or to change the detection options. You
	304	are unlikely to need any of this unless you are using LinuxBIOS.
	305	Say 'N'.
	306
	307	config MTD_DOCPROBE_ADDRESS
	308	hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
	309	depends on MTD_DOCPROBE
6be55f79	310	default "0x0"
1da177e4 LT	311	---help---
	312	By default, the probe for DiskOnChip devices will look for a
	313	DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
	314	This option allows you to specify a single address at which to probe
	315	for the device, which is useful if you have other devices in that
	316	range which get upset when they are probed.
	317
	318	(Note that on PowerPC, the normal probe will only check at
	319	0xE4000000.)
	320
	321	Normally, you should leave this set to zero, to allow the probe at
	322	the normal addresses.
	323
	324	config MTD_DOCPROBE_HIGH
	325	bool "Probe high addresses"
	326	depends on MTD_DOCPROBE_ADVANCED
	327	help
	328	By default, the probe for DiskOnChip devices will look for a
	329	DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
	330	This option changes to make it probe between 0xFFFC8000 and
	331	0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
	332	useful to you. Say 'N'.
	333
	334	config MTD_DOCPROBE_55AA
	335	bool "Probe for 0x55 0xAA BIOS Extension Signature"
	336	depends on MTD_DOCPROBE_ADVANCED
	337	help
	338	Check for the 0x55 0xAA signature of a DiskOnChip, and do not
	339	continue with probing if it is absent. The signature will always be
	340	present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
	341	Only if you have overwritten the first block of a DiskOnChip
	342	Millennium will it be absent. Enable this option if you are using
	343	LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
	344	you have managed to wipe the first block.
	345
	346	endmenu