Dear Alan,
Thank you for your patch.
Am 22.11.24 um 06:20 schrieb Alan Jones:
The Nintendo Wii uses a BCM2045 module running proprietary firmware.
This adapter is typically managed by emulation software via the raw
interface, and is incompatible with standard Bluetooth devices.
Attempting to initialize this adapter breaks synchronization with all
previously connected Wii Remotes, requiring applications to
re-synchronize the remotes on each usage.
Fix Wii Remote re-synchronization issues with the official Nintendo Wii
Bluetooth module by ignoring this adapter.
Out of curiosity, is anything logged by Linux?
Signed-off-by: Alan Jones <j.alan.jones@xxxxx>
---
drivers/bluetooth/btusb.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index e9534fbc92e3..11c9ea182ea4 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -185,6 +185,9 @@ static const struct usb_device_id quirks_table[] = {
/* Broadcom BCM2045 devices */
{ USB_DEVICE(0x0a5c, 0x2045), .driver_info = BTUSB_BCM2045 },
+ /* Broadcom BCM2045 with Nintendo Wii firmware */
+ { USB_DEVICE(0x057E, 0x0305), .driver_info = BTUSB_IGNORE },
Could you please write the ids lowercase? Also, sort it above 0x0a5c?
The comment above the existing entry suggests it’s for all BCM2045
devices. Could you explain, where the difference in the vendor id comes
from?
+
/* Atheros 3011 with sflash firmware */
{ USB_DEVICE(0x0489, 0xe027), .driver_info = BTUSB_IGNORE },
{ USB_DEVICE(0x0489, 0xe03d), .driver_info = BTUSB_IGNORE },
Kind regards,
Paul
