I'm running 3.11.0-7 Saucy kernel on Raring and the firmware gets loaded, but it doesn't enable A2DP. Seems that the firmware loader is working, but I have the wrong firmware?
I have an Iogear GBU521 / 0a5c:21e8 like Elijah. I fetched the windows driver from http://www.iogear.com/support/dm/driver/GBU521 and used hex2hcd on firmware BCM20702A1_001.002.014.0889.0896.hex from the bcbtums-win8x64-brcm.inf from my vid:pid. /proc/version: Linux version 3.11.0-7-generic (root@core) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #14 SMP Mon Sep 16 22:03:29 PDT 2013 usb-devices: T: Bus=01 Lev=03 Prnt=43 Port=03 Cnt=03 Dev#= 46 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a5c ProdID=21e8 Rev=01.12 S: Manufacturer=Broadcom Corp S: Product=BCM20702A0 S: SerialNumber=0002723E9EC0 C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA 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) dmesg/kern.log: Sep 19 20:01:29 core kernel: [173325.476969] usb 1-1.5.4: new full-speed USB device number 46 using ehci-pci Sep 19 20:01:29 core kernel: [173325.572574] usb 1-1.5.4: New USB device found, idVendor=0a5c, idProduct=21e8 Sep 19 20:01:29 core kernel: [173325.572580] usb 1-1.5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 19 20:01:29 core kernel: [173325.572583] usb 1-1.5.4: Product: BCM20702A0 Sep 19 20:01:29 core kernel: [173325.572586] usb 1-1.5.4: Manufacturer: Broadcom Corp Sep 19 20:01:29 core kernel: [173325.572588] usb 1-1.5.4: SerialNumber: 0002723E9EC0 Sep 19 20:01:31 core kernel: [173326.944094] Bluetooth: firmware loaded Sep 19 20:01:40 core kernel: [173336.196410] br0: port 1(eth0) entered forwarding state Sep 19 20:01:50 core kernel: [173346.481465] r8169 0000:06:00.0 eth0: link down Sep 19 20:01:50 core kernel: [173346.481570] br0: port 1(eth0) entered disabled state Sep 19 20:01:52 core kernel: [173348.142401] r8169 0000:06:00.0 eth0: link up Sep 19 20:01:52 core kernel: [173348.142904] br0: port 1(eth0) entered forwarding state Sep 19 20:01:52 core kernel: [173348.142931] br0: port 1(eth0) entered forwarding state Sep 19 20:02:07 core kernel: [173363.171462] br0: port 1(eth0) entered forwarding state -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Fix Committed Status in “linux” source package in Saucy: Fix Released Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
