diff options
author | Khoronzhuk, Ivan <ivan.khoronzhuk@ti.com> | 2014-07-04 15:03:25 +0300 |
---|---|---|
committer | Tom Rini <trini@ti.com> | 2014-07-25 15:21:06 -0400 |
commit | 67ac6ffaeefb93ff294f976cbb03479f84aa0b1a (patch) | |
tree | d97b87e29f4628241c2a114727786fe38c676fb1 /boards.cfg | |
parent | 7aa5598aac3faf9188559f7a50940df11c30b656 (diff) | |
download | u-boot-imx-67ac6ffaeefb93ff294f976cbb03479f84aa0b1a.zip u-boot-imx-67ac6ffaeefb93ff294f976cbb03479f84aa0b1a.tar.gz u-boot-imx-67ac6ffaeefb93ff294f976cbb03479f84aa0b1a.tar.bz2 |
mtd: nand: davinci: add opportunity to write keystone U-boot image
The Keystone SoCs use the same NAND driver as Davinci.
This patch adds opportunity to write Keystone U-boot image to NAND
device using appropriate RBL ECC layout. This is needed only if RBL
boots U-boot from NAND device and that's supposed that raw u-boot
partition is used only for writing image.
The main problem is that default Davinci ECC layout is different from
Keystone RBL layout. To read U-boot image the RBL needs that image was
written using RBL ECC layout.
The BBT table is written using default Davinci layout and has to
be updated using one. The BBT can be updated only while erasing
chip or by forced bad block assigning, so erase function has to
use native ecc layout in order to be able to write BBT correctly.
So if we're writing to NAND U-boot address we use RBL layout for
others we use default ECC layout.
Also remove definition for CONFIG_CMD_NAND_ECCLAYOUT as there is no
reasons to use ECC layout commands. It was added by mistake.
Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Diffstat (limited to 'boards.cfg')
0 files changed, 0 insertions, 0 deletions