Bug 1264153 - Missing firmware bluetooth BCM20702A1
Missing firmware bluetooth BCM20702A1
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: linux-firmware (Show other bugs)
23
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: David Woodhouse
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-17 12:00 EDT by Andrea Oliveri
Modified: 2015-10-18 14:56 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-18 14:56:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrea Oliveri 2015-09-17 12:00:31 EDT
Description of problem:
Missing firmware for BCM20702A1 bluetooth chipset (Thinkpad T430 

It is possible to correct it using the firmware extracted by the windows driver package.
You can copy BCM20702A1_001_002.014.1443.1453.hex from \windows\system32\driver from your windows installation and you can use hex2hcd (https://github.com/jessesung/hex2hcd) to convert it and copy it on /lib/firmware/brcm/BCM20702A0-0a5c-21e6.hcd
Comment 1 Andrea Oliveri 2015-09-17 12:20:40 EDT
ERRATA: Sorry the correct file is /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd
Comment 2 Josh Boyer 2015-09-17 12:53:38 EDT
Does the b43-fwcutter tool work for this?

We cannot distribute firmware files that are not explicitly granted redistribution permissions.  More specifically, we very rarely carry files in the linux-firmware package that are not in the upstream linux-firmware repository.  Extracting it from a Windows driver and putting it into linux-firmware isn't something we are going to do, which is why the b43-fwcutter tool exists.
Comment 3 Andrea Oliveri 2015-09-17 13:02:22 EDT
I have never used b43-fwcutter, sorry :(
Ok you have explained very well, thankyou

Note You need to log in before you can comment on or make changes to this bug.