← Back to team overview

kernel-packages team mailing list archive

[Bug 1065400] Re: Support for loading Broadcom bluetooth firmware


Now getting this error

$ uname -r

$ lsusb | grep -i bluetooth
Bus 001 Device 006: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0

$ dmesg | grep Bluetooth
[    7.584434] Bluetooth: Core ver 2.16
[    7.584464] Bluetooth: HCI device and connection manager initialized
[    7.584472] Bluetooth: HCI socket layer initialized
[    7.584473] Bluetooth: L2CAP socket layer initialized
[    7.584477] Bluetooth: SCO socket layer initialized
[    7.917151] Bluetooth: can't load firmware, may not work correctly
[   14.786237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   14.786241] Bluetooth: BNEP filters: protocol multicast
[   14.786249] Bluetooth: BNEP socket layer initialized
[   14.796522] Bluetooth: RFCOMM TTY layer initialized
[   14.796532] Bluetooth: RFCOMM socket layer initialized
[   14.796534] Bluetooth: RFCOMM ver 1.11
[   53.162408] Bluetooth: Wrong link type (-14)
[   53.321353] Bluetooth: Wrong link type (-14)
[   53.322600] Bluetooth: Wrong link type (-2)
[   63.331513] Bluetooth: Wrong link type (-2)

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  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: