btusb: add MediaTek generic USB ID 0e8d:7902 to quirks_table - #21
Open
ronaldnetawat wants to merge 1 commit into
Open
btusb: add MediaTek generic USB ID 0e8d:7902 to quirks_table#21ronaldnetawat wants to merge 1 commit into
ronaldnetawat wants to merge 1 commit into
Conversation
MT7902 modules that use MediaTek's generic VID/PID (0e8d:7902), as found in the Minisforum UM870 Slim, bind without BTUSB_MEDIATEK because the stripped-down quirks_table only lists OEM IDs and mainline's generic 0e8d catch-all entry was removed. Without the flag the MediaTek setup path never runs, no firmware is downloaded and the controller stays mute (Opcode 0x0c03 failed: -110, BD address 00:00:00:00:00:00). Add the ID with BTUSB_MEDIATEK | BTUSB_WIDEBAND_SPEECH, matching the neighboring 0e8d:1ede entry. Tested on a Minisforum UM870 Slim, Ubuntu 22.04.5, kernel 6.8.0-134-generic: firmware downloads on probe and the controller works fully. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
MT7902 modules that use MediaTek's generic USB ID
0e8d:7902(instead of an OEM-specific13d3:xxxxID) bind tobtusb_mt7902without theBTUSB_MEDIATEKflag, becausequirks_tabledoesn't list that ID and this stripped-down driver no longer carries mainline's generic catch-all entry (USB_VENDOR_AND_INTERFACE_INFO(0x0e8d, 0xe0, 0x01, 0x01)).As a result
hdev->setupis never wired to the MediaTek setup path, no firmware is downloaded, and the controller stays completely mute:hciconfigshowsBD Address: 00:00:00:00:00:00, 0 RX bytes, and the adapter never comes up.This affects at least the Minisforum UM870 Slim (and likely other mini PCs that ship MediaTek-branded MT7902 modules rather than AzureWave/IMC ones):
Fix
Add
0e8d:7902toquirks_tablewithBTUSB_MEDIATEK | BTUSB_WIDEBAND_SPEECH, next to the existing0e8d:1edeentry.Tested
Minisforum UM870 Slim (Ryzen 7 8745H), Ubuntu 22.04.5, kernel 6.8.0-134-generic (HWE), built via DKMS. With this change the firmware downloads on probe and the controller works fully (pairing, HID, audio):
🤖 Generated with Claude Code