diff options
| author | Alper Nebi Yasak <alpernebiyasak@gmail.com> | 2022-12-09 14:50:03 +0300 |
|---|---|---|
| committer | Alper Nebi Yasak <alpernebiyasak@gmail.com> | 2022-12-10 14:19:00 +0300 |
| commit | 1c62b003ad6014288114300de65844496dffaf72 (patch) | |
| tree | 3d770553466d481f78668892b77999df56ab316c /resources/coreboot/x301_8mb/config/libgfxinit_txtmode | |
| parent | 6cabcec51d39a6d4c6176de4486a95cbb492fc24 (diff) | |
build/roms: Support using "u-boot" ELF file as U-Boot payload
U-Boot runtime configuration is done with a device-tree file, which is
built alongside the executable in the upstream build system, and must be
available to U-Boot at runtime.
This device-tree is normally not linked into the default "u-boot" ELF
file. So far we have been handling it by re-creating a "u-boot.elf" from
the raw binary parts by setting REMAKE_ELF, and using that as the
coreboot payload. Unfortunately, that fails to build for x86 boards,
more specificly the "coreboot" boards upstream.
It's also possible (but discouraged) to set OF_EMBED to embed the
device-tree file into the U-Boot itself, in which case we could use the
"u-boot" file as the payload on the "coreboot" boards. Add support for
using the "u-boot" file as the payload if "u-boot.elf" doesn't exist.
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Diffstat (limited to 'resources/coreboot/x301_8mb/config/libgfxinit_txtmode')
0 files changed, 0 insertions, 0 deletions