Skip to content

WTLWireless 0.15.0: MT7927 in the chip table, switched off, testers wanted

Latest

Choose a tag to compare

@watchthelight watchthelight released this 12 Nov 13:18

The MT7927 (Filogic 380, also sold as AMD RZ738; PCI 14C3:7927, 14C3:6639, 14C3:0738) is in the chip table, switched off. I do not have the card, so its path has never run on hardware. On an MT7925 or RZ717 nothing changes, and there is no need to update from 0.14.0 unless you want to help test.

Download WTLWireless-0.15.0-RELEASE.zip. It has the kext, INSTALL.md, a config-snippet.plist, the licences and a Recovery folder with the mtkwifi tool. The three Kernel > Add entries are the same as in 0.14.0.

If you have an MT7927 or RZ738

  1. Install the kext as it is. The driver sees the card, publishes MtkChipMatched and MtkChipUnsupported on its WTLWireless node and does not touch the card: no register and no config-space access. Run bash tools/mtk-report.sh and attach the result to issue #2.
  2. To run it, add mtk7927=1 to boot-args. Keep a second way to boot first (a USB stick with your old config): an untested bring-up can hang the boot. Send the report again, pass or fail; MtkState holds the step it reached.

What the opt-in path does

  • Reset through CBTOP in place of the WFSYS reset register, RX rings 6, 4 and 7 with their interrupt bits, the MT7927 prefetch table, two more GLO_CFG bits, ASPM off, a band index in DEV_INFO and BSS_INFO, the DBDC command.
  • Firmware WIFI_MT6639_PATCH_MCU_2_1_hdr.bin and WIFI_RAM_CODE_MT6639_2_1.bin from linux-firmware, embedded beside the MT7925 pair (the kext grows by about 1.9 MB).
  • A board may report its CHIPID as 0x7927, 0x6639, 0x0738 or 0; anything else stops before the DMA setup.
  • Channel width up to 160 MHz. No 320 MHz, no MLO, and no Bluetooth for this chip yet (linux-firmware does not carry its Bluetooth firmware).
  • Written from Linux mt76 master at 79eb6679ef6a, which is BSD-3-Clause-Clear: see NOTICE.md and LICENSES/BSD-3-Clause-Clear-mt76.txt.

How it was checked

One boot on a Legion 5 15IAX10 (MT7925 14c3:7925, macOS 26.7.3 developer beta 25G416): Wi-Fi joined the saved WPA2 network at boot as with 0.14.0 (5 GHz, 80 MHz, MCS 9, 2 streams, 866 Mbit/s), MtkChipName is MT7925, none of the three new properties appear, Bluetooth is ready. On the host, tests/hwtrace/run.sh shows the MT7925 register trace is the same 3589 events as before the change, that a fake MT7927 without the boot-arg gets no hardware access, and that the opt-in run does what golden-mt7927.txt lists. That list is written by hand from the Linux code, so it checks my reading of Linux, not the hardware.

The binaries in the zip are the ones that booted, and ./build.sh at this tag gives the same three files.

sha256

63fdbb7cd8d269e0cc8394abdd3c01a42e7ca8f5ed3b86ab55e6fcf87c34431c  WTLWireless-0.15.0-RELEASE.zip
8c8eb1e46fa06283833df9c43a6026dde88845979b064108a9567187a0a2407f  WTLWireless.kext/Contents/MacOS/WTLWireless
1a8b2c0f3408b9f8806447efcb6d68bcac85be87585622401536cb59c1e45580  WTLWireless.kext/Contents/PlugIns/WTLWirelessNative.kext/Contents/MacOS/WTLWirelessNative
839bf76821dc6870cfa6abf3213680eb578cd223ae06e38c8e375ed60ddfdd86  WTLWireless.kext/Contents/PlugIns/WTLWirelessBt.kext/Contents/MacOS/WTLWirelessBt