From: patchwork-bot+bluetooth@kernel.org
To: Ivan Hu <ivan.hu@canonical.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
peter.tsao@mediatek.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware
Date: Fri, 04 Sep 2026 16:56:13 +0000 [thread overview]
Message-ID: <178854097314.344939.15082478069695241185.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904053007.667472-1-ivan.hu@canonical.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 4 Sep 2026 13:30:07 +0800 you wrote:
> btmtk_fw_get_filename() constructs the firmware name at runtime, so for
> the MT7920 variant (dev_id 0x7961 with fw_flavor set) it requests
> "mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin" without ever declaring it via
> MODULE_FIRMWARE(). Tools that select firmware from module metadata (e.g.
> "modinfo -F firmware") therefore omit this blob, so request_firmware()
> fails and Bluetooth does not initialise on MT7920, even though the file
> is present in linux-firmware.
>
> [...]
Here is the summary with links:
- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware
https://git.kernel.org/bluetooth/bluetooth-next/c/860043e48274
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-04 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 5:30 [PATCH] Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware Ivan Hu
2026-09-04 16:56 ` patchwork-bot+bluetooth [this message]
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=178854097314.344939.15082478069695241185.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ivan.hu@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=peter.tsao@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