From: Seth Forshee <seth.forshee@canonical.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
"Quan, David" <dquan@qca.qualcomm.com>,
"Green, Michael" <green@qca.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Problems with regulatory domain support and BCM43224
Date: Thu, 8 Mar 2012 15:42:06 -0600 [thread overview]
Message-ID: <20120308214205.GB13667@ubuntu-macmini> (raw)
In-Reply-To: <4F592542.7000005@broadcom.com>
On Thu, Mar 08, 2012 at 10:31:46PM +0100, Arend van Spriel wrote:
> >>Noticed your email yesterday, but did not get to chime into the
> >>conversation. brcmsmac does indeed provide a regulatory hint, which is
> >>either from SPROM or hard-coded to "US". Since "X0" is not a known
> >>regulatory domain for crda it does not make sense to pass it as a regulatory
> >>hint. However, the "full" story is told on linuxwireless.org (see [1]).
> >
> >The Linux kernel allows you to define custom regulatory domains, the
> >ath module uses these, it defines 13 of them. You can review that code
> >for an example of how to use them. So your X0 can still be used, you
> >just have to define the data structure.
> >
>
> Thanks, Luis
>
> I will dive into that.
Luis, Arend, thanks to both of you. Let me know if there's anything I
can do to help.
Seth
next prev parent reply other threads:[~2012-03-08 21:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 19:40 Problems with regulatory domain support and BCM43224 Seth Forshee
2012-03-08 17:41 ` Seth Forshee
2012-03-08 18:53 ` Luis R. Rodriguez
2012-03-08 19:07 ` Quan, David
2012-03-08 19:36 ` Luis R. Rodriguez
2012-03-08 19:45 ` Quan, David
2012-03-08 19:51 ` Luis R. Rodriguez
2012-03-08 20:07 ` Seth Forshee
2012-03-08 20:17 ` Luis R. Rodriguez
2012-03-08 21:01 ` Arend van Spriel
2012-03-08 21:06 ` Luis R. Rodriguez
2012-03-08 21:31 ` Arend van Spriel
2012-03-08 21:42 ` Seth Forshee [this message]
2012-03-20 22:07 ` Seth Forshee
2012-03-21 11:05 ` Arend van Spriel
2012-03-21 14:19 ` Seth Forshee
2012-03-21 17:51 ` Arend van Spriel
2012-03-21 18:17 ` Luis R. Rodriguez
2012-03-21 19:37 ` Seth Forshee
2012-03-22 0:27 ` Luis R. Rodriguez
2012-03-26 19:36 ` Seth Forshee
2012-04-04 2:46 ` Seth Forshee
2012-04-04 7:03 ` Arend van Spriel
2012-04-10 16:28 ` Seth Forshee
2012-04-11 10:16 ` Arend van Spriel
2012-04-11 13:39 ` Seth Forshee
2012-04-11 16:52 ` Arend van Spriel
2012-03-08 21:59 ` Seth Forshee
2012-03-08 22:12 ` Luis R. Rodriguez
2012-03-08 22:30 ` Seth Forshee
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=20120308214205.GB13667@ubuntu-macmini \
--to=seth.forshee@canonical.com \
--cc=arend@broadcom.com \
--cc=dquan@qca.qualcomm.com \
--cc=green@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rodrigue@qca.qualcomm.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).