"vcgencmd get_camera" is ONLY valid for the legacy camera stack. It is irrelevant for anything using the kernel drivers.
Likewise "start_x=1" only enables the legacy camera stack, which is irrelevant and actually counter-productive as it reduces the amount of memory available to Linux.
Both fragments are targeting csi0. The endpoint of that node is then pointed effectively at itself, so that isn't going to work.
Even if you have no control over the CSI source, you need a driver for it to define things like the resolution to be expected. That is what the dummy_sensor driver I was tinkering with on https://github.com/6by9/linux/tree/rpi- ... mmy_sensor was looking to do.
Likewise "start_x=1" only enables the legacy camera stack, which is irrelevant and actually counter-productive as it reduces the amount of memory available to Linux.
Code:
fragment@0 {target = <&csi0>;__overlay__ {status = "okay";port {mtrdwd_0: endpoint {remote-endpoint = <&csi0_ep>;clock-lanes = <0>;data-lanes = <0>;link-frequencies =/bits/ 64 <300000000>;};};};};fragment@1 {target = <&csi0>; // Assuming there's a csi0_ node to target__overlay__ {status = "okay";port {csi0_ep: endpoint {remote-endpoint = <&mtrdwd_0>;data-lanes = <0>;};};};};};Even if you have no control over the CSI source, you need a driver for it to define things like the resolution to be expected. That is what the dummy_sensor driver I was tinkering with on https://github.com/6by9/linux/tree/rpi- ... mmy_sensor was looking to do.
Statistics: Posted by 6by9 — Fri Mar 01, 2024 4:09 pm