It's not hacking VHDL in your basement type thing where everyone can adds new stuff and it just works together trough common agreed api. All changes must run trough long chain of verification and testing from functional models to physical placement, testing and verification.
But more to the point, most of Linux isn't developed in basements either. Someone like Google/Facebook/Amazon/Microsoft decides it's worth their resources to make a more power efficient chip for their datacenters and more valuable to get further improvements from third parties than to try to sell it externally at commodity margins, or that "commoditize your complement" would be a good thing to do for cell phone chips, and now you've got a billion dollars in funding.
IMHO Syndicate with clever licensing around RISC-V infrastructure would be the best idea.
The clever licensing part:
1) mandatory licensing: licensees must license to everyone with the same conditions. licensees can't refuse to license.
2) pricing model: licensees periodically announce valuations at which they commit to sell their IP, and must sell their intellectual property for that value to anyone who is willing to commit to smaller license fees. There can be a periodic auction each year.
Those companies are the ones with physical hardware.
But it's also not true that they'd be the only ones to make money. If you lower your supplier's margins on hardware and then pass half the savings on to your customers, you get both higher margins and higher volumes. But your customers still get lower prices, which means they make more money too, on top of the transactions that it made feasible that weren't previously.
What makes it possible to design small volumes of custom asics for reasonable price is old and well known process, increasing the error margins (and sacrificing performance) or using existing modules. Simulation mostly works and can be trusted, yield is predictable etc.
Android already removed their dependency on GCC, following Apple's footsteps, and depending on how Fuchsia turns out, eventually the Linux kernel as well.
I know about the Fuchsia project, but so-far it can't compete with Linux or other established OSes.
Quote:
"Android 8.0 and higher support only Clang/LLVM for building the Android platform. Join the android-llvm group to pose questions and get help. Report NDK/compiler issues at the NDK GitHub.
For the Native Development Kit (NDK) and legacy kernels, GCC 4.9 included in the AOSP master branch (under prebuilts/) may also be used."
From https://source.android.com/setup/build/requirements#software...
"Removed GCC and gnustl/stlport. Added lld."
From https://android.googlesource.com/platform/ndk/+/master/docs/...
There are also a couple of Linux/Clang Conferences where Google goes through the kernel and clang changes they have done to accomplish it.
Android might have the Linux kernel under the hood, but it isn't Linux as many know it.
Not like it matters. They're replacing even that. See Fuchsia.
And that's a good thing: Fuchsia seems to have a better design (microkernel, multiserver).
Probably some leftover thinking from proprietary products that tried to apply license restrictions on the compiled output.
"GCC Runtime Library Exception"
https://www.gnu.org/licenses/gcc-exception-3.1.en.html
This document was also the inspiration for the Classpath exception in OpenJDK.
> "In the FOSS world the license of the compiler has nothing to do with the license of the compiled software".
But it could be a step towards a "GPL for hardware" type of shift. Someone puts in the work or the money to do a core which is competitive on some important metric (power, cost, etc.), and licenses it at no cost but under the terms that if you make changes you have to publish them and under the same license.
Then some people use it because it's good enough and free-as-in-beer, but if any of them improve it then it gets better. So then more people use it, until it's the Linux of hardware.
Moreover, if you have to publish the changes then you have to document the changes (equivalent of releasing source code), which means hardware that isn't a black box will gain a competitive advantage over hardware that is.