subpackage - bluez-firmware-nonfree
another solution raspi-wireless-firmware and raspi3-wireless-firmware
subpackages
(maybe also raspi-bluetooth-firmware/raspi3-bluetooth-firmware)
On Wed, Jul 13, 2022 at 06:58:33PM +0200, Diederik de Haas wrote:
> On woensdag 13 juli 2022 15:41:25 CEST J
Package: raspi-firmware
Version: 1.20220331+ds-2
Severity: normal
Tags: d-i
raspi-firmware should depend on following packages:
- firmware-brcm80211
- firmware-misc-nonfree
- bluez-firmware
all packages above provide /lib/firmware/brcm files
bluez-firmware is needed to use bluetooth (tested
guilty commit is 959dc591c3cc577fbf8fdb4834228f0870730050
On Wed, Mar 23, 2022 at 9:33 AM Jiri Kastner wrote:
> Package: linux-image-arm64
> Version: 5.16.12-1~bpo11+1
> Severity: normal
> X-Debbugs-Cc: cz172...@gmail.com
>
> device tree overlays is nice feature, which is
Package: linux-image-arm64
Version: 5.16.12-1~bpo11+1
Severity: normal
X-Debbugs-Cc: cz172...@gmail.com
device tree overlays is nice feature, which is used a lot on sbc like
raspberry pi, beaglebone and so on.
arm64 kernel has bunch of industrialio drivers for spi/i2c as modules, to use
them, i
Package: linux-image-arm64
Version: 5.10.0
Severity: normal
Dear Maintainer,
removal of kernel config options for overlay is causing me
troubles to play with dtb without reboot.
for example jtag/swd/trace pins are usually muxed with gpio/sdmmc/lcd
on arm devices.
to be able debug or trace i
Package: kernel-package
Version: 12.036+nmu1
Severity: important
when i tried make-kpkg natively on armhf port, it started automatically cross
compilling, which ends on linking error, because there is no
arm-linux-gnueabihf-ld binary only ld.
expected is same behaviour like on ordinary
6 matches
Mail list logo
