Hi Salvatore,
On Sunday, 5 February 2023 16:17:58 CET Salvatore Bonaccorso wrote:
> > > So I guess we can close this bug here, and the files can be shipped
> > > with a new dedicated source package containing the firmware files,
> > > since the last option of having them merged upstream in
> > >
Hi Diederik,
On Sat, Feb 04, 2023 at 10:49:29PM +0100, Diederik de Haas wrote:
> On Saturday, 4 February 2023 22:12:24 CET Salvatore Bonaccorso wrote:
> > > 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
On Saturday, 4 February 2023 22:12:24 CET Salvatore Bonaccorso wrote:
> > 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
Hi,
On Wed, Feb 01, 2023 at 09:20:57PM -0600, Gunnar Wolf wrote:
> 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
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
Hi Salvatore and Gunnar,
On Tuesday, 31 January 2023 19:17:43 CET Salvatore Bonaccorso wrote:
> > Gunnar indicated that he's willing to remove the files from
> > raspi-firmware,
> > but they still need to be added to firmware-brcm80211, so pretty please?
>
> So I looked at this, and don't think
6 matches
Mail list logo
