On 07/30/2015 01:00 PM, Simon Glass wrote:
Hi Stephen,
On 30 July 2015 at 12:47, Stephen Warren <swar...@wwwdotorg.org> wrote:
...
At least initially, we're targeting booting the system with the same
bootloader that L4T and Android use for unification. U-Boot runs after the
base security/... environment is set up to provide a flexible user
experience for untrusted OS loading. Hopefully this won't make flashing a
system too much more complex, but there will inevitably be some differences.
Hopefully it'll get mostly hidden by tegra-uboot-flasher or some other tool.
At some point I hope we'll be able to get U-Boot to act as the first stage
bootloader rather than just the non-secure bootloader. However, that
requires a lot more work so certainly isn't something that's in the first
round of Tegra210 support.
Thanks for the explanation. Booting ARM devices might get as hard as
x86 if we try really hard. Maybe we can add some run-time services as
well...good luck!
Well, at least PSCI is required by the ARM64 kernel now I believe, and
there's plenty of push for ACPI in some environments too, so I expect
the complexity will indeed converge!
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
