From: "Anand Kumria" <wildfire@progsoc.org>
To: netdev@vger.kernel.org
Subject: Re: [RFC] [PATCH 2/3] adds ieee80211_regdomains support
Date: Wed, 25 Oct 2006 02:07:03 +0000 (UTC) [thread overview]
Message-ID: <ehmgs7$cba$1@sea.gmane.org> (raw)
In-Reply-To: 43e72e890610231547k3cf6c590r4abd0a6fe7965fda@mail.gmail.com
On Mon, 23 Oct 2006 18:47:25 -0400, Luis R. Rodriguez wrote:
> ieee80211_regdomains
>
> Breaks down regulatory domains into data structures which allow
> drivers to share channel and power contraints based on stack
> regulatory domain. This driver adds in-kernel support for common
> regulatory domains (such as FCC and ETSI), makes updating the
[snip]
+/* Stack regulatory domain values. Atheros seems to have started this
+ * convention and most hardware vendors followed their example.
+ * Although these are *very* common we allow for a hw-specific
+ * map between stack and device regdomain values. */
+enum stack_regdomain {
+ REGDOMAIN_WORLD = 0x00, /* World compliance, minimum set */
+ REGDOMAIN_FCC = 0x10, /* USA */
+ REGDOMAIN_IC = 0x20, /* Canada */
+ REGDOMAIN_ETSI = 0x30, /* Europe */
+ REGDOMAIN_SPAIN = 0x31, /* Spain */
+ REGDOMAIN_FRANCE = 0x32, /* France */
+ REGDOMAIN_MKK = 0x40, /* Japan */
+};
+
Why not pick either the country name or the organisation within the country that determines the frequency guidelines?
Regards,
Anand
next prev parent reply other threads:[~2006-10-25 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 22:47 [RFC] [PATCH 2/3] adds ieee80211_regdomains support Luis R. Rodriguez
2006-10-24 8:33 ` Johannes Berg
2006-10-24 17:10 ` Luis R. Rodriguez
2006-10-25 2:07 ` Anand Kumria [this message]
2006-10-25 15:16 ` 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='ehmgs7$cba$1@sea.gmane.org' \
--to=wildfire@progsoc.org \
--cc=netdev@vger.kernel.org \
/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).