From: Ping-Ke Shih <pkshih@realtek.com>
To: Maxim Skokov <skokovmaksimevg@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: rtw89: RTL8851B BTC entry requires unpublished firmware 0.29.133.0
Date: Sun, 6 Sep 2026 04:25:54 +0000 [thread overview]
Message-ID: <5976dee678a04857b862bc8745420fef@realtek.com> (raw)
In-Reply-To: <20260905131503.6160-1-skokovmaksimevg@gmail.com>
Maxim Skokov <skokovmaksimevg@gmail.com> wrote:
> To be clear, I am not reporting a malfunction. I have not observed any
> concrete problem that I can attribute to this, and the legacy profile may
> well be perfectly adequate. I simply cannot tell how the situation is
> meant to be read:
>
> - Is firmware 0.29.133 or newer expected to reach linux-firmware at
> some point, with the driver support having landed ahead of it?
This one.
When BTC expert does upgrade, he does review and implement the changes
across chips in one go, because the firmware is share to many chips.
Or, he will review the changes again and again.
Ping-Ke
next prev parent reply other threads:[~2026-09-06 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 13:14 rtw89: RTL8851B BTC entry requires unpublished firmware 0.29.133.0 Maxim Skokov
2026-09-06 4:25 ` Ping-Ke Shih [this message]
2026-09-06 11:58 ` Maxim Skokov
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=5976dee678a04857b862bc8745420fef@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=skokovmaksimevg@gmail.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