Message ID | 20200408185755.116336-1-sjg@chromium.org |
---|---|
Headers | show |
Series | x86: Improve support for chain-loading U-Boot | expand |
Hi Simon, On Thu, Apr 9, 2020 at 2:58 AM Simon Glass <sjg at 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. > > This series allows U-Boot to detect that it ran from coreboot and > automatically do the right thing. > > This series makes the most important changes to allow the same u-boot.bin > for coral to boot after coreboot (by itself) or bare metal (via TPL->SPL). > > Changes in v3: > - Add a new patch with a gd flag for chain loading > - Add new patch to detect running from coreboot Sorry it took me some time to have a look at this series. I have some comments against 5 & 6. Could you please update doc/arch/x86.rst for the purpose and usage of the chain loading? Regards, Bin