Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #66279 > unrolled thread

udeb for wireless-regdb?

Started byBen Hutchings <ben@decadent.org.uk>
First post2020-02-02 01:00 +0100
Last post2020-09-21 22:20 +0200
Articles 4 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  udeb for wireless-regdb? Ben Hutchings <ben@decadent.org.uk> - 2020-02-02 01:00 +0100
    Re: udeb for wireless-regdb? Cyril Brulebois <kibi@debian.org> - 2020-02-03 01:30 +0100
      Re: udeb for wireless-regdb? Ben Hutchings <ben@decadent.org.uk> - 2020-02-03 18:40 +0100
        Re: udeb for wireless-regdb? Ben Hutchings <ben@decadent.org.uk> - 2020-09-21 22:20 +0200

#66279 — udeb for wireless-regdb?

FromBen Hutchings <ben@decadent.org.uk>
Date2020-02-02 01:00 +0100
Subjectudeb for wireless-regdb?
Message-ID<zvaQa-3kx-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Starting with Linux 5.5, we'll enable the kernel to directly load
wireless regulatory information.  I don't think it's that important in
the installer - wireless interfaces should be passively scannming for
APs and the APs should provide regulatory information.  That's why I
haven't thought of adding it to the installer previously.

However, now it would just be a case of adding two files for the kernel
to pick up.  So perhaps a udeb would be worthwhile?

Ben.

-- 
Ben Hutchings
I haven't lost my mind; it's backed up on tape somewhere.


[toc] | [next] | [standalone]


#66287

FromCyril Brulebois <kibi@debian.org>
Date2020-02-03 01:30 +0100
Message-ID<zvxMJ-n6-3@gated-at.bofh.it>
In reply to#66279

[Multipart message — attachments visible in raw view] — view raw

Hi Ben,

Ben Hutchings <ben@decadent.org.uk> (2020-02-02):
> Starting with Linux 5.5, we'll enable the kernel to directly load
> wireless regulatory information.  I don't think it's that important in
> the installer - wireless interfaces should be passively scannming for
> APs and the APs should provide regulatory information.  That's why I
> haven't thought of adding it to the installer previously.
> 
> However, now it would just be a case of adding two files for the kernel
> to pick up.  So perhaps a udeb would be worthwhile?

Adding such a udeb (and maybe depending on it from kernel-image, or
adding it to pkg-lists…) looks sane enough to me at first glance.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [next] | [standalone]


#66294

FromBen Hutchings <ben@decadent.org.uk>
Date2020-02-03 18:40 +0100
Message-ID<zvNRw-1rf-11@gated-at.bofh.it>
In reply to#66287

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2020-02-03 at 01:23 +0100, Cyril Brulebois wrote:
> Hi Ben,
> 
> Ben Hutchings <ben@decadent.org.uk> (2020-02-02):
> > Starting with Linux 5.5, we'll enable the kernel to directly load
> > wireless regulatory information.  I don't think it's that important in
> > the installer - wireless interfaces should be passively scannming for
> > APs and the APs should provide regulatory information.  That's why I
> > haven't thought of adding it to the installer previously.
> > 
> > However, now it would just be a case of adding two files for the kernel
> > to pick up.  So perhaps a udeb would be worthwhile?
> 
> Adding such a udeb (and maybe depending on it from kernel-image, or
> adding it to pkg-lists…) looks sane enough to me at first glance.

I think it would make sense to add it as a dependency of nic-wireless-
modules-di.

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.


[toc] | [prev] | [next] | [standalone]


#68231

FromBen Hutchings <ben@decadent.org.uk>
Date2020-09-21 22:20 +0200
Message-ID<ARAs2-zT-11@gated-at.bofh.it>
In reply to#66294

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2020-02-03 at 17:34 +0000, Ben Hutchings wrote:
> On Mon, 2020-02-03 at 01:23 +0100, Cyril Brulebois wrote:
> > Hi Ben,
> > 
> > Ben Hutchings <ben@decadent.org.uk> (2020-02-02):
> > > Starting with Linux 5.5, we'll enable the kernel to directly load
> > > wireless regulatory information.  I don't think it's that important in
> > > the installer - wireless interfaces should be passively scannming for
> > > APs and the APs should provide regulatory information.  That's why I
> > > haven't thought of adding it to the installer previously.
> > > 
> > > However, now it would just be a case of adding two files for the kernel
> > > to pick up.  So perhaps a udeb would be worthwhile?
> > 
> > Adding such a udeb (and maybe depending on it from kernel-image, or
> > adding it to pkg-lists…) looks sane enough to me at first glance.
> 
> I think it would make sense to add it as a dependency of nic-wireless-
> modules-di.

I came back to this and remembered that kernel-wedge discards any
dependencies on packages that it doesn't generate.  Rather than
changing kernel-wedge to let us avoid that, I've added
wireless-regdb-udeb directly to all the package lists that include
nic-wireless-modules.

Ben.

-- 
Ben Hutchings
The Peter principle: In a hierarchy, every employee tends to rise to
their level of incompetence.


[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web