From: Javier Tia <floss@jetm.me>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Javier Tia <floss@jetm.me>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)
Date: Thu, 05 Mar 2026 11:18:12 -0600 [thread overview]
Message-ID: <20260305172813.12F6E1EA006C@mailuser.phl.internal> (raw)
In-Reply-To: CABBYNZL6MOoCE7Ft6tQLLJtUqs_uw5o-D5OSHTWC=Q_PE5kjdg@mail.gmail.com
Hi Luiz,
On Thu, Mar 5, 2026 Luiz Augusto von Dentz wrote:
> Is the lsusb information for these devices present in the links? We
> normally require that to confirm these ID's are real/valid.
Yes. Here is lsusb -v from my ASUS ROG Crosshair X870E Hero
(0489:e13a):
Bus 001 Device 005: ID 0489:e13a Foxconn / Hon Hai Wireless_Device
Device Descriptor:
idVendor 0x0489 Foxconn / Hon Hai
idProduct 0xe13a Wireless_Device
iManufacturer 5 MediaTek Inc.
iProduct 6 Wireless_Device
Interface Association:
bFunctionClass 224 Wireless
bFunctionSubClass 1 Radio Frequency
bFunctionProtocol 1 Bluetooth
The other four USB IDs have been confirmed by users on their hardware
with lsusb output in the tracking issue and bugzilla:
0489:e0fa - Lenovo Legion Pro 7 (kerberos272)
0489:e10f - Gigabyte Z790 AORUS MASTER X (Thex-Thex)
0489:e116 - TP-Link Archer TBE550E (marcin-fm)
13d3:3588 - ASUS ProArt X870E-Creator (samutoljamo)
Each is documented in the GitHub tracking issue [1] and the upstream
bugzilla [2] with lsusb and dmesg output.
> Ok, this is especially valid if AI assisted, otherwise we would
> probably need to ensure the agent has access to every board to list
> its IDs, etc.
>
> Regarding the use of AI, there doesn't seem to be a global policy.
> However, for Bluetooth Im not inclined to accept any patches that
> hasn't been properly reviewed by the author
Understood. To be clear: I wrote and reviewed these patches myself.
Claude Code was used as a coding assistant (editor-level help, similar
to copilot), not as an autonomous agent. The Assisted-by trailer
follows the kernel coding-assistants policy from Documentation/
process/coding-assistants.rst.
I tested the patches on my own hardware (ASUS ROG Crosshair X870E
Hero, BT 0489:e13a, Arch Linux kernel 6.19.6). The USB IDs come from
real hardware reports by real users, not generated by AI. The patches
have been running as a DKMS out-of-tree module [1] since January 2026
across Arch, Ubuntu, Fedora, NixOS, and openSUSE.
Your feedback is being read and responded to by me personally.
[1] https://github.com/jetm/mediatek-mt7927-dkms
[2] https://bugzilla.kernel.org/show_bug.cgi?id=221096
Javier
next reply other threads:[~2026-03-05 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 17:18 Javier Tia [this message]
2026-03-05 22:39 ` [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639) Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2026-03-26 0:18 Javier Tia
2026-03-05 22:56 Javier Tia
2026-03-05 16:04 [PATCH 0/2] Bluetooth: Add MediaTek MT7927 (MT6639) support Javier Tia
2026-03-05 16:05 ` [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639) Javier Tia
2026-03-05 17:00 ` Luiz Augusto von Dentz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260305172813.12F6E1EA006C@mailuser.phl.internal \
--to=floss@jetm.me \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox