Last rites: sys-firmware/iwl6050-ucode

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Last rites: sys-firmware/iwl6050-ucode

Mike Pagano
# Mike Pagano <[hidden email]> (2020-02-07)
# The standalone ebuild for this driver is made
# unnecessary as it is included in the package:
# sys-kernel/linux-firmware
sys-firmware/iwl6050-ucode

--
Mike Pagano
Gentoo Developer - Kernel Project
Gentoo Sources - Member
E-Mail     : [hidden email]
GnuPG FP   : EEE2 601D 0763 B60F 848C  9E14 3C33 C650 B576 E4E3
Public Key : http://pgp.mit.edu:11371/pks/lookup?search=0xB576E4E3&op=index

Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Mike Pagano
On Fri, Feb 07, 2020 at 12:10:38PM -0500, Mike Pagano wrote:
> # Mike Pagano <[hidden email]> (2020-02-07)
> # The standalone ebuild for this driver is made
> # unnecessary as it is included in the package:
> # sys-kernel/linux-firmware
> sys-firmware/iwl6050-ucode

Bug #708622



> --
> Mike Pagano
> Gentoo Developer - Kernel Project
> Gentoo Sources - Member
> E-Mail     : [hidden email]
> GnuPG FP   : EEE2 601D 0763 B60F 848C  9E14 3C33 C650 B576 E4E3
> Public Key : http://pgp.mit.edu:11371/pks/lookup?search=0xB576E4E3&op=index
>

--
Mike Pagano
Gentoo Developer - Kernel Project
Gentoo Sources - Member
E-Mail     : [hidden email]
GnuPG FP   : EEE2 601D 0763 B60F 848C  9E14 3C33 C650 B576 E4E3
Public Key : http://pgp.mit.edu:11371/pks/lookup?search=0xB576E4E3&op=index

Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Matt Turner-5
In reply to this post by Mike Pagano
On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]> wrote:
>
> # Mike Pagano <[hidden email]> (2020-02-07)
> # The standalone ebuild for this driver is made
> # unnecessary as it is included in the package:
> # sys-kernel/linux-firmware
> sys-firmware/iwl6050-ucode

How about all the others as well?

sys-firmware/iwl1000-ucode
sys-firmware/iwl3160-7260-bt-ucode
sys-firmware/iwl3160-ucode
sys-firmware/iwl6005-ucode
sys-firmware/iwl6030-ucode
sys-firmware/iwl7260-ucode
sys-firmware/iwl8000-ucode

Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Ulrich Mueller-2
>>>>> On Fri, 07 Feb 2020, Matt Turner wrote:

> On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]> wrote:
>>
>> # Mike Pagano <[hidden email]> (2020-02-07)
>> # The standalone ebuild for this driver is made
>> # unnecessary as it is included in the package:
>> # sys-kernel/linux-firmware
>> sys-firmware/iwl6050-ucode

> How about all the others as well?

> sys-firmware/iwl1000-ucode
> sys-firmware/iwl3160-7260-bt-ucode
> sys-firmware/iwl3160-ucode
> sys-firmware/iwl6005-ucode
> sys-firmware/iwl6030-ucode
> sys-firmware/iwl7260-ucode
> sys-firmware/iwl8000-ucode

I had asked the same question back in November, but an argument against
it was that sys-kernel/linux-firmware is quite a monster. In the default
configuration, its installation footprint is 515 MiB.

But yeah, either we should keep them all or remove them all.

Ulrich

signature.asc (517 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Matt Turner-5
On Fri, Feb 7, 2020 at 11:39 AM Ulrich Mueller <[hidden email]> wrote:

>
> >>>>> On Fri, 07 Feb 2020, Matt Turner wrote:
>
> > On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]> wrote:
> >>
> >> # Mike Pagano <[hidden email]> (2020-02-07)
> >> # The standalone ebuild for this driver is made
> >> # unnecessary as it is included in the package:
> >> # sys-kernel/linux-firmware
> >> sys-firmware/iwl6050-ucode
>
> > How about all the others as well?
>
> > sys-firmware/iwl1000-ucode
> > sys-firmware/iwl3160-7260-bt-ucode
> > sys-firmware/iwl3160-ucode
> > sys-firmware/iwl6005-ucode
> > sys-firmware/iwl6030-ucode
> > sys-firmware/iwl7260-ucode
> > sys-firmware/iwl8000-ucode
>
> I had asked the same question back in November, but an argument against
> it was that sys-kernel/linux-firmware is quite a monster. In the default
> configuration, its installation footprint is 515 MiB.

Oh yeah. The thread where the person arguing for keeping them didn't
know about USE=savedconfig :)

Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Michael 'veremitz' Everitt
On 07/02/20 19:50, Matt Turner wrote:

