Tom
On Mon, 30 Jul 2018 at 15:10 Alexander Graf agraf@suse.de wrote:
On 07/30/2018 02:39 PM, Alexander Graf wrote:
On 07/30/2018 02:16 PM, David Rusling wrote:
Success. I now have a u-boot built on Arm64 that works. Along the way I learnt various things:
[1] Raspberry Pi's first stage loader generates the device tree. Overlays are used to turn various things on (for example sound) at boot time.
Yes. In order for those to propagate into U-Boot you will want to enable CONFIG_OF_BOARD. That way the first stage generated DT gets consumed by U-Boot as well. This allows you to run on CM3 or have the same U-Boot binary for B and B+ for example.
Thanks for the tip, I'll play
I forgot to mention that for this to work fully with propagation of that same device tree to an upstream kernel, you will also want to add the "upstream" overlay. Just add a line saying "dtoverlay=upstream" to config.txt. Then plug in any installer or image that is UEFI enabled (and works with DT) and it should boot.
Alex
OK, that was going to be my next step, thanks
David