summaryrefslogtreecommitdiff
path: root/util/nvmutil/ChangeLog.md
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 /util/nvmutil/ChangeLog.md
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 'util/nvmutil/ChangeLog.md')
0 files changed, 0 insertions, 0 deletions