Each file needs to be converted to the right name to be found for a particular device. See for example https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=bcm20702a1-firmware, https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=bcm4350-firmware and http://www.slackwiki.com/Btfirmware-nonfree
Search Criteria
Package Details: bt-dw1560-firmware 1.0-1
| Git Clone URL: | https://aur.archlinux.org/bt-dw1560-firmware.git (read-only) |
|---|---|
| Package Base: | bt-dw1560-firmware |
| Description: | Bluetooth firmware for Dell DW1560 802.11ac (Broadcom BCM4352) adapter |
| Upstream URL: | None |
| Licenses: | |
| Provides: | |
| Submitter: | DonJaime |
| Maintainer: | None |
| Last Packager: | DonJaime |
| Votes: | 6 |
| Popularity: | 0.000928 |
| First Submitted: | 2016-03-10 07:43 |
| Last Updated: | 2016-03-10 07:46 |
Dependencies (2)
- bluez-utils (bluez-git, bluez-utils-compat) (make)
- cabextract (make)
Required by (0)
Sources (1)
Latest Comments
DonJaime commented on 2016-08-29 09:32
DonJaime commented on 2016-08-28 16:57
nTia89 commented on 2016-08-28 16:19
how can you state it?
DonJaime commented on 2016-08-28 16:05
The 1709 file is for a different device.
nTia89 commented on 2016-08-28 10:37
sorry, I bad copied the file!
comparing checksum, it shows me they are different:
[mattia@arch-xps tmp]$ sha256sum BCM20702A1_001.002.014.1443.1572.hex
521f0fc5eacc119407a242ee9fd4affdc9704aa0192dfb32448f4b8bbccad2f7
[mattia@arch-xps tmp]$ sha256sum BCM20702A1_001.002.014.1483.1709.hex
ed3df016456e9ecdc5292112aba4b30735c774b679642f2fcbabe5a98e7b33b0
DonJaime commented on 2016-08-28 09:15
The softpedia package appears to be newer but the firmware is unchanged.
nTia89 commented on 2016-08-28 07:39
seem to be a new version of the firmware.
I downloaded it from here: http://drivers.softpedia.com/get/BLUETOOTH/Broadcom/Broadcom-DW1560-Bluetooth-40-LE-Driver-1201713-for-Windows-10-64-bit.shtml
the version stops at: BCM20702A1_001.002.014.1483.1671
DonJaime commented on 2016-04-08 10:18
Some kernel versions looked for the one name, some look for the other. It's safer to include both.
nTia89 commented on 2016-04-07 16:39
Why we need to link BCM20702A1* to BCM20702A0* (I'm talking about the last line of PKGBUILD: ln -rs BCM20702A1-0a5c-216f.hcd BCM20702A0-0a5c-216f.hcd),
since kernel already looks for the BCM20702A1* one?
[mattia@arch-xps ~]$ dmesg | grep blue
[ 1.353778] Bluetooth: Core ver 2.21
[ 1.353794] Bluetooth: HCI device and connection manager initialized
[ 1.353797] Bluetooth: HCI socket layer initialized
[ 1.353800] Bluetooth: L2CAP socket layer initialized
[ 1.353805] Bluetooth: SCO socket layer initialized
[ 1.373102] Bluetooth: hci0: BCM: chip id 63
[ 1.389112] Bluetooth: hci0: BCM20702A
[ 1.390110] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 1.390476] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-216f.hcd failed with error -2
[ 1.390479] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-216f.hcd not found
The bcm20702a1-firmware package now includes this firmware, so as I see things this package is now redundant.