Skip to content

DEVICES: status after the 2026-10-28 evening merges - #140

Merged
derekross merged 1 commit into
mainfrom
devices-2026-10-28-evening
Oct 29, 2026
Merged

derekross merged 1 commit into
mainfrom
devices-2026-10-28-evening

Conversation

@derekross

Copy link
Copy Markdown
Owner

The matrix after the merges since #118 (4b88319). Each changed cell goes by merged notes in this repository; every matrix row keeps its 26 | separators (counted before and after).

Cell changes

Row Cell Before After Evidence
Pixel 7 (panther) Boot board file in review, kernel #108 the board file is in the published kernel, kernel #108 derekross/linux-omarchy-mobile#108 merged 2026-10-28
panther Storage in review, kernel #108 in the published kernel, kernel #108 as above (gs201-panther: enable UFS); testing word unchanged, from BRINGUP-M1 boot 4 / the Arch root
panther Buttons in review, kernel #108 in the published kernel, kernel #108 as above (add the volume and power keys); BRINGUP-M1 boot 5
panther USB net in review, kernel #108 in the published kernel, kernel #108 as above
panther Touch no (FT3658, no mainline driver) still no: the driver (derekross/linux-omarchy-mobile#109) and the rails (#108) are published, the touch node isn't; notes end with the chip not answering (link to BRINGUP-M1 boot 8) derekross/linux-omarchy-mobile#109 merged; panther's notes end at boot 8 with chip-ID reads of zero
Pixel 6 Pro (raven) Charging no works (MAX77759 charger at stock limits with its temperature guard, loaded at boot by device-raven 0.1.26; full charge to 100 %; battery node kernel #112, tested on an unpublished kernel; link to USB-PLAN §4) #112/#126 (device-raven 0.1.26); device/raven/USB-PLAN.md §4, C0-C5 passed 2026-10-28 (g3ba8c15c89b8, gdd5e1655ef91); derekross/linux-omarchy-mobile#112
raven Torch works (unpublished kernel, omamobile-gs101-torch) works (tested on omamobile-gs101-torch; the LED's node is now in the published kernel, kernel #113, not yet run from it) derekross/linux-omarchy-mobile#113 merged (plus leds: flash: lm3644: the Pixel 6 uses it too); CONFIG_LEDS_LM3644=m comes from kernel/configs/omamobile.config; device/raven/HAPTICS-TORCH-PLAN.md results are from gd2521ee96675 on the torch branch, none from the published kernel
Pixel 9a (tegu) Fingerprint no WIP (Trusty's TA runs and the HAL sees the sensor, unpublished kernel; enrollment waits for the factory calibration) device/tegu/FINGERPRINT-PLAN.md: F0, F2-F5, F6a, F6b passed (2026-10-27/28); F6c blocked on calibration; #101 (omamobile-fingerprint 0.1.10) maps the stores

Also: device/panther/BRINGUP-M1.md status and the header of device/panther/NOTES.md no longer say the board file is in review; BRINGUP-M1 no longer says the FT3658 "has no mainline driver" and now says it never answered in boots 7-8.

Left unchanged on purpose

Checks

  • tools/pr-check origin/main: all ok.
  • tests/all: passes (rootfs-smoke skipped, no root image).

🤖 Generated with Claude Code

The matrix after the merges since #118, with each cell going by the
merged notes:

- Pixel 7 (panther): the board file (derekross/linux-omarchy-mobile#108) and the
  FT3658 touch driver (derekross/linux-omarchy-mobile#109) have merged
  into the published kernel, so Boot, Storage, Buttons and USB net say
  "in the published kernel" instead of "in review". Touch stays "no":
  the driver and the touch rails are published, but the board file has
  no touch node, and panther's notes end at boot 8 with the controller
  not answering. BRINGUP-M1's status and NOTES' header say the same.
- Pixel 6 Pro (raven), Charging: no -> works. device-raven 0.1.26 (#112,
  #126) loads the MAX77759 charger at boot with its temperature guard;
  USB-PLAN section 4 records C0-C5 passed on 2026-10-28, a full charge to
  100 % included. The battery node is derekross/linux-omarchy-mobile#112;
  the runs were on an unpublished integration kernel, and the cell says so.
- raven, Torch: still works; the LED's node is now in the published
  kernel (derekross/linux-omarchy-mobile#113), tested on
  omamobile-gs101-torch and not yet run from the published kernel.
- Pixel 9a (tegu), Fingerprint: no -> WIP. FINGERPRINT-PLAN records F0
  and F2-F6b passed on an unpublished kernel: Trusty's TA runs and the HAL
  sees the sensor; enrollment waits for the factory calibration (F6c).
  omamobile-fingerprint 0.1.10 (#101) maps Trusty's stores for it.

Left as they were: tegu's Charging (the MAX77779 charger driver,
derekross/linux-omarchy-mobile#92, is published, but tegu's notes record
no run of it), the gs201 HSI2 pin controller
(derekross/linux-omarchy-mobile#123, no cell), felix (#35 is a plan) and
cheetah (nothing merged for it).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross
derekross merged commit e52abea into main Oct 29, 2026
2 checks passed
@derekross
derekross deleted the devices-2026-10-28-evening branch October 29, 2026 14:28
derekross added a commit that referenced this pull request Oct 30, 2026
The matrix and the Wanted list against what has merged since #140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were
  closed because they landed unchanged through kernel #134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the
  2026-10-28 notes. Touch stays WIP: kernel #134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel #133)
  and the kernel option with the touch notes (#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names
  its open kernel PR, #116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133)
  records it scanning through its own UART; kernel #98 and #98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes
  the merged tier 1 auto-sleep (#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open #171, #172, #174-#176.
- Wanted: coral's #52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (#55, #56, #58,
  #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and
  kernel #115, both open.

The Pixel 9a row and the Pixel 9 family line are left to #165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The matrix and the Wanted list against what has merged since derekross#140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were
  closed because they landed unchanged through kernel derekross#134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the
  2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133)
  and the kernel option with the touch notes (derekross#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names
  its open kernel PR, derekross#116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133)
  records it scanning through its own UART; kernel derekross#98 and derekross#98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes
  the merged tier 1 auto-sleep (derekross#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176.
- Wanted: coral's derekross#52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58,
  derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and
  kernel derekross#115, both open.

The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every
status word still parses with the website's parseCell.

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.

1 participant