MT7612 calibration regression in 24.10.2
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
Device: NETGEAR R6220
In OpenWrt 24.10, Configured Antennas of the 5G phy become TX 0x202 RX 0x202 instead of TX 0x3 RX 0x3.
From this issue we can know this is a calibration problem: calibration data are being read from an incorrect offset.
-----------------------------------------------------
OpenWrt 24.10.2, r28739-d9340319c6
-----------------------------------------------------
root@OpenWrt:~# iw phy1 info
Wiphy phy1
wiphy index: 1
max # scan SSIDs: 4
max scan IEs length: 2247 bytes
max # sched scan SSIDs: 0
max # match sets: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x202 RX 0x202
-----------------------------------------------------
OpenWrt 23.05.5, r24106-10cc5fcd00
-----------------------------------------------------
root@OpenWrt:~# iw phy1 info
Wiphy phy1
wiphy index: 1
max # scan SSIDs: 4
max scan IEs length: 2247 bytes
max # sched scan SSIDs: 0
max # match sets: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the calibration-offset discussion in mt76 issue 980 and comparing MT7612 behavior between OpenWrt 24.10.2 and 23.05.5. Reproduce the issue with iw phy1 info on the NETGEAR R6220; done means the 5G phy reports Configured Antennas as TX 0x3 RX 0x3 rather than TX 0x202 RX 0x202.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100