Skip to content

device/husky: Wi-Fi on a test kernel - #216

Closed
greenbrettmichael wants to merge 1 commit into
derekross:mainfrom
greenbrettmichael:husky-wifi-docs
Closed

greenbrettmichael wants to merge 1 commit into
derekross:mainfrom
greenbrettmichael:husky-wifi-docs

Conversation

@greenbrettmichael

Copy link
Copy Markdown
Contributor

The Pixel 8 Pro's Wi-Fi works on a test kernel, derekross/linux-omarchy-mobile#156 (a draft, stacked on #153, #143 and #56), with the firmware from #214.

device/husky/NOTES.md: a 2026-10-31 entry for Wi-Fi.

docs/DEVICES.md and device/husky/ROADMAP.md: husky's Wi-Fi goes from no to testing, since it isn't in the kernel the image ships. It can move to works once #156 and the PRs under it reach omamobile-int and the packaged kernel. The roadmap's first step for Wi-Fi is now a second phone's test.

tools/pr-check passes.

🤖 Generated with Claude Code

@derekross

Copy link
Copy Markdown
Owner

Thanks for writing this up so thoroughly. The notes on the NCI backplane, the trap before release and the BAR0 warning will save the next person a lot of time, and the "testing" cell reads right next to Touch.

#214 is merged now. The branch conflicts with main in docs/DEVICES.md (the Pixel 9a row above yours changed), so CI never ran; a rebase that keeps main's 9a row and your husky row fixes it.

A small one: NOTES pins the tested kernel at f47c5bd34, which is great. #156 has since been rebased to 717fba4f, and the only change I can see is #143's join-parameter struct (chanspec_list[1] → chanspec_list[]). Could you add a clause saying so, or re-check a join on the new head?

@greenbrettmichael

Copy link
Copy Markdown
Contributor Author

Thanks Derek. Rebased onto main, keeping main's 9a row and the husky row with the Wi-Fi cell, so CI should run now.

On 717fba4f: I re-checked rather than just adding a clause. The display test kernel husky-test-20261031-d3 contains 717fba4f, with an identical brcmfmac. The phone joined its network through NetworkManager at boot on it (2026-10-31), and again today on husky-test-20261101-e1, which has #156 rebased onto omamobile with the same Wi-Fi code. NOTES now says that the only change is #143's chanspec_list[] and that the join was re-checked.

A NOTES entry for the BCM4398 under kernel derekross#156 (draft): the chip and
its NCI backplane, the pins, zuma's PCIe PHY, how stock picks the
firmware files (derekross#214 does the same), what brcmfmac needed, the reload
fix, throughput, what isn't done, and the BAR read that hung the phone.

DEVICES and the ROADMAP move husky's Wi-Fi from no to testing: it is
not in the kernel the image ships until derekross#156 and the PRs under it land.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
@derekross

Copy link
Copy Markdown
Owner

Thanks, Brett. Both points are in:

The new throughput figures (108-132 down on e1, with the CPU0 load next to them) are a nice addition.

One thing for the order: Lef's battery PR (#249) changes the same husky row in docs/DEVICES.md, the Battery and Charging cells where you changed Wi-Fi. I'll merge yours first, and #249 picks up your cell when it rebases.

Merging. Thanks for writing this up so well.

@derekross derekross closed this in dc4e755 Nov 1, 2026
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The Pixel 8 Pro's Wi-Fi on a test kernel: the notes, the roadmap and the DEVICES cell (greenbrettmichael). Reviewed in round 32: see the pull request for the tests.

Closes derekross#216

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants