@satmandu thanks for the information! I'd got as far as figuring out the dram_init call was getting the available RAM info from the mailbox, which only permitted a single bank to be reported, which was then getting used in the fdt fixup called by the bootm. As it happens the fdt /memory node was already correct so there was no need for that particular fixup. Hence the hack applied for now is just to disable the fdt fixup.
Bumping to 2019.10 would be ideal, but unfortunately it's now too late in the cycle before release to re-test all the other platforms using u-boot. Still, it's useful to know that I can scrub that hack when we bump to 2019.10 (which we can probably do next cycle) - saves me digging further into it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847500 Title: Full RAM on Pi4 isn't accessible when using u-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1847500/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
