4 ms·
I think the thing you're missing is that RISC-V is already a huge success. It's now the de facto choice for "hidden" CPUs that don't need to run user code - aux
by IshKebab 3y ago
I think the thing you're missing is that RISC-V is already a huge success. It's now the de facto choice for "hidden" CPUs that don't need to run user code - auxiliary CPUs in SoCs, BMCs etc.
It might not seem like it because you never see those.
Given that it's already a success and not going anywhere I don't think it's a stretch to think that it will eventually break into the mobile/server market. Google already announced that they're going to support RISC-V on Android.
- pabs3 3y agoThose hidden cores need to be running open source firmware.
- IshKebab 3y agoNo they don't. You can run anything you like on them.
- pabs3 3y agoIt isn't possible to trust or fix proprietary software, same goes even more for proprietary firmware. All firmware needs to be open source.
- IshKebab 3y agoYou would like all firmware to be open source. I agree that would be nice. Though for most of these chips it wouldn't help too much without documentation for the chip and all its peripherals/registers, and probably a signing key to get it to actually run your code. The fact that the code is closed source doesn't really change the trust model much either since the code is usually supplied by the chip vendor. If they wanted to do nasty things and keep them secret they could do it in hardware.
- afiori 3y agoIt would be better if they did, but this has nothing to do with the ISA. The only possible link I can see is that you can arbitrarily modify RISC-V on your core, so it is easier to tivoize your software... but this seems like a reach.