Are there any plans to add MT7987 WED hardware path support?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Read the linked pull request and inspect the MT7987 WED attach path in the mt76 driver. Start by tracing why the boot log reports “failed to attach wed device” when wed_enable is set. Determine what hardware support is needed and whether it can be added; done means WED attaches successfully on MT7987 and the driver behavior is verified on that hardware.
Written by the indexing model from the issue text.
Description
Currently, WED cannot be enabled on MT7987, as described in this pr:
https://github.com/Telecominfraproject/wlan-ap/pull/1339/changes
Tenda BE12 Pro MT7987 bootlog:
[ 10.307868] Backport generated by backports.git v5.15.58-1-198-g2580fa90cb79
[ 10.396313] mt7996e 0000:01:00.0: assign IRQ: got 72
[ 10.401300] mt7996e 0000:01:00.0: enabling device (0000 -> 0002)
[ 10.407336] mt7996e 0000:01:00.0: enabling bus mastering
[ 10.473547] mt7996e 0000:01:00.0: attaching wed device 0 version 3
[ 10.497033] platform 15010000.wed: failed to attach wed device
[ 10.544368] mtk-pcie-gen3 11280000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11280c00 data 1
[ 10.594046] mt7996e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20260720170351a
[ 10.594046]
[ 10.771540] mt7996e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20260720165749
[ 10.802438] mt7996e 0000:01:00.0: DSP Firmware Version: ____000000, Build Time: 20260720165616
[ 10.861390] mt7996e 0000:01:00.0: WA Firmware Version: ____000000, Build Time: 20260720165649
[ 11.081406] mt7996e 0000:01:00.0: registering led 'mt76-phy0'
/etc/modules.conf:
options mt7996e wed_enable=Y
- Dominant language
- C
- Stars
- 895
- Forks
- 461
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from openwrt/mt76
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
MT76xx - WLAN leds doesn't work with the testing kernelMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
mt7925: Netgear A8000 (0846:9072) reports hw_path without WF0_5G, so 5 GHz band is never registeredOpen
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
SPIDevice selects an active-high device as soon as it is createdPossibly taken @mikeysklar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
adafruit/circuitpython#11869 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gnif/LookingGlass#1352 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100