bug 1244: add sv.lbz ffirst image

[libreriscv.git] / why_a_libresoc.mdwn

diff --git a/why_a_libresoc.mdwn b/why_a_libresoc.mdwn
index bf05b7ba83087096ca9a9ac268c81586f4918bd4..88e84944218ce98a70e1211611a31c32c7d0bf11 100644 (file)
--- a/why_a_libresoc.mdwn
+++ b/why_a_libresoc.mdwn
@@ -1,10 +1,22 @@
 # Why a Libre-SOC?
 
+## TLDR
+
+We believe a computer should be safe to use, and this starts with a open processor.
+
+We also believe that an open processor doesn't mean a weak processor.
+
+Check out our [mission](../The_Mission).
+
+## The Lengthier Explanation...
+
 Its quite hard to guarantee that performant processors (think pipelined, out-of-order) are functionally perfectly correct. In fact, it often turns out that they [aren’t](https://meltdownattack.com).
 
 There are entire [dissertations](http://www.kroening.com/diss/diss-kroe.pdf) dedicated to the subject matter of merely functionally verifying a pipeline (this doesn’t even consider out of order execution).
 
-Given the fact that performant bug-free processors no longer exist [1][2], how can you trust your processor? The next best thing is to have access to a processor’s design files. Not only have access to them, you must have the freedom to study, improve them, run the test suites and be able to improve those too.  Not only that, you and everyone who has a stake in the success needs to be entirely free from NDAs and other restrictions which prevent and prohibit communication.
+Given the fact that performant bug-free processors no longer exist [1][2], how can you trust your processor [3]? The next best thing is to have access to a processor’s design files. Not only have access to them, you must have the freedom to study, improve them, run the test suites and be able to improve those too.
+
+Not only that, you and everyone who has a stake in the success needs to be entirely free from NDAs and other restrictions which prevent and prohibit communication.  An example: although you yourself might not have the technical capability to review our SoC, you can always find a third party to pay those who can.  However if the source code was under NDA, do you think that would be practical to consider?
 
 *Collaboration, not competition*.
 
@@ -12,6 +24,7 @@ Such a processor is referred to as a Libre processor. However, processors themse
 
 * [1]: <https://it.slashdot.org/story/20/03/09/2347202/amd-processors-from-2011-to-2019-vulnerable-to-two-new-attacks>
 * [2]: <https://it.slashdot.org/story/20/03/10/176200/intel-cpus-vulnerable-to-new-lvi-attacks#comments>
+* [3]: <https://libreboot.org/faq.html#intelme>
 
 # Benefits: Privacy, Safety-Critical, Peace of Mind...