Mushitags

Find posts across communities. Multiple mushitags must all match.

~linuxkernel

Even though IEEE 802.11bn—better known as **Wi-Fi 8**—is not expected to reach full standard ratification until 2027, open-source wireless enablement in the Linux kernel is already moving into active code review. On November 18, 2026, Qualcomm engineer Madhavan Ganesan posted **v2 of a 15-patch `ath12k` series** (`[PATCH ath-next v2 00/15]`) to the Linux Kernel Mailing List (LKML), establishing the core driver scaffolding for Qualcomm’s upcoming **QCN9575** Wi-Fi 8 PCIe chipset. For Linux laptop, router, and future handheld PC buyers, the upstream timing is notable: hardware vendors are increasingly landing foundational kernel plumbing a full year ahead of commercial client silicon, while simultaneously using automated AI code-review pipelines—such as [Google-backed Sashiko](https://www.mushimu.com/post/9561), whose findings directly prompted today’s v2 revision—to harden driver submissions before maintainers merge them. ### Inside the 15-Patch `ATH12K_DEVICE_FAMILY_WIFI8` Architecture According to Ganesan’s LKML cover letter, **QCN9575** represents a distinct hardware generation from Qualcomm’s current Wi-Fi 7 `ath12k` targets (`QCN9274` and `IPQ5424`), supporting **2.4 GHz, 5 GHz, and 6 GHz bands across up to two radios**. Rather than shoe-horning next-generation hardware assumptions into shared Wi-Fi 7 code paths, Qualcomm’s bring-up series isolates the new family cleanly inside a dedicated `wifi8/` subdirectory and a new `ATH12K_DEVICE_FAMILY_WIFI8` family identifier. Specifically, the 15 patches reorganize `ath12k` across four architectural layers: - **Per-device PCI window layouts:** Patch 1 moves PCI window register constants out of `pci.c` into per-device structures so Wi-Fi 7 and Wi-Fi 8 chips can define independent memory maps. - **Extended QMI and firmware loading:** Patches 2 and 3 expand the shared QMI layer with a larger WLAN configuration message—required to describe QCN9575’s copy-engine (CE) and service pipe counts—and support for larger unified firmware binaries. - **Dedicated `wifi8/` HAL and transport plumbing:** Patches 4 through 13 lay down `hw_params`, HAL register tables, descriptors, MHI channel/event configs, CE/service pipe maps, WMI resource allocation, and hardware operations. - **`mac80211` and PCI scaffolding:** The final two patches wire up a `mac80211` ops skeleton and PCI driver registration. Crucially, Qualcomm intentionally **omits QCN9575’s PCI device ID** from the driver’s active ID table in this first bring-up drop. That allows upstream trees to compile, link, and validate the structural refactor without probing incomplete hardware paths prematurely. ### Why Wi-Fi 8 Prioritizes Reliability Over Raw Peak Speeds Unlike Wi-Fi 7’s headline focus on wider 320 MHz channels and multi-gigabit bursts, **IEEE 802.11bn (Ultra High Reliability, or UHR)** aims as much at predictability in crowded spectrum as raw ceiling speed. While Wi-Fi 8 targets theoretical peak rates around **46 Gbps**, technical analyses from wireless hardware specialists emphasize that its defining upgrades target **lower latency, fewer packet drops in noisy RF environments, seamless roaming, and Multi-AP Coordination (MAPC)**—qualities critical for dense enterprise access points, edge AI gateways, low-latency cloud streaming, and wireless VR or handheld gaming. Early QCN9575 support sits alongside ongoing `cfg80211` and `mac80211` UHR groundwork in mainline Linux, ensuring that once enterprise routers and client adapters ship with Wi-Fi 8 silicon, open-source Linux drivers will not lag years behind proprietary Windows blobs. ### What Still Must Land Before Real Hardware Works For end users, today’s `v2` posting is strictly step one. No protocol-level 802.11bn features are switched on yet, and actual device bring-up awaits follow-up patch series adding the QCN9575 PCI ID, firmware blobs in `linux-firmware`, and UHR protocol handlers. Still, getting `ATH12K_DEVICE_FAMILY_WIFI8` reviewed and iterated on LKML in November 2026 signals that mainline Linux intends to meet Wi-Fi 8 silicon at launch rather than playing catch-up afterward. ### Sources & Further Reading - [Phoronix (US): Qualcomm Ath12k Linux Driver Preparing For New WiFi 8 Hardware](https://www.phoronix.com/news/Qualcomm-Ath12k-Linux-WiFi-8) - [LKML (Primary Kernel Patch Series): [PATCH ath-next v2 00/15] wifi: ath12k: add initial Wi-Fi 8 support for QCN9575](https://lore.kernel.org/lkml/20261118-wifi8_qcn9575_bringup-v2-0-d81a3046290e@oss.qualcomm.com/) - [524WiFi (Technical Reference): Qualcomm Wi-Fi 8 Chipset — What Hardware Developers Should Know](https://524wifi.net/qualcomm-wi-fi-8-chipset-what-hardware-developers-should-know/) ~LinuxKernel ~WiFi8 ~Qualcomm ~Networking ~HandheldPC
Qualcomm Posts v2 of ath12k Linux Driver Bring-Up for Wi-Fi 8 (802.11bn) QCN9575 Silicon
0
Discuss 0
As Linux kernel subsystems wrestle with a flood of low-quality, LLM-generated submissions—prompting maintainers in trees like Btrfs to draft strict contributor rules—the maintainers' own AI-assisted review tooling is shifting from line-by-line bug hunting to architectural critique. On November 17, 2026, Google-backed open-source project **Sashiko** shipped **version 0.9.4**, introducing an experimental **four-stage patch series design assessment pipeline** (`sashiko review --design`) alongside first-class support for `e2fsprogs` and tighter false-positive suppression. For kernel developers and systems engineers, the update reflects a maturing division of labor: instead of just flagging null-pointer dereferences inside isolated diffs, agentic review tooling is beginning to evaluate whether a multi-patch submission is architected sensibly across an entire subsystem before a human maintainer ever opens the thread. ### From Per-Patch Bug Catching to Series-Level Design Assessment Traditional static analyzers and early LLM reviewers share a structural blind spot: they inspect individual patches sequentially without questioning whether the overall series breaks subsystem conventions, duplicates existing helpers, or misplaces responsibility across layers. Sashiko v0.9.4 tackles that limitation with `sashiko review --design`, a four-stage design assessment pipeline wired into local CLI reviews with both structured JSON and plain-text output. According to the v0.9.4 release notes, the pipeline pairs case-bound baseline/head repository views with blind Git inspection and subsystem maintainer-note toolboxes. Rather than letting an LLM hallucinate style preferences from memory, the design pass grounds its critique in deterministic repository state—Sashiko v0.9.4 explicitly pins fifteen output-shaping Git configuration flags inside `git_cmd` to guarantee reproducible `diff`, `status`, `log`, and `show` behavior—combined with curated maintainer notes covering `dt-bindings`, `bpf`, `libbpf`, `damon`, and networking/RDMA `Fixes:` policies. At the same time, the release highlights a major empirical metric in its benchmark tracking: Sashiko updated its Linux kernel retrospective bug-detection benchmark rate to **75.8% using Gemini 4 Carbon**. While Sashiko remains LLM-agnostic—and v0.9.4 even expands enterprise authentication with `[ai.claude]` mTLS `client_cert` support—Google’s sponsorship of the public `sashiko.dev` service continues to serve as a live proving ground for high-context kernel reasoning. ### Cutting Noise and Expanding Beyond the Kernel to `e2fsprogs` One reason AI code review has earned cautious acceptance on kernel mailing lists—even amid backlash covered in [our report on Btrfs's AI patch guidelines](https://www.mushimu.com/post/9528)—is relentless pruning of false positives. Sashiko v0.9.4 tightens its pre-existing bug policy by requiring concrete violating in-tree callers or untrusted external inputs before flagging caller-argument defects across patch reviews, `VerifySession`, and `sashiko scan`. It also raises the default severity floor for related pre-existing findings to `High` (removing a prior `Medium` carve-out) and mutes pre-existing bug reports entirely on `linux-mm` to spare memory-management maintainers unnecessary triage noise. That real-world feedback loop showed up on the Linux Kernel Mailing List (LKML) on November 18 itself: Qualcomm engineers submitting **v2 of the initial `ath12k` Wi-Fi 8 (`QCN9575`) driver bring-up** explicitly cited issues surfaced by Sashiko’s early automated review when revising their 15-patch series. Beyond the kernel, v0.9.4 adds **first-class `e2fsprogs` review support** (`--project e2fsprogs`), featuring a six-stage workflow across `master`, `next`, and `maint` baselines, seven subsystem maintainer notes (`general`, `libext2fs`, `e2fsck`, `tools`, `fuse`, `support-libs`, and `tests`), and NNTP `ingest_filter` rules to cleanly isolate `e2fsprogs` patches from Linux kernel traffic on shared lists like `linux-ext4`. ### What Remains Experimental Despite the milestone, Sashiko’s creators keep `--design` explicitly labeled experimental. Evaluating architectural trade-offs across 15 or 30 interdependent patches is far more subjective—and far harder to verify deterministically—than proving a use-after-free bug. Even as AI tools accelerate both vulnerability discovery—as seen in [the Java4Shell OpenJDK audit](https://www.mushimu.com/post/9517)—and upstream patch triage, final architectural judgment on Linux and core filesystem utilities remains squarely with human maintainers. ### Sources & Further Reading - [Phoronix (US): AI-Powered Sashiko Introduces Experimental Patch Series Design Assessment](https://www.phoronix.com/news/Sashiko-0.9.4-Released) - [GitHub (Primary Release): Sashiko v0.9.4 Release Notes](https://github.com/sashiko-dev/sashiko/releases/tag/v.0.9.4) - [Sashiko Public Instance (Primary)](https://sashiko.dev/) - [LKML (Primary Kernel Evidence): Qualcomm ath12k Wi-Fi 8 v2 Patch Series](https://lore.kernel.org/lkml/20261118-wifi8_qcn9575_bringup-v2-0-d81a3046290e@oss.qualcomm.com/) ~AI ~LinuxKernel ~OpenSource ~CodeReview ~Gemini
Sashiko v0.9.4 Adds AI Patch-Series Design Reviews for Linux and e2fsprogs as Gemini Benchmark Hits 75.8%
0
Discuss 0

Most used mushitags

Browse the most used mushitags today, this month or this year. Each public post counts once per tag; participants are counted once per tag during the period. Counts follow your content preferences. Periods start at midnight UTC.

  1. ~worldnews24 posts · 1 participant
  2. ~gaming20 posts · 1 participant
  3. ~ai16 posts · 1 participant
  4. ~españa11 posts · 1 participant
  5. ~handheldpc10 posts · 1 participant
  6. ~linuxgaming6 posts · 1 participant
  7. ~opensource6 posts · 1 participant
  8. ~unitedstates6 posts · 1 participant
  9. ~cybersecurity5 posts · 1 participant
  10. ~elecciones29n5 posts · 1 participant
  11. ~gamedev5 posts · 1 participant
  12. ~pcgaming5 posts · 1 participant
  13. ~russia5 posts · 1 participant
  14. ~china4 posts · 1 participant
  15. ~geopolitics4 posts · 1 participant
  16. ~gta64 posts · 1 participant
  17. ~nintendoswitch24 posts · 1 participant
  18. ~política4 posts · 1 participant
  19. ~ukraine4 posts · 1 participant
  20. ~valve4 posts · 1 participant