X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=index.mdwn;h=f9806a84fb36066ea65ea934b11977cbc07c624c;hb=3e7788c9b9b55e950670ff7c043225271f22a5fe;hp=3bfe8e095c228136f102bfc244e7b9f6b6fe5650;hpb=9d6594adcb4113b1b95b6594ad78ae054246d04c;p=libreriscv.git diff --git a/index.mdwn b/index.mdwn index 3bfe8e095..f9806a84f 100644 --- a/index.mdwn +++ b/index.mdwn @@ -1,101 +1,166 @@ -# Welcome to LibreSoC +
+

Welcome to Libre-SOC

+
+

We're building a chip. A fast chip. A safe chip. A trusted chip.

-> We're building a chip. A fast chip. A safe chip. A trusted chip. +

A chip with lots of peripherals. And a VPU. And a 3D GPU...

-> A chip with lots of peripherals. And a gpu. And an AI accelerator... +

Oh and here, have the source code...

+
+
-> Oh and here, have the source code... +

Why should I care?

-Sounds cool? Learn more [here](who_we_are) +With Libre-SOC, you can take complex algorithms usually intended for +power hungry servers with big fat GPUs, and run them on tiny devices +like smartwatches, cellphones, and pocket drones without changing your +code at all. -## [[our team | current_members]] +
-# Join us in Realizing the First Market Ready LibreSOC! +

Hasn't Somebody Already Done This?

