Bug 60847 - [REGRESSION][BISECTED][PATCH] Cambridge Silicon Radio Bluetooth Dongle doesn't work
Summary: [REGRESSION][BISECTED][PATCH] Cambridge Silicon Radio Bluetooth Dongle doesn'...
Status: ASSIGNED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-04 12:49 UTC by lbv5051
Modified: 2014-11-07 03:34 UTC (History)
12 users (show)

See Also:
Kernel Version: 3.10.7
Tree: Mainline
Regression: Yes


Attachments
bisect log (2.71 KB, text/plain)
2013-09-04 12:49 UTC, lbv5051
Details
hcidump output (3.31 KB, text/plain)
2013-09-12 03:58 UTC, lbv5051
Details
Bluetooth path (3.10 KB, patch)
2013-10-21 16:44 UTC, Boris Vinogradov
Details | Diff

Description lbv5051 2013-09-04 12:49:27 UTC
Created attachment 107414 [details]
bisect log

# lsusb
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

# hciconfig -a
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 00:19:86:00:05:47  ACL MTU: 1017:8  SCO MTU: 64:0
	DOWN 
	RX bytes:457 acl:0 sco:0 events:16 errors:0
	TX bytes:68 acl:0 sco:0 commands:16 errors:0
	Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: 
	Link mode: SLAVE ACCEPT 

# hciconfig hci0 up
Can't init device hci0: Operation not supported (95)
Comment 1 Gustavo Padovan 2013-09-10 16:09:35 UTC
Could you provide the output of hcidump or btmon when you try to run:

$ hciconfig hci0 down
$ hciconfig hci0 up
Comment 2 lbv5051 2013-09-12 03:58:11 UTC
Created attachment 108161 [details]
hcidump output
Comment 3 Johan Hedberg 2013-09-12 09:47:48 UTC
There's a discrepancy with the manufacturer of your device in the various pieces of information that you have provided. On the USB level (from your initial report) it's saying CSR:

> # lsusb
> Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)

However, from your latest attachment on the HCI level it's saying Broadcom:

> < HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> > HCI Event: Command Complete (0x0e) plen 12
>     Read Local Version Information (0x04|0x0001) ncmd 1
>     status 0x00
>     HCI Version: 2.0 (0x3) HCI Revision: 0x3000
>     LMP Version: 2.0 (0x3) LMP Subversion: 0x420b
>     Manufacturer: Broadcom Corporation (15)

So it doesn't seem like the original report and your attachment are for the same hardware (or if they are then the hardware is probably neither CSR nor Broadcom and more likely some cheap Asian clone)
Comment 4 lbv5051 2013-09-12 10:32:45 UTC
(In reply to Johan Hedberg from comment #3)

This is the same device.

hciconfig and lsusb output (kernel 2.9.11):

$ lsusb | grep -i bluetooth
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

$ hciconfig hci0 version
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 00:19:86:00:05:47  ACL MTU: 1017:8  SCO MTU: 64:0
	HCI Version: 2.0 (0x3)  Revision: 0x3000
	LMP Version: 2.0 (0x3)  Subversion: 0x420b
	Manufacturer: Broadcom Corporation (15)
Comment 5 lbv5051 2013-09-12 11:06:05 UTC
(In reply to lbv5051 from comment #4)
> (kernel 2.9.11):
3.9.11 //fix
Comment 6 Younes Manton 2013-10-01 17:23:30 UTC
This is the same issue as 60824, there's a patch there that fixes it.
Comment 7 lbv5051 2013-10-02 11:35:07 UTC
I have tested patch from 60824 on 3.11.3 - works fine.
Comment 8 Boris Vinogradov 2013-10-21 16:44:33 UTC
Created attachment 111861 [details]
Bluetooth path
Comment 9 Boris Vinogradov 2013-10-21 16:45:08 UTC
I testing path on 3.11.5 and it working.
Comment 10 Boris Vinogradov 2013-10-23 03:04:59 UTC
This actuality to 3.11.x branch of kernel release (tested on 3.11.5 and 3.11.6 kernels)

Note You need to log in before you can comment on or make changes to this bug.