redonkable
/
remarkable-uboot
1
0
Fork 0
Code Releases Activity

nand: Remove unused CONFIG_MTD_NAND_ECC_JFFS2 option 

This option was removed along with legacy NAND support in
be33b046b5.  Clean up some remnants.

Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
utp
Peter Tyser 2015-02-03 10:11:59 -06:00 committed by Scott Wood
parent 88a2cbb2ae
commit aff092ed13
2 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/README.nand
View File

@ -99,12 +99,6 @@ Configuration Options:
CONFIG_CMD_NAND_TORTURE
Enables the torture command (see description of this command below).
CONFIG_MTD_NAND_ECC_JFFS2
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.
CONFIG_SYS_MAX_NAND_DEVICE
The maximum number of NAND devices you want to support.
@ -312,12 +306,6 @@ Platform specific options
NOTE:
=====
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

1
include/configs/ethernut5.h
View File

@ -153,7 +153,6 @@
/* JFFS2 */
#ifdef CONFIG_CMD_JFFS2
#define CONFIG_MTD_NAND_ECC_JFFS2
#define CONFIG_JFFS2_CMDLINE
#define CONFIG_JFFS2_NAND
#endif