rockchip: mkimage: set init_boot_size to avoid confusing the boot ROM
authorPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
Tue, 30 May 2017 21:32:10 +0000 (23:32 +0200)
committerSimon Glass <sjg@chromium.org>
Wed, 7 Jun 2017 13:29:23 +0000 (07:29 -0600)
commita1c29d4b43dc1bdc57878204bf3e4316fdb1b8b0
tree1e61e4d310e04f9b55a28bd1c059aa41a372aef9
parentad972ac3d948ae1e8b9e75ef96e9dbe8392a4678
rockchip: mkimage: set init_boot_size to avoid confusing the boot ROM

This change restores the earlier setting of init_boot_size to include
the maximum area covered by the the boot ROM of each chip for resolve
issues with back-to-bootrom functionality reported by Kever and Heiko.

To ensure that we don't run into the same issue again in the future,
I have updated the comments accordingly and added a reference to the
mailing list archive (there's some very helpful info from Andy Yan
that provides background on the BootROM requirements regarding these
fields).

See https://lists.denx.de/pipermail/u-boot/2017-May/293267.html for
some background (by Andy Yan) of how the BootROM processes this field.

Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
tools/rkcommon.c