From: Javier Tia <floss@jetm.me>
To: Sean Wang <sean.wang@kernel.org>
Cc: linux-bluetooth@vger.kernel.org,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Subject: Re: [PATCH 1/2] Bluetooth: btmtk: Add MT6639 (MT7927) Bluetooth support
Date: Wed, 25 Mar 2026 18:22:52 -0600 [thread overview]
Message-ID: <20260326002348.4F98B1EA006B@mailuser.phl.internal> (raw)
In-Reply-To: CAGp9Lzrysz8Tyh2KUMWVgHMsfUqojiJgPseG+CTULTqH=QQhaw@mail.gmail.com
Hi Sean,
On Fri, Mar 7, 2026 Sean Wang wrote:
> BT and WiFi use separate firmware.
> I'm not sure why those WiFi sections are included in the binary.
> Another concern is whether it is appropriate to upload the firmware
> used in Windows to the linux-firmware repository,
> The firmware files are probably intended for dedicated OEMs.
The section filtering remains in v2 since the binary from the ASUS
driver package does contain mixed BT+WiFi sections. The firmware
upload question is being tracked separately in linux-firmware
MR !946.
On that topic - would it be possible for MediaTek to provide a
proper BT firmware binary for linux-firmware, or to sign off on
the one extracted from the ASUS driver package? That would resolve
the firmware provenance concern. If a formal submission from
MediaTek is required, could you help coordinate that?
> This is common logic for the other mediatek chips. It only takes
> longer on the first power-on.
[...]
> If the firmware download is properly handled in
> btmtk_setup_firmware_79xx, we don't need the extra bit.
Understood. The BTMTK_FIRMWARE_LOADED flag and skip logic are
removed in v2. Firmware persistence is handled by the existing
framework as you suggested.
v2 is sent with these changes addressed.
Best,
Javier
next reply other threads:[~2026-03-26 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 0:22 Javier Tia [this message]
2026-03-26 4:48 ` [PATCH 1/2] Bluetooth: btmtk: Add MT6639 (MT7927) Bluetooth support Sean Wang
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 23:18 Javier Tia
[not found] <177272816248.352280.12453518046823439297@jetm.me>
[not found] ` <20260305162928.5E8F11EA006C@mailuser.phl.internal>
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=20260326002348.4F98B1EA006B@mailuser.phl.internal \
--to=floss@jetm.me \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=sean.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox