News for hackers. Stuff that matters.
Re:RISC-V on the Verge of Broad Adoption by AnthonyMouse on Thursday February 14, 2019 @03:16PM (#19165563)
> But what about "bigger" systems? Laptops or desktops or servers? Do the pareto analysis on those systems, compare an ARM SoC to a RISC-V one. The costs are in memory, support chips, PCBs, tooling etc. Not the CPU license.

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.

Re:RISC-V on the Verge of Broad Adoption by Nokinside on Thursday February 14, 2019 @03:31PM (#19165688)
New high performance microarchitecture costs hundreds of millions to develop. You need to develop new microarchitecture every five years or so to stay competitive.

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.

Re:RISC-V on the Verge of Broad Adoption by AnthonyMouse on Thursday February 14, 2019 @03:36PM (#19165738)
Which is why you don't start off by trying to challenge AMD and Intel on raw performance.

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.

Re:RISC-V on the Verge of Broad Adoption by Nokinside on Thursday February 14, 2019 @04:15PM (#19166103)
I believe there is a good economic model for open hardware design but it's not the software model. "commoditize your complement" means that only those whit physical hardware can make money.

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.

Re:RISC-V on the Verge of Broad Adoption by AnthonyMouse on Thursday February 14, 2019 @04:46PM (#19166368)
> "commoditize your complement" means that only those whit physical hardware can make money.

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.

Re:RISC-V on the Verge of Broad Adoption by dfox on Thursday February 14, 2019 @07:53PM (#19167602)
Reportedly, Intel does mostly fully automated synthesis and instead of manually tuning the layout, they improve their essentially fully in-house Verilog to silicon toolchain.
Re:RISC-V on the Verge of Broad Adoption by Nokinside on Thursday February 14, 2019 @11:51PM (#19168533)
Everyone uses automated toolchains, but getting physical layout from toolchain does not mean it works or performs.

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.

Re:RISC-V on the Verge of Broad Adoption by pjmlp on Thursday February 14, 2019 @03:54PM (#19165911)
In a time where most sponsors for FOSS software are moving away from GPL.
Re:RISC-V on the Verge of Broad Adoption by AnthonyMouse on Thursday February 14, 2019 @04:36PM (#19166286)
The GPL continues to be a popular license. It just got popular enough that in v3 they could take a more aggressive stance on patents and tivoization. Which is inherently a trade off between goals and adoption. They chose to achieve more of their goals at the expense of some usage.
Re:RISC-V on the Verge of Broad Adoption by pjmlp on Thursday February 14, 2019 @05:42PM (#19166793)
To the point that all major FOSS alternatives on the embedded space, including Zephyr from Linux Foundation aren't based on GPL.

Android already removed their dependency on GCC, following Apple's footsteps, and depending on how Fuchsia turns out, eventually the Linux kernel as well.

Re:RISC-V on the Verge of Broad Adoption by protomikron on Thursday February 14, 2019 @08:41PM (#19167827)
But Android is still based on Linux and you need GCC to compile the kernel (yeah I know, other compilers can do it too, but GCC is in some kind of symbiosis with Linux, which is a good thing I guess).

I know about the Fuchsia project, but so-far it can't compete with Linux or other established OSes.

Re:RISC-V on the Verge of Broad Adoption by pjmlp on Friday February 15, 2019 @01:07AM (#19168815)
No you don't, Android has removed all dependencies on GCC with Treble changes, upstream just did not took all the changes done by Google.

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.

Re:RISC-V on the Verge of Broad Adoption by snvzz on Friday February 15, 2019 @03:47PM (#19174561)
>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).

Re:RISC-V on the Verge of Broad Adoption by pertymcpert on Thursday February 14, 2019 @10:24PM (#19168223)
Why is gcc dependency a good thing for the kernel?
Re:RISC-V on the Verge of Broad Adoption by saagarjha on Thursday February 14, 2019 @10:28PM (#19168242)
It keeps both GPL?
Re:RISC-V on the Verge of Broad Adoption by sigjuice on Friday February 15, 2019 @02:13AM (#19169065)
How?
Re:RISC-V on the Verge of Broad Adoption by onli on Friday February 15, 2019 @05:58AM (#19169919)
You're right to ask, it does not. In the FOSS world the license of the compiler has nothing to do with the license of the compiled software, and that also goes for the GPL 3.

Probably some leftover thinking from proprietary products that tried to apply license restrictions on the compiled output.

Re:RISC-V on the Verge of Broad Adoption by pjmlp on Friday February 15, 2019 @08:21AM (#19170657)
Actually GCC has an explicit clause that GPL doesn't apply to the generated binary, otherwise you could not link to the C runtime library

"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.

Re:RISC-V on the Verge of Broad Adoption by pertymcpert on Friday February 15, 2019 @01:02PM (#19173113)
Right but that's because the compiler is emitting code into the binary that exists verbatim in the GCC source.
Re:RISC-V on the Verge of Broad Adoption by pjmlp on Friday February 15, 2019 @03:40PM (#19174510)
Which makes the assertion false, otherwise there wouldn't be a need for the "GCC Runtime Library Exception".

> "In the FOSS world the license of the compiler has nothing to do with the license of the compiled software".

Re:RISC-V on the Verge of Broad Adoption by onli on Saturday February 16, 2019 @05:22AM (#19178034)
There is no other FOSS compiler that influences the license of the compiled software, afaik. So I think that statement holds up anyway.