Hacker News new | past | comments | ask | show | jobs | submit login

People also seem to forget that everything needs to be ported. If you're an Android manufacturer, you're not going to stop shipping phones, waiting for the Android RISC-V to catch-up to ARM, or for RISC-V to get the speed and features of current ARM CPUs. You're going to buy ARM processors from another vendor.

The Windows ARM port is going to take even longer, I doubt that Microsoft has that working at anything beyond research stage, if that.

Getting the RISC-V ecosystem up to par with ARM is going to take years.

If you want to spin this in RISC-Vs favor, then yes, forcing a company like Qualcomm to switch would speed things up, but it might also give them a bit of a stranglehold on the platform, in the sense that they'd be the dominant platform, with all of their own customisations.




In theory, the Raspberry Pi foundation could easily move 3 million 1.8GHz RVA23 in 1 quarter... with 64 cores + DSP ops it wouldn't necessarily need a GPU initially. =3


The Raspberry Pi community would probably jump on a RISC-V board, but that doesn't help Qualcomm or it's customers.


Manufacturers adapt quickly to most architectural changes.

If you are running in a posix environment, than porting a build is measured in days with a working bootstrap compiler. RISC-V already has the full gcc and OS available for deployment.

We also purchase several vendors ARM products for deployment. Note, there was a time in history, when purchasing even a few million in chips would open custom silicon options.

Given how glitched/proprietary/nondeterministic ARM ops are outside the core compatibility set, it is amazing it was as popular as the current market demonstrates.

Engineers solve problems, and ARM corporation has made themselves a problem. =3




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: