4 ms·
I do not understand why for the GPU they did not go the VisionFive-1 way. When the driver is FOSS they could release new boards.
by fithisux 4y ago
I do not understand why for the GPU they did not go the VisionFive-1 way. When the driver is FOSS they could release new boards.
- snvzz 4y agoAIUI VisionFive 1 had no GPU. Just a framebuffer. >When the driver is FOSS they could release new boards. The driver is FOSS. OP used mesa3d to get acceleration. What it isn't is finished and rock solid. It is very hard to get to that point w/o hardware availability. This is why VisionFive 2 exists. Making a chip on a competitive node has a lot of cost upfront. To make it viable, they'd have to sell long millions of them. The approach here has been to design a chip that can be put almost everywhere; This is a very low power design, with great performance vs watt, error correction and extremely useful set of peripherals, all of it in a chip designed to function in an industrial range of temperature, while at room temperature even without a heatsink it won't get anywhere near its maximum, by like 60C. The VisionFive 2 SBC is the "development board" for this chip. Its purpose is to accelerate upstream support for this SoC. Of course, as it is the very first such board at <$100, the fastest to date and the first one to ship in the tens of thousands, which is more than the aggregate of every previous RISC-V development board shipped, it also means accelerating the RISC-V ecosystem as a whole, so everybody wins.