Hi! Diederik de Haas dijo [Tue, Jan 31, 2023 at 10:33:41PM +0100]: > > Would they fit into a separate source package not associated with > > raspi-config? > > I do strongly think they do not belong in the raspi-firmware package for the > reason I retitled this bug and retitled my response Subject. Another reason > is > that the raspi-firmware package makes (several) assumptions, namely that they > are only used/usable on RPi devices and have a /boot/firmware directory > (where > a FAT partition is mounted, although that part is not checked for). > I have previously expressed my concerns/doubts about that, but that's outside > the scope of this bug. > It also looks 'weird' to install the raspi-firmware package while you only > care > about the wifi firmware and not care about RPi's at all.
Right, I agree this should be a package of its own. I didn't know raspi-nonfree came from a "coherent" set of firmware sources provided by a single upstream. It is a distorsion that peopleinterested in brcmfmac firmware have to install raspi-firmware if they have different hardware. > > The other option is that they get included upstream in > > linux-firmware.git by upstream? > > Gunnar knows I'm not much of a fan of Raspberry Pi Foundation (RPF) and that > was confirmed once again by their typical reaction to this exact request. > > I'm too 'lazy' to look it up, so I'll paraphrase it: > "It works for us (so fsck off). Can't you just use our files?" I doubt we will find true RPF fans here 😉
signature.asc
Description: PGP signature
