What I found interesting initially was how the 32 bit CPU was disrupting the 8 bit CPU market. People using Cortex M0 chips where they used to use ATMega chips. Identical package size, faster, more resources, not too much more memory. And some unreal bargains[1].
And now as FPGAs get cheaper and cheaper, RISC-V was becoming the default 'soft' processor because everything else cost money and didn't have any sort of ecosystem. Amazing times.
[1] Not sure how these folks make money -- https://satoshinm.github.io/blog/171212_stm32_blue_pill_arm_...
[1] https://www.eetimes.com/author.asp?section_id=36&doc_id=1333...
It would seem taking risks on new architectures, and all the extra development time (both chip and tooling) would far outweigh the cost of just licensing arm.
Can someone explain the economics of it all?
Don't get me wrong, I am all for a free competitor to ARM's near monopoly on the mobile embedded space. I don't just get it.
Folks like WD want a processor that is cheap, and specialized like running an error correcting algorithm across spectrum. Generic CPU is too slow, custom CPU is fine. Custom CPU where there is already a lot of other support because other people are using it, is super fine.
Unlimited right to use / modify is a really valuable thing for these companies.
If WD is making their own chips, it almost certainly isn't to save a couple grand a year; it's probably to save many millions.
"Can't you do that in software?" 50M units later you understand the reason why that hardware guy made your life a living hell for two weeks just before release, because what he did saved ten cents on the motherboard and at scale that's real money.
RISC-V feels like CPU hardware's linux moment right now.
'Patent minefield' means there are so many patents for so many basic things it's impossible to do anything without violating something. You'll never know you've violated a patent until your competitor sues you. A lot of these patents are probably invalid, but the fights in court will take years, judgement will sometimes happen by someone without know how, and losing 1 fight will cause you severe damage.
The 'solution' is trying to hide all your violations by closing the driver. Reverse engineering costs a lot, so if someone is doing it to find your patent violations, you build your own patent war chest and cross license with them - they have engineers so they probably produce something that has violations for your patents.
I find Intel is pretty solid about open sourcing everything they provide for Linux that runs on the host — it's a pity they haven't applied the same policy to the ME.
https://appleinsider.com/articles/11/01/10/intel_and_nvidia_...
By any chance, does anyone know if Intel is funding RISC-V? According to the logic of "Commoditizing the Complement" one way of hurting a competitor is to make their product a commodity.
https://www2.eecs.berkeley.edu/Research/Projects/Data/106902...
Since then they also invested in RISC-V startups, like SiFive.
> The press release linked by OP doesn't give the full story. For a better perspective see [the random blog post].
Could also integrate manufacturing services, but fabs is incredibly capital intensive, making it another kind of business.
Could also keep IP licensing as a model, but open the core and push it further and further out into peripherals. Problem is that would probably kill the surrounding ecosystem of partners that do this today.
That would require the extensions to be popular, though, and having a corner of one fort is less ideal than having an entire fort.
If you're just joining us, Arm very much sees the up and coming RISC-V stack as an immediate threat to the future of their business and is taking pro-active countermeasures - doing everything from awkward, backfiring smear campaigns against RISC-V[1] to straight up license dumping their own product to prevent developers jumping ship.
It's interesting to see because RISC-V is wonderful and Arm seems to recognize that. Arm Holdings is acting rationally as someone in a privileged competitive position would do. At the same time, big players like Western Digital are migrating to RISC-V so Arm is internally freaking out [2].
[1] https://www.theregister.co.uk/2018/07/10/arm_riscv_website/
[2] https://www.theregister.co.uk/2017/12/01/wdc_risc_v_edge_str...