>>947
he probably meant this:
https://www.phoronix.com/scan.php?page=news_item&px=Libre-RISC-V-Eyeing-POWER
and
>The summary is this: Libre and Open contributors to RISC-V
>have been disregarded for several years. Long before I
>joined the RISC-V mailing lists, it was well-known within
>that small and tightly-knit community that if you were not
>associated directly with UC Berkeley, you were basically
>not welcome. Caveat: if you signed the NDA-like agreement
>which conflicts directly with, for example, the Debian
>Charter and the whole purpose of libre licenses, then you
>got a “voice” and you got access to the closed and
>secretive RISC-V resources and mailing lists.
https://www.crowdsupply.com/libre-risc-v/m-class/updates/nlnet-grants-approved-power-isa-under-consideration
finally: https://riscv.org/faq/
>1. What is the license model?
>The RISC-V ISA is free and open with a permissive license
>for use by anyone in all types of implementations.
>Designers are free to develop proprietary or open source
>implementations for commercial or other exploitations as
>they see fit. The RISC-V Foundation encourages all
>implementations that are compliant to the specifications.
>
>Note that the use of the RISC-V trademark requires a
>license which is granted to members of the RISC-V
>Foundation for use with compliant implementations. The
>RISC-V specification is based around a structure which
>allows flexibility with modular extensions and additional
>custom instructions/extensions. If an implementation was
>based on the RISC-V specification but includes
>modifications beyond this framework, then it cannot be
>referenced as RISC-V.
RISC-V allow vendors to develop proprietary designs, if well adopted, would results in fragmented and vendor-lockin cpu extensions, compilers, and firmware. Or simply botnet.