1 <div class="jumbotron">
2 <h1 class="display-5">Welcome to Libre-SOC</h1>
4 <p>We're building a chip. A fast chip. A safe chip. A trusted chip.</p>
6 <p>A chip with lots of peripherals. And a VPU. And a 3D GPU...</p>
8 <p>Oh and here, have the <a href="http://git.libre-riscv.org">source code</a>...</p>
12 <h2 class="display-5">Why should I care?</h2>
14 With LibreSOC, you can take complex algorithms usually intended for
15 power hungry servers with big fat GPUs, and run them on tiny devices
16 like smartwatches, cellphones, and pocket drones without changing your
21 <h2 class="display-5">Hasn't Somebody Already Done This?</h2>
23 To the best of our knowledge, no. The closest systems would be ARM Cortex
24 devices which currently offer mediocre GPU and OpenCL support. Often
25 times, it is quite diffcult for customers to get their hands on the
26 drivers and install them due to their locked down nature. LibreSOC is
27 providing our own Free/Libre drivers. Easy as 1, 2, 3!
31 <h2 class="display-5">Does Open Hardware Really Work?</h2>
32 <p>A few names come to mind:</p>
35 <li><a href="https://www.raspberrypi.org">Raspberry Pi</a></li>
36 <li><a href="https://www.arduino.cc">Arduino</a></li>
37 <li><a href="https://www.raptorcs.com">Raptor Computing Systems</a></li>
38 <li><a href="https://www.bitcraze.io">CrazyFlie</a></li>
39 <li><a href="https://www.scopefun.com">ScopeFun</a></li>
43 <a class="btn btn-primary btn-lg" href="https://libre-soc.org/why_a_libresoc/" role="button">Learn more</a>
52 We are proud of our talented and diverse [team](about_us).
56 * [Purism](http://puri.sm) donates to us through [NLNet](nlnet)
58 * [Raptor CS](http://raptorcs.com) has given us access to a powerful
59 18-core 128 GB RAM TALOS II workstation, online.
63 If you would like to fund us, see [[funding]]. We currently have some
64 funding and always appreciate more! If you are a Corporation or an
65 individual you can donate tax-free to NLNet, and they can in turn gift
66 our developers. Contact lkcl@lkcl.net for more information.
68 If you want to write code with us, keep reading. If you want to *learn*
69 so that you can write code with us, see below. If there is anything else,
70 just get in touch on the list, there is plenty to do.
73 [mailing list](http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev),
74 introduce yourself (people will happily say "hello" back"). Read through
75 [recent posts](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/)
76 and the [[charter]], and let everyone know, on the list that you're
77 happy with it and agree to it.
78 2. The next thing you should do is read through the [bugs
79 list](http://bugs.libre-riscv.org) and see if there are any bugs that
81 3. After that, go ahead and take a look at the
82 [git repositories](https://git.libre-riscv.org).
83 Try and clone a repository with
84 ``git clone https://git.libre-riscv.org/git/repositoryname.git``
85 4. If you plan to do HDL work, you should familiarize yourself with our
87 5. We do have funding available (see [[nlnet]]) upon completion of issues -
88 we are also working on procuring more funding which gets the project to
89 nanometre scale tapeout.
90 6. After all this, if you feel that Libre-SOC is a something
91 that you would like to contribute to, add yourself to the
92 [current_members](about_us) page, fill in some information about yourself,
93 and join the mailing list and say hello.
95 Also note that you can edit this wiki. You can experiment in the [[Sandbox]].
99 The whole purpose of this project is to be a learning environment as well
100 as an actual business. If you want to learn how to do ASIC design, with
101 a view to contributing or starting your own ASIC business, start here:
102 [[3d_gpu/tutorial]]. Yes, really: do not let anyone tell you that you
103 can't learn this stuff too.
105 Along the way, if you find any [[resources]] or links that you found
106 particularly helpful, please add them to that page so that other people
107 can also benefit (and you have a place to remember them, too).
111 Most labor is currently being applied to developing the GPU portion of
114 The highest priority needed at the moment is a c++ engineer to work on
115 a MESA 3D driver. This will begin life similar to SwiftShader however
116 retaining the vectorisation and predication intrinsics as well as hardware
117 accelerated opcodes (all of which SwiftShader lacks)
119 Medium to long-term we need HDL engineers. Particularly those familiar
120 with nMigen or just python. Most of the techniques being used require
121 software engineering skills (OO design, polymorphism) than they do more
122 traditional HDL programming skills. Basically if you have experience in 2
123 of the following you'll do fine: python, nmigen, verilog/VHDL/gate-level
124 design. See [[HDL_workflow]]
126 Also, individuals with experience in formal mathematical verification