Hi All,I've been trying to get a USB bluetooth dongle going recently, based on the Broadcom BCM2035B chipset. It appeas from the surface that this chip is supported, however it seems this particular dongle is having difficulties working under Linux.
When the device is plugged in, `dmesg` reports: > [...]
[ 2560.963622] usb 5-1: new full speed USB device using ohci_hcd and address 3 [ 2561.133938] usb 5-1: configuration #1 chosen from 1 choice [ 2561.151391] usb 5-1: New USB device found, idVendor=0a5c, idProduct=2035 [ 2561.151403] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2561.151409] usb 5-1: Product: BCM2035B [ 2561.151414] usb 5-1: Manufacturer: Broadcom Corp
> [...] The USB device description is as follows:
wander ~ # cat /proc/bus/usb/devices [...] T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a5c ProdID=2035 Rev= 1.00 S: Manufacturer=Broadcom Corp S: Product=BCM2035B C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb [...]
The kernel loads the hci-usb driver, and a hci0 device appears in sysfs. However, the address is null:
wander ~ # cat /sys/bus/bluetooth/devices/hci0/address 00:00:00:00:00:00
BlueZ utils (3.28) see the USB HCI adaptor, and can scan devices:
wander ~ # hciconfig hci0: Type: USB BD Address: 00:00:00:00:00:00 ACL MTU: 377:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:982 acl:0 sco:0 events:28 errors:0 TX bytes:610 acl:0 sco:0 commands:28 errors:0
wander ~ # hcitool scan --flush Scanning ... 20:07:35:xx:xx:xx KF-700 00:1E:E1:xx:xx:xx SGH-A412
I have the BlueZ firmware package installed, however the bcm203x module seems to completely ignore the dongle, and no firmware is loaded. (I understand this module is used with the BCM2033. The name suggests it should also handle other 203x devices, such as the 2035. I assume I'm mistaken?)
I haven't been able to pair any devices with my laptop. I've also tried this dongle on an old PII laptop, and a Lemote Fulong minicomputer, with identical results. My laptop is running kernel 2.6.25-rc6, the older laptop is running -rc8, and the Lemote computer is running kernel 2.6.23.
Is there anything I should try? I'm not sure how to enable the debugging in the Bluetooth stack. It would appear that this device is very close to actually working. While I could go and buy another dongle (I don't really have the money), I'd much prefer to fix the driver so the device actually works.
-- Stuart Longland (aka Redhatter) .'''. Gentoo Linux/MIPS Cobalt and Docs Developer '.'` : . . . . . . . . . . . . . . . . . . . . . . .'.' http://dev.gentoo.org/~redhatter :.' I haven't lost my mind... ...it's backed up on a tape somewhere.
Attachment:
signature.asc
Description: OpenPGP digital signature
