summaryrefslogtreecommitdiff
path: root/config/u-boot/gru_kevin
AgeCommit message (Collapse)Author
2024-01-21allow multitree projects to define xgcc treeLeah Rowe
let them specific it, rather than falling back to coreboot/default (can also be used for coreboot boards) Signed-off-by: Leah Rowe <leah@libreboot.org>
2023-12-27update/trees: further simplify crossgcc handlingLeah Rowe
arch no longer needs to be set, on multi-tree projects, and it has been renamed to xarch the new behaviour is: if xarch is set, treat it as a list of crossgcc targets and go through the list. set the first one as the target, for what lbmk builds, but build all of the defined crossgccc targets crossgcc_ada is now xlang, and defines which languages to build, rather than whether to build gcc-gnat Signed-off-by: Leah Rowe <leah@libreboot.org>
2023-12-21update/trees: simplified crossgcc handlingLeah Rowe
only call crossgcc for coreboot and u-boot, but use hostcc for everything else. simplify the checking of which architecture to compile for. "arch" in target.cfg files has been modified, to allow further simplification. without this patch, the logic currently only *barely* avoids using crossgcc on things like utils, and only works in practise because, in practise, lbmk only works on x86_64 anyway. the new logic, as per this patch, is simpler and more robust. Signed-off-by: Leah Rowe <leah@libreboot.org>
2023-10-14u-boot: gru: Do not persist EFI variablesAlper Nebi Yasak
By default U-Boot stores EFI variables in a ubootefi.var file in whatever EFI System Partition it finds, which would be a FAT filesystem. I'm occasionally finding out while testing that my ESPs somehow end up with a corrupted filesystem, and I'm suspecting it's this. For now, disable storing EFI environment variables on disk so that U-Boot doesn't try to manipulate the filesystem. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-10-14u-boot: gru: Enable more EFI commandsAlper Nebi Yasak
Enable U-Boot commands to manipulate EFI environment storage, to self-test EFI implementation, and to run a basic EFI test application. These are so that we can test and debug EFI functionality easier. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-10-14u-boot: gru: Enable more bootstd featuresAlper Nebi Yasak
U-Boot upstream is switching to a new code framework for discovering and booting OSes ("Standard Boot", or "bootstd"). Enable more features for it, including commands we can use for introspection and debugging. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-10-14u-boot: gru: Do not reset on panicAlper Nebi Yasak
Normally U-Boot immediately resets the board on a panic. I had run into "Synchronous Abort"s from shim and rEFInd, and having a traceback in those cases can be useful. Hang instead of resetting, so the panic reason stays on the screen. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-10-14u-boot: gru: Enable poweroff commandAlper Nebi Yasak
We should be able to power the board off from U-Boot command line. Enable the "poweroff" command for gru boards so we can. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-10-14u-boot: gru: Disable VIDEO_COPYAlper Nebi Yasak
U-Boot can keep a "copy" framebuffer to read from, for devices where reading from hardware framebuffer is expensive. This needs the video driver to support it. The Rockchip video driver doesn't need or support it, so this option does nothing on gru boards. Disable it. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-10-14u-boot: Set EFI variable buffer size to upstream valueAlper Nebi Yasak
U-Boot upstream used to have 16KB for EFI variables, and this was causing problems with shim. Commit f0236acbc663 ("u-boot: Increase EFI variable buffer size") fixed this by raising it to 32KB in our builds. It has now been raised to 64K upstream, so raise it here as well. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-10-14u-boot: Avoid building U-Boot-only binman imagesAlper Nebi Yasak
For Rockchip boards U-Boot tries to build SPI and MMC images that require an externally built BL31 file to be provided, and the build fails otherwise. This is not really as configurable as it should be. In Libreboot, we only care about the build outputs for U-Boot proper. There is a BL31 built during our coreboot builds, but using that in U-Boot builds is a chicken-and-egg problem. Building BL31 outside the coreboot build and passing it to both projects is possible, but needs work. For now, stop trying to build these U-Boot-only images as a workaround, by removing the binman image descriptions from the device-tree sources. Additionally, disable in our configs the BINMAN_FDT functionality that allows using these at runtime as it requires them to be present. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-10-14u-boot: Update to v2023.10Alper Nebi Yasak
Set default U-Boot revision to v2023.01 and rebase patches on top of that. Another series about 16x32 fonts was merged upstream, so drop some now-unnecessary patches we had for that. For the video damage tracking series, switch to the version I'm trying to upstream. Upstream kconfig status is a bit unstable, so updating configs with `make oldconfig` would miss important upstream changes, since they rely on carrying defaults via upstream defconfigs. Update the configs as such: - Turn old configs into defconfigs (./update project trees -s u-boot) - Save the diff from old upstream defconfig (diffconfig $theirs $ours) - Update U-Boot revision, rebase patches, and clean old trees - Prepare new U-Boot tree (./update project trees -f u-boot) - Review the diffconfigs to see if any options were renamed upstream - Copy over the new upstream defconfigs and apply earlier diff - Turn new defconfigs into configs (./update project trees -l u-boot) Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2023-09-04merge config/ and resources/Leah Rowe
Signed-off-by: Leah Rowe <leah@libreboot.org>