* a Wishbone streaming enhancement to add A/V timecode stamps to Wishbone B4,
and to develop independent libre-licensed peripherals as examples
* two interrelated proposals to develop libre cell Libraries
- ([Chips4Makers](http://chips4makers.be)), to be used by a team at
+ ([Chips4Makers](http://chips4makers.io/)), to be used by a team at
[LIP6.fr](http://lip6.fr) using the Alliance / Coriolis2 ASIC layout
tools; Additional funding will go to the nmigen team for ASIC
improvements and special integration with Coriolis2
-The goal here is to get to a working, commercially viable 180 nm single-core
-ASIC at around 300 to 350 MHz, suitable for use as a high-end embedded
-controller. Staf from Chips4Makers will act as the "NDA firebreak" between
-us and TSMC.
-(side-note: Staf ran a
-[Crowdsupply](https://www.crowdsupply.com/chips4makers/retro-uc)
-campaign, and the NLNet funding will help him to realise that project and
+The goal here is to get to a working, commercially viable 180 nm
+single-core ASIC at around 300 to 350 MHz, suitable for use as a
+high-end embedded controller. Staf from Chips4Makers will act as the
+"NDA firebreak" between us and TSMC. (Side note: Staf ran a [Crowd
+Supply campaign](https://www.crowdsupply.com/chips4makers/retro-uc),
+and the NLNet funding will help him to realise that project and
perhaps re-start a new campaign for the Retro-uC one day).
All of these have been approved by NLNet, and, crucially, the external
* that the core OpenPower members had *already been discussing* how to make
sure that new Libre teams with a commercial focus could join and not
have any transparency / patent / NDA / royalty / licensing conflicts
- of interest. The only major thing that the other members wanted was
- a "public relations blackout period," right around the time of announcement of
- new standards, which sounds perfectly reasonable to me.
+ of interest. The only major thing that the other members particularly
+ wanted was a "public relations blackout period," right around the time
+ of announcement of new standards, which sounds perfectly reasonable
+ to me.
* that IBM will be providing a royalty-free unlimited license grant
for *all* of its patents, as long as firstly the licensees do not
make any effort to assert patents **against** IBM, and secondly,
* that the use of a certification mark - not a service mark or a trade mark -
is the most appropriate thing for ISA standards. I mentioned this
only briefly however it takes a lot more than 15 minutes to properly
- explain, so I am not going to push it: Hugh is doing so much already.
+ explain, so I am not going to push it: Hugh is doing so much fantastic
+ work already.
It was a very busy and positive conversation, where it is clear that
-we caught them right at the beginning of the process. Consequently,
+we caught them at just the right time in the process. Consequently,
my discussion with Hugh was just at the right time. Without that,
the existing OpenPower members might never have really truly believed
that any Libre **commercial** project would ever in fact come forward
PowerISA POSIX applications, however the **kernel** (supervisor) space will
be entirely PowerISA.
-The video and 3D acceleration opcodes will be **entirely in the Power ISA**.
-We are sick and tired of the RISC-V Foundation's blatant mismanagement.
-Therefore, we will comply to the absolute minimal letter with RV64GC for
-the benefit of our users, backers, and sponsors. However, RISC-V and the
-RISC-V ISA itself
-will no longer receive the benefit of the advancements and innovation
-that we have received funding and support to develop.
+The video and 3D acceleration opcodes will be **entirely in the Power
+ISA**. We are sick and tired of the RISC-V Foundation's intransigence
+and blatant mismanagement. Therefore, we will comply to the absolute
+minimal letter with RV64GC for the benefit of our users, backers, and
+sponsors who will be expecting RISC-V Compliance. However, RISC-V and the
+RISC-V ISA itself will no longer receive the benefit of the advancements
+and innovation that we have received funding and support to develop.
So, the assembly-code being written by hand for the video acceleration
side, as well as the 3D drivers for Kazan and MESA, will "flip" from RV64GC
projects / crowdsupply.git / blobdiff