Repository navigation
device/bluejay: keep pinned startup outside the passive package - #565
Conversation
|
Thanks, Chris. Moving the pinned start-up into |
c15ce0d to
5e97ba4
Compare
|
Thanks, Chris. Both README notes are in as I asked, the helper clears the same marker #562 writes, and I read the whole thing again since the branch was rewritten: no register access from userspace, nothing in the tree enables a unit, and One file is in the wrong place, and I should have caught it last time. Could you move it to Two small things while you're there, neither blocking: a README line that the overlays don't apply to the published kernel (they name labels only the development tree has), and, before these units ever run again, the runbook will need the lines that copy and enable the check and ready services and the lines that undo that. I'll merge this after #562. |
…encies (#561) Records the Pixel 6a's persistent desktop on its development kernel, what can and can't be reproduced from published sources, the one slot-success write with its before and after bytes, and the hold on further marking. Lists the split pull requests (#562, #563, #565) and the kernel pull requests the port still waits on. Documentation only. Co-Authored-By: OpenAI Codex <noreply@openai.com>
Split experimental services, overlays and probe tools from derekross#543. Retain the exact old development-kernel pins and explicit enable gates; these helpers refuse the revised kernel topics. Remove userspace display-register access and use the descriptor/init trigger contract. The proposed SSH-ready helper clears the neutral root marker only when USB and sshd are ready. No new phone run or automatic installation is claimed. Co-Authored-By: OpenAI Codex <noreply@openai.com>
Name the exact historical kernel source and release that the pinned helpers support. Warn that input-controller.dtso replaces the complete chosen bootargs string, so combining overlays requires inspecting both final DT variants and preserving the selected recovery policy. Co-Authored-By: OpenAI Codex <noreply@openai.com>
Keep the fixed release string and module choices out of ordinary Bluejay builds. Describe manual use with the exact historical kernel, overlay compatibility and installation and restoration of the matching root gates. Co-Authored-By: Codex <noreply@openai.com>
5e97ba4 to
5d5bd6b
Compare
|
Thanks, Chris. The fragment is now One thing in the new install section, not blocking: the install block also copies I'll merge this right after #562. |
|
Acknowledging the nonblocking README point for the next runbook: the root-gate-only install must not imply a working desktop. The SDDM drop-in requires the separately staged hardware/GPU units and hardware-ready marker; installing only the check/ready pair cannot meet that desktop expectation. The next source follow-up will keep that drop-in out of the root-only snapshot/install/undo set and make its Expect cover the root check, SSH and cleared pending marker. Desktop readiness belongs to the separate hardware/GPU integration. No source correction is included in this comment, and this merged historical runbook must not be treated as a revised-kernel recipe. The new headless stage results and restored historical desktop are reported in #348. |
…encies (derekross#561) Records the Pixel 6a's persistent desktop on its development kernel, what can and can't be reproduced from published sources, the one slot-success write with its before and after bytes, and the hold on further marking. Lists the split pull requests (derekross#562, derekross#563, derekross#565) and the kernel pull requests the port still waits on. Documentation only. Co-Authored-By: OpenAI Codex <noreply@openai.com>
…lled by nothing (derekross#565) The Pixel 6a's historical start-up helpers, units, overlays, probe tools and kernel config fragment live under `device/bluejay/bringup/` and `overlays/`; no package installs them, no unit is enabled, and the descriptor lists no overlay, so builds and images for bluejay are unchanged. They belong to the tested kernel `c934e316b` (`7.3.0-rc6-omamobile-bluejay-input-gated0`) and refuse any other. The ready helper clears the pending marker derekross#562's `persistent-development` mode writes, once the USB address and sshd are up; the README carries the next-run gate and the install and undo commands for the check and ready pair, none of them executed yet. Co-Authored-By: OpenAI Codex <noreply@openai.com> Co-Authored-By: Codex <noreply@openai.com>
Keep the historical Pixel 6a startup helpers, experimental overlays and kernel configuration under device/bluejay/bringup. Nothing is installed automatically or enabled by a package. The historical config fragment has moved out of the normal device build path.
The README pins source c934e316b and release 7.3.0-rc6-omamobile-bluejay-input-gated0, explains historical overlay-label compatibility and /chosen/bootargs replacement, and provides fail-stop install/undo instructions for the root check and ready services. The instructions snapshot prior files and service states before installation and verify the complete snapshot before undo. Run them against the installed development root, not the RAM recovery root. These helpers intentionally refuse the revised kernel stack.
Merge #562 first: its neutral root-ready marker is the prerequisite. This PR does not include the passive package proposed in #346.
Validation on main 6ee77fb: full tests/all, policy and root-ready fixtures pass; independent review exercised install/restore in private roots. No phone operation, new kernel qualification or package installation is claimed. Fresh published-head CI is tracked below.
Published-head validation: both Policy and Tests (tests/all, every package) passed on
5d5bd6bd77c60457d2c3c217eabdee3e0544e12e. The complete combined local integration also passes tests/all and tests/packages with PYTHONUNBUFFERED unset, matching CI.