add chicken pic
[libreriscv.git] / why_a_libresoc.mdwn
1 ## Why a Libre SOC?
2
3 Its quite hard to guarantee that a performant processors (think pipelined, out-of-order) are functionally perfectly correct. In fact, it often turns out that they [aren’t](https://meltdownattack.com).
4
5 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).
6
7 Given the fact that performant bug-free processors no longer exist, 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 and improve them.
8
9 Such a processor is referred to as a Libre processor. However, processors themselves are only a part of the picture. Nowadays, most contemporary computing tasks involve artificial intelligence, media consumption, wireless connectivity, etc... Thus, we must deliver an entire LibreSOC.
10
11 ## Benefits: Privacy, Safety-Critical, Peace of Mind...
12 Our LibreSOC will not have backdoors that plague modern [processors](https://www.csoonline.com/article/3220476/researchers-say-now-you-too-can-disable-intel-me-backdoor-thanks-to-the-nsa.html).
13
14 There is a very real need for reliable safety critical processors (think airplane, smart car, nuclear power plant, pacemaker...).
15 LibreSOC posits that it is impossible to trust a processor in a safety critical environment without both access
16 to that processor's source and a cycle accurate HDL simulator that guarantees developers their code behaves as they
17 expect. An ISA level simulator is no longer satisfactory.
18
19 Refer to this [IEEE article](https://ieeexplore.ieee.org/document/4519604) by Cyberphysical System expert Ed-Lee for more details.