In many areas of embedded, Linux is the default OS choice for a SoC these days. Sometimes Android for things with screen/UI. I expect Linux to be the default for RISC-V SoCs (not microcontrollers) also, even without any RPI involvement.
But the Board Support Packages from typical vendors tend to be as-closed-as-possible, with limited access to documentation, software updates and support for small customers. RPi comes from a different direction, much more open and accessible. So hopefully they will drag/push the vendors to be this type of open from the start in the RISC-V space.
> But the Board Support Packages from typical vendors tend to be as-closed-as-possible, with limited access to documentation, software updates and support for small customers. RPi comes from a different direction, much more open and accessible. So hopefully they will drag/push the vendors to be this type of open from the start in the RISC-V space.
Yes, I was thinking from the perspective of the end user, as in those of normal embedded devices are intentionally ignorant of it's workings... where as the audience of the raspberry pi is the exact opposite.
I doubt they'll design their own chip, but I wouldn't be shocked to find that they joined to try to steer other partners and development into the areas they'd need to make a board comparable with a RISC-V cpu and some kind of GPU.
For someone like Western Digital, that's probably a huge deal. I don't think it saves the RPi folks much. I suspect they get a loss leader deal. The total volume can't be that high, but it's good press for Texas Instruments.
Around 0%. Its not about cutting cost, its about finding new ways of continuing hardware effort. Broadcom has ~zero incentive screwing with outdated SoC at this point, but it might be relatively easy to sell company board on RISC-V research initiative.
