kernel-packages team mailing list archive

[Thilo Cestonaro <1065400@xxxxxxxxxxxxxxxxxx>]

Thx for the answer.
Sadly, there is no indication of a missing firmware :(.

----
[   29.980043] Bluetooth: Core ver 2.19
[   29.980058] Bluetooth: HCI device and connection manager initialized
[   29.980064] Bluetooth: HCI socket layer initialized
[   29.980066] Bluetooth: L2CAP socket layer initialized
[   29.980073] Bluetooth: SCO socket layer initialized
[   32.874973] Bluetooth: RFCOMM TTY layer initialized
[   32.874984] Bluetooth: RFCOMM socket layer initialized
[   32.874997] Bluetooth: RFCOMM ver 1.11
[   33.702638] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   33.702641] Bluetooth: BNEP filters: protocol multicast
[   33.702649] Bluetooth: BNEP socket layer initialized
[ 4216.638384] Bluetooth: hci0 urb ffff8800c5e09600 failed to resubmit (2)
----

And anyway, in my case it should be a BCM20802A0 .... 
can I place the working firmware at /lib/firmware/brcm/ and hope it will be picked? What naming do I need to take care of?
Currently the file is called, BCM20702A0_001.001.024.0156.0204.hex, which I do download by bcmfwup.py to make my bluetooth work.

Any hints?

-- 
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 Released
Status in “linux” source package in Raring:
  Fix Released
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