On Tue, Feb 11, 2020 at 09:25:52AM +0530, Lokesh Vutla wrote: > From: Tero Kristo <t-kri...@ti.com> > > Keystone2 u-boot loads the initrd image into non-LPAE addressed memory > but linux kernel is running in LPAE. This causes a conflict as kernel > detects that non-memory address is passed and kernel ignores initrd. > There is an existing fixup logic to modify the address in the proper > configuration, but this is disabled at the moment. Enable the fixup > by setting the env variable for this so that initrd can be used > properly. > > Signed-off-by: Tero Kristo <t-kri...@ti.com> > Signed-off-by: Lokesh Vutla <lokeshvu...@ti.com> > --- > - This fixes boot on k2g platforms. > > include/configs/ti_armv7_keystone2.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/include/configs/ti_armv7_keystone2.h > b/include/configs/ti_armv7_keystone2.h > index ba12428dbe..1b014c1022 100644 > --- a/include/configs/ti_armv7_keystone2.h > +++ b/include/configs/ti_armv7_keystone2.h > @@ -213,6 +213,7 @@ > "tftp_root=/\0" \ > "nfs_root=/export\0" \ > "mem_lpae=1\0" \ > + "uinitrd_fixup=1\0" \ > "addr_ubi=0x82000000\0" \ > "addr_secdb_key=0xc000000\0" \ > "name_kern=zImage\0" \
OK, hold up. Why is any of this code needed and can't the normal bootm_size / bootm_low / etc as documented in the README enforce these constraints? Thanks! -- Tom
signature.asc
Description: PGP signature
