Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions device/husky/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,34 @@ Sources:
- `P/`: postmarketOS pmaports `device/testing` (2026-10-21).
- `G/`: Google's GPL kernel for this phone, `android-gs-shusky-6.1-android16` ([source.android.com: Build Pixel kernels](https://source.android.com/docs/setup/build/building-pixel-kernels)).

## 2026-10-31: Wi-Fi

Wi-Fi works on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (a draft, stacked on #153, #143 and #56), at `f47c5bd34` on greenbrettmichael/linux-omarchy-mobile `omamobile-zuma-husky-wifi`, with the repository's husky config (`CONFIG_PHY_ZUMA_PCIE=m` is in #214), `modules-push` and the firmware from [#214](https://github.com/derekross/omarchy-mobile/pull/214). The phone joins its network at boot through NetworkManager. #156 has since been rebased to `717fba4f`; the only change is #143's join-parameter struct (`chanspec_list[1]` to `chanspec_list[]`). The phone joined at boot on that head too, as part of the display test kernel (tag `husky-test-20261031-d3`, which contains `717fba4f`), on 2026-10-31.

- **The chip** [V]: a BCM4398 D0 (chip `0x4398` rev 3, PCI `14e4:4444`) on pcie_1, one Gen3 lane, as on stock.
- Its backplane is Broadcom's newer NCI interconnect (socitype 6), not AI. #156 ports enough of Google's `nciutils.c` to brcmfmac to find the cores and run the ARM.
- The firmware is stock's 24.100.671.86.2 (shared-memory API 9).
- **Power and pins** [V, `R/` live DT]: WL_REG_ON is `gph3-4`, PERST `gph3-0`, CLKREQ `gph3-1`, dev_wake `gph3-5` and host_wake `gpa5-1` (FAR_ALIVE). BT_REG_ON (`gpn8-0`) isn't wired yet.
- **The PCIe PHY** [V, `G/`]: zuma's Gen3 PHY is not gs201's, so #156 adds its own driver from stock's tables, and releases the PHY's isolation through the PMU (0x3ec8). The host is gs201's driver with a zuma compatible.
- **The firmware files** [V, the first husky's stock log]: stock loads `fw_bcmdhd.bin_4398_d0`, `bcmdhd_clm.blob_4398_d0` and `bcmdhd_txcap.blob_4398_d0` by chip revision.
- It picks the NVRAM by the hardware SKU: `bcmdhd.cal_MMW` on this phone.
- `tools/extract-vendor-firmware -d husky -s SKU` (#214) does the same from the owner's own image.
- **What brcmfmac needed** [V]:
- `event_msgs_ext`, a 4-entry band list, escan v3, v114 BSS info, and the versioned join without firmware supplicant;
- control buffers at the lowest packet IDs;
- D2H items read only after the firmware's checksum and epoch say they're finished;
- the 4389's host-side 802.3/LLC TX header (without it the firmware trapped in `txq_hw_fill`);
- a wait for the firmware's boot interrupt before reading its shared address.
- **Reloading** [V]: the chip's always-on domain keeps the firmware's state across WL_REG_ON, FLR and a PMU watchdog. A second load got no boot interrupt until the phone rebooted.
- #156 makes the firmware trap before release (doorbell 7, `0xdead0002`, as bcmdhd's `DHD_DONGLE_TRAP_IN_DETACH`).
- Since then, `brcmfmac` reloads and `pcie_gs201` + `brcmfmac` reloads reconnect in 17–18 s.
- **Throughput** [V]: on 2.4 GHz at -44 to -46 dBm (216 Mbit/s receive rate), 108–132 Mbit/s down over five 50 MB downloads from Cloudflare, and 58–73 up; 11 ms to 1.1.1.1, with no loss. A Pixel 9 gets about 95 down on the same network. That's on `husky-test-20261101-e1`, 2026-11-01, over a Gen3 x1 link with INTx: all the Wi-Fi interrupts land on CPU0, which was 22–48 % busy at 132 Mbit/s, so INTx isn't the limit at these rates. Earlier test kernels got 50–87 down and 47–70 up. The scan sees 5 GHz networks; none was joined yet.
- **Not done** [V]:
- P2P: `brcmf_p2p_create_p2pdev: timeout occurred` at load, since the firmware never confirms the P2P device interface. Station mode doesn't need it.
- A reload after a real firmware crash, which can't take the trap, is untested.
- Bluetooth.
- **Lesson** [V]: a raw `/dev/mem` read of the Wi-Fi chip's BAR0 while it was in a bad state hung the phone, which panicked and rebooted. Don't read the endpoint's BARs from userspace.

## 2026-10-31: a second phone: Kioxia 256 GB, UFS 4.0

A second retail Pixel 8 Pro, first run through the same read-only steps. `R2/` below means read-only queries of this phone (`adb shell getprop` while booted, `fastboot getvar all`, the fastboot screen), facts only, no serial, IMEI or MACs. The kernel is `omamobile` at `1c5ba1aa2` unless noted.
Expand Down
4 changes: 2 additions & 2 deletions device/husky/ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Status words as in DEVICES.md. "9a" is the Pixel 9a (`tegu`) work. "Needs" lists
| Touch | testing (c6) | [Brett](https://github.com/greenbrettmichael) | done | [#153](https://github.com/derekross/linux-omarchy-mobile/pull/153) in review; the ACPM probe order fix (Brett); W4HO's [#150](https://github.com/derekross/linux-omarchy-mobile/pull/150) fixes the SPI FIFO flush for every port (not needed for touch) | none: re-test after each kernel |
| Buttons | testing (c6) | Brett | done | [#148](https://github.com/derekross/linux-omarchy-mobile/pull/148) in review | none |
| USB net | testing | Brett (per his comments on #1) | done | USB host and Type-C are in Charging | none |
| Wi-Fi | no | Brett (per his comment on #1) | 9a [#56](https://github.com/derekross/linux-omarchy-mobile/pull/56) (BCM4383, open); cheetah [#143](https://github.com/derekross/linux-omarchy-mobile/pull/143) (BCM4389, open); [WIFI-BATTERY-PLAN](../cheetah/WIFI-BATTERY-PLAN.md) | BCM4398: the PCIe link comes up (Gen3 x1, `14e4:4444`), then `brcmfmac` stops at "chip backplane type 6 is not supported": the chip uses Broadcom's newer NCI interconnect, which Brett is porting from Google's GPL driver ([his status on #1](https://github.com/derekross/omarchy-mobile/issues/1#issuecomment-6543682102)) | Review and test his branches when they appear; read WIFI-BATTERY-PLAN W1 to W4 meanwhile |
| Wi-Fi | testing | [Brett](https://github.com/greenbrettmichael) | done | [#156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (draft): zuma's PCIe PHY and the BCM4398 (NCI backplane) in brcmfmac, stacked on #153, #143 (BCM4389) and #56 (API9), which have to land first; firmware from the owner's image with [#214](https://github.com/derekross/omarchy-mobile/pull/214). Open: P2P, recovery after a firmware crash, joining 5 GHz ([NOTES](NOTES.md)) | Test #156 on a second phone: `tools/extract-vendor-firmware -d husky -s <SKU>`, then check the scan and a join |
| Bluetooth | no | unassigned | 9a [#122](https://github.com/derekross/linux-omarchy-mobile/pull/122) (open); cheetah [BLUETOOTH-PLAN](../cheetah/BLUETOOTH-PLAN.md) | The controller is probably the combo chip that does Wi-Fi [I]; its UART, power and wake lines [I: not known to me] | Find the Bluetooth node in Google's tree; write `BLUETOOTH-PLAN.md` |
| Battery | no | Lef | cheetah [POWER-PLAN](../cheetah/POWER-PLAN.md), [WIFI-BATTERY-PLAN](../cheetah/WIFI-BATTERY-PLAN.md); `gs201-cheetah.dts` has the same chip family. The 9a's [#119](https://github.com/derekross/linux-omarchy-mobile/pull/119) is the MAX77779 and does not apply as is | Stock overlay [V, same source as Display]: fuel gauge `maxim,max77759` @0x36, charger `max77759chrg` @0x69, Type-C `max77759tcpc` @0x25 and `max77729pmic` @0x66, all on `hsi2c_11`; also `nxp,pca9468` and the wireless charger `idt,p9412`. Zuma has no clock controller for that I2C block yet (CMU_PERIC, not in `clk-zuma.c`) and no I2C or USI nodes [V]. `tools/phone-smoke` reports "no battery power supply" [V] | Derive the PERIC clocks from Google's cmucal tables, add the I2C nodes, then probe the gauge read-only. **Do not poke the PMIC from userspace** (AGENTS.md §1) |
| Charging, USB-C | no | Lef | cheetah [USB-C-PLAN](../cheetah/USB-C-PLAN.md); 9a: [#97](https://github.com/derekross/linux-omarchy-mobile/pull/97) is `tcpci_maxim` for the MAX77779 (merged), so check what husky's MAX77759 needs [I] | Same I2C bus as Battery; the USB data switch closes on unplug (AGENTS.md gotcha) | As Battery |
Expand All @@ -56,7 +56,7 @@ A proposal, not a verdict; Brett and Derek know the hardware better.
5. **Suspend**, after UFS hibern8 and the regulators; then **Bluetooth** once the combo chip's firmware path is clear (it depends on the Wi-Fi work), then **audio, sensors, fingerprint**, each gated.
6. **Modem** once a SIM is found, after power, USB-C and the NV-protection steps in MODEM-PLAN.

Brett has Wi-Fi; coordinate on #1.
Wi-Fi works on a test kernel (#156); a second phone's test is the next step there.

## How to help without risking a phone

Expand Down
Loading