linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: "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>,
	Arend van Spriel <arend@broadcom.com>
Subject: Re: Problems with regulatory domain support and BCM43224
Date: Thu, 8 Mar 2012 14:07:34 -0600	[thread overview]
Message-ID: <20120308200734.GC28133@ubuntu-macmini> (raw)
In-Reply-To: <CAB=NE6X9c1m63xayNsEf9XZ3AgPZDV2SiRivg3SV2Day83fPQA@mail.gmail.com>

On Thu, Mar 08, 2012 at 11:51:03AM -0800, Luis R. Rodriguez wrote:
> On Thu, Mar 8, 2012 at 11:45 AM, Quan, David <dquan@qca.qualcomm.com> wrote:
> > I think there is to it more than SW.
> > Where ever you get this card, is the card tested and regulatory approved for those countries, DFS or not?
> 
> Seth, what driver are you using? I know you are using a BCM43224 card.

brcmsmac

> > It is possible that this card is only regulatory tested for non DFS channels, but now you enable them for passive.
> 
> That's a good point.
> 
> > This means that yes, you are save and not violate DFS rules because you are in passive mode. However, you are in complete violation if the STA finds an AP on that DFS channel and then connects and transmits as this STA is not allow to transmit on that channel since it is not approved.
> 
> If the driver being used is a supported vendor driver then I'll punt
> this to the vendor (Broadcom). If this is the reversed engineered
> driver (b43) that Broadcom to this day seems to blindly ignore even
> for regulatory, then I'm happy to recommend based on your input to
> leave the regulatory domain as-is given that we cannot guarantee what
> the vendor meant as they have not done any work on releasing either
> documentation or code to help with their regulatory situation.

It would be nice if Broadcom could weigh in. Cc-ing Arend.

This is actually a special case. This is an Apple machine, and it's not
that there's no regulatory hint in the ROM, it's that the hint is the
bogus country code "X0". From reading online, Apple uses this to
indicate the regulatory domain is unknown, and it uses the first
regulatory hint it sees in a country IE. I can connect to DFS channels
using MacOS on the machine, so I'll assume it was approved for DFS
channels.

Since Linux (afaict) only uses hits from country IEs for APs it's
connected to, much of the time this card ends up using the world domain
and is unable to scan DFS channels.

Thanks,
Seth


  reply	other threads:[~2012-03-08 20:07 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 [this message]
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
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=20120308200734.GC28133@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).