I'll skip this one, and wait for RVA22-compliant devices.
This machine uses the Allwinner D1[0] SoC, which is pre-standard V, incompatible with the standard V extension ratified in December.
Even if not enabling/using the V, and thus considering it just RV64GC, it is a fairly slow one relative to what's already available in the market, and it comes with just one core.
I already have the ~$21 LicheeRV w/Dock[1], which uses the same D1 SoC. IMHO much more cost efficient if you want to play with D1.
Essentially it is shortform for standardising a set of optional instruction sets into a bundle. RV for RISC-V, A for "applcation supporting" (as opposed to being used in embedded or microcontroller) and 22 for 2022 (in 2100 it'll be 100)
>Essentially it is shortform for standardising a set of optional instruction sets into a bundle.
This is a common misconception. RVA22 is not just a bunch of profiles, but 2022's OS-A Platform.
Platforms do, among many things, require profiles, which are what you've described. In this particular case the RVA22 platform requires the RVA22 profiles.
From your link, documenting profiles, there's an entire section[0] addressing the difference.
The actual platform specification can be found here[1].
Thanks for pointing out RVA22 - I wasn’t aware of the initiative but it’s a great idea. I still have reservations about the core architecture but having some standards for the rest of the ecosystem is a big win.
This machine uses the Allwinner D1[0] SoC, which is pre-standard V, incompatible with the standard V extension ratified in December.
Even if not enabling/using the V, and thus considering it just RV64GC, it is a fairly slow one relative to what's already available in the market, and it comes with just one core.
I already have the ~$21 LicheeRV w/Dock[1], which uses the same D1 SoC. IMHO much more cost efficient if you want to play with D1.
[0]: https://linux-sunxi.org/D1
[1]: https://linux-sunxi.org/Sipeed_Lichee_RV