Repository navigation
Conversation
|
Thanks, Nate. The devinfo record is careful (one byte, with before and after images), and so is the recovery acceptance. Before this can merge: please rebase onto main; make |
|
A friendly check-in: this has been quiet for over a week and now conflicts with main. If you'd like to continue, a rebase onto main will get it reviewed again. If I don't hear back within a week I'll close it to keep the queue tidy; it can be reopened any time. |
|
Still active. I'm rebasing this onto main now. As you asked, it lands together with the comet board DTS, which I'm rebasing onto the zumapro stack that came in with linux-omarchy-mobile#187. |
1c5ef41 to
a30c278
Compare
|
Thank you, Nate, and thank you for putting stock back on both slots. That was a full reinstall and I know what it costs. The package itself is what I asked for: Four things before it can merge:
Smaller things: a first package starts at 0.1.0, not 0.1.60. The descriptor says "headless … No shell" while the package depends on The record of the three |
a30c278 to
116160e
Compare
|
Rebased onto main ( 1. The notes now describe the phone after the restore. NOTES has a dated entry, "2026-11-07/08: stock restored on both slots, Linux back on slot B", and BRINGUP-M1,
2. Boot-success.
3. The kernel side. The board is derekross/linux-omarchy-mobile#273 (draft), with the USB glue in #271, and #270 (pinctrl) and #272 (main camera) alongside. The board PR leads with the 4. The two procedures are now in BRINGUP-M1 under "Recovery procedures", as
Smaller things:
Checks on |
|
Thank you, Nate. This is a thorough answer: every point from 11-12 is in the files, not only in the reply. The restore has its own dated entry with the commands, the old entry is marked historical, the two recovery procedures are written out line by line, the package starts at 0.1.0 and no longer pretends to need the shell, and the descriptor is still refused by The record also tells me three things I didn't know, and I need to settle them before this can go in.
On the kernel side: this still lands together with the board file, and two things there may change this pull request. The board draft (derekross/linux-omarchy-mobile#273) can't be booted yet because USB is off, and on derekross/linux-omarchy-mobile#271 I've asked for one boot with the 9a's plain Two small questions. What does |
derekross
left a comment
There was a problem hiding this comment.
CI has run on this head and both jobs pass: the policy check, and tests/all with every package's tests, your package's own test among them. One thing it could not show: the run tested the merge with main as it was when you pushed, and main has since changed the Pixel 9a's row in docs/DEVICES.md, right above the row you add, so the pull request now shows a conflict. The fix is to keep main's 9a row and put the Fold's row under it. I ran the descriptor suites and your package's test on that merge here and they pass, so there is no need to push only for this; fold it into your next push, and I'll approve its run.
Nothing else changes: the three points in my comment above and the kernel side are what this waits for.
…licy The first comet submission after issue derekross#143: the descriptor, curated hardware observations, the remaining gates and an inert boot-policy package. Boot-success stays off: the package ships no boot-success script, unit or devinfo writer and enables nothing, and status, install and README agree. SOC_COMPATIBLE stays commented out, as on tegu, so install-phone and flash refuse comet until the public board DTB lands. The storage guard allows only the five slot-B boot images and userdata. NOTES records the 2026-11-07 stock restore (CP3A.261005.005 on both slots), the commands that put Linux back on slot B, the slot-B marking and the fresh protected backup, and marks the 2026-10-30 slot-state paragraphs as historical. BRINGUP-M1 writes out both recovery procedures as fastboot commands now that slot A is a live stock fallback. The package starts at 0.1.0. It no longer depends on omamobile-shell and the descriptor drops MONITOR_SCALE (the panel-size scale is derekross#635's job). The AoC blacklist names the modules the comet zumapro kernel builds, not gs201's. reboot-to.c follows cheetah's current copy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Answers the maintainer's 11-18 questions on derekross#203. The slot B mark of 2026-11-08 gets its time (01:25:18Z), what made devinfo writable (the helper's own setrw on sdd and sdd1 around its single bootctl call, set read-only again right after and from an exit trap), the before/after bytes at 0x30-0x37 and the one-byte compare. The post-restore backup (01:28-01:41Z) is recorded as taken after the mark. The earlier text said stock booted again on 2026-11-11. It did not: that night's boots are all Linux on slot B, and the 2026-11-14 capture is byte-identical, devinfo included, to the 2026-11-08 02:32Z one. The entry now says so and places the Fold's first storage start (03:31:11Z) after the 03:29:09Z capture. BRINGUP-M1: with B marked there is no fallback, so a broken slot B means the buttons and R1, whose flashes clear the mark. R2's --set-active=b waits for the maintainer's decision. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
116160e to
edd38aa
Compare
|
Pushed 1. The 11-08 mark. Understood: from now on, any
2. R2. BRINGUP-M1 now says that step 4 ( 3. The timeline.
The two small questions.
On #271: the plain Checks on |
linux-omarchy-mobile#273 now enables comet's USB the Pixel 9a's way, on a plain snps,dwc3 node, and derekross#271's zumapro glue is closed: a cold boot of derekross#273's DT bound 11210000.usb to dwc3 directly and the host configured the gadget, with no glue module. The shared kernel config builds dwc3 in, so dwc3-zumapro leaves the initramfs module list and device/comet/kernel.config, which only selected the glue, goes. BRINGUP-M1 and the package README now name derekross#273 as the one kernel dependency. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Pushed
The branch merges cleanly onto today's main ( |
Summary
The first comet submission following #143, rebased onto main (
bb02e11a).omamobile-boot-successscript or unit, nodevinfowriter, and installing the package enables nothing.install,statusand the README all say boot-success is off. On the phone the unit is masked.SOC_COMPATIBLEstays commented out, as on tegu, soinstall-phoneandflashrefuse comet until the public board DTB lands.boot_b,init_boot_b,vendor_boot_b,vendor_kernel_boot_b,dtbo_banduserdata.omamobile-shell; the descriptor scale it reads comes with omamobile-shell 0.2.135: an optional device.lua after the shared phone rules #204.Evidence
packages/omamobile-device-comet/test/all: passes. It checks that boot-success is disabled and that no writer or enablement is shipped.tools/pr-check upstream/main: all checks pass.tests/packageson Linux: the same five failures as main atbb02e11a(audio, shell, settings, speaker-tuning, sensors), none in this package.The board DTS and module sources are in linux-omarchy-mobile, on top of the zumapro stack from #187: derekross/linux-omarchy-mobile#273 (board, draft) and derekross/linux-omarchy-mobile#271 (USB glue). This PR lands with them, as you asked. Until then, this descriptor is not an install profile.
Merge Danger
Door: two-way. Repository and package only, with no hardware writes.
Blast Radius: comet only.
🤖 Generated with Claude Code