Bug#948712: [Pkg-raspi-maintainers] Bug#948712: Pinebook Pro also uses this chip
On Tue, 2022-07-12 at 20:18 +0200, Adam Borowski wrote: > On Tue, Jul 12, 2022 at 12:45:11PM +0200, Diederik de Haas wrote: > > On dinsdag 12 juli 2022 01:47:21 CEST Adam Borowski wrote: > > > Pinebook Pro also wants this firmware, and it's definitely not a raspi, > > > and it doesn't have /boot/firmware either. > > > > Is this about the /lib/firmware/brcm/brcmfmac434* files? > > > > IMO, that group of files shouldn't be part of this package, but be moved to > > another firmware package, perhaps firmware-brcm80211? > > Yeah, that. > > The idea of moving these files to another package seems good; steev proposed > firmware-linux, firmware-brcm80211 would be a more specific fit. > Both packages are maintained by debian-kernel@l.d.o, could you folks > comment please? So long as those files are in linux-firmware.git, it should be fine to ship them in firmware-brcm80211. If they aren't, they should be added there first. Ben. -- Ben Hutchings friends: People who know you well, but like you anyway. signature.asc Description: This is a digitally signed message part
Bug#948712: [Pkg-raspi-maintainers] Bug#948712: Pinebook Pro also uses this chip
Hi, In the FWIW catagory, I'm following this thread beacuse installed Debian (11) on an RPI4B using the Debian installer. Following the instructions: https://wiki.debian.org/RaspberryPi4?action=show=InstallingDebianOn%2FRaspberryPi%2FRaspberry+Pi+4#Using_EFI_Firmware_and_the_regular_Debian_Installer and following the link to: https://forums.raspberrypi.com/viewtopic.php?t=282839 What I found, I think, was that /boot/firmware does not then exist on the resulting system. I _believe_ I solved the issue by creating a symlink. (Maybe to /boot/UEFI/firmware/ ??) All this was some time ago and I will have to (eventually) go back and look at my notes and report back. (I'd put off reporting anything until I'd figured out something that worked. By then I'd forgotten about this thread and was just reminded by the recent emails.) I'm not even 100% certain that the rpi firmware package is relevant. But I think so, to get wireless working. Here's hoping that this is useful feedback and not noise. Regards, Karl Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein
Bug#948712: [Pkg-raspi-maintainers] Bug#948712: Pinebook Pro also uses this chip
On Tue, Jul 12, 2022 at 12:45:11PM +0200, Diederik de Haas wrote: > On dinsdag 12 juli 2022 01:47:21 CEST Adam Borowski wrote: > > Pinebook Pro also wants this firmware, and it's definitely not a raspi, > > and it doesn't have /boot/firmware either. > > Is this about the /lib/firmware/brcm/brcmfmac434* files? > > IMO, that group of files shouldn't be part of this package, but be moved to > another firmware package, perhaps firmware-brcm80211? Yeah, that. The idea of moving these files to another package seems good; steev proposed firmware-linux, firmware-brcm80211 would be a more specific fit. Both packages are maintained by debian-kernel@l.d.o, could you folks comment please? Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ What kind of a drug are "base" and "red pill"? I think acid is ⢿⡄⠘⠷⠚⠋⠀ LSD, which would make base... ? Judging from the behaviour of ⠈⠳⣄ those "based and redpilled", something nasty.
Bug#948712: [Pkg-raspi-maintainers] Bug#948712: Pinebook Pro also uses this chip
On dinsdag 12 juli 2022 01:47:21 CEST Adam Borowski wrote: > Pinebook Pro also wants this firmware, and it's definitely not a raspi, > and it doesn't have /boot/firmware either. Is this about the /lib/firmware/brcm/brcmfmac434* files? IMO, that group of files shouldn't be part of this package, but be moved to another firmware package, perhaps firmware-brcm80211? signature.asc Description: This is a digitally signed message part.
