Bug#1014865: [Pkg-raspi-maintainers] Bug#1014865: raspi-firmware dependencies
firmware-misc-nonfree i added because it adds some blobs to /lib/firmware/brcm: $ dpkg -S /lib/firmware/brcm/*.hcd firmware-misc-nonfree: /lib/firmware/brcm/BCM-0a5c-6410.hcd firmware-misc-nonfree: /lib/firmware/brcm/BCM-0bb4-0306.hcd bluez-firmware: /lib/firmware/brcm/BCM43430A1.hcd bluez-firmware: /lib/firmware/brcm/BCM43430B0.hcd bluez-firmware: /lib/firmware/brcm/BCM4345C0.hcd bluez-firmware: /lib/firmware/brcm/BCM4345C5.hcd just checked on amd64 and arm64, that those files are probably not needed by any kernel module explicitly, but probably requested by btusb module. maybe another 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 Jiri Kastner wrote: > > raspi-firmware should depend on following packages: > > - firmware-brcm80211 > > - firmware-misc-nonfree > > - bluez-firmware > > I'd object to the use (and implementation) of the word 'depend'. > A recommends or suggests seems more appropriate. -- signature.asc Description: PGP signature
Bug#1014865: [Pkg-raspi-maintainers] Bug#1014865: Bug#1014865: raspi-firmware dependencies
On Wednesday, 13 July 2022 18:58:33 CEST Diederik de Haas wrote: > On woensdag 13 juli 2022 15:41:25 CEST Jiri Kastner wrote: > > raspi-firmware should depend on following packages: > > - firmware-brcm80211 > > - firmware-misc-nonfree > > - bluez-firmware > > I'd object to the use (and implementation) of the word 'depend'. > A recommends or suggests seems more appropriate. I (now) even think 'recommends' is too strong, 'suggests' is (still) fine I guess for firmware-brcm80211 and bluez-firmware (partly due to its small size). But firmware-misc-nonfree uses 40MB (with f.e. nvidia firmware). FTR: firmware-brcm80211 package uses 17MB While those packages may be useful for some RPi models, it is useless bloat for others. Adding (some of) those to the image generation scripts, which can differentiate between RPi models, seems more appropriate. My 0.02 signature.asc Description: This is a digitally signed message part.
Bug#1014865: [Pkg-raspi-maintainers] Bug#1014865: raspi-firmware dependencies
On woensdag 13 juli 2022 15:41:25 CEST Jiri Kastner wrote: > raspi-firmware should depend on following packages: > - firmware-brcm80211 > - firmware-misc-nonfree > - bluez-firmware I'd object to the use (and implementation) of the word 'depend'. A recommends or suggests seems more appropriate. signature.asc Description: This is a digitally signed message part.
Bug#1014865: raspi-firmware dependencies
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 with zero v2) -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.18.0-2-rt-arm64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages raspi-firmware depends on: ii dosfstools 4.2-1 ii dpkg1.21.9 raspi-firmware recommends no packages. raspi-firmware suggests no packages. -- Configuration Files: /etc/default/raspi-firmware changed: ROOTPART=LABEL=RASPIROOT -- no debconf information
