Linux bluetooth development
 help / color / mirror / Atom feed
From: Christoph Zwerschke <cito@online.de>
To: stable@vger.kernel.org
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	Sasha Levin <sashal@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Salvatore Bonaccorso <carnil@debian.org>,
	Erik Brangs <erik.brangs@gmx.de>,
	benh@debian.org, Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev,
	1149377@bugs.debian.org
Subject: [PATCH 6.12 2/2] Revert "Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU"
Date: Mon,  2 Nov 2026 16:32:43 +0100	[thread overview]
Message-ID: <20261102153243.373899-2-cito@online.de> (raw)
In-Reply-To: <20261102153243.373899-1-cito@online.de>

This reverts commit f05baf6e0680d8c10d2fbbc5953848fc3e3db957 which is
commit 980084de4d9b25193398d89a1c0430ba3501b683 upstream.

With the device ID in the table, the adapter is handed over to btrtl,
which in this tree, together with the backport of commit 4a23ce935f74
("Bluetooth: btrtl: Add the support for RTL8761CUV"), now requires
rtl_bt/rtl8761cu_fw.bin. That file is only shipped by linux-firmware
since 20251111. On systems with older firmware packages, such as
Debian trixie, the adapter no longer initializes. Without the ID entry
it binds via the generic Bluetooth class and works on its ROM firmware,
as it did before the backport.

Mainline keeps the ID entry, so this revert is for 6.12.y only, as agreed
in the regression thread.

Reported-by: Erik Brangs <erik.brangs@gmx.de>
Closes: https://bugs.debian.org/1149377
Link: https://lore.kernel.org/all/179104011040.2214689.5921682013387867802@eldamar.lan/
Signed-off-by: Christoph Zwerschke <cito@online.de>
---
 drivers/bluetooth/btusb.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index bb83dc0b031e..f8b5492c8021 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -817,10 +817,6 @@ static const struct usb_device_id quirks_table[] = {
 	{ USB_DEVICE(0x37ad, 0x0600), .driver_info = BTUSB_REALTEK |
 						     BTUSB_WIDEBAND_SPEECH },
 
-	/* Additional Realtek 8761CU Bluetooth devices */
-	{ USB_DEVICE(0x0b05, 0x1bef), .driver_info = BTUSB_REALTEK |
-						     BTUSB_WIDEBAND_SPEECH },
-
 	/* Additional Realtek 8821AE Bluetooth devices */
 	{ USB_DEVICE(0x0b05, 0x17dc), .driver_info = BTUSB_REALTEK },
 	{ USB_DEVICE(0x13d3, 0x3414), .driver_info = BTUSB_REALTEK },
-- 
2.56.0


  reply	other threads:[~2026-11-02 15:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 15:15 [regression 6.12.y] After backport of 980084de4d9b ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU") bluethooth not anymore working on 0b05:1bef ASUSTek Computer, Inc. Bluetooth Controller (requests firmware) Salvatore Bonaccorso
2026-10-04 16:29 ` Sasha Levin
2026-10-12 12:00   ` Thorsten Leemhuis
2026-10-12 17:28     ` Salvatore Bonaccorso
2026-10-13  9:03       ` Thorsten Leemhuis
2026-10-23 13:43         ` Thorsten Leemhuis
2026-10-24 14:32           ` Erik Brangs
2026-10-24 20:10           ` Sasha Levin
2026-10-25  6:16             ` Greg Kroah-Hartman
2026-10-25  6:27               ` Thorsten Leemhuis
2026-10-25  7:37                 ` Christoph Zwerschke
2026-10-25  8:07                   ` Thorsten Leemhuis
2026-10-25 23:29                     ` Sasha Levin
2026-10-29  6:02                       ` Salvatore Bonaccorso
2026-11-02 11:04                         ` Thorsten Leemhuis
2026-11-02 11:05                           ` Thorsten Leemhuis
2026-11-02 15:32                           ` [PATCH 6.18 1/2] Revert "Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU" Christoph Zwerschke
2026-11-02 15:32                             ` [PATCH 6.18 2/2] Revert "Bluetooth: btusb: Add ASUS USB-BT540 " Christoph Zwerschke
2026-11-02 15:32                           ` [PATCH 6.12 1/2] Revert "Bluetooth: btusb: Add ASUS USB-BT600 " Christoph Zwerschke
2026-11-02 15:32                             ` Christoph Zwerschke [this message]
2026-11-02 19:01                             ` [6.12,1/2] " bluez.test.bot

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=20261102153243.373899-2-cito@online.de \
    --to=cito@online.de \
    --cc=1149377@bugs.debian.org \
    --cc=benh@debian.org \
    --cc=carnil@debian.org \
    --cc=erik.brangs@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.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