Hi Andy,
On Wed, 19 Feb 2020 at 02:37, Andy Shevchenko andy.shevchenko@gmail.com wrote:
On Wed, Feb 19, 2020 at 4:46 AM Simon Glass sjg@chromium.org wrote:
This little series adds a few checks into the code to allow better operation when booting a build from a previous-state loader such as coreboot.
At present we have a 'coreboot' target but this runs very different code from the bare-metal targets, such as coral. There is very little in common between them.
It is useful to be able to boot the same U-Boot on a device, with or without a first-stage bootloader. For example, with chromebook_coral, it is helpful for testing to be able to boot the same U-Boot (complete with FSP) on bare metal and from coreboot. It allows checking of things like CPU speed, comparing registers, ACPI tables and the like.
The idea is to change ll_boot_init() to false, and rebuild without changing anything else.
This series makes the most important changes to allow coral to boot on coreboot.
Is there any patchwork instance or branch which I may use for testing?
Yes I always push to u-boot-dm before sending.
This one is in branch cor3chain-working
It will be collected into patchwork automatically, normally a few minutes after sending.
Regards, Simon