My understanding is that ffmpeg needs to be compiled to do hardware acceleration. I use it (straight from the Debian repository) to transcode videos on my RK3588 board (Orange PI 5 Plus) running the Armbian edge kernel, and it runs just as fast as the vendor-compiled ffmpeg did using the Orange Pi company's vendor kernel.

My understanding is that v4l2request is for vendor kernel that does RKMPP, so that V4L2 API is available for browser or mpv to play video, so decoding only. I have not focused on that, although HEVC HW accelerated decoding would be really welcome. W.r.t. camera capture and encoding, I only used RPI1 (legacy firmware V4L2 stack) and RPi3/4 (libcamera). Many variants, but is it possible to get uncompressed frames from a camera, push it through the h264 HW encoder (h264_v4l2m2m) and then to some RTSP sink (MediaMTX) to show it as WebRTC in a browser. That is with RPi kernel and RPi ffmpeg, so 'vendor' solution. Although V4L2, it won't work with a standard/mainline Debian kernel yet AFAIK. For Rockchip, I use ffmpeg that comes with jellyfin to do transcoding (HEVC->H264). It works fine with 6.1.115 vendor kernel, I have not used it for camera. It might miss certain things w.r.t. V4L2 controlling camera attributes. Below is what I get on a NanoPi-R6C (RK3588s, Trixie). You can see only JPEG encoder is available. root@ranc:~# uname -a Linux ranc 6.18.0-rc3-edge-rockchip64 #1 SMP PREEMPT Sun Oct 26 22:59:49 UTC 2025 aarch64 GNU/Linux root@ranc:~# ls -al /dev/media* crw-rw----+ 1 root video 238, 0 Nov 4 13:53 /dev/media0 crw-rw----+ 1 root video 238, 1 Nov 4 13:53 /dev/media1 lrwxrwxrwx 1 root root 6 Nov 4 13:53 /dev/media-dec0 -> media0 lrwxrwxrwx 1 root root 6 Nov 4 13:53 /dev/media-dec1 -> media1 root@ranc:~# media-ctl -d 0 -p Media controller API version 6.18.0 Media device information ------------------------ driver hantro-vpu model hantro-vpu serial bus info platform:fdba0000.video-codec hw revision 0x0 driver version 6.18.0 Device topology - entity 1: rockchip,rk3588-vepu121-enc-sou (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: SOURCE -> "rockchip,rk3588-vepu121-enc-pro":0 [ENABLED,IMMUTABLE] - entity 3: rockchip,rk3588-vepu121-enc-pro (2 pads, 2 links) type Node subtype Unknown flags 0 pad0: SINK <- "rockchip,rk3588-vepu121-enc-sou":0 [ENABLED,IMMUTABLE] pad1: SOURCE -> "rockchip,rk3588-vepu121-enc-sin":0 [ENABLED,IMMUTABLE] - entity 6: rockchip,rk3588-vepu121-enc-sin (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: SINK <- "rockchip,rk3588-vepu121-enc-pro":1 [ENABLED,IMMUTABLE] root@ranc:~# media-ctl -d 1 -p Media controller API version 6.18.0 Media device information ------------------------ driver hantro-vpu model hantro-vpu serial bus info platform:fdc70000.video-codec hw revision 0x0 driver version 6.18.0 Device topology - entity 1: rockchip,rk3588-av1-vpu-dec-sou (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: SOURCE -> "rockchip,rk3588-av1-vpu-dec-pro":0 [ENABLED,IMMUTABLE] - entity 3: rockchip,rk3588-av1-vpu-dec-pro (2 pads, 2 links) type Node subtype Unknown flags 0 pad0: SINK <- "rockchip,rk3588-av1-vpu-dec-sou":0 [ENABLED,IMMUTABLE] pad1: SOURCE -> "rockchip,rk3588-av1-vpu-dec-sin":0 [ENABLED,IMMUTABLE] - entity 6: rockchip,rk3588-av1-vpu-dec-sin (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: SINK <- "rockchip,rk3588-av1-vpu-dec-pro":1 [ENABLED,IMMUTABLE]

Is i2c-1 actually mapped out to i2c-1? It should be if the aliases are setup correctly. Secondly even if the i2c bus is enabled, have the pins been successful muxed into i2c mode? You should be able to check by: sudo cat /sys/kernel/debug/pinctrl/300b000.pinctrl/pinmux-pins | grep i2c

From what I see online that box has an s905 amlogic CPU

Hello everyone! Saw that some luckfox boards were getting supported and I was like: YES!!! Flashed an sd-card with the community image. Latest I could find is 25.11.0-trunk.413. And plonked in my working Luckfox Lyra Zero W and it failed to boot. From what I gather there seems to be a missing partition called "misc" and I think it is expected about after the current unallocated 16MB(16,777,216 bytes). I tried creating a 4MB partition after the current unallocated space but it complained about something called "Magic" and my limited u-boot/rockchip/embedded linux experience made me get lost there. This is the serial output: Where the "No misc partition" is where I began. My current board has buildroot flashed to the SPI and boots if i don't have any sd-card inserted. DDR 0ac6b06a19 typ 24/11/13-17:22:47,fwver: v1.04 tREFI:4x, sr_idle:93, pd_idle:13 PHY drv:clk:40,ca:48,DQ:40,odt:240 vrefinner:50%, vrefout:50% dram drv:40,odt:120 sr_dq:0, sr_ca:0, sr_clk:0 rg:0xc-0x1-0x2, 0x3d-0x0-0x2,status:a007 rdtrn:0x14-0x30-0x4c(0x38) wrtrn:0x3-0x20-0x3d(0x3a) DDR3, 750MHz BW=16 Col=10 Bk=8 CS0 Row=15 CS=1 Size=512MB out U-Boot SPL board init U-Boot SPL 2017.09-g4d88b0a #hxj (Jul 30 2025 - 20:08:42) sfc cmd=03H(6BH-x4) SPI Nand ID ef aa 22 unrecognized JEDEC id bytes: ff, ef, aa Trying to boot from MMC1 No misc partition spl: partition error Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking op-tee 0x00001000 ... sha256(93603ca22c...) + OK ## Checking u-boot 0x00100000 ... sha256(606b868a00...) + OK ## Checking fdt-1 0x0018baf0 ... sha256(6ae9f912c7...) + OK Jumping to U-Boot(0x00001000) I/TC: I/TC: OP-TEE version: 3.13.0-958-g46dcf51e88a #chenjh (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Thu Mar 6 10:17:27 CST 2025 arm, fwver: v2.10 I/TC: Status: cluster=0xc00, core=0xe100, bootcpu=0 I/TC: Next entry point address: 0x03f011a7 I/TC: OP-TEE memory size: TEEOS 0x5e000 TA 0x1000 SHM 0x1000 I/TC: Primary CPU initializing I/TC: Primary CPU switching to normal world boot