144e94bbb9b2049a9470a58d420dae51026fdb9c
[crowdsupply.git] / updates / 021_2019dec29_nlnet_grants_approved.mdwn
1 Across several projects, nearly EUR 400,000 worth of additional funding
2 applications were put in, and around EUR 200,000 to 250,000 of those have
3 been approved. The RISC-V Foundation's continued extreme unethical
4 actions have led us to consider using Power ISA.
5
6 ### NLnet Grants
7
8 [NLnet](http://nlnet.nl) were first approached eighteen months ago, with
9 an initial application to develop the core of a privacy-respecting trustable
10 processor. Whilst NLnet's primary focus of the past fifteen years has been
11 software, they have funded reverse-engineering for
12 [Osmocon BB](https://nlnet.nl/project/sdr-phy/) and for
13 [OpenBSC](https://nlnet.nl/project/iuh-openbsc/) so are no strangers to
14 hardware. The problem with software is: if the hardware cannot be trusted,
15 then no amount of trustable, open and transparent software will help.
16
17 The [additional proposals](https://libre-riscv.org/nlnet_proposals/)
18 expand on the core, to cover:
19
20 * formal mathematical correctness proofs for the entire processor, including
21 the FPU (no more Intel Pentium FPDIV bugs...)
22 * a special video acceleration focus, adding video decode instructions
23 * an additional 3D driver based on AMDVLK or MESA
24 * some funding to be able to properly develop and document ISA standards
25 * a Wishbone streaming enhancement to add A/V timecode stamps to Wishbone B4,
26 and to develop independent libre-licensed peripherals as examples
27 * two interrelated proposals to develop libre cell Libraries
28 ([Chips4Makers](http://chips4makers.io/)), to be used by a team at
29 [LIP6.fr](http://lip6.fr) using the Alliance / Coriolis2 ASIC layout
30 tools; Additional funding will go to the nmigen team for ASIC
31 improvements and special integration with Coriolis2
32
33 The goal here is to get to a working, commercially viable 180 nm
34 single-core ASIC at around 300 to 350 MHz, suitable for use as a
35 high-end embedded controller. Staf from Chips4Makers will act as the
36 "NDA firebreak" between us and TSMC. (Side note: Staf ran a [Crowd
37 Supply campaign](https://www.crowdsupply.com/chips4makers/retro-uc),
38 and the NLnet funding will help him to realise that project and
39 perhaps re-start a new campaign for the Retro-uC one day).
40
41 All of these have been approved by NLnet, and, crucially, the external
42 independent review process successfully completed for each. The exact
43 amounts of each grant is to be confirmed, with each being possible to be
44 up to the limit of EUR 50,000 for each sub-project.
45
46 Part of the process was a little tricky, initially: the independent reviewers
47 expressed surprise at the amounts being requested for *sub*-tasks when the
48 initial application back in December 2019 was so small, relative to
49 the intended goal. The reason was very simple: both Jacob
50 and I have unique low-income circumstances that simply do not need European /
51 Western style living expenses. Whereas, when we get to much more specialist
52 tasks (such as formal mathematical proofs, video assembly-level drivers,
53 and so on), these fields are so specialized that finding people who are good
54 *and* who are able to exist on student or southeast-asia-level funding is just not
55 practical.
56
57 Therefore, we made sure that the calculations were based around an approximate
58 EUR 3,000 per month budget per person, bearing in mind that due to NLnet's
59 international tax agreements, this being donations, that's equivalent to a
60 "wage" of approximately nearly twice that amount (three times if, as a
61 business, you have to take into consideration corporation tax / employee
62 insurance as well).
63
64 We now need to find people willing to help do the work. What is
65 really nice is that NLnet will donate money to them for completion of that work!
66 Therefore, if you've always wanted to work on a 3D processor, its drivers
67 and its source code, do get in touch.
68
69 ### PowerPC
70
71 This is a
72 [long story](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2019-October/003035.html)
73 that was picked up by
74 [Phoronix](https://www.phoronix.com/scan.php?page=news_item&px=Libre-RISC-V-Eyeing-POWER)
75 before we had a chance to make any kind of real "announcement." However,
76 we're always really grateful to Michael for his coverage of the Libre SoC,
77 as it always sparks some insightful, useful, and engaging discussions.
78
79 The summary is this: Libre and Open contributors to RISC-V have been
80 disregarded for several years. **Long** before I joined the RISC-V
81 mailing lists, it was *well-known* within that small and tightly-knit
82 community that if you were not associated directly with UC Berkeley, you were
83 basically not welcome. Caveat: if you signed the NDA-like agreement
84 which conflicts directly with, for example, the Debian Charter and
85 the whole purpose of libre licenses, then you got a "voice" and you
86 got access to the closed and secretive RISC-V resources and mailing
87 lists.
88
89 Michael puts it extremely well: I have absolutely no problem with the
90 ISA itself, it's the abuse of power and the flagrant ignoring and abuse
91 of basic tenets of trademark law that are just completely untenable.
92 Not only that: one well-paid employee of SiFive has *repeatedly* engaged
93 in defamation attacks for over eighteen months. Even raising a formal
94 complaint through the newly-established relationship with the Linux
95 Foundation failed to keep that individual under control. Also adversely
96 impacted was the newly-established Open Graphics Alliance initiative,
97 which was independently started by Pixilica back in October,
98 proposed at SIGGRAPH 2019 and welcomed by world-leading 3D industry
99 experts.
100
101 At some point you just have to appreciate that to continue to support
102 an unethical organisation is itself unethical, and thus I made the
103 decision to reach out to MIPS and Power. The MIPS website didn't even
104 work, so I gave up there immediately. The Open Power Foundation on
105 the other hand, I was both delighted and surprised to hear back from
106 a former colleague when I was in Canberra, 20 years ago: Hugh Blemings.
107
108 Hugh is extremely knowledgeable, highly intelligent, and completely
109 understands Libre and Open principles. We had only 15 minutes to
110 talk before he had to focus on preparing for the upcoming Open Power
111 Conference: in that short time, we covered:
112
113 * the need for ISANS / ISAMUX "breakout" system. Hugh even said,
114 without prompting, that the scheme I quickly described would
115 allow full software-level ISA emulation and that that was a really
116 good and necessary thing. With this **formally** in place as part
117 of an officially-approved Power ISA Standard, not only could our team
118 expand the Power ISA in a safe and controlled fashion, so could other
119 adopters of the Power ISA.
120 * that the core OpenPower members had *already been discussing* how to make
121 sure that new Libre teams with a commercial focus could join and not
122 have any transparency / patent / NDA / royalty / licensing conflicts
123 of interest. The only major thing that the other members particularly
124 wanted was a "public relations blackout period," right around the time
125 of announcement of new standards, which sounds perfectly reasonable
126 to me.
127 * that IBM will be providing a royalty-free unlimited license grant
128 for *all* of its patents, as long as firstly the licensees do not
129 make any effort to assert patents **against** IBM, and secondly,
130 as long as implementations are fully-compliant with the OpenPower
131 standards.
132 * that there is discussion underway as to the creation and maintenance
133 of formal compliance test suites, just as there is today with the
134 RISC-V ISA.
135 * that the use of a certification mark - not a service mark or a trade mark -
136 is the most appropriate thing for ISA standards. I mentioned this
137 only briefly however it takes a lot more than 15 minutes to properly
138 explain, so I am not going to push it: Hugh is doing so much fantastic
139 work already.
140
141 It was a very busy and positive conversation, where it is clear that
142 we caught them at just the right time in the process. Consequently,
143 my discussion with Hugh was just at the right time. Without that,
144 the existing OpenPower members might never have really truly believed
145 that any Libre **commercial** project would ever in fact come forward
146 and that the steps the OpenPower members were taking were purely hypothetical.
147 Out of the blue (pun intended), I contact Hugh and highlight that no,
148 it's not hypothetical.
149
150 The next step, then, will be to wait until mid-january when people come
151 back from holiday, and wait for the announcement of the OpenPower
152 license agreement. Hugh reassures me that there's nothing spectacularly
153 controversial in it, and given his long-standing experience of several
154 decades with the Libre and Open Communities, I cannot think of a reason
155 why it would not be possible to sign it. We just have to see.
156
157 The timing here with NLnet is just on the edge: we have to create a
158 full list of milestones and assign a fixed budget to each (then later
159 subdivide them into sub-tasks under that milestone). This is a leeeetle
160 bit challenging when we have not yet reviewed the OpenPower agreement,
161 however, given that the majority of the tasks are ISA-independent, it
162 will actually work out fine.
163
164 The only other major thing: what the heck do we do with the libre-riscv.org
165 domain? As you can see on the mailing list decision, we decided to go
166 with a *userspace* RV64GC dual-ISA front-end. **Userspace** RISC-V POSIX
167 (Linux / Android) applications will work perfectly well, as will **userspace**
168 PowerISA POSIX applications, however the **kernel** (supervisor) space will
169 be entirely PowerISA.
170
171 The video and 3D acceleration opcodes will be **entirely in the Power
172 ISA**. We are sick and tired of the RISC-V Foundation's intransigence
173 and blatant mismanagement. Therefore, we will comply to the absolute
174 minimal letter with RV64GC for the benefit of our users, backers, and
175 sponsors who will be expecting RISC-V Compliance. However, RISC-V and the
176 RISC-V ISA itself will no longer receive the benefit of the advancements
177 and innovation that we have received funding and support to develop.
178
179 So, the assembly-code being written by hand for the video acceleration
180 side, as well as the 3D drivers for Kazan and MESA, will "flip" from RV64GC
181 RISC-V over to the Power ISA, which will be fully 3D accelerated with advanced
182 Simple-V Vector operations, then return back to userspace RISC-V RV64GC ISA
183 to continue serving the user application.
184
185 Next steps for us include setting up a foundation under which the processor
186 can be developed, and to look towards the next major funding step: USD 10M
187 to 20M.