Repository navigation
device-panther: open the DMA heaps to the video group, as cheetah - #428
Closed
angelrenefm wants to merge 1 commit into
Closed
angelrenefm wants to merge 1 commit into
angelrenefm wants to merge 1 commit into
Conversation
libcamera's software ISP allocates its buffers from /dev/dma_heap. Without cheetah's rule the heaps are root-only on the Pixel 7, so the simple pipeline logs "Could not open any dma-buf provider", disables software debayering, and the camera app gets raw BA10 frames it can't show. The rule is cheetah's file, unchanged; test/all checks that it stays so and that install stages it. Tested on a Pixel 7 with the camera nodes from kernel commits not yet proposed and the camera overlays: with the rule copied by hand, omacam streams the main camera at 2008x1136. This package build itself has not been installed on the phone. I used AI help (Claude) to work on this.
Owner
derekross
added a commit
that referenced
this pull request
Nov 5, 2026
#443, from #428 and #430) Two device-panther changes from angelrenefm (#428, #430), carried together because they conflict in the README and neither bumped the version (main was at 0.1.8): - The DMA heap rule, cheetah's file unchanged: libcamera's software ISP allocates from /dev/dma_heap, which was root-only on the Pixel 7, so the camera app got raw frames it couldn't show. - The camera start, cheetah's with two changes: it checks panther's CSIS (1a450000) and doesn't load sem1215, the telephoto's focus controller. The drivers never autoload; the timer loads them 40 s into the boot behind a hang marker, and on a DTB without the camera receiver the service's condition skips it. Both stay inert until the camera device tree is proposed. Co-authored-by: Ángel René <17342133+angelrenefm@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
derekross#443, from derekross#428 and derekross#430) Two device-panther changes from angelrenefm (derekross#428, derekross#430), carried together because they conflict in the README and neither bumped the version (main was at 0.1.8): - The DMA heap rule, cheetah's file unchanged: libcamera's software ISP allocates from /dev/dma_heap, which was root-only on the Pixel 7, so the camera app got raw frames it couldn't show. - The camera start, cheetah's with two changes: it checks panther's CSIS (1a450000) and doesn't load sem1215, the telephoto's focus controller. The drivers never autoload; the timer loads them 40 s into the boot behind a hang marker, and on a DTB without the camera receiver the service's condition skips it. Both stay inert until the camera device tree is proposed. Co-authored-by: Ángel René <17342133+angelrenefm@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
libcamera's software ISP allocates its buffers from
/dev/dma_heap. Without cheetah's udev rule the heaps are root-only on the Pixel 7, so the simple pipeline logs "Could not open any dma-buf provider", disables software debayering, and the camera app gets raw BA10 frames it can't show. This ships cheetah's70-omamobile-dma-heap.rulesunchanged;test/allchecks that it stays identical to cheetah's and thatinstallstages it (without the install line the test fails).Tested on a second Pixel 7 with the camera nodes from kernel commits not yet proposed and the camera overlays, with the rule copied by hand: omacam streams the main camera at 2008x1136. On today's
omamobileDTB (no cameras) it changes nothing visible.Not checked: this package build installed on the phone.
Checks:
test/allof omamobile-device-panther andtools/pr-check origin/mainpass.tools/phone-smoke (the same phone, 2026-11-04T18:47Z)
phone-smoke: panther
Kernel
7.3.0-rc6-omamobile-push1-g44048a9aa795, tools at3435ed4, 2026-11-04T18:47Z.Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-audio 0.5.13-1, omamobile-device-panther 0.1.5-1, omamobile-firstboot 0.1.3-1, omamobile-gnss 0.2.7-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.28-1, omamobile-owl-widgets 0.1.1-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.79-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1
I used AI help (Claude) to work on this.