Repository navigation
Conversation
1a907db to
c717b3b
Compare
|
Thank you, Peter. This is a tidy, conservative package: every file is a copy of one that runs on a Pixel today, the test pins each copy, and leaving out bootctl, the USB rescue and every service until a 6a has booted is exactly right. Including raven's s2idle drop-in, since bluejay's bootargs don't set Two things before it can land:
A small one: raven's and tegu's READMEs carry the SPDX header line; please add it here too. |
c717b3b to
e12583a
Compare
|
Thank you, Peter, and sorry for the slow reply. Everything I asked for on the 3rd is in: the package's I re-ran the package's test today on top of current Nothing more is needed from you until a Pixel 6a boots. Two things I'll take care of when this lands, so you don't need to chase them:
Thanks again for keeping this one so conservative. |
…bled The package device/bluejay/device.conf names, so tools/build-rootfs can build a 6a image with the [omamobile] repository configured: felix's first-light shape without the fold's lid and cover-touch parts, plus the suspend-to-idle drop-in. The storage udev rule, the usb0 address with USB as the last gateway, NetworkManager off usb0, logind ignoring the power key, [Sleep] on s2idle with no hibernation, the mirrorlist and pacman hook, reboot-to (cheetah's source) and a copy of the descriptor; provides and conflicts omamobile-device, depends on omamobile-keyring. The sleep drop-in is raven's, byte for byte: gs101's firmware offers PSCI SYSTEM_SUSPEND, so the kernel lists deep, and Linux has no gs101 sleep sequence to wake from it (device/raven/SUSPEND-PLAN.md). Bluejay's bootargs, like oriole's, don't set mem_sleep_default, so the file is what keeps systemctl suspend on s2idle, as asked in the review of linux-omarchy-mobile#179. No service is enabled, no modprobe policy ships, and there is no omamobile-bootctl: marking slot B on the gs101 phones is on hold (derekross#252), and bin/omamobile initramfs builds its freestanding helpers without the source, as for oriole. No Pixel 6a has run it; every file is a copy of one that runs on raven or cheetah, and test/all pins each copy. The descriptor copy carries the AVB lines the factory image settled (derekross#350), the same bytes as device/bluejay/device.conf. The first boot's phone-smoke report goes to derekross#348, the 6a's own thread, and NOTES.md. test/all and tests/packages pass on the laptop. The README carries the SPDX header line raven's and tegu's do. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
e12583a to
8d0e50f
Compare
|
The first Pixel 6a boot/smoke result is now posted in #348, with the persistent desktop/dependency notes already merged through #561. This is the historical development stack, not a release-kernel or passive-package qualification. I kept the follow-up on your current The earlier local patch's retained-display trigger is intentionally excluded. This branch enables no service, driver, experimental display refresh or slot-success writer. Historical startup/configuration stays in #565. Validation: the complete package fixtures and policy checks pass, independent source review found no remaining blocker, and the candidate builds as an aarch64 package. The shared reboot-to source already matches current main, so no extra source-refresh delta is needed. The current development handset reports device-bluejay 0.1.1 too, but its older package owns active check/service/modprobe files that this passive candidate omits. I have not replaced it and do not claim a qualified upgrade: those files need an explicit preserved/migrated startup arrangement first. No package agreement or hardware migration is assumed here. The automatic boot-success mask and AUTO_WRITE=no remain in force. |
|
Thank you, Peter, for the rebase: it resolved the One thing is needed from you. CI is red on a lint that landed on ! sed -n '/^\[Network\]/,/^\[/p' "$net" | grep -c '^Gateway=' >/dev/null || fail "usb0 sets no default route in [Network] (metric 0)"Because On leaving draft: not yet, and it isn't waiting on you. A Pixel 6a boots now (thank you, @latentoperator, for the report in #348), but on a development kernel with a private package of the same name that owns start-up services and a module blacklist, and this package hasn't been installed on a 6a. What I'd like to see before it leaves draft is a smoke report from a 6a where @latentoperator, three things on how that comes together:
Peter, when you push the one-line fix, two sentences could also catch up with the first boot: the description's "no Pixel 6a has booted our kernel" and the README's "merged without a boot" are now "a 6a boots a development kernel (#348); the published kernel and this package haven't run on it yet". |
|
November 13 coordination update: #562, #563 and #565 have landed, and this 6a is now running Omarchy 4.5.0-3 with its mobile migrations completed. The revised kernel's headless RAM/touch/pool/PCIe/Wi-Fi stages also passed; the current graphical desktop is restored on the historical development kernel (details in #348). The package gate remains exactly as requested: the passive 0.1.0-1 package has not been installed or smoke-qualified. The locally active 0.1.1 package remains protected by I am not asking to fold the earlier boot-update.conf-owning 0.1.1 coordination follow-up into this PR; your requested ownership boundary stands. The author's lint fix and passive-package phone qualification remain separate from the new kernel results. |
|
Thank you, @latentoperator, for the update, and for keeping the local package held and leaving the @PeterXMR, two one-line changes are needed when you next push, and the second one is my fault:
While you're in there, the two sentences from last time can catch up too: "no Pixel 6a has booted our kernel" in the description and "merged without a boot" in the README are now "a 6a boots a development kernel (#348); the published kernel and this package haven't run on it yet". Nothing else has changed: the pull request stays a draft until there's a smoke report from a 6a with |
The boot-update.conf ownership follow-up was not accepted on derekross#346. Keep the package passive and describe the attended migration and smoke report that still gate it. Assisted-by: OpenAI Codex
The boot-update.conf ownership follow-up was not accepted on derekross#346. Keep the package passive and describe the attended migration and smoke report that still gate it. Assisted-by: OpenAI Codex
The boot-update.conf ownership follow-up was not accepted on derekross#346. Keep the package passive and describe the attended migration and smoke report that still gate it. Assisted-by: OpenAI Codex
…ejay UPSTREAM status (#666) The transfer profile behind linux-omarchy-mobile #225's aggregation-retry fix needs a phone, so it lives here and not in the kernel's selftests. Sixteen fresh `tools/phone-ssh` connections each pull 2 MiB of zeros from the phone, checked by size and SHA-256 under one 20 s deadline, with no retry and no write on the phone. A failure names the transfer and the check and shows ssh's stderr. `tests/ncm-transfer` runs it against a stand-in `ssh`. A pass shows that the link carried the transfers, not that the retry ran, and it covers neither laptop sleep nor a replug. Bluejay's UPSTREAM page is brought up to the November kernel revisions, none of which has booted on the phone, and it records that #346 stays passive. Assisted-by: OpenAI Codex
What and why
Stage 0, part 2 of the Pixel 6a port (#2):
packages/omamobile-device-bluejay0.1.0, the packagedevice/bluejay/device.confnames, sotools/build-rootfscan build a 6a image with the[omamobile]repository configured. It follows the merged first-light DTS (linux-omarchy-mobile#179) the same way: nothing has booted it, and it stays a draft until a 6a owner posts the firsttools/phone-smokereport on #2.It is felix's first-light shape without the fold's lid and cover-touch parts, plus the suspend-to-idle drop-in the #179 review asked for: the storage udev rule, the usb0 address with USB as the last gateway, NetworkManager off usb0, logind ignoring the power key,
[Sleep]on s2idle with no hibernation (raven's file byte for byte: gs101's firmware offers PSCI SYSTEM_SUSPEND, the kernel listsdeep, and Linux has no gs101 sleep sequence to wake from it; bluejay's bootargs, like oriole's, don't setmem_sleep_default), the mirrorlist and pacman hook,reboot-toand a copy of the descriptor.provides/conflicts=(omamobile-device),dependsonomamobile-keyring.Not in it, on purpose: no service is enabled, no modprobe policy ships, no
omamobile-bootctlor boot-success marker (marking slot B on the gs101 phones is on hold, #252;bin/omamobile initramfsbuilds its freestanding helpers without the source, as for oriole), no USB rescue, Wi-Fi, charger, haptics, display options or cameras. Each comes in when a booted 6a has given it a runbook and the evidence. The package is also not added totools/build-packages'ORDERor totests/all's package list: husky, tegu and dodge aren't there either, so joining them is the maintainer's call when a package is published. A defaulttools/build-packagesstill builds it, through the trailing glob after the listed packages.Every file is a copy of one that runs on the Pixel 7 Pro (cheetah) or the Pixel 6 Pro (raven, the same SoC), and
test/allpins each copy withcmp, the descriptor againstdevice/bluejay/device.conf, and checks that the staged tree holds no system unit, no modprobe policy and nothing that marks a slot, loads a driver or starts hardware. Thecmppins run only from the repository (tests/packages, CI):makepkg'scheck()on a copied package directory skips them, as #222 asked.Two caveats the README records: a replug may need a reboot, because nothing closes the Type-C chip's USB2 switch again (raven's package does for its MAX77759; the 6a's chip, bus and address are unread), and on a first boot
reboot-to bootloadermost likely just boots slot B again, because the descriptor lists noINITRAMFS_MODULES(raven's records the PMIC and reboot-mode modules it needs), so fastboot is by the buttons.Device and build
uname -r): n/aChecks (no phone needed)
tools/pr-check origin/mainpasses (7 ok)tests/allpasses: all 34 suites ok, run in CI'sarchlinux:latestcontainer with Docker on this Mac (the host shell alone can't: bash 3.2, BSD sed), and CI's Tests job is greentests/packagespasses: omamobile-device-bluejay 17 ok, 24 of 26 suites ok in the same container; omamobile-audio and omamobile-omarchy fail there only under x86_64 emulation (a 2 s watchdog wait, a missing exec reported as 127 instead of ENOENT) and pass in CIversionbumped, and the new version is in the commit subjectCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:On the phone
makepkgbuild on aarch64, an install on a 6a,tools/phone-smokeuserdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)tools/phone-smokereportNot run: no Pixel 6a has booted this build. The first boot's report goes here and to #2.