> On Fri, Feb 7, 2020 at 11:39 AM Ulrich Mueller <[hidden email]> wrote:
>>>>>>> On Fri, 07 Feb 2020, Matt Turner wrote:
>>> On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]> wrote:
>>>> # Mike Pagano <[hidden email]> (2020-02-07)
>>>> # The standalone ebuild for this driver is made
>>>> # unnecessary as it is included in the package:
>>>> # sys-kernel/linux-firmware
>>>> sys-firmware/iwl6050-ucode
>>> How about all the others as well?
>>> sys-firmware/iwl1000-ucode
>>> sys-firmware/iwl3160-7260-bt-ucode
>>> sys-firmware/iwl3160-ucode
>>> sys-firmware/iwl6005-ucode
>>> sys-firmware/iwl6030-ucode
>>> sys-firmware/iwl7260-ucode
>>> sys-firmware/iwl8000-ucode
>> I had asked the same question back in November, but an argument against
>> it was that sys-kernel/linux-firmware is quite a monster. In the default
>> configuration, its installation footprint is 515 MiB.
> Oh yeah. The thread where the person arguing for keeping them didn't
> know about USE=savedconfig :)
>
You still have to install the full 515MiB before you can apply savedconfig,
unless you already know the list of firmwares included, and create the file
in advance. For some systems (esp. storage constrained) that's not a very
good option ...


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Matt Turner-5
On Fri, Feb 7, 2020 at 12:03 PM Michael 'veremitz' Everitt
<[hidden email]> wrote:

>
> On 07/02/20 19:50, Matt Turner wrote:
> > On Fri, Feb 7, 2020 at 11:39 AM Ulrich Mueller <[hidden email]> wrote:
> >>>>>>> On Fri, 07 Feb 2020, Matt Turner wrote:
> >>> On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]> wrote:
> >>>> # Mike Pagano <[hidden email]> (2020-02-07)
> >>>> # The standalone ebuild for this driver is made
> >>>> # unnecessary as it is included in the package:
> >>>> # sys-kernel/linux-firmware
> >>>> sys-firmware/iwl6050-ucode
> >>> How about all the others as well?
> >>> sys-firmware/iwl1000-ucode
> >>> sys-firmware/iwl3160-7260-bt-ucode
> >>> sys-firmware/iwl3160-ucode
> >>> sys-firmware/iwl6005-ucode
> >>> sys-firmware/iwl6030-ucode
> >>> sys-firmware/iwl7260-ucode
> >>> sys-firmware/iwl8000-ucode
> >> I had asked the same question back in November, but an argument against
> >> it was that sys-kernel/linux-firmware is quite a monster. In the default
> >> configuration, its installation footprint is 515 MiB.
> > Oh yeah. The thread where the person arguing for keeping them didn't
> > know about USE=savedconfig :)
> >
> You still have to install the full 515MiB before you can apply savedconfig,
> unless you already know the list of firmwares included, and create the file
> in advance. For some systems (esp. storage constrained) that's not a very
> good option ...

Even that's not true. Just look at the git repo.

Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Alexander Tsoy-3
In reply to this post by Matt Turner-5
7 февраля 2020 г. 22:50:13 GMT+03:00, Matt Turner <[hidden email]> пишет:

>On Fri, Feb 7, 2020 at 11:39 AM Ulrich Mueller <[hidden email]> wrote:
>>
>> >>>>> On Fri, 07 Feb 2020, Matt Turner wrote:
>>
>> > On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]>
>wrote:
>> >>
>> >> # Mike Pagano <[hidden email]> (2020-02-07)
>> >> # The standalone ebuild for this driver is made
>> >> # unnecessary as it is included in the package:
>> >> # sys-kernel/linux-firmware
>> >> sys-firmware/iwl6050-ucode
>>
>> > How about all the others as well?
>>
>> > sys-firmware/iwl1000-ucode
>> > sys-firmware/iwl3160-7260-bt-ucode
>> > sys-firmware/iwl3160-ucode
>> > sys-firmware/iwl6005-ucode
>> > sys-firmware/iwl6030-ucode
>> > sys-firmware/iwl7260-ucode
>> > sys-firmware/iwl8000-ucode
>>
>> I had asked the same question back in November, but an argument
>against
>> it was that sys-kernel/linux-firmware is quite a monster. In the
>default
>> configuration, its installation footprint is 515 MiB.
>
>Oh yeah. The thread where the person arguing for keeping them didn't
>know about USE=savedconfig :)

USE=savedconfig is very inconvinient, especially for a package that can introduce new firmware files for the same hardware. Adding support for masks would improve that a bit.

--
Alexander Tsoy

Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Mike Gilbert-2
In reply to this post by Ulrich Mueller-2
On Fri, Feb 7, 2020 at 2:39 PM Ulrich Mueller <[hidden email]> wrote:

