summaryrefslogtreecommitdiffstats
path: root/drivers/bluetooth/btusb.c
diff options
context:
space:
mode:
authorJohan Hedberg <johan.hedberg@intel.com>2013-07-24 02:32:46 +0300
committerGustavo Padovan <gustavo.padovan@collabora.co.uk>2013-07-29 12:12:27 +0100
commit3f8e2d75c14660abc8b69206f30190ab93304379 (patch)
tree9bc4f9e8f42ac77228044aac125c4aae18e234d3 /drivers/bluetooth/btusb.c
parent1d5b569ef85d013a775560a90050dc630614c045 (diff)
downloadop-kernel-dev-3f8e2d75c14660abc8b69206f30190ab93304379.zip
op-kernel-dev-3f8e2d75c14660abc8b69206f30190ab93304379.tar.gz
Bluetooth: Fix HCI init for BlueFRITZ! devices
None of the BlueFRITZ! devices with manufacurer ID 31 (AVM Berlin) support HCI_Read_Local_Supported_Commands. It is safe to use the manufacturer ID (instead of e.g. a USB ID specific quirk) because the company never created any newer controllers. < HCI Command: Read Local Supported Comm.. (0x04|0x0002) plen 0 [hci0] 0.210014 > HCI Event: Command Status (0x0f) plen 4 [hci0] 0.217361 Read Local Supported Commands (0x04|0x0002) ncmd 1 Status: Unknown HCI Command (0x01) Reported-by: Jörg Esser <jackfritt@boh.de> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Tested-by: Jörg Esser <jackfritt@boh.de> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Diffstat (limited to 'drivers/bluetooth/btusb.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud