From: David Runge <dvzrv@archlinux.org>
To: linux-mediatek@lists.infradead.org
Subject: Addition of BT_RAM_CODE_MT6639_2_1_hdr.bin to linux-firmware
Date: Tue, 25 Aug 2026 09:20:33 +0200 [thread overview]
Message-ID: <ao1CQXyKli3LzxIZ@hmbx> (raw)
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
Hi all,
sorry for sending this into a larger round.
I don't know whether anyone of you is responsible for specific segments of
mediatek firmware, but you have all contributed firmware to the linux-firmware
project over the last year.
Would it be possible to add the BT_RAM_CODE_MT6639_2_1_hdr.bin firmware blob
to linux-firmware?
A third-party had already attempted to add it [1], but was missing the
permission to do so.
Please note, that without this firmware blob, on machines with relevant
hardware, the firmware loading fails on first boot and on successive boots
stalls the process for around 60s due to USB failures (which is fairly confusing
and of course annoying).
Thus, it would be really fantastic, if you could either add this firmware blob
yourself to the linux-firmware repository, or alternatively point me at a public
resource I can link to, that allows me to do this myself.
Greetings from Berlin,
David
[1] https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/946
P.S.: This mail has been sent to all contributors of the linux-firmware project
with a mediatek.com mail address, that have been active within this year on
2026-08-11.
I am not a subscriber to this mailing list (seem to be unable to sign up, as
the list host redirects to https://lists.openwrt.org/mailman/listinfo), but have
been asked to write here by Mario Limonciello, who maintains the linux-firmware
project.
--
https://archlinux.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2026-08-25 7:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ao1CQXyKli3LzxIZ@hmbx \
--to=dvzrv@archlinux.org \
--cc=linux-mediatek@lists.infradead.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