Michal Fita

Raspberry OS has weird quirks that automate the process of setting up the system for using cameras, but I'm looking for clean way to set up the device tree to use the imx219 camera. Anyone knows what overlays to enable to get this to work on Armbian? Additionally where's the location of device tree overlays sources for Raspberry Pi 5 on Armbian?

Whoa. I'm not representing Rockchip in anyway - just need to use RK3566 in a project. Without these drivers the support for the chip is incomplete from the perspective of the Armbian user. I don't have powers, energy and money to push particular chip drivers into mainline - there are several vendors our there who don't have theirs and Ubuntu still doing distros for these (👀 Xilinx/AMD). If that's the case what's the usefulness of Armbian for average tinkerer who want to run Rockchip based SBC with CSI-2 cameras? In Windows world you take the installer and add drivers to the system - in Linux world at best someone could cook DKMS package with extra set, but that's at the moment probably significantly more effort than set of patches for Armbian's build. Money, money, money. SBC makers doesn't pay them enough to justify effort required and they probably deliver customized kernels as part of paid support to they customers under NDAs. These things happen probably in violation of GPL license, but no one is willing to pay layers to chase this especially as 5.10 is out to the world. I don't have to PR my changes if you don't like such approach. That, however, doesn't change my need to do this as I need to boot the board with CSI-2 support and working GPU 🤷

Thanks @Igor. How to provide information that OrangePi 3B for example boots on Edge? We could run GPU stuff on it with success. I find it useful it allows board customization w/o maintaining whole kernel fork. However, it's maybe we started from official Ubuntu for Xilinx? Looks like I have to. I need Rockchip's MIPI CSI2 drivers to connect camera to OrangePi 3B and Radxa Zero 3E.

I believe this question goes to @rpardini as maintainer of patches for Rockchip series in the `build` repo: I'm trying connect camera to Orange Pi 3B (yes, it boots from community support on edge kernels), but spent 2h digging to find no drivers for CSI2 from Rockchip's fork are ported to patches for recent kernels (for example: https://github.com/armbian/linux-rockchip/blob/rk-5.10-rkr6/drivers/phy/rockchip/phy-rockchip-csi2-dphy.c and corresponding device trees to instantiate these drivers). This is a little chicken egg problem as I need recent kernels to have access to open source GPU drivers - they're not present on 5.10 based original system images for OrangePi 3B. I created a DT overlay for imx219 camera, but it cannot work as right references don't exist on Armbian yet. I could help with porting these, but I need to know the procedure - that's some amount of drivers I can figure out based on `compatible = ` entries from Rockchip's device trees. I probably need to get them built with 6.6 and 6.7, then generate patches with these and PR changes. Any more hints appreciated. I'm interested in having both MIPI CSI2 and GPU working on these boards for now: OrangePi 3B (that one I have on my desk) Radxa Zero 3E Radxa Zero 3W Thank you. How you can live with forum not supporting humanly Markdown?

I found it very confusing that Armbian doesn't seem to follow the Ubuntu/Debian traditional scheme for naming kernel modules: linux-image-*, linux-modules-* and linux-headers-*. I need them to cross compile out-of-tree kernel module in `schroot`. Armbian seem to have only `linux-image-edge-rockchip64` and `linux-headers-edge-rockchip64`. What's the reasoning behind such design decision? Moreover, I've noticed kernel packages incorporate all the logic that make the board bootable, instead having more generic kernel binaries and relying on `flash-kernel` tool that both Ubuntu and Debian widely use. I wonder why not? What are chances in future `linux-image-*` could be split and have matching `linux-modules-*` package as upstream? Is there any maintained roadmap to figure out most recent supported numbered kernel package, so I could have Orange Pi 3B board with fixed (pinned) kernel version out-of-the-box? Thank you.