summaryrefslogtreecommitdiff
path: root/script/build
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2023-12-23 06:54:56 +0000
committerLeah Rowe <leah@libreboot.org>2023-12-23 06:59:48 +0000
commitf44b99c808ed834dceea1109c34a2f587bb46a06 (patch)
tree414a31aeffb179a1f5d6ddfbe51593234bd5b061 /script/build
parent72cd169ee5ddc435a7742d7a05be1f59756a3aae (diff)
don't delete microcode updates in rom images
at present, lbmk can remove microcode updates on images for a given target, if the target specifies microcode_required="n" in target.cfg lbmk then provides images with microcode, and images without, in a given release. although the user can also remove them manually, this just makes it a bit more convenient, for those users who do wish to run without the updates. this functionality is provided only on those platforms where no-microcode is tested. well, this behaviour implements a compromise on libreboot policy, which is to always include microcode updates by default. see: Binary Blob Reduction Policy the *canoeboot* project now exists, developed in parallel with libreboot, and it ships without microcode updates, on the same targets where lbmk also handled this. running without microcode updates is foolish, and should not be encouraged. clean up lbmk by not providing this kludge. the libreboot documentation will be updated, telling such users to try canoeboot instead, or to remove the update from a given libreboot rom - this is still possible, and mitigations such as PECI disablement on GM45 are still in place (and will be kept), so that this continues to work well. Signed-off-by: Leah Rowe <leah@libreboot.org>
Diffstat (limited to 'script/build')
-rwxr-xr-xscript/build/roms19
1 files changed, 6 insertions, 13 deletions
diff --git a/script/build/roms b/script/build/roms
index 2926f297..f72b66b6 100755
--- a/script/build/roms
+++ b/script/build/roms
@@ -22,7 +22,7 @@ kmapdir="config/grub/keymap"
pv="payload_grub payload_grub_withseabios payload_seabios payload_memtest t"
pv="${pv} payload_seabios_withgrub payload_seabios_grubonly payload_uboot memtest_bin"
v="romdir cbrom initmode displaymode cbcfg targetdir tree arch"
-v="${v} grub_timeout ubdir vendorfiles board grub_scan_disk uboot_config"
+v="${v} grub_timeout ubdir board grub_scan_disk uboot_config"
eval "$(setvars "n" ${pv})"
eval "$(setvars "" ${v} boards _displaymode _payload _keyboard all targets)"
@@ -107,8 +107,6 @@ check_target()
payload_uboot="n"
[ "${payload_uboot}" = "y" ] && [ -z "${uboot_config}" ] && \
uboot_config="default"
- [ "${vendorfiles}" != "n" ] && [ "${vendorfiles}" != "y" ] && \
- vendorfiles="y"
# Override all payload directives with cmdline args
[ -z "${_payload}" ] && return 0
@@ -401,17 +399,12 @@ mkUbootRom() {
printf "%s\n" "${tmprom}"
}
-# it is assumed that no other work will be done on the ROM
-# after calling this function. therefore this function is "final"
-moverom() {
- rompath="${1}"
- newrom="${2}"
-
- [ "${vendorfiles}" = "n" ] && newrom="${newrom%.rom}_noblobs.rom"
- printf "Creating target image: %s\n" "${newrom}"
+moverom()
+{
+ printf "Creating target image: %s\n" "$2"
- x_ mkdir -p "${newrom%/*}"
- x_ cp "${rompath}" "${newrom}"
+ x_ mkdir -p "${2%/*}"
+ x_ cp "$1" "$2"
}
usage()