4 ms·
The RISC-V CPU cores are open source. The other stuff on the chip is the same proprietary IP you find on any other silicon. The example given in the article i
by ajross 8y ago
The RISC-V CPU cores are open source. The other stuff on the chip is the same proprietary IP you find on any other silicon. The example given in the article is the DRAM controller, which they probably bought from the foundry.
I don't really see this as a ding against HiFive, per se. They only have so many engineer minutes to spend, and making a whole chip is hard. Someone needs to sit down and generate open source DRAM[1] and clock/PLLs and power gating frameworks and GPIO and ADC/DAC and I2C and SPI and flash[2] and USB and...
These guys are great and they make great products. We just need more. This is like writing an article in 1985 about how GNU isn't "really" open source because all this RMS guy has is an editor and a compiler.
[1] Which really means the analog signaling end, not the "controller" interface which is pretty simple.
[2] Particularly hard, given that the cell dimensions themselves are usually foundry trade secrets.
- foobiekr 8y agoIt is inevitable that the first sentence will itself become false. As things go forward the ISA will be open source but the cores themselves will cease to be.
- ajross 8y agoThat's not the way it happened in software. As free implementations come to dominate it's the proprietary products that tend to wither. The existence of ANSI C89 as an open standard didn't result in an explosion of proprietary yet compatible compilers, instead GCC ate the world within a decade. I mean, sure. You can make a closed-off RISC-V. But I don't see why that's required or "inevitable".
- flukus 8y agoGCC is licensed under the GPL, RISC-V chose a license that allows for proprietary modifications. Inevitable might be taking things too far, but it's certainly within the realm of possibilities and thanks to the license always will be.
- nickik 8y agoWhy? There are many different organisations including universities companies and so on that want to use the open cores and many of them either develop new stuff fully open or partly open. Also, the chips can be both, you can have open source implementations and close source implementations and when you are building a chip you have to make the choices just as in software.
- makomk 8y agoSince the other stuff on the chip is the main obstacle to running open source software like Linux, Coreboot, u-boot or even your own OS on typical ARM SoCs, this means that these RISC-V chips aren't actually an improvement in this area. Having to reverse-engineer the proprietary, undocumented DRAM controller is basically the same as bringing up (say) one of Allwinner's much cheaper SoCs. (Except Allwinner released the DRAM init code as open source a few years back, so I don't think you even have to do that for most of their SoCs these days.) As it currently stands, I think the $10 quad-core ARM board based around a set top box chip currently sitting on my desk is running a more open software stack than anything available for SiFive's $1000 board. (To be fair, the SiFive board does have sixteen times the RAM.)