From: "Jean-Pierre Tosoni" <jp.tosoni@acksys.fr>
To: "'Adrian Chadd'" <adrian@freebsd.org>,
"'ath9k-devel'" <ath9k-devel@venema.h4ckr.net>,
<linux-wireless@vger.kernel.org>
Subject: RE: ath9k/ath10k DFS testing / certification
Date: Wed, 18 Jan 2017 11:26:10 +0100 [thread overview]
Message-ID: <009701d27175$499fafc0$dcdf0f40$@acksys.fr> (raw)
In-Reply-To: <CAJ-Vmo=_apPFE1LQmXj6pn9g1c0bvzAS-gk86Hi7-CX+KuZtrw@mail.gmail.com>
Hi Adrian,
Also, about ath9k:
I don't know if it's relevant to you, but we had the same problem of
NO_IR/RADAR mismatch in ath9k.
We fixed this in mac80211 layer at that time. Here is the patch. We didn't
send it upstream since
We have no experience with other chipsets, and we didn't know whether it
would be generic enough.
--- a/net/mac80211/scan.c
+++ b/net/mac80211/scan.c
@@ -598,7 +598,7 @@ static int __ieee80211_start_scan(struct
ieee80211_hw_config(local, 0);
if ((req->channels[0]->flags &
- IEEE80211_CHAN_NO_IR) ||
+ (IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_RADAR)) ||
!req->n_ssids) {
next_delay = IEEE80211_PASSIVE_CHANNEL_TIME;
} else {
@@ -646,7 +646,7 @@ ieee80211_scan_get_channel_time(struct i
* TODO: channel switching also consumes quite some time,
* add that delay as well to get a better estimation
*/
- if (chan->flags & IEEE80211_CHAN_NO_IR)
+ if (chan->flags & (IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_RADAR))
return IEEE80211_PASSIVE_CHANNEL_TIME;
return local->scan_req->probe_delay_ticks +
local->scan_req->max_channel_time_ticks;
}
@@ -810,7 +810,7 @@ static void ieee80211_scan_state_set_cha
*
* In any case, it is not necessary for a passive scan.
*/
- if (chan->flags & IEEE80211_CHAN_NO_IR || !scan_req->n_ssids) {
+ if (chan->flags & (IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_RADAR) ||
!scan_req->n_ssids) {
*next_delay = IEEE80211_PASSIVE_CHANNEL_TIME;
local->next_scan_state = SCAN_DECISION;
return;
--
Diff -u
> -----Message d'origine-----
> De : ath10k [mailto:ath10k-bounces@lists.infradead.org] De la part de
> Adrian Chadd
> Envoyé : dimanche 15 janvier 2017 22:17
> À : ath9k-devel; ath10k@lists.infradead.org
> Objet : ath9k/ath10k DFS testing / certification
>
> hiya,
>
> I'm working on a set of things that will involve DFS certification for
> ath9k/ath10k. Initially it'll be for FCC but I'll branch out to the other
> regions shortly afterwards.
>
> I'd love to hear from anyone else who has done this and what their
> challenges were, including whether they have any local patches / tools
> that haven't yet been upstreamed.
>
> Thanks!
>
>
> -adrian
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2017-01-18 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 21:17 ath9k/ath10k DFS testing / certification Adrian Chadd
2017-01-16 10:06 ` Jean-Pierre Tosoni
2017-01-16 17:42 ` Adrian Chadd
2017-01-24 11:16 ` Simon Wunderlich
2017-01-24 15:05 ` Adrian Chadd
2017-01-24 15:10 ` Simon Wunderlich
2017-01-24 14:53 ` Jean-Pierre Tosoni
2017-01-24 16:26 ` Adrian Chadd
2017-01-24 16:52 ` Jean-Pierre Tosoni
2017-01-24 17:42 ` Adrian Chadd
2017-01-24 18:00 ` Jean-Pierre Tosoni
2017-01-24 18:14 ` Adrian Chadd
2017-01-26 8:33 ` Jean-Pierre Tosoni
2017-01-18 10:26 ` Jean-Pierre Tosoni [this message]
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='009701d27175$499fafc0$dcdf0f40$@acksys.fr' \
--to=jp.tosoni@acksys.fr \
--cc=adrian@freebsd.org \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.