From: Kalle Valo <kvalo@codeaurora.org>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: "Nuno Gonçalves" <nunojpg@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Ubuntu regulatory database
Date: Mon, 27 Apr 2015 15:24:35 +0300 [thread overview]
Message-ID: <87pp6ppxmk.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20150427113437.GA4268@ubuntu-hedt> (Seth Forshee's message of "Mon, 27 Apr 2015 06:34:37 -0500")
Seth Forshee <seth.forshee@canonical.com> writes:
> On Mon, Apr 27, 2015 at 08:08:01AM +0300, Kalle Valo wrote:
>> Seth Forshee <seth.forshee@canonical.com> writes:
>>
>> > On Sat, Apr 25, 2015 at 06:26:34PM +0100, Nuno Gonçalves wrote:
>> >> I was surprised that the wireless regdb provided with Ubuntu 15.04 is
>> >> almost 2 years old.
>> >>
>> >> Are you aware of the reason Ubuntu is not providing a updated regdb by default?
>> >
>> > This doesn't really seem on topic for the mailing list as it's a distro
>> > issue.
>> >
>> > But yes, it recently came to my attention that our distro package hadn't
>> > been updated in a while (I don't maintain the distro package and
>> > obviously wasn't paying close enough attention). It will be updated
>> > soon.
>>
>> Oh, so does this mean that the old regdb doesn't support 80 MHz
>> channels? Is there any way to make it easier to update the regdb in
>> older Ubuntu versions?
>
> It's likely we'll start pulling in updates on a continuing basis for as
> long as a release is supported. It's been on the list of things to get
> worked out right after 15.04 releases, i.e. this week.
Nice, that would be perfect.
--
Kalle Valo
prev parent reply other threads:[~2015-04-27 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 17:26 Ubuntu regulatory database Nuno Gonçalves
2015-04-25 19:09 ` Seth Forshee
2015-04-27 5:08 ` Kalle Valo
2015-04-27 5:21 ` Luca Coelho
2015-04-27 6:22 ` Kalle Valo
2015-04-27 11:34 ` Seth Forshee
2015-04-27 12:24 ` Kalle Valo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pp6ppxmk.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nunojpg@gmail.com \
--cc=seth.forshee@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.