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, deren.wu@mediatek.com,
mingyen.hsieh@mediatek.com, sean.wang@mediatek.com
Subject: Re: [PATCH 1/2] Bluetooth: btmtk: Add MT6639 (MT7927) Bluetooth support
Date: Thu, 05 Mar 2026 11:18:13 -0600 [thread overview]
Message-ID: <20260305172817.3B8F51EA006B@mailuser.phl.internal> (raw)
In-Reply-To: CABBYNZJj0i2aNQdH2DXEnn+JBwNn+xkJU901vLFnnAzdtxtFDQ@mail.gmail.com
Hi Luiz,
On Thu, Mar 5, 2026 Luiz Augusto von Dentz wrote:
> Ditto, we will probably some evidence this was actually tested on
> systems e.g. dmesg of the pre/post change, also in this case
> specifically we need a mediatek engineer to confim, with a
> Signed-off-by, that these changes works as intended.
Here is the dmesg evidence from my system (ASUS ROG Crosshair X870E
Hero, 0489:e13a, kernel 6.19.6).
Pre-patch (vanilla 6.19.6 btusb/btmtk, no MT6639 support):
Bluetooth: hci0: Unsupported hardware variant (00006639)
Bluetooth: hci0: Device setup failed (-22)
Post-patch (this series applied):
Bluetooth: hci0: HW/SW Version: 0x00000000, Build Time: 20250606201235
Bluetooth: hci0: Device setup in 8287370 usecs
Bluetooth: hci0: AOSP extensions version v1.00
bluetoothctl shows the controller is fully operational:
Controller 78:46:5C:9B:C2:C2 (public)
Manufacturer: 0x0046 (70)
Name: jetm-rog-crosshair-hero-x870e
Powered: yes
This has been tested on 6 different boards across multiple distros.
The DKMS package [1] has been the primary driver for all MT7927
Bluetooth users since January.
Deren, Mingyen, Sean - could you please review the btmtk changes in
this patch and provide a Signed-off-by or Reviewed-by if the
implementation looks correct? Luiz requires a MediaTek engineer to
confirm these changes work as intended before merging.
For context: the BT firmware (BT_RAM_CODE_MT6639_2_1_hdr.bin) was
extracted from MediaTek's mtkwlan.dat combo blob shipped in the ASUS
Windows driver package (V5603998). The extraction uses a Python script
that parses the container format and pulls out the BT firmware
section. The firmware has been submitted to linux-firmware as GitLab
MR !946 [2].
The driver changes (firmware naming, section filtering, persistence
skip, CONNV3 reset) were developed by studying the Windows driver USB
captures and the existing btmtk code paths for MT7925/MT7961.
[1] https://github.com/jetm/mediatek-mt7927-dkms
[2] https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/946
Javier
next reply other threads:[~2026-03-05 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 17:18 Javier Tia [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-26 0:22 [PATCH 1/2] Bluetooth: btmtk: Add MT6639 (MT7927) Bluetooth support Javier Tia
2026-03-26 4:48 ` Sean Wang
2026-03-19 23:18 Javier Tia
2026-03-05 16:04 [PATCH 0/2] Bluetooth: Add MediaTek MT7927 (MT6639) support Javier Tia
2026-03-05 16:05 ` [PATCH 1/2] Bluetooth: btmtk: Add MT6639 (MT7927) Bluetooth support Javier Tia
2026-03-05 17:07 ` Luiz Augusto von Dentz
2026-03-07 16:03 ` Sean Wang
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=20260305172817.3B8F51EA006B@mailuser.phl.internal \
--to=floss@jetm.me \
--cc=deren.wu@mediatek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=mingyen.hsieh@mediatek.com \
--cc=sean.wang@mediatek.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