>
> >>>>> On Fri, 07 Feb 2020, Matt Turner wrote:
>
> > On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]> wrote:
> >>
> >> # Mike Pagano <[hidden email]> (2020-02-07)
> >> # The standalone ebuild for this driver is made
> >> # unnecessary as it is included in the package:
> >> # sys-kernel/linux-firmware
> >> sys-firmware/iwl6050-ucode
>
> > How about all the others as well?
>
> > sys-firmware/iwl1000-ucode
> > sys-firmware/iwl3160-7260-bt-ucode
> > sys-firmware/iwl3160-ucode
> > sys-firmware/iwl6005-ucode
> > sys-firmware/iwl6030-ucode
> > sys-firmware/iwl7260-ucode
> > sys-firmware/iwl8000-ucode
>
> I had asked the same question back in November, but an argument against
> it was that sys-kernel/linux-firmware is quite a monster. In the default
> configuration, its installation footprint is 515 MiB.
>
> But yeah, either we should keep them all or remove them all.

It looks like several different people maintain the individual
iwlXXXX-ucode packages.

Removing them all would require some consensus among those maintainers.

Keeping them all means forcing maintainers to work on stuff they don't
care about, or will result in stuff getting dropped to
maintainer-needed.

Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Michael 'veremitz' Everitt
In reply to this post by Matt Turner-5
On 07/02/20 20:39, Matt Turner wrote:

> On Fri, Feb 7, 2020 at 12:03 PM Michael 'veremitz' Everitt
> <[hidden email]> wrote:
>> On 07/02/20 19:50, Matt Turner wrote:
>>> On Fri, Feb 7, 2020 at 11:39 AM Ulrich Mueller <[hidden email]> wrote:
>>>>>>>>> On Fri, 07 Feb 2020, Matt Turner wrote:
>>>>> On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]> wrote:
>>>>>> # Mike Pagano <[hidden email]> (2020-02-07)
>>>>>> # The standalone ebuild for this driver is made
>>>>>> # unnecessary as it is included in the package:
>>>>>> # sys-kernel/linux-firmware
>>>>>> sys-firmware/iwl6050-ucode
>>>>> How about all the others as well?
>>>>> sys-firmware/iwl1000-ucode
>>>>> sys-firmware/iwl3160-7260-bt-ucode
>>>>> sys-firmware/iwl3160-ucode
>>>>> sys-firmware/iwl6005-ucode
>>>>> sys-firmware/iwl6030-ucode
>>>>> sys-firmware/iwl7260-ucode
>>>>> sys-firmware/iwl8000-ucode
>>>> I had asked the same question back in November, but an argument against
>>>> it was that sys-kernel/linux-firmware is quite a monster. In the default
>>>> configuration, its installation footprint is 515 MiB.
>>> Oh yeah. The thread where the person arguing for keeping them didn't
>>> know about USE=savedconfig :)
>>>
>> You still have to install the full 515MiB before you can apply savedconfig,
>> unless you already know the list of firmwares included, and create the file
>> in advance. For some systems (esp. storage constrained) that's not a very
>> good option ...
> Even that's not true. Just look at the git repo.
>
In that case, and in truth this is what I do in practice, I just simply
download the relevant firmware files Direct from git, and side-step all
this package nonsense :)


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Last rites: sys-firmware/iwl6050-ucode

Matt Turner-5
In reply to this post by Alexander Tsoy-3
On Fri, Feb 7, 2020 at 12:44 PM Alexander Tsoy <[hidden email]> wrote:

>
> 7 февраля 2020 г. 22:50:13 GMT+03:00, Matt Turner <[hidden email]> пишет:
> >On Fri, Feb 7, 2020 at 11:39 AM Ulrich Mueller <[hidden email]> wrote:
> >>
> >> >>>>> On Fri, 07 Feb 2020, Matt Turner wrote:
> >>
> >> > On Fri, Feb 7, 2020 at 9:10 AM Mike Pagano <[hidden email]>
> >wrote:
> >> >>
> >> >> # Mike Pagano <[hidden email]> (2020-02-07)
> >> >> # The standalone ebuild for this driver is made
> >> >> # unnecessary as it is included in the package:
> >> >> # sys-kernel/linux-firmware
> >> >> sys-firmware/iwl6050-ucode
> >>
> >> > How about all the others as well?
> >>
> >> > sys-firmware/iwl1000-ucode
> >> > sys-firmware/iwl3160-7260-bt-ucode
> >> > sys-firmware/iwl3160-ucode
> >> > sys-firmware/iwl6005-ucode
> >> > sys-firmware/iwl6030-ucode
> >> > sys-firmware/iwl7260-ucode
> >> > sys-firmware/iwl8000-ucode
> >>
> >> I had asked the same question back in November, but an argument
> >against
> >> it was that sys-kernel/linux-firmware is quite a monster. In the
> >default
> >> configuration, its installation footprint is 515 MiB.
> >
> >Oh yeah. The thread where the person arguing for keeping them didn't
> >know about USE=savedconfig :)
>
> USE=savedconfig is very inconvinient, especially for a package that can introduce new firmware files for the same hardware. Adding support for masks would improve that a bit.

Agreed. Mask/wildcard support would solve that problem well.