Repository navigation
device/akita: first light and the boot console (M1) - #414
Conversation
The Pixel 8a boots our kernel from slot B, with USB networking, SSH and the framebuffer console. - BRINGUP-M1.md: the M1 runbook and its results (tests 1-5). - kernel.config: the lockup detectors the board file's bootargs need, as in husky's. - device.conf: SIMPLEFB_TRIG_CON="0x19470030 0x3061", after TRIG_CON read 0x3070 (masked) at handover on a booted 8a. - NOTES.md: the booted tree, the kernel command line (this bootloader keeps VENDOR_CMDLINE), the three display registers and the panel's command mode. - DEVICES.md: the 8a's clause in the zuma Wanted row. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, @aninmucek, this is a really clean first light. The runbook reads exactly like husky's, every step went the way it was written (the read-only I checked the descriptor line against your notes: Two small things before I merge:
Smaller suggestions, none blocking:
On the panel size: leaving it out for M1 is fine. You're right that 70 x 149 mm is too big for a 6.1-inch active area (stock's DPI reproduces exactly those numbers). We'll need some value before the session runs, because simpledrm otherwise assumes 96 dpi and the keyboard comes out half-height on husky. We can settle that then. I'll merge #192 first, then this one. Thanks again! |
From the review of derekross#414: - The status line names derekross/linux-omarchy-mobile#192 and its commits. M1.3's kernel commit, ce160abd9, is derekross#192's 1253914a9 with the same files. M1.4's -dirty run is derekross#192's 6a2999804: the kept DTS is blob 381ad1e0 and the flashed DTB has sha256 9a5d92a5, as derekross#192's. - Risks: every unmarked boot uses one of slot B's tries. If stock boots, decline any factory reset and take a fresh backup. - M1.2 lists the fastboot getvar values instead of a local helper, and the two rollbacks pin the serial. - NOTES.md: the COMPATIBLE and DTB rows point at derekross#192. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for the thorough review! Both are done in the new commit:
The same goes for M1.3's boot. Its kernel commit, I took the smaller suggestions too:
I also pointed NOTES.md's On the panel size: agreed, it can wait until the session needs it. |
|
Thank you, @aninmucek, everything I asked is in, and the source check matches. Your DTS blob I'll merge derekross/linux-omarchy-mobile#192 first, once its CI has run, then this. At merge I'll update the DEVICES.md clause from "a board DTS, not yet merged" to a link to #192. Thanks again for such a clean first light! |
The matrix re-read against what merged and ran on hardware since 2026-11-02: - Pixel 7: Bluetooth and the torch move to testing (kernel #196, #197, #426); fingerprint moves to WIP (kernel #207; the package side, #458, is in review); AVB footers and reboot=warm noted. - Pixel 8a: a new row, from first light and UFS behind the guard (kernel #192, #206; #414). - Pixel 6 Pro: GPU scaling and cooling (kernel #189) and UFS suspend (kernel #188) merged. - Pixel 9a: GPU levels merged through kernel #96; GNSS's moving-car session (#114) and the link driver (kernel #185). - Pixel 7a: Bluetooth's device tree merged (kernel #98). The Pixel 8 Pro's row is left to #472. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Pixel 8a (akita) boots our kernel from slot B with USB networking, SSH and the framebuffer console; the board file is linux-omarchy-mobile#192. BRINGUP-M1.md holds the runbook in husky's format with tests 1-5 and the image checksums; kernel.config adds the lockup detectors the board file's bootargs rely on; device.conf gets SIMPLEFB_TRIG_CON="0x19470030 0x3061", from TRIG_CON read once (0x3070, husky's value) before the write went in. NOTES records the booted tree, the command line and the display registers, and two findings: this bootloader keeps VENDOR_CMDLINE (so `splash` takes effect), and Google's panel driver gives a size too large for the panel, so the board sets none yet. Only slot B's five images were written, slot B was never marked, and the -dirty M1.4 kernel's DTS and DTB match derekross#192's.
The matrix re-read against what merged and ran on hardware since 2026-11-02: - Pixel 7: Bluetooth and the torch move to testing (kernel derekross#196, derekross#197, derekross#426); fingerprint moves to WIP (kernel derekross#207; the package side, derekross#458, is in review); AVB footers and reboot=warm noted. - Pixel 8a: a new row, from first light and UFS behind the guard (kernel derekross#192, derekross#206; derekross#414). - Pixel 6 Pro: GPU scaling and cooling (kernel derekross#189) and UFS suspend (kernel derekross#188) merged. - Pixel 9a: GPU levels merged through kernel derekross#96; GNSS's moving-car session (derekross#114) and the link driver (kernel derekross#185). - Pixel 7a: Bluetooth's device tree merged (kernel derekross#98). The Pixel 8 Pro's row is left to derekross#472. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Follows #308 and #349. The Pixel 8a (akita) boots our kernel from slot B, with USB networking, SSH and the framebuffer console. The board file is in derekross/linux-omarchy-mobile#192.
device/akita/BRINGUP-M1.md(new): the M1 runbook, in husky's format: the build, the checks before a flash, the first boot and the console. It also records results: tests 1-5 and the image checksums.device/akita/kernel.config(new): the soft and hard lockup detectors the board file'sbootargsrely on, as in husky's.device/akita/device.conf:SIMPLEFB_TRIG_CON="0x19470030 0x3061". As you asked on device/akita: stage 0 notes and descriptor for the Pixel 8a #308,TRIG_CONwas read once from our initramfs shell with the bootloader's logo still on the panel, and recorded in the notes before the write went in. It reads 0x3070 (masked), husky's value.device/akita/NOTES.md:RDMA_BASEADDR_P00xfac00000, DECON0GLOBAL_CON0x133,TRIG_CON0x3070) and the panel's command mode;docs/DEVICES.md: the 8a's clause in the zuma Wanted row.Two findings that may matter beyond akita:
VENDOR_CMDLINE. The kernel command line is our DTBbootargs, thenVENDOR_CMDLINE, then ABL's own arguments. cheetah's notes say gs201's ABL ignores the vendor command line, and husky's test 9 says the same of zuma; on the 8a it doesn't. Sosplashis on, and the init draws Omarchy's splash, as for Plymouth, instead of its status lines. The panel showed the splash in place and in the right colours, then console text written over it.How it was tested:
*_bboot images were written, bybin/omamobile flash. Slot A was never touched, and slot B was never marked successful.reboot-to bootloader.Checks:
tests/all: 375 ok, 0 not ok.tools/pr-check: passes (identifiers, blobs, sign-offs, scripts).DEVICE=akita bin/omamobile initramfs-config: it packs the trigger pair andgoogle,zuma-akita.tools/phone-smoke: not run. It needs the Arch root and a session, and M1 boots only the initramfs.🤖 Generated with Claude Code