From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221096] New: [PATCH AVAILABLE]Please add MediaTek MT7927 (MT6639) Bluetooth support to mainline
Date: Mon, 16 Feb 2026 16:10:52 +0000 [thread overview]
Message-ID: <bug-221096-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221096
Bug ID: 221096
Summary: [PATCH AVAILABLE]Please add MediaTek MT7927 (MT6639)
Bluetooth support to mainline
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: nvaert1986@hotmail.com
Regression: No
Created attachment 309389
--> https://bugzilla.kernel.org/attachment.cgi?id=309389&action=edit
The specified patch
Dear sir/miss,
As of very recent, there's a patch that adds Bluetooth support for the MediaTek
MT7927 (which uses the MT6639) Bluetooth, requiring minimal kernel changes.
Please see:
https://github.com/clemenscodes/linux-mediatek-mt6639-bluetooth-kernel-module/blob/main/patches/mt6639-bt-6.19.patch.
I've tested it on my machine and several others with several devices and I can
confirm this is working with several Bluetooth devices.
Also see: https://github.com/openwrt/mt76/issues/927 for details.
The only obstacle would be the firmware that's not available in linux-firmware,
but can be obtained from official vendors and then extracted using a python
script (see the OpenWRT github for details).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2026-02-16 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 16:10 bugzilla-daemon [this message]
2026-02-17 13:34 ` [Bug 221096] [PATCH AVAILABLE]Please add MediaTek MT7927 (MT6639) Bluetooth support to mainline bugzilla-daemon
2026-02-17 13:56 ` bugzilla-daemon
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=bug-221096-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.