From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 v5] cfg80211: Add new wireless regulatory infrastructure
Date: Fri, 05 Sep 2008 22:01:32 +0200 [thread overview]
Message-ID: <1220644892.11109.18.camel@johannes.berg> (raw)
In-Reply-To: <1220643824-11398-1-git-send-email-lrodriguez@atheros.com>
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]
On Fri, 2008-09-05 at 12:43 -0700, Luis R. Rodriguez wrote:
> This adds the new wireless regulatory infrastructure. The
> main motiviation behind this was to centralize regulatory
> code as each driver was implementing their own regulatory solution,
> and to replace the initial centralized code we have where:
>
> * only 3 regulatory domains are supported: US, JP and EU
> * regulatory domains can only be changed through a module parameter
> * all rules are built statically in the kernel
>
> We now have support for regulatory domains for many countries
> and regulatory domains are now queried through a userspace agent
> (CRDA) through udev allowing distributions to update regulatory rules
> without updating the kernel. Updates on regulatory rules can
> now be left as an independent effort.
>
> Each driver can regulatory_hint() a regulatory domain
> based on either their EEPROM mapped regulatory domain value to a
> respective ISO/IEC 3166-1 country code or pass an internally built
> regulatory domain. We also add support to let the user set the
> regulatory domain through userspace in case of faulty EEPROMs to
> further help compliance.
>
> Support for world roaming will be added soon for cards capable of
> this.
>
> For more information see:
>
> http://wireless.kernel.org/en/developers/Regulatory/CRDA
>
> For now we leave an option to enable the old module parameter,
> ieee80211_regdom, and to build the 3 old regdomains statically
> (US, JP and EU). This option is CONFIG_WIRELESS_OLD_REGULATORY.
> These old static definitions and the module parameter is being
> scheduled for removal for 2.6.29.
>
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Looks fine to me now, as far as I've looked, I guess there'll be some
odd fixes required etc. but we can figure that out.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-09-05 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 19:43 [PATCH 1/2 v5] cfg80211: Add new wireless regulatory infrastructure Luis R. Rodriguez
2008-09-05 20:01 ` Johannes Berg [this message]
2008-09-06 2:33 ` Marcel Holtmann
2008-09-09 5:48 ` 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=1220644892.11109.18.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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