Missing support in btusb for broadcom dongle 0a5c:2009
Hello,
It seems this particular dongle needs a quirk that existed in hci_usb, but doesn't in btusb.
Is it possible to send some command to use this dongle (as hciconfig reset can replace the reset quirk) ?
Or should the quirk be introduced in btusb too ?
Regards,
Guillaume B.
Marcel Holtmann
maintainerHi Guillaume,
Quoted 7 lines
It seems this particular dongle needs a quirk that existed in
hci_usb, but doesn't in btusb.Is it possible to send some command to use this dongle (as hciconfig reset can replace the reset quirk) ?
Or should the quirk be introduced in btusb too ?
you can load btusb with reset=1 and that does the same trick, but the quirk should be added to btusb directly. Send in the lsusb output and content of /proc/bus/usb/devices for your dongle.
Regards
Marcel
PATCH 1/1 Missing support in btusb for broadcom dongle 0a5c:2009
Quoted 5 lines · Marcel Holtmann
Hi Guillaume,
Quoted 3 lines
It seems this particular dongle needs a quirk that existed in
hci_usb, but doesn't in btusb.
Quoted 8 lines
Quoted 4 lines
Is it possible to send some command to use this dongle (as hciconfig reset can replace the reset quirk) ?
Or should the quirk be introduced in btusb too ?
you can load btusb with reset=1 and that does the same trick, but the quirk should be added to btusb directly. Send in the lsusb output and content of
/proc/bus/usb/devicesfor your dongle.
Sorry I was not clear enough...
It's a different init quirk that concern only that dongle at the moment. With this patch it should be clearer.
Regards,
Guillaume B.
This patch should allow the 0a5c:2009 broadcom dongle to work with btusb.
See this Mandriva bug for more information:
http://qa.mandriva.com/show_bug.cgi?id=44886
(and soon, for results of Jan tests especially)
drivers/bluetooth/btusb.c +1 -0
@@ -96,6 +96,7 @@/* Broadcom BCM2035 */ { USB_DEVICE(0x0a5c, 0x2035), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU }, { USB_DEVICE(0x0a5c, 0x200a), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU }, + { USB_DEVICE(0x0a5c, 0x2009), .driver_info = BTUSB_BCM92035 }, /* Broadcom BCM2045 */ { USB_DEVICE(0x0a5c, 0x2039), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
Marcel Holtmann
maintainerHi Guillaume,
Quoted 8 lines
Quoted 8 lines
Quoted 7 lines
It seems this particular dongle needs a quirk that existed in
hci_usb, but doesn't in btusb.Is it possible to send some command to use this dongle (as hciconfig reset can replace the reset quirk) ?
Or should the quirk be introduced in btusb too ?
Quoted 8 lines
Quoted 3 lines
you can load btusb with reset=1 and that does the same trick, but the quirk should be added to btusb directly. Send in the lsusb output and content of
/proc/bus/usb/devicesfor your dongle.Sorry I was not clear enough...
It's a different init quirk that concern only that dongle at the moment. With this patch it should be clearer.
hah. We forgot to port this one over from hci_usb :(
Regards
Marcel