Package: bluez-firmware (1.2-160000.2.2)
Micrologiciel Bluetooth(TM)
Micrologiciel Bluetooth(TM). Le paquet contient des images de micrologiciel pour certains adaptateurs Bluetooth(TM). Actuellement pris en charge : * Broadcom Corporation BCM2033 * AVM Computersysteme Vertriebs GmbH BLUEFRITZ! USB Les marques BLUETOOTH appartiennent à Bluetooth SIG, Inc., USA.
Package information
- Homepage
- [http://www.bluez.org/]
- License
- GPL-2.0-only AND GPL-2.0-or-later AND SUSE-Firmware
- Mainteneur du paquet aval
- Inconnu : non déclaré dans la source indexée
- Paquet source
- [bluez-firmware]
- Software project
- [bluez]
Versions and downloads for bluez-firmware
| Version / release | Architecture / repository | Package size | Installed size | Files | Publisher repository artifact |
|---|---|---|---|---|---|
| 1.2-160000.2.2leap-16.0 / oss | aarch64openSUSE Leap 16.0 · OSS · multi-architecture | 313 KiB | 565 KiB | list of files | bluez-firmware-1.2-160000.2.2.aarch64.rpm |
| 1.2-160000.2.2leap-16.0 / oss | ppc64leopenSUSE Leap 16.0 · OSS · multi-architecture | 313 KiB | 565 KiB | list of files | bluez-firmware-1.2-160000.2.2.ppc64le.rpm |
| 1.2-160000.2.2leap-16.0 / oss | s390xopenSUSE Leap 16.0 · OSS · multi-architecture | 313 KiB | 565 KiB | list of files | bluez-firmware-1.2-160000.2.2.s390x.rpm |
| 1.2-160000.2.2leap-16.0 / oss | x86_64openSUSE Leap 16.0 · OSS · multi-architecture | 313 KiB | 565 KiB | list of files | bluez-firmware-1.2-160000.2.2.x86_64.rpm |
About these downloads
Chaque ligne est une métadonnée d'index pour une version, une architecture, une suite et un dépôt. Noms, URL et tailles viennent de la source ; un lien est un emplacement de récupération mutable, pas une redistribution OpenFactory.
Dependencies and recommendations for bluez-firmware
enh: modalias(usb:v057Cp2200d*dc*dsc*dp*ic*isc*ip*)
Package not available
enh: modalias(usb:v0A5Cp2033d*dc*dsc*dp*ic*isc*ip*)
Package not available
Chemins de fichiers du paquet (15)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
- /usr/lib/firmware/BCM2033-FW.bin
- /usr/lib/firmware/BCM2033-MD.hex
- /usr/lib/firmware/bfubase.frm
- /usr/lib/firmware/STLC2500_R4_00_03.ptc
- /usr/lib/firmware/STLC2500_R4_00_06.ssf
- /usr/lib/firmware/STLC2500_R4_02_02_WLAN.ssf
- /usr/lib/firmware/STLC2500_R4_02_04.ptc
- /usr/share/doc/packages/bluez-firmware
- /usr/share/doc/packages/bluez-firmware/AUTHORS
- /usr/share/doc/packages/bluez-firmware/BCM-LEGAL.txt
- /usr/share/doc/packages/bluez-firmware/ChangeLog
- /usr/share/doc/packages/bluez-firmware/INSTALL
- /usr/share/doc/packages/bluez-firmware/README
- /usr/share/licenses/bluez-firmware
- /usr/share/licenses/bluez-firmware/COPYING
Field source: openSUSE Leap 16.0 OSS
