Bug 1264153

Summary:	Missing firmware bluetooth BCM20702A1
Product:	[Fedora] Fedora	Reporter:	Andrea Oliveri <oliveriandrea>
Component:	linux-firmware	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	23	CC:	dwmw2, jforbes, kernel-maint
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-18 18:56:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrea Oliveri 2015-09-17 16:00:31 UTC

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 16:20:40 UTC

ERRATA: Sorry the correct file is /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd

Comment 2 Josh Boyer 2015-09-17 16:53:38 UTC

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 17:02:22 UTC

I have never used b43-fwcutter, sorry :(
Ok you have explained very well, thankyou