diff options
author | Simon Glass <sjg@chromium.org> | 2016-03-16 07:44:40 -0600 |
---|---|---|
committer | Bin Meng <bmeng.cn@gmail.com> | 2016-03-17 10:27:27 +0800 |
commit | e5aa8a9b1593f524af07318d4e84352b06a53402 (patch) | |
tree | e1890998f6f00e1e4f7f3a27f4012f3104ab9e88 /arch/sh/include/asm/string.h | |
parent | 69ca6fd85091518f592344be35b92ab23dd7fc9f (diff) | |
download | u-boot-imx-e5aa8a9b1593f524af07318d4e84352b06a53402.zip u-boot-imx-e5aa8a9b1593f524af07318d4e84352b06a53402.tar.gz u-boot-imx-e5aa8a9b1593f524af07318d4e84352b06a53402.tar.bz2 |
x86: Support a chained-boot development flow
Sometimes it is useful to jump into U-Boot directly from coreboot or UEFI
without any 16-bit init. This can help during development by allowing U-Boot
to avoid doing all the init required by the platform.
U-Boot expects its GDT to be set up correctly by its 16-bit code. If
coreboot doesn't do this (because it hasn't run the payload setup code yet)
then this won't happen.
In this case we cannot rely on the GDT settings. U-Boot will hang or crash
if these are wrong. Provide a development-only option to set up the GDT
correctly. This is just a hack so you can jump to U-Boot from any stage of
coreboot, not just at the end.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'arch/sh/include/asm/string.h')
0 files changed, 0 insertions, 0 deletions