Repository navigation
omamobile-device-panther 0.1.9: the camera start and the DMA heap rule (from #428 and #430) - #443
Merged
Merged
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. (cherry picked from commit e39c8d3)
The Pixel 7 had no omamobile-camera-start, so its cameras only came up when their drivers were loaded by hand. Ship the Pixel 7 Pro's blacklist (unchanged), script, service and timer: the drivers never autoload, and 40 s into the boot the script loads the camera PMIC drivers, the sensors and lenses, the DC-PHY and the CSIS behind a hang marker. Two changes for panther: the CSIS it checks for is 1a450000 (cheetah's is 1a460000), and it does not load sem1215, the telephoto's focus controller (no telephoto here). On a DTB without the camera receiver enabled, as on omamobile today, the service's condition skips it and nothing loads. test/all: the files are staged, the timer is enabled by a wants link, the script and unit use panther's CSIS, every driver it loads but the PMIC core is blacklisted, the list matches cheetah's. On a Pixel 7 with the camera nodes from kernel commits not yet proposed and the camera overlays, with these files copied by hand and the timer enabled: the script ran in 0.3 s and left three media graphs (imx386; s5kgn1 with ak7375; s5k3j1), and autofocus worked in omacam. This package build has not been installed on the phone. I used AI help (Claude) to work on this. (cherry picked from commit 829dbbd)
This was referenced Nov 5, 2026
This was referenced Nov 7, 2026
derekross
added a commit
that referenced
this pull request
Nov 7, 2026
…tart, unloaded around suspend (#419) (#475) The Pixel 7's Wi-Fi (BCM4389 on PCIe) starts at boot through the Pixel 7 Pro's guarded start: the PCIe controller, then brcmfmac, behind a hang marker, with the modules blacklisted for autoload and the unit run only when the DTB enables the controller. The link gets the bootloader's MAC before NetworkManager takes it. The Pixel 7 Pro's sleep hook, copied byte for byte, unloads Wi-Fi around suspend unless /etc/omamobile/wifi-keep-across-sleep exists. Three attended suspend cycles with the package installed all woke and reconnected. Merged onto main with the conflicts against the camera work (#443) resolved; the test's list of boot-time links also takes omamobile-camera.timer. Co-Authored-By: Ángel René <17342133+angelrenefm@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…tart, unloaded around suspend (derekross#419) (derekross#475) The Pixel 7's Wi-Fi (BCM4389 on PCIe) starts at boot through the Pixel 7 Pro's guarded start: the PCIe controller, then brcmfmac, behind a hang marker, with the modules blacklisted for autoload and the unit run only when the DTB enables the controller. The link gets the bootloader's MAC before NetworkManager takes it. The Pixel 7 Pro's sleep hook, copied byte for byte, unloads Wi-Fi around suspend unless /etc/omamobile/wifi-keep-across-sleep exists. Three attended suspend cycles with the package installed all woke and reconnected. Merged onto main with the conflicts against the camera work (derekross#443) resolved; the test's list of boot-time links also takes omamobile-camera.timer. 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.
Carries @angelrenefm's #428 (the DMA heap rule, cheetah's file unchanged) and #430 (the camera start, cheetah's with panther's CSIS and no telephoto focus driver) as their own commits, both reviewed in round 41. They conflict with each other in the device-panther README and neither bumped the version (main is at 0.1.8), so this PR keeps both README rows and sets 0.1.9. The package test passes. Both stay inert until the camera device tree is proposed.
Closes #428, closes #430 once merged.
🤖 Generated with Claude Code