Attempting on re-send via webportal: Thunderbird is chewing-up the reply-to header. If this fails to thread I'll walk-away for a bit.
Here's what happens when the module is plugged in and I press a button
on a previously paired remote.
[483044.866453] usb 3-4: new full-speed USB device number 47 using
xhci_hcd
[483045.477740] usb 3-4: New USB device found, idVendor=057e,
idProduct=0305, bcdDevice= 1.00
[483045.477749] usb 3-4: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[483045.477754] usb 3-4: Product: BCM2045A
[483045.477757] usb 3-4: Manufacturer: Broadcom Corp
[483047.572500] Bluetooth: hci0: Opcode 0x0c14 failed: -110
Beyond this is gets weird. The version of weird depends on the next steps.
The Nintendo stack is almost, but not quite, entirely unlike Bluetooth.
The unique vendor and product IDs are a result of the firmware payload.
In the manufacturing manual for the component there's a note regarding
this (after firmware install):
"USD Vender ID and product ID of nintendo module is not same as it
of Pre-write module."
Link:
https://fccid.io/MCLJ27H002/User-Manual/Users-Manual-721663.pdf
So in theory: yes, this would apply to all BCM2045 devices re-flashed
with Nintendo's firmware.
I don't know how feasible this actually is: to my knowledge it isn't
widely done.
In practice, hobbyists extract the Foxconn WML-C43 or Foxconn/Panasonic
J27H002 module from a Wii console and add the wiring to interface to a PC.
Example using a daughtercard adapter here:
https://www.abbiedoobie.com/product/bluetooth-passthrough-adapter/
Ack on requested changes; I'll send a follow-up
Alan
On Friday, November 22nd, 2024 at 12:29 AM, Paul Menzel <pmenzel@xxxxxxxxxxxxx> wrote:
>
>
> 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
