X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=why_a_libresoc.mdwn;h=88e84944218ce98a70e1211611a31c32c7d0bf11;hb=b1331f37e6b41ac133f4286486a4af27b3f7fc1a;hp=bbe7795f12c8068acf91a040e83b900b9646be54;hpb=a66a63e5b9fddb1bd526fa582f6cd667863d0d4c;p=libreriscv.git diff --git a/why_a_libresoc.mdwn b/why_a_libresoc.mdwn index bbe7795f1..88e849442 100644 --- a/why_a_libresoc.mdwn +++ b/why_a_libresoc.mdwn @@ -1,39 +1,38 @@ -This page really needs more/better content! +# Why a Libre-SOC? -# Who we are and why a LibreSOC +## TLDR -Short paragraph on how a libreSOC makes sense from a business perspective... +We believe a computer should be safe to use, and this starts with a open processor. -see [[3d_gpu/business_objectives]] +We also believe that an open processor doesn't mean a weak processor. -# Our Gameplan +Check out our [mission](../The_Mission). -## Customer Discovery +## The Lengthier Explanation... -Who are our competitors(Intel, ARM, AMD?) +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). -Who might be on our side?(Samsung, IBM) +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). -What is our market size +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. -Why are they going to buy this and why are customers not satisfied with what already exists on the market +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? - - secure processors - safety critical applications like medical applications - - DARPA doesn’t have to order parts in bulk for big contracts for fear of obsolescence. DARPA can change designs more frequently… - - why is processor trust so important(SPECTRE MELTDOWN), JP Morgan recently replaced all their intel processors because of this +*Collaboration, not competition*. -## Customer Validation +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 Libre-SOC. -Give it to potential customer (who might be some direct customers? OnePlus Chinese Phone Manufacturers??) +* [1]: +* [2]: +* [3]: -Customer likes it. +# Benefits: Privacy, Safety-Critical, Peace of Mind... -Customer gives letter of intent that they will purchase this product. +Our Libre-SOC 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). -## Customer Creation +There is a very real need for reliable safety critical processors (think airplane, smart car, nuclear power plant, pacemaker...). +Libre-SOC posits that it is impossible to trust a processor in a safety critical environment without both access +to that processor's source, a cycle accurate HDL simulator that guarantees developers their code behaves as they +expect, and formal correctness proofs. An ISA level simulator is no longer satisfactory. -First customer leads to more customers. - -#Company Building - -Lots of customers = start focusing on building the company. +Refer to this [IEEE article](https://ieeexplore.ieee.org/document/4519604) by Cyberphysical System expert Ed-Lee for more details.