-1. First, join the -[mailing list](http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev), -introduce yourself, and read through -[recent posts](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/) -and the [[charter]]. +To the best of our knowledge, no. The closest systems would be ARM Cortex +devices which currently offer mediocre GPU and OpenCL support. Often +times, it is quite difficult for customers to get their hands on the +drivers and install them due to their locked down nature. Libre-SOC is +providing our own Free/Libre drivers. Easy as 1, 2, 3! -2. The next thing you should do is read through the [bugs -list](http://bugs.libre-riscv.org) and see if there are any bugs that -pique your interest. +
-3. After that, go ahead and take a look at the resources section below. -Try and clone a repository with ``git clone https://git.libre-riscv.org/git/repositoryname.git`` +

Does Open Hardware Really Work?

+

A few names come to mind:

-4. If you plan to do HDL work, you should familiarize yourself with our [[HDL_workflow]]. + -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. +

+ Learn more -6. After all this, if you feel that Libre-SoC is a good cause that -you would like to contribute to, add yourself to the [[current_members]] -page, fill in some information about yourself, and join the mailing list -and say hello. +

-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. +# Our Team -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 -retaining the vectorisation and predication intrinsics as well as hardware accelerated opcodes (all of which SwiftShader lacks) +We are proud of our talented and diverse [team](about_us). -Medium to long-term we need HDL engineers. Particularly those familiar -with nMigen or just python. Most of the techniques being used require -software engineering skills (OO design, polymorphism) than they do more -traditional HDL programming skills. Basically if you have experience in 2 -of the following you'll do fine: python, nmigen, verilog/VHDL/gate-level -design. See [[HDL_workflow]] +# Our sponsors and partners -Also, individuals with experience in formal mathematical verification -are quite welcome. +* [Purism](http://puri.sm) donates to us through [NLNet](nlnet) + charitable gifting +* [Raptor CS](http://raptorcs.com) has given us access to a powerful + 18-core 128 GB RAM TALOS II workstation, online. +* [Raptor Engineering](https://raptorengineering.com) is providing + additional assistance including access to an [[shakti/m_class/LPC]] + interface (more to come) +* [MarketNext](http://marketnext.org) is helping us connect to developer + resources in Emerging markets, for completion of NLNet-funded tasks. + See the upcoming [Hackathon](https://www.youtube.com/embed/Px6eakWja3Q"), + deadline May 15th +* The [[PowerPC Notebook]] Project -TODO: add a list of upcoming project tasks/milestones (link to -bugtracker). +# How Can I Help? -# Resources +If you would like to fund us, see [[funding]]. We currently have some +funding and always appreciate more! If you are a Corporation or an +individual you can donate tax-free to NLNet, and they can in turn gift +our developers. Contact lkcl@lkcl.net for more information. -| Resource | Link | -| --- | --- | -| Bugs and Tasks | | -| Mailing Lists | | -| Archives | | -| Git repositories | | -| Kazan (Vulkan driver) | | -| Further Information | [[resources]] | +# How Can I Help as a Developer? -# Main Pages +If you want to write code with us (and receive donations from NLNet +for doing so), keep reading. If you want to *learn* +so that you can write code with us, see "How can I learn" section, +below. If there is anything else, +just get in touch on the list, there is plenty to do. -* Libre-SoC [[charter]] -* [[shakti/m_class]] -* [[alt_rvp]] -* [[3d_gpu]] -* [[vpu]] -* [[simple_v_extension]] -* [[zfpacc_proposal]] -* [[ztrans_proposal]] -* [[simple_v_extension/specification/mv.x]] -* [[simple_v_extension/specification/ld.x]] -* Specifications and [[resources]] +1. First, join the + [mailing list](http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev), + introduce yourself (people will happily say "hello" back"). Read through + [recent posts](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/) + and the [[charter]], and let everyone know, on the list that you're + happy with it and agree to it. +2. The next thing you should do is read through the + [bugs list](http://bugs.libre-riscv.org) and + see if there are any bugs that pique your interest. + A fascinating way to do that is to view the + [dependency graph](https://bugs.libre-soc.org/showdependencygraph.cgi?id=1&display=web&rankdir=LR) +3. After that, go ahead and take a look at the + [git repositories](https://git.libre-riscv.org). +4. If you plan to do HDL work, you should familiarize yourself with our + [[HDL_workflow]]. If you would like to help with the ASIC layout, + see [[HDL_workflow/coriolis2]] +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 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. + +Also note that you can edit this wiki. You can experiment in the [[Sandbox]]. + +## Quick peek at the code + +Here is an example process of how to play with the soc code: + + pip3 install virtualenv requests + mkdir ~/.virtualenvs && cd ~/.virtualenvs + python3 -m venv libresoc + source ~/.virtualenvs/libresoc/bin/activate + + cd ~; mkdir libresoc; cd libresoc + git clone https://git.libre-soc.org/git/nmutil.git + git clone https://git.libre-soc.org/git/ieee754fpu.git + git clone https://git.libre-soc.org/git/soc.git + + cd nmutil; make install; cd .. + cd ieee754fpu; make install; cd .. + cd soc; make gitupdate; make install; cd .. + + python3 soc/src/soc/decoder/power_decoder.py + yosys -p "read_ilang decoder.il; show dec31" + +## How can I learn? + +The whole purpose of this project is to be a learning environment as well +as an actual business. If you want to learn how to do ASIC design, with +a view to contributing or starting your own ASIC business, start here: +[[3d_gpu/tutorial]]. Yes, really: do not let anyone tell you that you +can't learn this stuff too. + +Along the way, if you find any [[resources]] or links that you found +particularly helpful, please add them to that page so that other people +can also benefit (and you have a place to remember them, too). -# Spike Emulator -* [Set-Up Instructions][1] +## Needed Skills -[1]: https://libre-riscv.org/3d_gpu/spike_sv/ +Most labor is currently being applied to developing the GPU portion of +the Libre-SOC. -# Wiki Structure +Our highest priority short-term and medium-term: we need HDL engineers. +Particularly those familiar +with nMigen or just python. Most of the techniques being used require +software engineering skills (OO design, polymorphism) than they do more +traditional HDL programming skills. Basically if you have experience in 2 +of the following you'll do fine: python, nmigen, verilog/VHDL/gate-level +design. See [[HDL_workflow]] -This is a publicly editable wiki. +We also need to find a c++ engineer with compiler experience to work on +a MESA 3D driver. This will begin life similar to SwiftShader however +retaining the vectorisation and predication intrinsics as well as hardware +accelerated opcodes (all of which SwiftShader lacks) -All wikis are supposed to have a [[SandBox]], so this one does too. +Also, individuals with experience in formal mathematical verification +are quite welcome. -This wiki is powered by [[ikiwiki]]. +# Documentation -This is the sitemap: [[sitemap]] + - [Source Code](/Documentation/index) + - [Architecture](3d_gpu/architecture)