From: "John W. Linville" <linville@tuxdriver.com>
To: Rick Farina <sidhayn@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Question on regulatory settings.
Date: Thu, 22 May 2014 15:22:49 -0400 [thread overview]
Message-ID: <20140522192249.GF12779@tuxdriver.com> (raw)
In-Reply-To: <537E4C81.3060001@gmail.com>
On Thu, May 22, 2014 at 03:14:09PM -0400, Rick Farina wrote:
>
>
> On 05/22/2014 02:30 PM, John W. Linville wrote:
> > On Thu, May 22, 2014 at 10:41:55AM -0700, Ben Greear wrote:
> >> On 05/22/2014 09:50 AM, Ben Greear wrote:
> >>> Hello!
> >>>
> >>> I'm having issues where when we add several ath10k NICs to a system,
> >>> the regulatory domain goes quite restricted.. There is an ath9k NIC
> >>> with eeprom over-ride hack, and user-space sets regdomain to 'US'.
> >>>
> >>> Later, when registering ath10k, at least one of those NICs registeres
> >>> as 'TW'. The ending domain looks like this:
> >>>
> >>> [root@lf1011-13060017 ~]# iw reg get
> >>> country 98: DFS-UNSET
> >>> (2402 - 2472 @ 40), (N/A, 30)
> >>> (5270 - 5330 @ 40), (N/A, 17), DFS
> >>> (5735 - 5835 @ 80), (N/A, 30)
> >>>
> >>>
> >>> I tried adding a hack to ath10k to zero out the ar->ath_common.regulatory.current_rd,
> >>> but in fact it seems to be reported as zero to begin with.
> >>>
> >>> I am obviously missing something. Either my hacks to ath10k are not
> >>> sufficient, or possibly the system is getting regulatory info from
> >>> somewhere else?
> >>>
> >>> Any ideas where else it might be getting the idea it should be in TW
> >>> domain? Can it get this from beacons from other systems?
> >
> > FWIW, yes it can get this information from beacons.
> >
> >> Ahh, sneaky nasty code....it was being set based on the timezone
> >> of all things!
> >
> > You're welcome... ;-)
>
> To be fair, when I travel I rarely set my timezone at all, and when I do
> I normally make sure the offset is right and not much else. It's easily
> possible to have timezone set for a country you aren't in just because
> the offset matches.
>
> I'm not saying I have a better idea, but I am saying that timezone is
> very unreliable to determine position.
Yes, but no less reliable than nothing at all. And if you _do_
set it properly, so much the better.
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:[~2014-05-22 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 16:50 Question on regulatory settings Ben Greear
2014-05-22 17:41 ` Ben Greear
2014-05-22 18:30 ` John W. Linville
2014-05-22 19:14 ` Rick Farina
2014-05-22 19:22 ` John W. Linville [this message]
2014-05-22 19:46 ` Ben Greear
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=20140522192249.GF12779@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sidhayn@gmail.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).