Repository navigation
device-panther: Pixel 7 first port, and contributor builds with a local key - #79
Conversation
|
Thank you, @nesmeck. This is the best-documented first port we've had: one register per call with the reason it's safe to read, the trigger derived on this phone and only then put into the descriptor, the guard checked partition by partition against stock's by-name map, the Arch root through The local-key tooling does what I wanted: the key lives in
Two smaller things, not blocking:
Merge order: #75 touches the same line of |
|
Thanks for the review. Both changes are in ec91153:
|
Review of derekross#79. The board file is on a local kernel branch, so the matrix says "unpublished kernel" in the Storage, Buttons and USB cells, as the Pixel 9a row does, until it is pushed and can be linked. Boot 6's fallback to slot A was a stock boot, and stock recovery mounts persist, efs and modem_userdata. NOTES.md records that the data reset was declined, what changed against the baseline, and the fresh backup taken afterwards; the runbook's rollback now says to do the same after any fallback. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The board file is public now as derekross/linux-omarchy-mobile#108 (with the FT3658 driver in derekross/linux-omarchy-mobile#109). It is linked from the Pixel 7 row (Boot, Storage, Buttons and USB, in place of "unpublished kernel"), NOTES.md and the runbook's status. |
|
Thank you, @nesmeck. Both changes are in, and done well:
Thanks too for tracking down the The one thing left is mechanical: the branch now conflicts with main in three files, because main moved after your push (#75 is still open, so you don't need to wait for it). When you rebase:
I resolved it this way on a scratch copy, and the matrix still has 25 cells in every row. Whichever of #75 and this lands second will need a one-line touch in Two optional things that can wait for a later PR:
Once it's rebased and CI is green, I'll merge it. |
Slot B on the Pixel 7 (panther, gs201) boots a mainline 7.3-rc6 kernel into the Arch root on userdata, with Hyprland and the Omarchy lock screen on simpledrm. The board DTS is a local kernel branch and will be the kernel pull request against omamobile. What passed on the phone, in order (BRINGUP-M1.md): - first light: USB SSH, both cluster watchdogs stopped; - the bootloader's framebuffer at 0xfac00000 (DPP0 RDMA_BASEADDR_Y8), shown after DECON0 TRIG_CON 0x1c240030 is set to 0x3061; - UFS behind the storage guard, with every partition number equal to stock's by-name map and a fresh backup taken from Linux; - the Arch root through tools/install-phone, and bin/omamobile push; - the power and volume keys, wired as on the Pixel 7 Pro. The touch controller (FocalTech FT3658 on SPI0) does not answer yet; the notes record what was ruled out. Slot B is not marked successful: devinfo is version 3.19 here, against cheetah's verified 3.15, so each boot spends one of the three retries that --set-active gives. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Pixel 7's device package, from omamobile-device-felix without the lid and cover-touch parts: the udev rule that keeps every partition outside UFS_RW read-only, the systemd-networkd and NetworkManager files for the USB link, logind ignoring the power key (Omarchy's menu takes it), the mirror list and reboot-to (cheetah's source). It has no omamobile-boot-success: that writes devinfo, whose layout is version 3.19 on this phone and has not been checked against ABL yet. test/all passes. The package is installed in the root image that runs on the phone, built with tools/build-packages --local. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A contributor building packages for a new device had two bad options: sign with the maintainer's keys/ (which they don't have), or mix their packages into out/repo, which tools/repo-push publishes (L-7). - tools/local-key-init CODENAME makes keys/CODENAME/ once: an ed25519 signing key, its fingerprint and public.asc. - tools/fetch-published DIR downloads pkgs.omamobile.org with each signature, and refuses an index or package that a key in packages/omamobile-keyring does not trust, that is revoked, or that does not match the signed index's checksum. - tools/build-packages --local NAME signs with keys/NAME only, into out/NAME/repo, and keeps the published packages' own signatures when they are imported. The Pixel 7's package joins the build order. - tools/build-rootfs --local NAME builds from out/NAME/repo, into out/NAME, and the image trusts the local key (alarm-setup lsigns it). - docs/RELEASES.md §10 and AGENTS.md describe the flow. tests/local-builds runs every refusal against a fake server and test keys, in a copy of the repository with its own GNUPGHOME. tests/all passes. The root image that runs on the Pixel 7 was built this way (rootfs-smoke 12/12). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review of derekross#79. The board file is on a local kernel branch, so the matrix says "unpublished kernel" in the Storage, Buttons and USB cells, as the Pixel 9a row does, until it is pushed and can be linked. Boot 6's fallback to slot A was a stock boot, and stock recovery mounts persist, efs and modem_userdata. NOTES.md records that the data reset was declined, what changed against the baseline, and the fresh backup taken afterwards; the runbook's rollback now says to do the same after any fallback. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The board file is now public as linux-omarchy-mobile#108, so the Pixel 7 row links it in place of "unpublished kernel" (Boot, Storage, Buttons and USB), as the Pixel Fold row links its kernel PRs, and the notes and the runbook point at it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Rebased on main as you described (tests/all keeps main's list with the panther test and tests/local-builds at the end; panther after raven in ORDER; the Pixel 7 row after husky and the Wanted line dropped). |
|
Thank you, @nesmeck. The rebase is exactly what I described, and nothing else moved: the five commits carry the same changes as before, apart from the three conflict resolutions.
Main moved twice more after your push (the raven version fix, and the kernel tree's new default location). Your branch still merges onto today's main cleanly, and on that merge I ran CI is waiting for my approval because the branch was pushed again. I'll approve the run, and once it's green I'll merge this with the squash title A few small things for your next PR. None of them blocks this one:
The |
L-279 to L-293: the 9a's slot B hold and what made devinfo writable (#125), per-device flags checked by building both command lines (#101), env defaults in the shared build library and CI waiting for approval (#79), GLib retry paths and radio stops checked at the controller (#99), silent re-pushes and stacks with several tops (the tegu stack), and two of our own: merge only after every check has finished (#126), and an empty diff is checked for empty inputs (kernel #123). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From the laptop, phone-smoke reaches the phone on bash's stdin (tools/phone-ssh "bash -s" < tools/phone-smoke). pacman -Q also loads the sync databases, and one signed by a key the phone doesn't trust (a --local build's, RELEASES §10) makes it ask on stderr whether to import the key and read the answer from stdin: the rest of the script. The report then never printed. A contributor found this on panther (#79). pacman -Q now reads /dev/null, which also means it can never answer yes to a key import, and so do the commands run as the desktop user, which never need input. Reproduced with a stand-in pacman that reads stdin as fgets does, piped like tools/phone-ssh: before, it took the last 1212 bytes and no report printed; after, it reads nothing and the full report prints. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…wenty-sixth rounds (#127) * docs/review: 19 lessons and 3 corrections from the twenty-fifth round The confirmed candidates from round 25 (L-260 to L-278): the 9a slot B marking as a devinfo question, cross-repository links, squash-merged stacks and version files, stale hand-built prebuilts, and before-merge Pixel 7 Pro runs on omamobile-int. C-16 to C-18 correct our own earlier comments on kernel #98, kernel #80 and #74; L-241 is corrected in place. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs/review: 15 lessons from the twenty-sixth round L-279 to L-293: the 9a's slot B hold and what made devinfo writable (#125), per-device flags checked by building both command lines (#101), env defaults in the shared build library and CI waiting for approval (#79), GLib retry paths and radio stops checked at the controller (#99), silent re-pushes and stacks with several tops (the tegu stack), and two of our own: merge only after every check has finished (#126), and an empty diff is checked for empty inputs (kernel #123). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
What and why
A first port to the Pixel 7 (panther, gs201), which was under Wanted in
docs/DEVICES.md, plus the tooling a contributor needs to build a root image
for a new device without the maintainer's signing key.
device/panther/: the descriptor, an empty board dtbo, NOTES.md andBRINGUP-M1.md, with the record of every boot (first light, the
bootloader's framebuffer, UFS behind the guard, the Arch root, the push
loop, the keys, and the touch work so far).
docs/DEVICES.mdgets aPixel 7 row.
packages/omamobile-device-panther0.1.0: the storage guard rule, theUSB link, the power key and reboot-to, from omamobile-device-felix
without the lid and cover-touch parts. No
omamobile-boot-success: thisphone's devinfo is version 3.19, and bootctl is verified on 3.15 only
(L-36).
tools:local-key-init,fetch-published, and--local NAMEinbuild-packagesandbuild-rootfs, so a contributor's packages aresigned with
keys/NAMEand land inout/NAME/instead ofkeys/andout/repo(L-7).tests/local-buildscovers the refusals;docs/RELEASES.md §10 and AGENTS.md describe the flow.
The board DTS and a work-in-progress FT3658 touch driver are on a local
kernel branch; they will be a separate pull request against
linux-omarchy-mobile's
omamobileonce they are reworked for it.Device and build
bootloader cloudripper-17.0-15902555 on both slots
uname -r): 7.3.0-rc6-omamobile-push1-g1cb4bd36f3be-dirty(
omamobile-intplus the local panther board file)Checks (no phone needed)
tools/pr-check upstream/mainpassestests/allpassestests/packagespasses (the package I touched: omamobile-device-panther)versionbumped, and the new version is in the commit subjectCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:On the phone
(first light, framebuffer and trigger, UFS behind the guard, Arch root
through install-phone); the push loop and boot 5 (keys) pass. Boot 8
(HSI1 pin controller) passes; the touch controller does not answer yet.
Bluetooth, battery, sound, sensors, cameras, suspend; marking slot B
successful;
tools/phone-provision. The root image was built with--localfrom published packages plus the tree's omamobile-omarchy0.1.12, omamobile-shell 0.2.28 and omamobile-firstboot 0.1.2.
userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)tools/phone-smokefrom the laptop printed no report: a command in thescript reads the rest of it from stdin under
bash -s. The report belowwas produced by copying the script to the phone and running it with
--here < /dev/null. The phone's clock is wrong (no RTC, no network).tools/phone-smokereportphone-smoke: panther
Kernel
7.3.0-rc6-omamobile-push1-g1cb4bd36f3be-dirty, tools at4b81e04, 2026-10-18T17:25Z.Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.21, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-device-panther 0.1.0-1, omamobile-firstboot 0.1.2-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.12-1, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.28-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1
🤖 Generated with Claude Code