From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?q?Nikolaj_Klitlund_B=C3=B8rty_=3Cnbn=40sj=2Edk=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btusb: Add device ID for Realtek RTL8761BUE (StarTech AV53C1)
Date: Tue, 08 Sep 2026 16:30:37 +0000 [thread overview]
Message-ID: <178888503713.3627954.5248734968096243658.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260905-startech-av53c1-v1-1-3385f9bb220c@sj.dk>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 05 Sep 2026 14:05:12 +0200 you wrote:
> From: Nikolaj Klitlund Børty <nbn@sj.dk>
>
> Add the USB ID 0x14b0:0x047a for the StarTech AV53C1-USB-BLUETOOTH
> adapter, a Realtek RTL8761BUE based Bluetooth 5.3 dongle.
>
> Without this entry btusb treats the device as a generic Bluetooth
> adapter and never loads the Realtek firmware, leaving the controller on
> its ROM firmware. In that state it advertises and scans actively, but
> never reports advertisements during passive scanning. LE connections
> initiated by the kernel wait for a passive-scan report before issuing
> LE Create Connection, so connecting and pairing from BlueZ time out
> without any error from the controller.
>
> [...]
Here is the summary with links:
- Bluetooth: btusb: Add device ID for Realtek RTL8761BUE (StarTech AV53C1)
https://git.kernel.org/bluetooth/bluetooth-next/c/76b8d73b706e
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-08 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 12:05 Nikolaj Klitlund Børty via B4 Relay
2026-09-08 16:30 ` 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=178888503713.3627954.5248734968096243658.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?q?Nikolaj_Klitlund_B=C3=B8rty_=3Cnbn=40sj=2Edk=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®