Hi Raphael,
> Yet another vendor specific ID for this chipset; this one for the ASUS
> USB-BT400 Bluetooth 4.0 adapter.
>
> T: Bus=03 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 6 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=0b05 ProdID=17cb Rev=01.12
> S: Manufacturer=Broadcom Corp
> S: Product=BCM20702A0
> S: SerialNumber=000272C64400
> C: #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
> I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=(none)
> I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
> Cc: stable@xxxxxxxxxxxxxxx
> Signed-off-by: Raphael Kubo da Costa <rakuco@xxxxxxxxxxx>
> ---
> drivers/bluetooth/btusb.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index d3313e6..c0a9df4 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -99,6 +99,7 @@ static struct usb_device_id btusb_table[] = {
>
> /* Broadcom BCM20702A0 */
> { USB_DEVICE(0x0b05, 0x17b5) },
> + { USB_DEVICE(0x0b05, 0x17cb) },
> { USB_DEVICE(0x04ca, 0x2003) },
> { USB_DEVICE(0x0489, 0xe042) },
> { USB_DEVICE(0x413c, 0x8197) },
I wonder if we should stop this crazy and just this one line
USB_VENDOR_AND_INTERFACE_INFO(0x0b05, 0xff, 0x01, 0x01)
for all Broadcom originated devices.
Same as we do for all Apple Bluetooth devices that are based on Broadcom chips. It seems that Broadcom decided to use ff:01:01 for their chips instead of the official e0:01:01.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
