CONFIG_MTD_NAND_ECC_YAFFS would be another useful choice for
someone to implement.
- CFG_MAX_NAND_DEVICE
+ CONFIG_SYS_MAX_NAND_DEVICE
The maximum number of NAND devices you want to support.
NAND Interface:
These definitions are needed in the board configuration for now, but
may really belong in a header file.
TODO: Figure which ones are truly configuration settings and rename
- them to CFG_NAND_... and move the rest somewhere appropriate.
+ them to CONFIG_SYS_NAND_... and move the rest somewhere appropriate.
#define SECTORSIZE 512
#define ADDR_COLUMN 1
#define NAND_MAX_FLOORS 1
#define NAND_MAX_CHIPS 1
+ #define CONFIG_SYS_DAVINCI_BROKEN_ECC
+ Versions of U-Boot <= 1.3.3 and Montavista Linux kernels
+ generated bogus ECCs on large-page NAND. Both large and small page
+ NAND ECCs were incompatible with the Linux davinci git tree (since
+ NAND was integrated in 2.6.24).
+ Turn this ON if you want backwards compatibility.
+ Turn this OFF if you want U-Boot and the Linux davinci git kernel
+ to use the same ECC format.
NOTE:
=====
The old NAND handling code has been re-factored and is now confined
to only board-specific files and - unfortunately - to the DoC code
(see below). A new configuration variable has been introduced:
-CFG_NAND_LEGACY, which has to be defined in the board config file if
+CONFIG_NAND_LEGACY, which has to be defined in the board config file if
that board uses legacy code.
The necessary changes have been made to all affected boards, and no