path: root/doc
diff options
authorPeter Tyser <>2015-02-03 10:11:59 -0600
committerScott Wood <>2015-03-30 23:16:54 -0500
commitaff092ed13dd1e26f0bed24dddaccf2b91275c89 (patch)
tree37ac7a5bfd4fc4503dcb55a95e6d3d822a289ed6 /doc
parent88a2cbb2aeb34c7c91f7cd30b59066368063bd07 (diff)
nand: Remove unused CONFIG_MTD_NAND_ECC_JFFS2 option
This option was removed along with legacy NAND support in be33b046b549ad88c204c209508cd7657232ffbd. Clean up some remnants. Signed-off-by: Peter Tyser <>
Diffstat (limited to 'doc')
1 files changed, 0 insertions, 12 deletions
diff --git a/doc/README.nand b/doc/README.nand
index dee0e00a61..46d7edd179 100644
--- a/doc/README.nand
+++ b/doc/README.nand
@@ -99,12 +99,6 @@ Configuration Options:
Enables the torture command (see description of this command below).
- Define this if you want the Error Correction Code information in
- the out-of-band data to be formatted to match the JFFS2 file system.
- CONFIG_MTD_NAND_ECC_YAFFS would be another useful choice for
- someone to implement.
The maximum number of NAND devices you want to support.
@@ -312,12 +306,6 @@ Platform specific options
-The current NAND implementation is based on what is in recent
-Linux kernels. The old legacy implementation has been removed.
-If you have board code which used CONFIG_NAND_LEGACY, you'll need
-to convert to the current NAND interface for it to continue to work.
The Disk On Chip driver is currently broken and has been for some time.
There is a driver in drivers/mtd/nand, taken from Linux, that works with
the current NAND system but has not yet been adapted to the u-boot
OpenPOWER on IntegriCloud