agherzan
Fix rp1 camera
Fixes #1303
- What I did Use RPI foundation libcamera, install libpisp, upgrade libcamera-apps
Please take a look whether this is the best way to integrate this.
@kraj @agherzan could either of you get a look out on this? Would be nice to know if this is the right direction according to you guys?
And in my testing getting libpisp installed and used by libcamera was the only way to get cam support working on the RPI CM5 I have on my desk....
@gizahNL This looks fine to me the way it is. Could you check the commits and clean them up a bit using the guidelines in https://meta-raspberrypi.readthedocs.io/en/latest/contributing.html. For example, the Signed-Off-By missing footers.
I think it will be good to apply the needed patches on top of upstream libcamera, is that possible ?
@kraj it’s not. The raspberry libcamera repo is a fork and is required to be used with raspberry pi Linux kernel. The mainline libcamera only works when using mainline Linux kernel, and vice versa. Unclear why the two aren’t in sync.
@gizahNL you’re not setting the ipas build flag, which means you’re running the plugin in a sandbox; lower perf. Setting pipeline to auto also adds all, when you only need one of two. Preferable is only set one based on machine. It will enumerate all at runtime for each call; enable debug logs to see behavior.
I came up with similar recipes two days ago; didn’t see this issue, yet they’re a bit less. No disable warnings, etc; it builds fine.
My PR: https://github.com/agherzan/meta-raspberrypi/pull/1517/ Addresses all open camera issues and rolls recipes to latest release
@gizahNL you’re not setting the ipas build flag, which means you’re running the plugin in a sandbox; lower perf. Setting pipeline to auto also adds all, when you only need one of two. Preferable is only set one based on machine. It will enumerate all at runtime for each call; enable debug logs to see behavior.
It's set at line 28 & 30 of the libcamera bbappend ;)