summaryrefslogtreecommitdiffstats
path: root/site/faq
diff options
context:
space:
mode:
Diffstat (limited to 'site/faq')
-rw-r--r--site/faq/index.php6
1 files changed, 6 insertions, 0 deletions
diff --git a/site/faq/index.php b/site/faq/index.php
index 0f60f9e..b0ee4f0 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -295,6 +295,12 @@
you had the source code. If you try to upload your own modified updates, the CPU will reject them. In other words,
the microcode updates are <em><a href="https://www.gnu.org/proprietary/proprietary-tyrants.html">tivoized</a></em>.
</p>
+ <p>
+ The microcode updates alter the way instructions behave on the CPU. That means they affect the way the CPU works, in
+ a very fundamental way. That makes it software. The updates are proprietary, and are software, so we exclude them from
+ libreboot. The microcode built into the CPU already is not so much of an issue, since we can't change it anyway (it's
+ read-only).
+ </p>
<h3 id="intelbastards">Intel is uncooperative <span class="r"><a href="#intelbastards">#intelbastards</a></span></h3>
<p>
For years, coreboot has been struggling against Intel. Intel has been shown to be extremely uncooperative in general.