summaryrefslogtreecommitdiffstats
path: root/site/faq
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-07-28 07:58:15 (EDT)
committer Francis Rowe <info@gluglug.org.uk>2015-07-28 07:58:15 (EDT)
commitc5b865de743f3b20efb62812b51bfd535fbcff67 (patch)
tree0e9ca86b26a8e524283ea97cce52a5fe9ca1168b /site/faq
parentce571135dd7c66b650fabc7a614f8b692f738d7f (diff)
downloadlibreboot.org-c5b865de743f3b20efb62812b51bfd535fbcff67.zip
libreboot.org-c5b865de743f3b20efb62812b51bfd535fbcff67.tar.gz
libreboot.org-c5b865de743f3b20efb62812b51bfd535fbcff67.tar.bz2
FAQ (FSP): emphasize the scope of the problem
Diffstat (limited to 'site/faq')
-rw-r--r--site/faq/index.php4
1 files changed, 2 insertions, 2 deletions
diff --git a/site/faq/index.php b/site/faq/index.php
index ea08eb3..b8cf02d 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -149,8 +149,8 @@
On all recent Intel systems, coreboot support has revolved around integrating a blob (for each system) called
the <i>FSP</i> (firmware support package), which handles most of the hardware initialization, including
memory initialization. At present, it is believed that this can be replaced, but it will require a lot
- of work on reverse engineering which will likely take many years. Intel distributes the FSP blob to
- firmware developers (including coreboot).
+ of work on reverse engineering which will likely take many years, even for the most skilled developer working full-time.
+ Intel distributes the FSP blob to firmware developers (including coreboot).
</p>
<h3>Intel is uncooperative</h3>
<p>