Repository navigation
Conversation
… tree Stage 0, part 1 of the Pixel 6a port (derekross#2), from Google's GPL device trees for bluejay and gs101 (kernel/devices/google/bluejay and kernel/devices/google/gs101 at android-16.0.0_r0.9) and the image facts oriole's notes record, with no bluejay factory image read and no phone: device.conf, an empty board dtbo source, NOTES.md, the Wanted row in DEVICES.md and bluejay in the two pack-time tests. No matrix row yet: no gate has passed, so the device stays under Wanted as mustang does. Confirmed from the GPL trees: bluejay boots the same two gs101 base DTBs as oriole, soc_id 0x9845000 (A0) and 0x9845001 (B0), which also settles the labels oriole's notes left [I]; six board ids, the MP 1.0 entry being 0x20506/0x10000; the S6E3FC3 panel at 1080x2400 and an ST FTS touch controller on SPI; and that the two LDOs upstream's oriole DTS describes are shared gs101 PMIC rails, so the board DTS leaves them out. Still inferred from oriole and marked [I] in NOTES.md: that a retail 6a boots the MP 1.0 dtbo entry (raven boots its DVT entry, so only the stock dtbo.img or ro.boot.dtbo_idx settles it), the vendor command line, the vendor_boot page size, the OS version and patch level, and the partition layout (no init_boot, no vendor_kernel_boot). The bluejay factory image confirms or corrects them. Open, and a stop before any flash: whether the 6a's vbmeta_b chains boot and vendor_boot, so whether slot B needs AVB_FOOTERS; stock's vbmeta.img and the boot images' footers decide it. No SIMPLEFB_TRIG_CON and no BRINGUP_PROBE until a booted 6a has read gs101's DECON register. The DTB, exynos/google/gs101-bluejay.dtb, comes from the first-light board DTS prepared on a local omamobile-gs101-bluejay-dts kernel branch, to be opened as a pull request against linux-omarchy-mobile's omamobile; images can't be built for bluejay until that DTS is in a kernel build. The descriptor carries no comments: the provenance of every key is a table in NOTES.md. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Thank you, Peter, and welcome. This is a careful stage-0 PR: every value in the descriptor has a source and a mark, the [I] values are honest about what only a retail 6a or its factory image can settle, and the AVB question is written down as a stop before any flash rather than guessed. What I checked:
A few small things. I'm happy to make them myself before merging, since you've allowed edits:
A question, not a blocker: do you have a Pixel 6a to bring up, or is this groundwork for whoever does? Either is welcome. If you have one, the next step is the read-only stock capture in your "Still needs a phone" list (CONTRIBUTING §5.1, with captures kept off the repository), and then the factory image's Thanks again. With those three edits in, this is ready to merge. |
… tree (derekross#265) Stage 0 for the Pixel 6a (bluejay, gs101): the device descriptor and notes, every value sourced from Google's GPL bluejay device tree at android-16.0.0_r0.9 (board id 0x20506, rev 0x10000, A0/B0 soc_id, the S6E3FC3 panel at 1080x2400). The descriptor carries no register write and no probe. Images wait for the board DTS in linux-omarchy-mobile#179. Maintainer edits at merge: link kernel derekross#179, describe the board-id rule in plain words, and drop a source line that backs no value. Closes derekross#265 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Stage 0, part 1 of the Pixel 6a port (#2):
device/bluejay/device.conf, an empty board dtbo source,NOTES.md, the Wanted row indocs/DEVICES.md, and bluejay in the two pack-time tests (tests/storage-guard,tests/usb-product). Nothing has been flashed or booted, no 6a has been queried, and no factory image has been read. No matrix row: no gate has passed, so bluejay stays under Wanted as mustang does, with its notes linked.Where the values come from. Google's GPL device trees for bluejay and gs101 (
kernel/devices/google/bluejayandkernel/devices/google/gs101atandroid-16.0.0_r0.9), with the raviole tree as the oriole control, and oriole's recorded image facts for what a 6a shares with a Pixel 6. The descriptor carries no comments; the table "Whatdevice.confrests on" inNOTES.mdgives each key its source and mark.soc_id(0x9845000 A0, 0x9845001 B0, which also settles the labels oriole left [I]); the six bluejay board ids, with MP 1.0 at 0x20506/0x10000; the S6E3FC3 panel at 1080x2400; an ST FTS touch controller on SPI; and why the board DTS leaves out the two LDOs upstream's oriole DTS describes (shared gs101 PMIC rails).dtbo.imgorro.boot.dtbo_idx),VENDOR_CMDLINE,VENDOR_PAGESIZE,OS_VERSION/OS_PATCH_LEVEL(informational on a GKI header; stock ships 0), and the partition layout (BOOT_IMAGES,UFS_RW: noinit_boot, novendor_kernel_boot).vbmeta_bchainsbootandvendor_boot, so whether slot B needsAVB_FOOTERS(RELEASES §3.1). The factoryvbmeta.imgand the boot images' footers decide it; the notes list what to read.SIMPLEFB_TRIG_CONandBRINGUP_PROBE, until a booted 6a has read gs101's DECON register (L-4, L-365).The kernel side.
DTB=exynos/google/gs101-bluejay.dtbis a first-light board DTS (binding entry plusgs101-bluejay.dts: oriole's file with bluejay's model, compatible andsoc_id, without the LDO block), prepared on a localomamobile-gs101-bluejay-dtsbranch and to be opened as a pull request against linux-omarchy-mobile'somamobileunder the title "arm64: dts: exynos: google: Add Pixel 6a (bluejay) first-light board". It is in no published kernel, and the Wanted row says so (L-149).DEVICE=bluejay bin/omamobile imagescan't run until that DTS is in a kernel build; this descriptor PR doesn't need it to merge.Checks.
tools/pr-check origin/mainandtests/allin the project's build container on this commit (results below);dtc -@compiles the overlay andfdtoverlayapplies it to the host-builtgs101-bluejay.dtbwith no change to the DTB; the identifier grep over the diff finds nothing; Google's tree was re-read at the tag and every cited value matches; the Wanted row is the only bluejay mention inDEVICES.md.Container run, 2026-11-01,
omamobile-build:24.04overmain053583e (the commit was then rebased onto 7ea8ab5 with the same diff; on the host,tools/pr-check origin/mainon the rebased commit passes its six identifier, blob and sign-off checks, andbash -nof both touched tests passes):Kernel pull request: derekross/linux-omarchy-mobile#179 (
omamobile-gs101-bluejay-dts, heade85110d61).