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
