Yeah, they somehow released a SBC without telling us what processor it contains.

It seems to be the same one as the BananaPi BPI-F3, see: https://www.reddit.com/r/RISCV/comments/1j6c6xz/orange_pi_rv...

As per the article: "The biggest difference between the two boars is that the Orange Pi RV has a 1.5 GHz StarFive JH7110 quad-core processor, while the new Orange Pi RV2 has a an octa-core Ky X1 chip with a 2 TOPS AI accelerator."

The link you posted goes to the exact same board as in the article.

It's not about the article, but the comment from u/12101111:

> It's a cheaper Spacemit K1.

> The CPU spec from dtb:

> compatible = "ky,x60", "riscv"; model = "Ky(R) X60"; riscv,isa = "rv64imafdcv"; riscv,isa-extensions = "i", "m", "a", "f", "d", "c", "v", "zicbom", "zicboz", "zicntr", "zicond", "zicsr", "zifencei", "zihintpause", "zihpm", "zfh", "zfhmin", "zba", "zbb", "zbc", "zbs", "zkt", "zvfh", "zvfhmin", "zvkt", "sscofpmf", "sstc", "svinval", "svnapot", "svpbmt";

> It also have a ARM China Linlon v5 VPU and Imagination IMG GPU. The PMIC and UART is same as K1.

> And the ubuntu image from orangepi just use the same BSP kernel/uboot/opensbi from Spacemit's linux-bianbu.

From memory, the SpacemiT K1 doesn't support extensions like Zvkt?

EDIT: okay, looks like the official documentation lists it, but many places I looked didn't. Maybe it wasn't being detected in cpuinfo?

It seems likely to be the same as this chip, so yes. https://docs.banana-pi.org/en/BPI-F3/SpacemiT_K1

It has a JH7110 onboard. From what I can tell, all of the vector processing is in dedicated hardware subsystems, not individual vector instructions.

We're still very early in the RISC V ecosystem, so most of the processors in production pre-date current standardizations, which requires applications to target specific silicon. To add insult to injury, those individual processors are relatively new, so the dedicated image processing and vector/tensor hardware doesn't have much support yet.

This is not JH7110 based.

I have one.

Yes, I'm currently using it to successfully test vector instructions. A blog post is being written, but may take a week or so.

Keep an eye on blog.habets.se, or ping me here on HN in about a week.

Seems I can't add another reply, nor edit the one I created. But [here's more info about the Orange Pi RV2 and RVV](https://blog.habets.se/2025/03/Exploring-RISC-V-vector-instr...).