From 690f74608558afa8fd8efe898060740f5927fe84 Mon Sep 17 00:00:00 2001 From: Jacob Lifshay Date: Sun, 16 Feb 2020 01:58:37 -0800 Subject: [PATCH] change Libre-SOC spelling to consistently use results of bug #180 --- HDL_workflow.mdwn | 2 +- charter.mdwn | 2 +- future_feature_proposals.mdwn | 2 +- index.mdwn | 10 +++++----- lkcl.mdwn | 2 +- mnolan.mdwn | 2 +- nlnet.mdwn | 2 +- nlnet_2019_amdvlk_port.mdwn | 2 +- tplaten.mdwn | 2 +- who_we_are.mdwn | 12 ++++++------ why_a_libresoc.mdwn | 8 ++++---- 11 files changed, 23 insertions(+), 23 deletions(-) diff --git a/HDL_workflow.mdwn b/HDL_workflow.mdwn index 14b845b4a..e39078260 100644 --- a/HDL_workflow.mdwn +++ b/HDL_workflow.mdwn @@ -1,7 +1,7 @@ # HDL workflow This section describes the workflow and some best practices for developing -the Libre-SoC hardware. We use nmigen, yosys and symbiyosys, and this +the Libre-SOC hardware. We use nmigen, yosys and symbiyosys, and this page is intended not just to help you get set up, it is intended to help advise you of some tricks and practices that will help you become effective team contributors. diff --git a/charter.mdwn b/charter.mdwn index 054e9d9d0..b7b69da78 100644 --- a/charter.mdwn +++ b/charter.mdwn @@ -1,4 +1,4 @@ -# Libre-SoC Charter Agreement +# Libre-SOC Charter Agreement * Draft Status (v0) * Last Edited: 11 Aug 2019 diff --git a/future_feature_proposals.mdwn b/future_feature_proposals.mdwn index 82b2548a2..78b57170c 100644 --- a/future_feature_proposals.mdwn +++ b/future_feature_proposals.mdwn @@ -1,6 +1,6 @@ # AI Acceleration -As mentioned earlier - it may be time to consider adding AI support in the form of NLP and CNN accelerators to LibreSOC. +As mentioned earlier - it may be time to consider adding AI support in the form of NLP and CNN accelerators to Libre-SOC. ## List of Ethical concerns related to CNN Accelerators - training a CNN to discriminate against people you diff --git a/index.mdwn b/index.mdwn index f7def914b..b07c7ddee 100644 --- a/index.mdwn +++ b/index.mdwn @@ -1,4 +1,4 @@ -# Welcome to LibreSOC +# Welcome to Libre-SOC > We're building a chip. A fast chip. A safe chip. A trusted chip. @@ -6,7 +6,7 @@ > Oh and here, have the source code... -Sounds cool? Learn more about the [why](why_a_libresoc) behind LibreSOC +Sounds cool? Learn more about the [why](why_a_libresoc) behind Libre-SOC and [our mission](The_Mission). # Our Team @@ -38,7 +38,7 @@ Try and clone a repository with 5. We do have funding available (see [[nlnet]]) upon completion of issues - we are also working on procuring more funding which gets the project to nanometre scale tapeout. -6. After all this, if you feel that Libre-SoC is a something that +6. After all this, if you feel that Libre-SOC is a something that you would like to contribute to, add yourself to the [current_members](about_us) page, fill in some information about yourself, and join the mailing list and say hello. @@ -48,7 +48,7 @@ Also note that you can edit this wiki. See the last section of this page. ## Needed Skills Most labor is currently being applied to developing the GPU portion of -the Libre-SoC. +the Libre-SOC. The highest priority needed at the moment is a c++ engineer to work on a MESA 3D driver. This will begin life similar to SwiftShader however @@ -82,7 +82,7 @@ bugtracker). # Main Pages -* Libre-SoC [[charter]] +* Libre-SOC [[charter]] * [[shakti/m_class]] * [[alt_rvp]] * [[3d_gpu]] diff --git a/lkcl.mdwn b/lkcl.mdwn index 7870f1e34..c1c80fae2 100644 --- a/lkcl.mdwn +++ b/lkcl.mdwn @@ -1,6 +1,6 @@ # Luke Kenneth Casson Leighton -Lead dev and Project Coordinator for LibreSOC. +Lead dev and Project Coordinator for Libre-SOC. # Status tracking diff --git a/mnolan.mdwn b/mnolan.mdwn index f388376d1..e21470af1 100644 --- a/mnolan.mdwn +++ b/mnolan.mdwn @@ -1,6 +1,6 @@ # Michael Nolan -Bored college student and contributor to LibreSOC +Bored college student and contributor to Libre-SOC # Status Tracking ## Currently working on diff --git a/nlnet.mdwn b/nlnet.mdwn index bdbdcc9ed..e119ea5aa 100644 --- a/nlnet.mdwn +++ b/nlnet.mdwn @@ -12,7 +12,7 @@ The process is as follows: * Accepted proposals submit a Project Plan listing a set of milestones, each of which has a fixed budget associated with it (note: not an hourly rate!) * The Project Plan becomes part of a Memorandum of Understanding, signed by the team (note: not a contract!) * On 100% completion of tasks *or subtasks* (which must add up ultimately to the total allocated budget) after approval by the project leader, an rfp (Request for Payment) is submitted by email to nlnet. -* The rfp is paid directly by bank transfer from NLNet *not by the Libre SoC project* +* The rfp is paid directly by bank transfer from NLNet *not by the Libre-SOC project* Note that the lack of hourly rate and the lack of contractual obligation is what enables this to be considered charitable donations (and why Corporations may not be paid or involved). diff --git a/nlnet_2019_amdvlk_port.mdwn b/nlnet_2019_amdvlk_port.mdwn index d81fcb3b5..6fc3d7b53 100644 --- a/nlnet_2019_amdvlk_port.mdwn +++ b/nlnet_2019_amdvlk_port.mdwn @@ -189,4 +189,4 @@ all picked up the story. The list is updated and maintained here: # Management Summary -The Libre SoC Project core is funded from an initial 2018 proposal. This includes a 3D Driver, called Kazan, and its purpose is to provide a Vulkan compliant hybrid hardware-software API. Given the complex nature of 3D driver development, and because Kazan is a novel approach (written in rust, for security reasons) a second oroposal was submitted to develop a Mesa3D driver (in c++). A second more traditional (c++) 3D Driver allows for increased transparency and collaboration on this ambitious project. +The Libre-SOC Project core is funded from an initial 2018 proposal. This includes a 3D Driver, called Kazan, and its purpose is to provide a Vulkan compliant hybrid hardware-software API. Given the complex nature of 3D driver development, and because Kazan is a novel approach (written in rust, for security reasons) a second oroposal was submitted to develop a Mesa3D driver (in c++). A second more traditional (c++) 3D Driver allows for increased transparency and collaboration on this ambitious project. diff --git a/tplaten.mdwn b/tplaten.mdwn index 672fe3cb4..4a4c870d8 100644 --- a/tplaten.mdwn +++ b/tplaten.mdwn @@ -1,6 +1,6 @@ # Tobias Platen -New contributor to LibreSOC (since 2019) +New contributor to Libre-SOC (since 2019) # Status tracking diff --git a/who_we_are.mdwn b/who_we_are.mdwn index d69ffd630..a14e1813f 100644 --- a/who_we_are.mdwn +++ b/who_we_are.mdwn @@ -7,7 +7,7 @@ providing the customer the **freedom to study, modify, and redistribute** the full SoC source from HDL and boot loader to down to the VLSI. -## LibreSOC is currently targeting: +## Libre-SOC is currently targeting: - chromebooks - smartphones @@ -18,7 +18,7 @@ a (quad core, 800mhz, dual issue, GPU, VPU, [and later an ML inference core] ) SOC. -## Why a Libre SOC? +## Why a Libre-SOC? 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). @@ -26,13 +26,13 @@ There are entire [dissertations](http://www.kroening.com/diss/diss-kroe.pdf) ded 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. -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. +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. ## Benefits: Privacy, Safety-Critical, Peace of Mind... -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). +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). There is a very real need for reliable safety critical processors (think airplane, smart car, nuclear power plant, pacemaker...). -LibreSOC posits that it is impossible to trust a processor in a safety critical environment without both access +Libre-SOC posits that it is impossible to trust a processor in a safety critical environment without both access to that processor's source and a cycle accurate HDL simulator that guarantees developers their code behaves as they expect. An ISA level simulator is no longer satisfactory. @@ -40,7 +40,7 @@ Refer to this [IEEE article](https://ieeexplore.ieee.org/document/4519604) by Cy ## Still Have Questions? -Read about the business and practical benefits of a LibreSOC below. +Read about the business and practical benefits of a Libre-SOC below. [[why_a_libresoc]] diff --git a/why_a_libresoc.mdwn b/why_a_libresoc.mdwn index da41fe563..61b2fb212 100644 --- a/why_a_libresoc.mdwn +++ b/why_a_libresoc.mdwn @@ -1,4 +1,4 @@ -## Why a Libre SOC? +## Why a Libre-SOC? 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). @@ -8,14 +8,14 @@ Given the fact that performant bug-free processors no longer exist, how can you *Collaboration, not competition*. -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. +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. ## Benefits: Privacy, Safety-Critical, Peace of Mind... -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). +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). There is a very real need for reliable safety critical processors (think airplane, smart car, nuclear power plant, pacemaker...). -LibreSOC posits that it is impossible to trust a processor in a safety critical environment without both access +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. -- 2.30.2