Comment 122 for bug 1065400

I found this page from the archlinux forums in this topic:

https://bbs.archlinux.org/viewtopic.php?id=133093&p=1

I wrote up the steps I took to get my card partially working in this post:

https://bbs.archlinux.org/viewtopic.php?pid=1430884#p1430884

I say partially because I've only been able to stream music to some bluetooth speakers so far. My phone pairs, but I'm unable to do anything with it.

I'm having a weird problem though. Using the tool posted in the archlinux topic I'm able to inject the firmware that I found in the windows driver, but things aren't working very well as I mentioned above, and I just noticed that I've done the same thing as the user in post #101, namely:

usb-devices
-----------------------------
T: Bus=03 Lev=01 Prnt=01 Port=03 Cnt=03 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0b05 ProdID=17cf Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=54271E328D4F
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
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)
-----------------------------

So you can see that my chipset is BCM20702A0, but the only hex file that's mentioned in the windows driver relating to my prodID of 17cf is:

BCM20702A1_001.002.014.1443.1469.hex

As you can see, BCM20702A1 != BCM20702A0, so I'm wondering if anyone can provide some advice.