mirror of
https://github.com/u-boot/u-boot.git
synced 2024-11-28 23:23:30 +08:00
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>
This commit is contained in:
parent
88a2cbb2ae
commit
aff092ed13
@ -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
|
||||
|
@ -153,7 +153,6 @@
|
||||
|
||||
/* JFFS2 */
|
||||
#ifdef CONFIG_CMD_JFFS2
|
||||
#define CONFIG_MTD_NAND_ECC_JFFS2
|
||||
#define CONFIG_JFFS2_CMDLINE
|
||||
#define CONFIG_JFFS2_NAND
|
||||
#endif
|
||||
|
Loading…
Reference in New Issue
Block a user