Skip to content

device-panther: open the DMA heaps to the video group, as cheetah - #428

Closed
angelrenefm wants to merge 1 commit into
derekross:mainfrom
angelrenefm:pr-panther-dma-heap
Closed

angelrenefm wants to merge 1 commit into
derekross:mainfrom
angelrenefm:pr-panther-dma-heap

Conversation

@angelrenefm

Copy link
Copy Markdown
Contributor

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's 70-omamobile-dma-heap.rules unchanged; test/all checks that it stays identical to cheetah's and that install stages 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 omamobile DTB (no cameras) it changes nothing visible.

Not checked: this package build installed on the phone.

Checks: test/all of omamobile-device-panther and tools/pr-check origin/main pass.

tools/phone-smoke (the same phone, 2026-11-04T18:47Z)

phone-smoke: panther

Kernel 7.3.0-rc6-omamobile-push1-g44048a9aa795, tools at 3435ed4, 2026-11-04T18:47Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-g44048a9aa795, slot b, up 865s
storage guard (required) ok 55 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 8 error lines in dmesg (8 known, 0 new)
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card2-DSI-1 connected, 1080x2400
GPU ok render node on panthor
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked true)
touch ok FocalTech FT3658
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 91% Charging, 33 °C
sound cards ok googleaocsndcar
sensors ok Accelerometer AmbientLight Proximity
cameras skip no libcamera tools
thermal ok hottest zone 49 °C

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.

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.
@derekross

Copy link
Copy Markdown
Owner

Thanks, this is a clean copy of the 7 Pro's rule, with the test keeping it identical. I'll merge it as is and set the version and title then. It conflicts with #429 and #430 only in the README (and #419 in install), so I'll take them in order and resolve those lines myself; no need to rebase.

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>
@derekross

Copy link
Copy Markdown
Owner

Merged as part of #443 together with #430, with your commits unchanged and you as co-author: the two conflicted in the README and needed a version (device-panther 0.1.9). Thank you!

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants