summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2016-01-12 22:29:08 (EST)
committer Francis Rowe <info@gluglug.org.uk>2016-01-12 22:29:08 (EST)
commit3c95a777da129949aae9221adf2c7de96afc8a3f (patch)
tree00a46742a334b8109ff45574f3832e178938a325
parent58f63e572f376ef3cbb62901835c287eefbd198b (diff)
downloadlibreboot.org-3c95a777da129949aae9221adf2c7de96afc8a3f.zip
libreboot.org-3c95a777da129949aae9221adf2c7de96afc8a3f.tar.gz
libreboot.org-3c95a777da129949aae9221adf2c7de96afc8a3f.tar.bz2
fixlinks
-rw-r--r--site/faq/index.php12
1 files changed, 6 insertions, 6 deletions
diff --git a/site/faq/index.php b/site/faq/index.php
index b73ac2d..80200fc 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -377,7 +377,7 @@
severe security and freedom issues; so severe, that <em>the libreboot project recommends avoiding all modern AMD hardware.
If you have an AMD based system affected by the problems described below, then you should get rid of it as soon as possible</em>. The main issues are as follows:
</p>
- <h3 id="amdpsp">AMD Platform Security Processor (PSP) <span class="r"><a href="#amd">#amdpsp</a></span></h3>
+ <h3 id="amdpsp">AMD Platform Security Processor (PSP) <span class="r"><a href="#amdpsp">#amdpsp</a></span></h3>
<p>
This is basically AMD's own version of the <a href="#intelme">Intel Management Engine</a>. It has
all of the same basic security and freedom issues, although the implementation is wildly different.
@@ -413,11 +413,11 @@
would have the ability to remotely monitor and control any PSP enabled
machine. completely outside of the user's knowledge.
</p>
- <h3 id="amdimc">AMD IMC firmware <span class="r"><a href="#amd">#amdimc</a></span></h3>
+ <h3 id="amdimc">AMD IMC firmware <span class="r"><a href="#amdimc">#amdimc</a></span></h3>
<p>
Read <a href="https://www.coreboot.org/AMD_IMC">https://www.coreboot.org/AMD_IMC</a>.
</p>
- <h3 id="amdsmu">AMD SMU firmware <span class="r"><a href="#amd">#amdsmu</a></span></h3>
+ <h3 id="amdsmu">AMD SMU firmware <span class="r"><a href="#amdsmu">#amdsmu</a></span></h3>
<p>
Read <a href="https://www.coreboot.org/AMD_IMC">https://www.coreboot.org/AMD_IMC</a>.
</p>
@@ -433,20 +433,20 @@
free firmware, but on the relevant system (ASUS F2A85-M) there were still other blobs present (Video BIOS, and others) preventing
the hardware from being supported in libreboot.
</p>
- <h3 id="amdagesa">AMD AGESA firmware <span class="r"><a href="#amd">#amdagesa</a></span></h3>
+ <h3 id="amdagesa">AMD AGESA firmware <span class="r"><a href="#amdagesa">#amdagesa</a></span></h3>
<p>
This is responsible for virtually all core hardware initialization on modern AMD systems. In 2011,
AMD started cooperating with the coreboot project, releasing this as source code under a
free license. In 2014, they stopped releasing source code and started releasing AGESA
as binary blobs instead. This makes AGESA now equivalent to <a href="#intelfsp">Intel FSP</a>.
</p>
- <h3 id="amdmicrocode">AMD CPU microcode updates <span class="r"><a href="#amd">#amdmicrocode</a></span></h3>
+ <h3 id="amdmicrocode">AMD CPU microcode updates <span class="r"><a href="#amdmicrocode">#amdmicrocode</a></span></h3>
<p>
Read the Intel section <a href="#microcode">#microcode</a>. AMD's updates are practically the same, though
it was found with much later hardware in AMD that you could run without microcode updates. It's unknown
whether the updates are needed on all AMD boards (depends on CPU).
</p>
- <h3 id="amdbastards">AMD is incompetent (and uncooperative) <span class="r"><a href="#amd">#amdbastards</a></span></h3>
+ <h3 id="amdbastards">AMD is incompetent (and uncooperative) <span class="r"><a href="#amdbastards">#amdbastards</a></span></h3>
<p>
AMD seemed like it was on the right track in 2011 when it started cooperating with
and releasing source code for several critical components to the coreboot project.