lbmk.git/config/coreboot/ga_g41m_es2l, branch quackboot libreboot build system (LibreBoot MaKe) coreboot: set build_depend on target.cfg files 2024-07-06T10:34:27+00:00 Leah Rowe leah@libreboot.org 2024-07-06T05:34:24+00:00 c241a3ef485fcfde06f60abaf7e16bc5c549e53b set a default one in mkhelper.cfg Signed-off-by: Leah Rowe <leah@libreboot.org> 
set a default one in mkhelper.cfg

Signed-off-by: Leah Rowe <leah@libreboot.org>
roms: don't insert timeout.cfg 2024-06-19T13:32:42+00:00 Leah Rowe leah@libreboot.org 2024-06-19T13:32:42+00:00 893e88bc814966d88a313d2c6d3a53d6ee54c9fb this is bloat, because it's something the user can already do at runtime configuration anyway. set it to a reasonable default of 8 seconds instead of 5, and don't honour the timeout variable in target.cfg. this will be documented in the next release. Signed-off-by: Leah Rowe <leah@libreboot.org> 
this is bloat, because it's something the user can already
do at runtime configuration anyway.

set it to a reasonable default of 8 seconds instead of 5,
and don't honour the timeout variable in target.cfg.

this will be documented in the next release.

Signed-off-by: Leah Rowe <leah@libreboot.org>
grub: only enable nvme if needed on a board 2024-06-11T23:58:22+00:00 Leah Rowe leah@libreboot.org 2024-06-11T23:58:22+00:00 0b37653ab908093a108cfe3cbcb4e8d378428d26 remove nvme support from the "default" grub tree now there are three trees: * default: no xhci or nvme patches * nvme: contains nvme support * xhci: contains xhci and nvme support this is in case a bug like lbmk issue #216 ever occurs again, as referenced before during lbmk audit 5 there is no indication that the nvme patch causes any issues, but after previous experience i want to be sure Signed-off-by: Leah Rowe <leah@libreboot.org> 
remove nvme support from the "default" grub tree

now there are three trees:

* default: no xhci or nvme patches
* nvme: contains nvme support
* xhci: contains xhci and nvme support

this is in case a bug like lbmk issue #216 ever occurs
again, as referenced before during lbmk audit 5

there is no indication that the nvme patch causes any
issues, but after previous experience i want to be sure

Signed-off-by: Leah Rowe <leah@libreboot.org>
do not allow dashes in coreboot target names 2024-05-29T02:15:25+00:00 Leah Rowe leah@libreboot.org 2024-05-29T02:15:25+00:00 e7cb10d68b46bd4efb9a87c36d337f8a4fe1e24c Command: ./vendor download kcma-d8-rdimm_16mb Output was: include/lib.sh: line 115: kcma-d8-rdimm=config/vendor: No such file or directory That will have to be audited later on, but the recent more stringent error checking in vendor.sh triggered this previously untriggered error message. The error was in fact already occuring before, silently. Anyway, mitigate by renaming all coreboot targets so that they do not contain hyphens in the name. This should avoid triggering errors in that eval command, on line 115 in lib.sh Signed-off-by: Leah Rowe <leah@libreboot.org> 
Command: ./vendor download kcma-d8-rdimm_16mb

Output was:

include/lib.sh: line 115: kcma-d8-rdimm=config/vendor: No such file or directory

That will have to be audited later on, but the recent
more stringent error checking in vendor.sh triggered
this previously untriggered error message. The error
was in fact already occuring before, silently.

Anyway, mitigate by renaming all coreboot targets so
that they do not contain hyphens in the name. This
should avoid triggering errors in that eval command,
on line 115 in lib.sh

Signed-off-by: Leah Rowe <leah@libreboot.org>