On Wed, Feb 05, 2020 at 03:51:42PM +0000, Oliver Graute wrote: > Remove 'fdt_high' and 'initrd_high' environment variables (set to 0xFFFFFFFF) > from default environment which prevents relocation of FDT and initrd. > > Signed-off-by: Oliver Graute <oliver.gra...@kococonnector.com> > Cc: Stefano Babic <sba...@denx.de> > Cc: Fabio Estevam <feste...@gmail.com> > Cc: Peng Fan <peng....@nxp.com> > Cc: Simon Glass <s...@chromium.org> > Cc: Ye Li <ye...@nxp.com> > Cc: uboot-imx <uboot-...@nxp.com> > --- > include/configs/imx8qm_rom7720.h | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/include/configs/imx8qm_rom7720.h > b/include/configs/imx8qm_rom7720.h > index 865863eb7c..8beb65e96b 100644 > --- a/include/configs/imx8qm_rom7720.h > +++ b/include/configs/imx8qm_rom7720.h > @@ -63,11 +63,9 @@ > "panel=NULL\0" \ > "console=ttyLP0\0" \ > "fdt_addr=0x83000000\0" \ > - "fdt_high=0xffffffffffffffff\0" \ > "boot_fdt=try\0" \ > "fdt_file=imx8qm-rom7720-a1.dtb\0" \ > "initrd_addr=0x83800000\0" \ > - "initrd_high=0xffffffffffffffff\0" \ > "mmcdev="__stringify(CONFIG_SYS_MMC_ENV_DEV)"\0" \ > "mmcpart=" __stringify(CONFIG_SYS_MMC_IMG_LOAD_PART) "\0" \ > "mmcroot=" CONFIG_MMCROOT " rootwait rw\0" \
Is bootm_size or CONFIG_SYS_BOOTMAPSZ already being set somewhere for these platforms? In Linux, Documentation/arm64/booting.rst does describe limitations on where FDT/initrd can reside in memory so we need to make sure they're obeyed. That's best done by using bootm_size in environment or CONFIG_SYS_BOOTMAPSZ at build time to ensure alignment and non-overlap within those limits and not "don't move anything ever" as fdt_high/initrd_high=0xff... does. Thanks! -- Tom
signature.asc
Description: PGP signature
