From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@qca.qualcomm.com>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>
Subject: Re: [RFC] wireless: improve dfs-region intersection.
Date: Wed, 25 Jun 2014 10:34:32 -0700 [thread overview]
Message-ID: <53AB0828.8060207@candelatech.com> (raw)
In-Reply-To: <CAB=NE6WY978KkB6KL3MLDJOekgwBk4r--vjQ-+Qke6SLJn9EGg@mail.gmail.com>
On 06/25/2014 10:20 AM, Luis R. Rodriguez wrote:
> On Wed, Jun 25, 2014 at 9:48 AM, Ben Greear <greearb@candelatech.com> wrote:
>> I started trying to do some more DFS testing on a 3.14.8+ kernel,
>> and from what I can tell, the US region is configured for
>> DFS-Unset. I was assuming this should be set to DFS_FCC.
>>
>> I tried installing the latest regulatory.bin. crda is whatever
>> is standard on Fedora 19.
>>
>> Do you know if DFS is supposed to work at all in the 3.14 kernel?
>
> DFS region support was added upstream via 8b60b07805
>
> mcgrof@ergon ~/linux (git::master)$ git describe --contains 8b60b07805
> v3.3-rc1~182^2~44^2~384
>
> Now, that doesn't mean a driver will have DFS support of course. I'm
> not going to treasure hunt that for you.
The driver (ath10k) works, and if I manually force the 'US' regulatory domain
to use DFS-FCC in set_regdom in reg.c, then it shows up as DFS-FCC in 'iw reg get'
and hostapd & driver properly detects radar since airport is nearby, hostapd
chooses a different channel, and things go on working.
>> I'm certain I had this working earlier on this machine,
>> but I was on a somewhat patched linux.ath tree at the
>> time it seems....
>
> There's an issue Krishna reported about internal db now parsing the
> new db.txt format properly after the antenna gain removal but a patch
> is supposed to be on the way. You don't seem to be using that though
> so you may want to debug things a bit further.
Is the 'regulatory.bin' from today's wireless-regdb repository
correct? I did not try regenerating it..I just did a git pull...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-06-25 17:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 20:08 [RFC] wireless: improve dfs-region intersection greearb
2014-06-23 19:15 ` Luis R. Rodriguez
2014-06-23 20:37 ` Ben Greear
2014-06-23 20:54 ` Luis R. Rodriguez
2014-06-23 21:20 ` Ben Greear
2014-06-24 0:44 ` Luis R. Rodriguez
2014-06-24 2:35 ` Ben Greear
2014-06-24 2:53 ` Luis R. Rodriguez
2014-06-25 16:48 ` Ben Greear
2014-06-25 17:20 ` Luis R. Rodriguez
2014-06-25 17:34 ` Ben Greear [this message]
2014-06-25 17:37 ` Luis R. Rodriguez
2014-06-26 6:50 ` Janusz Dziedzic
2014-06-24 5:47 ` Kalle Valo
2014-06-25 16:52 ` Luis R. Rodriguez
2014-06-25 17:56 ` Kalle Valo
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=53AB0828.8060207@candelatech.com \
--to=greearb@candelatech.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=wireless-regdb@lists.infradead.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).