duo-files VS cvitek-linux-5.10

I'm sorry, but bit banging WS2812 on that hardware is stupid. Find some peripheral that you can use to output WS2812 bitstreams, and use that. For example, for the Raspberry Pi there is a library at https://github.com/jgarff/rpi_ws281x that can use either PWM, PCM or SPI to do this. I know you're dealing with a different CPU, but this should give you ideas about how you can use its peripherals. The data sheet is available: https://github.com/milkv-duo/duo-files/blob/main/hardware/CV1800B/CV1800B-CV1801B-Preliminary-Datasheet-full-en.pdf

Datasheet: https://github.com/milkv-duo/hardware

Reading the datasheet, it looks like there is one C906 cpu with 700 Mhz without the the vector extension and one C906 cpu at 1Ghz with rvv 0.7.1. The C906 design has been opensourced and is available here: https://github.com/T-head-Semi/openc906

The C906 supports rv64gc with optimal rvv 0.7.1 with a vlen of 128, but a 256 wide ALU.

They list H.264/H.265 support, but I don't think it's a standardized extension.

But see my other comment about using the pre ratification vector extension:

> Also, is that mainline Linux or are we going down the hacked kernel route of the ARM boards where someone is going to have to pick through the source to get the patches otherwise it will remain on an ancient unsupported kernel?

My initial impression is that there are no binary blobs[1]. You can look at the repo it is using over here: https://github.com/milk-v/cvitek-linux-5.10

I think getting the full sources alone is sufficient. It might not be desirable for the Linux team to accept patches for every standalone piece of hardware. As long as the patches for the actual ISA are mainlined I consider that a win.

[1] Maybe there are, I didn't look too closely at the repo, but it looks to me that it's all source code.