1 # drivers/mtd/nand/Kconfig
2 # $Id: Kconfig,v 1.17 2004/08/10 14:24:07 dwmw2 Exp $
4 menu "NAND Flash Device Drivers"
8 tristate "NAND Device Support"
11 This enables support for accessing all type of NAND flash
12 devices. For further information see
13 <http://www.linux-mtd.infradead.org/tech/nand.html>.
15 config MTD_NAND_VERIFY_WRITE
16 bool "Verify NAND page writes"
19 This adds an extra check when data is written to the flash. The
20 NAND flash device internally checks only bits transitioning
21 from 1 to 0. There is a rare possibility that even though the
22 device thinks the write was successful, a bit could have been
23 flipped accidentaly due to device wear or something else.
25 config MTD_NAND_AUTCPU12
26 tristate "SmartMediaCard on autronix autcpu12 board"
27 depends on ARM && MTD_NAND && ARCH_AUTCPU12
29 This enables the driver for the autronix autcpu12 board to
30 access the SmartMediaCard.
32 config MTD_NAND_EDB7312
33 tristate "Support for Cirrus Logic EBD7312 evaluation board"
34 depends on ARM && MTD_NAND && ARCH_EDB7312
36 This enables the driver for the Cirrus Logic EBD7312 evaluation
37 board to access the onboard NAND Flash.
40 tristate "NAND Flash device on SPIA board"
41 depends on ARM && ARCH_P720T && MTD_NAND
43 If you had to ask, you don't have one. Say 'N'.
46 tristate "NAND Flash device on TOTO board"
47 depends on ARM && ARCH_OMAP && MTD_NAND
49 Support for NAND flash on Texas Instruments Toto platform.
53 default y if MTD_NAND = y || MTD_DOC2000 = y || MTD_DOC2001 = y || MTD_DOC2001PLUS = y
54 default m if MTD_NAND = m || MTD_DOC2000 = m || MTD_DOC2001 = m || MTD_DOC2001PLUS = m
56 config MTD_NAND_TX4925NDFMC
57 tristate "SmartMedia Card on Toshiba RBTX4925 reference board"
58 depends on TOSHIBA_RBTX4925 && MTD_NAND && TOSHIBA_RBTX4925_MPLEX_NAND
60 This enables the driver for the NAND flash device found on the
61 Toshiba RBTX4925 reference board, which is a SmartMediaCard.
63 config MTD_NAND_TX4938NDFMC
64 tristate "NAND Flash device on Toshiba RBTX4938 reference board"
65 depends on TOSHIBA_RBTX4938 && MTD_NAND && TOSHIBA_RBTX4938_MPLEX_NAND
67 This enables the driver for the NAND flash device found on the
68 Toshiba RBTX4938 reference board.
70 config MTD_NAND_AU1550
71 tristate "Au1550 NAND support"
72 depends on SOC_AU1550 && MTD_NAND
74 This enables the driver for the NAND flash controller on the
77 config MTD_NAND_PPCHAMELEONEVB
78 tristate "NAND Flash device on PPChameleonEVB board"
79 depends on PPCHAMELEONEVB && MTD_NAND
81 This enables the NAND flash driver on the PPChameleon EVB Board.
83 config MTD_NAND_DISKONCHIP
84 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
85 depends on MTD_NAND && EXPERIMENTAL
87 This is a reimplementation of M-Systems DiskOnChip 2000,
88 Millennium and Millennium Plus as a standard NAND device driver,
89 as opposed to the earlier self-contained MTD device drivers.
90 This should enable, among other things, proper JFFS2 operation on
93 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
94 bool "Advanced detection options for DiskOnChip"
95 depends on MTD_NAND_DISKONCHIP
97 This option allows you to specify nonstandard address at which to
98 probe for a DiskOnChip, or to change the detection options. You
99 are unlikely to need any of this unless you are using LinuxBIOS.
102 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
103 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
104 depends on MTD_NAND_DISKONCHIP
107 By default, the probe for DiskOnChip devices will look for a
108 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
109 This option allows you to specify a single address at which to probe
110 for the device, which is useful if you have other devices in that
111 range which get upset when they are probed.
113 (Note that on PowerPC, the normal probe will only check at
116 Normally, you should leave this set to zero, to allow the probe at
117 the normal addresses.
119 config MTD_NAND_DISKONCHIP_PROBE_HIGH
120 bool "Probe high addresses"
121 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
123 By default, the probe for DiskOnChip devices will look for a
124 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
125 This option changes to make it probe between 0xFFFC8000 and
126 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
127 useful to you. Say 'N'.
129 config MTD_NAND_DISKONCHIP_BBTWRITE
130 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
131 depends on MTD_NAND_DISKONCHIP
133 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
134 and 2000 TSOP/Alon), Linux reserves some space at the end of the
135 device for the Bad Block Table (BBT). If you have existing INFTL
136 data on your device (created by non-Linux tools such as M-Systems'
137 DOS drivers), your data might overlap the area Linux wants to use for
138 the BBT. If this is a concern for you, leave this option disabled and
139 Linux will not write BBT data into this area.
140 The downside of leaving this option disabled is that if bad blocks
141 are detected by Linux, they will not be recorded in the BBT, which
142 could cause future problems.
143 Once you enable this option, new filesystems (INFTL or others, created
144 in Linux or other operating systems) will not use the reserved area.
145 The only reason not to enable this option is to prevent damage to
146 preexisting filesystems.
147 Even if you leave this disabled, you can enable BBT writes at module
148 load time (assuming you build diskonchip as a module) with the module
149 parameter "inftl_bbt_write=1".