diff options
author | Simon Glass | 2020-04-26 09:13:00 -0600 |
---|---|---|
committer | Bin Meng | 2020-04-30 17:48:17 +0800 |
commit | 86ee14f58b9aff105c1f58aaab9a117664bd5618 (patch) | |
tree | e57c9ec9dff24118076fe16c7f8dd051137f184e /.azure-pipelines.yml | |
parent | cfe7a1068b4b84768dca82e81118d8bac9c4b8d5 (diff) |
x86: Use the existing stack when chain-loading
With chromebook_coral we normally run TPL->SPL->U-Boot. This is the
'bare metal' case.
When running from coreboot we put u-boot.bin in the RW_LEGACY portion
of the image, e.g. with:
cbfstool image-coral.serial.bin add-flat-binary -r RW_LEGACY \
-f /tmp/b/chromebook_coral/u-boot.bin -n altfw/u-boot \
-c lzma -l 0x1110000 -e 0x1110000
In this case U-Boot is run from coreboot (actually Depthcharge, its
payload) so we cannot access CAR. Use the existing stack instead.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to '.azure-pipelines.yml')
0 files changed, 0 insertions, 0 deletions