RuView v0.9.1-mediatek-beta.1
This simulator-first beta adds a Rust MediaTek Filogic MIMO CSI transport and
RuView ingestion path while preserving the boundary between demonstrated host
integration and unavailable physical CSI export.
Included
- ADR-266 selects OpenWrt One (MT7981/MT7976) as the primary future hardware
target and BPI-R3 (MT7986/MT7975) as the secondary 4x4 target. - ADR-267 defines the bounded, versioned, CRC-protected
MTC1wire protocol. mediatek-csi-simprovides deterministic MT7981, MT7986, and MT7996 profiles,
complex MIMO CSI, per-chain RSSI, UDP streaming, and replay output.- RuView validates MediaTek datagrams, publishes bounded WebSocket summaries,
and exposes/api/v1/csi/mediatek/latest. mediatek:simulatedprovenance is retained end to end.
Validation
- Codec round trips, deterministic output, corruption/truncation rejection,
dimension limits, finite-value enforcement, and prefix parsing are tested. - All hardware and sensing-server regression tests pass.
- All three profiles were streamed over loopback UDP and verified through the
RuView REST API.
Hardware boundary
Upstream mt76 and public MediaTek SDK material do not currently expose a
supported raw complex CSI API. This release does not redistribute private SDK
material, invent a firmware ABI, or claim physical MediaTek capture. Hardware
support requires a documented firmware/driver channel-estimate export followed
by calibration and repeatability validation.
Collaboration and project update
- Upstream mt76 announcement/RFC: openwrt/mt76#1106
- Realtek + MediaTek update gist for 2026-07-18 (Toronto): https://gist.github.com/ruvnet/5ca5a27f2e607dcfcf0e3655fdec2d62
This remains simulator-validated beta support. Physical capture validation will follow when hardware and vendor SDK access arrive.