adzio

Thank you Armbian guys for providing and supporting a working 5.10 image for the Rock Pi 4C board.

Has anyone been successful in configuring and using a matched CSI camera with a 5.x kernel for this board? If so, can you share the required conf steps here?
Radxa's website (https://wiki.radxa.com/Rockpi4/MIPI_Camera) claims that their provided Debian image supports both RPi ov5647 and RPi imx219 based cameras so that confirms hardware compatibility but so far I haven't been able to capture images/video with neither on Armbian when attached to a Rock Pi 4C.

$ ls -l /dev/video*
crw-rw---- 1 root video 81, 0 Apr 3 07:30 /dev/video0
crw-rw---- 1 root video 81, 1 Apr 3 07:30 /dev/video1
crw-rw---- 1 root video 81, 2 Apr 3 07:30 /dev/video2
crw-rw---- 1 root video 81, 3 Apr 3 07:30 /dev/video3
exist,

v4l2-compliance and v4l2-ctl --list-formats-ext work and provide good output.
However, capturing the actual photo doesn't work:

$ fswebcam -d /dev/video0 -r 2048x1536 --jpeg 95 test.jpg
--- Opening /dev/video0...
Trying source module v4l2...
/dev/video0 opened.
No input was specified, using the first.
Unable to query input 0.
VIDIOC_ENUMINPUT: Inappropriate ioctl for device

I had enabled ov5647 manually in /etc/modules
$ lsmod | grep ov
ov5647 20480 0
v4l2_fwnode 28672 1 ov5647
governor_performance 16384 0
videodev 299008 8 rockchip_vdec,v4l2_fwnode,ov5647,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_common,v4l2_mem2mem
mc 61440 7 rockchip_vdec,videodev,ov5647,videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem

But still no joy, one gets the dreaded VIDIOC_ENUMINPUT error.

What else am I missing? I’ve seen references to disabling twi2 but I’m unable to find where to make this change in 5.10 if that's indeed the cause.

@balbes150 It works both ways. I can choose not to waste my time and not to get involved with folks whose first reaction is to generalize and spew negativity rather than to internalize feedback and to make it actionable.
 
I had tried debugging your CSC software to get it to even finish booting and you decided to disparage me that I’m reinventing the wheel.
 
I've seen, read and followed your recommendations and they didn’t work, simple as that. I'm not a noob with Linux, but well above enthusiast level.
 
Your custom Armbian_21.05.0-trunk_Station-p1_focal_current_5.10.25.img.xz image boots to prompt on my setup. So we’re getting somewhere. My board has two PCIe modules attached, without which it’s quite useless to me. So that's probably the difference (the issue) booting bare board vs. with PCIE attached but the board should still finish booting with any 5.10 image. This configuration boots fine with other flavors (debian, ubuntu) with both modules attached, so it should work here too.
 
The issue in these Release images may be PCIe related. The station version boots with the PCIe -110 error in dmsg and lspci output is empty. Perhaps the other versions don’t finish boot because they are running into some sort of PCIe init issue. BTW the station image is different than what is shipped in other Armbian 5.10 images because the -110 error is absent there and lspci has correct output (basically, my PCIE stuff works on Armbian 5.10 + Rock Pi 4C).
 
So, a bug found in the field. No problem, but also no need to throw feces at people for reporting and no need to disparage them when they’re trying to debug from their side which in the end may only help you, like in this case.