Feature status

As of 2026-11-05, 1:57 PM EST. Kernel: torvalds a804c57 plus kernel/patches/0001-0011. Board DTS: dts/x1e80100-google-mica.dts. The default state is “untested”. Every row cites the recon note it rests on, or “none” when no note covers it.

This is the feature matrix of ADR 0010: the milestones note, recommendation 2, which the owner adopted on 2026-11-04 (“all a” to its section 5). Asahi and Nura publish their feature tables the same way.

Patch numbers: 0008 and 0009 here are the PCIe GDSC and PCIe PHY GDSC retention patches. Both numbers named other patches before the rule against reusing numbers. 0008 was a GENI I2C timing test (commit 16a2828, attempt 2026-11-04-2), and 0009 was the IRQ-to-CPU-1 diagnostic (commit cee735d, attempt 2026-11-04-3, deleted by ADR 0009). Recon notes about those two attempts mean the old patches.

Legend

• State: works, partial, broken or untested. A parked row keeps its state, and its note says “parked until ” (ADR 0010, update 2026-11-04).
• Where it works:
  • mainline at a804c57: the driver is unchanged;
  • + patch NNNN: a local patch in kernel/patches/;
  • board DTS: needs the mica device tree;
  • config fragment (name): kernel/<name>.config builds the driver in, because the initramfs loads no modules.
  • These combine as needed; — means it works nowhere yet. In the Upstream column, — means there is nothing to report.
• Upstream: what mainline or linux-firmware already has, and what gbook would have to send.
  • “mica DTS not sent” covers both the board DTS and the google,mica binding (dts/README.md, “Before sending upstream”).
  • The patch words follow ChromiumOS, with LOCAL in place of its CHROMIUM: FROMLIST means posted to a list but not merged, and LOCAL means carried here and not sent.
  • Nothing is sent before M5.
• Evidence: the dated recon note, plus the attempt id where the note gives one. “none” means no note covers the feature.
• Note: kept short. inference marks a judgement call, such as the choice of state.

Boot and consoles

SoC: power, clocks, SCMI/cpufreq, idle, suspend

Storage and buses: USB, Type-C, PCIe, NVMe

Network: Wi-Fi, Bluetooth

Display and GPU

Input and EC

Security

Remoteprocs

Multimedia

Power

Userspace

Milestone M2: where it stands

M2 is done (2026-11-04, 12:38 PM ET): all four criteria are met. Criterion 1 is met by the unbound= proxy, and the s2idle row’s boots ran on test images.

M2 is “board on the console” in ADR 0010, from the milestones note, section 4. The ADR’s bar has four criteria:

1. every enabled DT node binds;
2. the M2 rows read works: USB host, Type-C, PCIe enumeration, Wi-Fi, eDP + backlight, GPU probe, EC keyboard, touchpad, TPM, SCMI cpufreq and the s2idle round trip;
3. every other row reads works or partial, or is parked with a note;
4. one base image (no debug command-line or DT extras) has 3 clean cold boots by scripts/attempt.sh tally.

Under criterion 3, rootfs, Mesa and the audio state are also M3 criteria in the ladder (section 4).

Counts (checked by scripts/status_check.py): 55 rows: 36 works, 5 partial, 3 broken, 11 untested; 14 parked. The line above is the one scripts/check.sh compares with the tables (retro-8/06), so it changes with them.

Criterion 4, read-only from dumps/firstboot/attempts.tsv (gitignored), at 11:24 AM ET:

$ scripts/attempt.sh tally '^2026-11-04-12$'
group 1 /^2026-11-04-12$/: attempts=1 health=1 boots=3 known=3 stalled=0 clean=3 unknown=0 max=0.1-0.1ms
  2026-11-04-12 0/3

• The base image: packaged with no command-line or DT extras; attempt.sh verify recorded “base image: no command-line or DT extras” and image sha256 2f08fb87463eeac6. All three boots started cold (EC G3->S5).
• What “clean” means: in tally, “clean” is an SCMI verdict: no timeout, and every reply under 100 ms (scripts/boot_health.py). It does not judge the whole boot.
• Before 2026-11-04-12 the only row with 0008 + 0009 was 2026-11-04-11, a test image (gbook.suspend=1).
• Next: M3, userspace from USB (a rootfs with Mesa, ADR 0010).