Hi.
I encountered some initrd issues I can't explain.
Using a 2023.05 and can't find any significant differences to master related to this.
Barebox iomem output looks like:
0x0000000000000000 - 0xffffffffffffffff (size 0x0000000000000000) iomem
0x0000000000000000 - 0x000000001fffffff (size 0x0000000020000000) ram0
0x000000000fe94000 - 0x000000001fe93fff (size 0x0000000010000000) malloc space
0x000000001fe94464 - 0x000000001fe9c463 (size 0x0000000000008000) stack
0x000000001fe9c464 - 0x000000001fefb32f (size 0x000000000005eecc) barebox
0x000000001fefb330 - 0x000000001ff1df0b (size 0x0000000000022bdc) barebox data
0x000000001fffc464 - 0x000000001fffefff (size 0x0000000000002b9c) bss
0x00000000e8000000 - 0x00000000efffffff (size 0x0000000008000000) cfi_flash0
0x00000000fe118000 - 0x00000000fe1180ff (size 0x0000000000000100) i2c-fsl0
0x00000000fe118100 - 0x00000000fe1181ff (size 0x0000000000000100) i2c-fsl1
0x00000000fe119000 - 0x00000000fe1190ff (size 0x0000000000000100) i2c-fsl2
0x00000000fe11c500 - 0x00000000fe11c50f (size 0x0000000000000010) ns16550_serial0
When loading a newer FIT image (Around 25M size) with 5.17 kernel, things work just fine.
Placement ends up at (kernel print):
Found initrd at 0xc111a000:0xc2458000
With an older image (slightly smaller) with a 4.11 kernel, placement ends up with kernel
not recognizing the initrd (squashfs).
Placement here ends up at:
Found initrd at 0xc097e000:0xc19c1000
Now if I hand pick the initrd loadaddr for the older itb, to the same as the newer one or just slightly bigger,
ie, 0x111a000 or 0x1200000. Then everything loads just fine.
I can't find anything relevant in barebox or u-boot regarding this.
There seems to be some 64M limit in ppclinux.c but that looks historical and does not make much sense to me.
Either way, it should be fine with the lower address.
Any hints would be much appreciated.
/Christian
