From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: tim.gardner@canonical.com,
reinette chatre <reinette.chatre@intel.com>,
"stable@kernel.org" <stable@kernel.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Please apply to stable: cfg80211: add support for custom firmware regulatory solutions
Date: Fri, 6 Mar 2009 09:36:12 -0500 [thread overview]
Message-ID: <20090306143612.GA3712@tuxdriver.com> (raw)
In-Reply-To: <43e72e890903051633w7880648djdd798c5a28285a6b@mail.gmail.com>
On Thu, Mar 05, 2009 at 04:33:37PM -0800, Luis R. Rodriguez wrote:
> On Thu, Mar 5, 2009 at 4:26 PM, Tim Gardner <tim.gardner@canonical.com> wrote:
> > What is the downside of just turning OLD_REG back on for 2.6.28?
>
> You default to the "US" regulatory domain so channels 12-14 will not
> be available by default. This is also why we offloaded regulatory crap
> to userspace in the first place, so you won't have to upgrade your
> kernel based on reg changes or fixes.
>
> I'll send a patch to enable passive scan on channels 12-14 for the
> world regulatory domain. That and the 5 GHz patch should at least let
> you see channels 12-14 with a fix from userspace. This can also go
> into 28 for the world regulatory domain and since it would be fixing
> an issue maybe we should consider it.
>
> Thoughts John?
Honestly I don't think it is worth swizzling -stable for this.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-03-06 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 21:35 Please apply to stable: cfg80211: add support for custom firmware regulatory solutions Luis R. Rodriguez
2009-03-05 17:54 ` reinette chatre
2009-03-05 19:24 ` Luis R. Rodriguez
2009-03-05 22:49 ` Tim Gardner
2009-03-05 23:13 ` Luis R. Rodriguez
2009-03-06 0:26 ` Tim Gardner
2009-03-06 0:33 ` Luis R. Rodriguez
2009-03-06 14:36 ` John W. Linville [this message]
2009-03-06 22:00 ` Luis R. Rodriguez
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=20090306143612.GA3712@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=reinette.chatre@intel.com \
--cc=stable@kernel.org \
--cc=tim.gardner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).