Repository navigation
device/dipper: add a RAM-only first-light build path - #505
Conversation
a841ad2 to
91ff102
Compare
|
Thank you for this. A RAM-only first-light path is the right way to start a phone with no second slot, and the descriptor does what you say. A few things before it can merge: 1. The matrix row. DEVICES.md's matrix is for devices with merged notes, and the notes are still in review in #330. Until #330 merges, the Mi 8 belongs in the "Wanted" table, with a link to this PR and #330. Once #330 is in, a matrix row is welcome, with these changes:
2. One run of this image. The description says no kernel build or phone probe ran for this PR. A device change needs a report from the phone.
3. The runbook in gated form. BRINGUP-M1 explains the recovery well. The phone steps need the usual shape, though: Expect/Pass, a stop condition, a rollback and a risk level for each step, read-only checks first. Also please pass Smaller things:
On order: this goes after #330, since its links and the matrix row need the notes. It builds only on linux-omarchy-mobile #218, because |
|
Thanks for working through the list. The Mi 8 now sits in the Wanted table with the right links. The runbook has a backup gate, a fastboot gate and a RAM boot gate, with What's still needed before merge: 1. One run of this image. This is the same request as last time, and the main one. Please boot the image this builder makes once, attended, and record in the notes:
One expectation to put in that step: with kernel #220 as it stands, the screen will most likely go dark about 30 seconds after boot. I've explained why on #220. If the screen does go dark there, that's the regulator cleanup, not a hang. 2. The RAM boot gate's Pass. "USB/SSH checks succeed" should name the checks above, the read-only flags first, with "any partition reads 0" as a stop condition. The rollback ("power-cycle to the installed boot image") also needs the forced-restart combination, which I've asked for on #499. 3. Order. This branch now also carries #503's init change (your Smaller things:
The title is fine for the squash. |
|
2026-11-09 device check update:
|
|
Thank you for the new recovery gate. Putting "find out how to force a restart" ahead of the first RAM boot is the right order on a phone with no second slot, and I'd rather wait for that than have you guess. The rest of my last list is done: the RAM boot gate's Pass now names every check, any One thing I missed last time: One correction, also mine. Last time I wrote that the screen would most likely go dark about 30 seconds after boot. That was true of kernel #220 when I wrote it, but you fixed #220 the same evening: the panel supplies are back on the framebuffer node, and simpledrm, which is built in, keeps them on. So step 4 should now expect the screen to stay lit. Something like: "The screen should stay lit: simpledrm holds the panel's VCI and VDDIO rails. If it goes dark about 30 s in, record Two smaller points:
Nits, only if you're in the files anyway: The order is unchanged: this merges after #503. The title is fine for the squash. |
|
Thank you for running it. This is what I hoped for: the image this PR builds, booted by RAM, attended, with What's left: 1. A rebase. Main has added four suites to the same 2. Step 4's whole-disk check. It now asks for every whole-disk 3. The status line. It credits Volume Down to this PR's image, but the notes on #330 say that result came from the second boot and the current image hasn't been rechecked. "Volume Down produced 4. One line about Not conditions: The order stays #484, #503, then this. The title is fine for the squash. |
|
I addressed the four follow-ups in
The panel overlay test is recorded with the visible console, brightness and DPMS results. That test predates #484: |
|
The latest #505 runbook update records the actual Power-hold result from installed Android (restart back into Android), and explicitly says it has not been tested under the RAM kernel. The current recovery image is identified as stock from its 4.9.337 kernel header; the rescue path still uses the tested |
|
The recovery gate now records the 2026-11-09 attended result: a 10-second Power-only hold restarted back into Android from both installed Android and the Omarchy Mobile RAM kernel. Volume Down + Power then entered fastboot from Android. A simulated hard kernel hang remains untested. |
|
Thank you for the quick turn on all four points, and for two things beyond them: the full backup read through the guarded RAM boot, and the Power-hold restart tried under our kernel, which is the result I most wanted to see before anything gets flashed. Step 3 now records both. Three things before this can merge. The second one is my mistake. 1. The panel pieces make the builder depend on kernel #218. 2. Step 4, where I gave you the wrong wording. I suggested "every whole-disk node (
The sentence "Repeat the whole-disk node check after #484 is included" can then go. 3. The rebase, and no more waiting for #484. On 2026-11-09 I merged #530, which changed the same guard lines that #503 edits, so #503 and this PR now conflict with main itself. I've posted the resolution on #503. Once #503 has landed, Two wording points:
The title is fine for the squash. |
|
Owner follow-ups are implemented in the updated head |
|
The owner follow-ups are implemented in the updated head The combined #503/#505 non-NFS image booted by RAM on the Mi 8 (SHA-256 I have not rebased #505 yet because #503 has not landed; the PR order you requested is preserved. |
b39f7eb to
a952d38
Compare
|
Resolved the base conflict by rebasing onto current main. Dropped the stale shared #503 commit; #505 now contains only its Dipper changes on top of main. |
|
Thank you, this is nearly there. The panel pieces are out, so the builder needs only what #220 provides again. Step 4 now holds on today's guard, after #484 and in NFS mode. The rebase is clean on main, and I also merged it together with #503 and ran Three small text changes are left, none needing a boot. If you'd rather, I can make them when I merge:
Suggestions, not conditions: the builder mounts the whole repository into the container, and The order stays #503, then this. #503 is waiting on one boot of my own phone, not on you. The title is fine for the squash. |
a952d38 to
4edbe44
Compare
|
Addressed the remaining review notes in 4edbe44: the runbook now names the installed-system backup and says no reviewed restore procedure exists; it links CONTRIBUTING.md §3.1 and calls the recovery image the installed ROM’s. The device row describes the RAM-only WIP and current kernel status. The container now mounts only the four build inputs, SSH is printed only after Dropbear starts, and dipper-probe syntax-checks the patched init. Rebased onto current main after #503 merged. |
|
Thank you, @quatrixone. The runbook now says "the backup of the installed system" and "the installed ROM's One of my own optional suggestions has broken the builder, so one more small push, please:
Two small things for the same push:
The order is #330, then kernel #220, then this. The title is fine for the squash. |
The Mi 8 has one OS boot partition, so a failed persistent update has no known-good OS slot to return to. Keep this first integration RAM-only: the descriptor is non-installable, the builder emits an Android v1 image for fastboot boot, and its storage allowlist is empty. Add the Dipper kernel fragment, a bounded image packer, a read-only initramfs build, recovery instructions, and a WIP device matrix row. Wi-Fi identity, firmware and any persistent install path stay out until their own safety gates are met. Checks: git diff --check and bash -n passed. Kernel build and hardware probe not run in this session.
4edbe44 to
c4238ab
Compare
Signed-off-by: quatrixone <quatrix1@gmail.com>
Signed-off-by: quatrixone <quatrix1@gmail.com>
|
Completed the follow-up on head
The new run is recorded in |
|
Thank you, @quatrixone. Everything from last time is done, and a bit more:
Here: I'm merging this after linux-omarchy-mobile#220. Three lines will be slightly off once both are in, and I'll fix them on main myself rather than ask you for another push (say so if you'd rather do it):
Thank you for your patience through all these rounds. The Mi 8 now has a reviewed, read-only way to first light, and the panel (#218) and touch tests can build on it. |
…i 8 lines #505 left (#680) The Pixel 8a's row still described first light. Since then Omarchy's image runs from userdata (BRINGUP-M2 gate e, #456 and kernel #206 merged), and the buttons and the touchscreen passed gates f and g (kernel #238 and #241 merged): Boot, Storage, Touch and Buttons say so. For the Mi 8, three lines promised on #505: BRINGUP-M1's [NOTES.md] link had no definition, the board DTS (kernel #220) is merged, not in review, and the status line names the 2026-11-11 boot NOTES records. The POCO F3 row said #25 was in review; it was closed as paused on 2026-11-11. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Adds the Xiaomi Mi 8's descriptor (`BOOT_METHOD=ram-only`, no boot images, an empty UFS write allowlist), its kernel config fragment, a builder for a `fastboot boot` image (`tools/dipper/build`: the shared init patched for the Qualcomm watchdog and a USB-only SSH server, in an Android v1 boot image with the DTB appended) and a gated runbook in BRINGUP-M1. Nothing here flashes, pushes or installs: the phone has one OS slot and no reviewed restore procedure yet. Booted by RAM on 2026-11-11 with linux-omarchy-mobile derekross#220's device tree (image sha256 `665fcbd6…abf2b1`): every UFS partition read-only, watchdog fed, simpledrm and USB SSH working; keys, touch, GPU and Wi-Fi untested.
…i 8 lines derekross#505 left (derekross#680) The Pixel 8a's row still described first light. Since then Omarchy's image runs from userdata (BRINGUP-M2 gate e, derekross#456 and kernel derekross#206 merged), and the buttons and the touchscreen passed gates f and g (kernel derekross#238 and derekross#241 merged): Boot, Storage, Touch and Buttons say so. For the Mi 8, three lines promised on derekross#505: BRINGUP-M1's [NOTES.md] link had no definition, the board DTS (kernel derekross#220) is merged, not in review, and the status line names the 2026-11-11 boot NOTES records. The POCO F3 row said derekross#25 was in review; it was closed as paused on 2026-11-11. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Adds the Xiaomi Mi 8 (
dipper) as a WIP, RAM-only first-light target. The descriptor refuses generic install, flash and push paths. The image boots withfastboot boot; its empty UFS write allowlist keeps every partition read-only. There is no persistent install or update path.The runbook gates the verified backups, serial-pinned fastboot commands, forced restart and RAM boot. #330 is merged; the device row links the bring-up notes.
The builder uses the Dipper DTS from linux-omarchy-mobile #220. The EA8074 panel is disabled in this first-light DTS; its separate driver and attended panel test are in kernel PR #218. Touch changes from #219 are in the kernel tree but touch remains disabled pending a hardware test.
Validation on head
5d917b4b198f454123f2ac029a665325e2262288:tools/pr-check origin/main,tests/dipper-probe, andgit diff --checkpass. Both CI checks pass, includingtests/all.Attended RAM boot on 2026-11-11 used kernel/DTS #220 head
26aa77c317cd029d16e58890c532562ca275c9f0.boot.imgSHA-256:665fcbd682cd8e64b3ffec1ff7f4ab9ca33a26b9b47b11073be7a3c267abf2b1;uname -r:7.3.0-rc6-omamobile-push1./dev/sdawas absent, every UFS partition readro=1, andsdb–sdfreadro=1. The watchdog driver and feeder, simpledrm framebuffer, USB/SSH, and the reserved0x85fc0000–0x8a8fffffmemory range were verified. No UFS partition was written.Physical screen state, keys, touch, GPU rendering, Wi-Fi and NFS link-loss recovery have not been tested in this run. Detailed boot records are in
device/dipper/NOTES.md.