libreboot
/
lbwww
1
0
Fork 0
Code Packages Projects Releases Activity

fix link 

Signed-off-by: Leah Rowe <leah@libreboot.org>
c20230710
Leah Rowe 2023-06-20 05:44:46 +01:00
parent 2d6bdc0d10
commit 9466f3e813
1 changed files with 6 additions and 5 deletions
site/news

11
site/news/microcode.md
View File

@ -22,11 +22,12 @@ mainboards supported in Libreboot (in `lbmk.git` and in releases) can boot
with entirely free software, requiring *zero* blobs of any kind from *coreboot*. with entirely free software, requiring *zero* blobs of any kind from *coreboot*.
The nuance of how Libreboot *implements* this policy is described in The nuance of how Libreboot *implements* this policy is described in
the [Freedom Status](freedom-status.md) page. Although coreboot (which Libreboot the [Freedom Status](../freedom-status.md) page. Although coreboot (which
uses for hardware initialisation) *is* a free software project, certain binary Libreboot uses for hardware initialisation) *is* a free software project,
blobs are needed on some platforms, for things like raminit (memory controller certain binary blobs are needed on some platforms, for things like raminit
initialisation). Libreboot tries to reduce or eliminate these, or mitigate (memory controller initialisation). Libreboot tries to reduce or eliminate
their existence (for example, `me_cleaner` is used on newer Intel platforms). these, or mitigate their existence (for example, `me_cleaner` is used on newer
Intel platforms).
One exception made in that policy is that CPU microcode updates *must* be One exception made in that policy is that CPU microcode updates *must* be
provided by default, on all x86 mainboards. The ARM platforms do not use provided by default, on all x86 mainboards. The ARM platforms do not use