Raspberry Pi camera modules not being detected on libcamera0.5
Bug #2110144 reported by
Pragyansh Chaturvedi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libcamera (Ubuntu) |
New
|
Undecided
|
Pragyansh Chaturvedi |
Bug Description
With the latest version of libcamera in Ubuntu, the camera modules on a Raspberry Pi are no longer being detected.
libcamera 0.5.0-1:
cam -l returns an empty list
qcam does not list any sensors as well.
libcamera 0.4.0-5ubuntu1:
cam -l lists the connected sensors and qcam works fine.
Related branches
~r41k0u/ubuntu/+source/libcamera:ubuntu/devel
- Dave Jones (community): Needs Fixing
-
Diff: 15639 lines (+15601/-1)5 files modifieddebian/changelog (+17/-0)
debian/control (+2/-1)
debian/patches/add_syncmode_and_tensors.patch (+15479/-0)
debian/patches/fix_pisp_cfe_entities.patch (+101/-0)
debian/patches/series (+2/-0)
To post a comment you must log in.
I have narrowed this down to the new PiSP driver upstreamed in libcamera. They are matching the wrong entity names for CFE devices. /gitlab. freedesktop. org/camera/ libcamera/ -/blame/ v0.5.0/ src/libcamera/ pipeline/ rpi/pisp/ pisp.cpp# L883 /github. com/raspberrypi /libcamera/ blob/d83ff0a4ae 4503bc56b7ed48c d142c3dd423ad3b /src/libcamera/ pipeline/ rpi/pisp/ pisp.cpp# L883
https:/
Curiously, Raspberry Pi's fork of libcamera still uses the old match strings, even when they upstreamed these changes to Debian: https:/
This might suggest that there may be changes to the camera related devicetree overlays in the future. For now the fix will be to try for both older and newer match strings