On Thu, Mar 15, 2018 at 01:55:02PM +0530, Prabhakar Kushwaha wrote:
commit 20e072f37402 ("image: check "bootm_low" and "bootm_size" if "initrd_high" is missing"), forces to check "bootm_low" and "bootm_size" if "initrd_high" is missing. It causes Linux boot up failure with ramdisk size > 90MB.
So setting initrd_high to avoid rootfs relocation.
Signed-off-by: Alison Wang alison.wang@nxp.com Signed-off-by: Prabhakar Kushwaha prabhakar.kushwaha@nxp.com
I'm _really_ against disabling relocation of the device tree or ramdisk when we have enough information to do said checks as it inevitably leads to people finding a kernel + ramdisk + dtb combination where the kernel BSS ate something. What exactly is the layout you're seeing where things fail, and why can we not use (or, update) bootm_size to describe the overall region? Thanks!