Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pavel Zverev <playximik29@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: Add support for 1357:c123 Realtek 8852BE device
Date: Fri, 10 Jul 2026 20:10:11 +0000	[thread overview]
Message-ID: <178371421139.843459.11063854284998153443.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260707221549.27269-1-playximik29@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed,  8 Jul 2026 01:15:49 +0300 you wrote:
> Wiko Hi MateBook 14 Ryzen 200 laptops (DMI system-product-name
> "MNCA-XX", board "M1060") are equipped with an RTL8852BE Wi-Fi/BT
> combo chip (rtw89_8852be), whose Bluetooth radio enumerates as
> 1357:c123 instead of one of the already-supported 1358:c123 / 0bda:c123
> identifiers, presumably due to OEM rebranding. Without a matching
> entry it only matches the generic USB Bluetooth class fallback, so the
> Realtek firmware/config (rtl8852btu_fw.bin / rtl8852btu_config.bin) is
> never loaded and the adapter cannot discover or connect to any device,
> even though hciconfig reports it as powered and scanning.
> 
> [...]

Here is the summary with links:
  - Bluetooth: btusb: Add support for 1357:c123 Realtek 8852BE device
    https://git.kernel.org/bluetooth/bluetooth-next/c/1386e748cfc0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-10 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 22:15 [PATCH] Bluetooth: btusb: Add support for 1357:c123 Realtek 8852BE device Pavel Zverev
2026-07-07 22:44 ` bluez.test.bot
2026-07-10 20:10 ` 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=178371421139.843459.11063854284998153443.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=playximik29@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