From: "Jean-Pierre Tosoni" <jp.tosoni@acksys.fr>
To: 'Adrian Chadd' <adrian@freebsd.org>
Cc: ath10k@lists.infradead.org, Cedric VONCKEN <cedric.voncken@acksys.fr>
Subject: RE: ath9k/ath10k DFS testing / certification
Date: Tue, 24 Jan 2017 15:53:53 +0100 [thread overview]
Message-ID: <00d601d27651$ae648ee0$0b2daca0$@acksys.fr> (raw)
In-Reply-To: <CAJ-VmokegH87gnsJ8Rp57OPnNUo_C=_7V0b9AD4-NcaYtLxJHw@mail.gmail.com>
> -----Message d'origine-----
> De : ath10k [mailto:ath10k-bounces@lists.infradead.org] De la part de
> Adrian Chadd
> Envoyé : lundi 16 janvier 2017 18:43
> À : Jean-Pierre Tosoni
> Cc : Cedric VONCKEN; ath10k@lists.infradead.org
> Objet : Re: ath9k/ath10k DFS testing / certification
>
> hiya,
>
> Yeah - i was a part of that discussion. :) That's why I was pointing out
> that likely I'm going to bug QCA to get this fixed when the time is right.
>
> So, time is right :)
>
> Did you do DFS certification for AP/master devices, or just client?
We did it for both AP and client modes.
We had the same problem with IPERF than Simon, and we solved that by defining a huge packet size and IPERF would send it every now and then just enough to meet the throughput required.
Jean-Pierre
>
>
>
> -adrian
>
>
> On 16 January 2017 at 02:06, Jean-Pierre Tosoni <jp.tosoni@acksys.fr>
> wrote:
> > Hi Adrian,
> >
> >> -----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
> >
> > For the record, a summary of our discussion last month.
> >
> > We went to an independent lab with wpa_supplicant+ath10k+Compex
> > WLE900VX
> > (QCA988x) for ETSI certification.
> > We passed for the most part, but we were rejected because the
> > supplicant sends probes on DFS channels.
> > We applied the following patch that did solve the issue at hand, but
> > made another issue appear:
> > => the QCA firmware believes any rogue system that sends out beacons
> > on a DFS channel, so that the firmware active-scans that channel,
> > without checking for radar signatures on its own.
> >
> > So the patch solves only part of the issue.
> >
> > Patch:
> >
> > Process NO_IR and RADAR flags in the same manner. Do this only when
> > channels are prepared for a scan, in order to avoid side effects.
> > ---
> > --- a/drivers/net/wireless/ath/ath10k/wmi.c
> > +++ b/drivers/net/wireless/ath/ath10k/wmi.c
> > @@ -5679,6 +5679,9 @@ ath10k_wmi_op_gen_scan_chan_list(struct
> > ci = &cmd->chan_info[i];
> >
> > ath10k_wmi_put_wmi_channel(ci, ch);
> > +
> > + if (ch->chan_radar)
> > + ci->flags |=
> > + __cpu_to_le32(WMI_CHAN_FLAG_PASSIVE);
> > }
> >
> > return skb;
> > --
> > 1.7.2.5
> >
> > Jouni Malinen suggested an equivalent, more general, form of the
> > above, which seems to work as well:
> >
> > diff --git a/drivers/net/wireless/ath/ath10k/mac.c
> > b/drivers/net/wireless/ath/ath10k/mac.c
> > index aa545a1..758dbbd 100644
> > --- a/drivers/net/wireless/ath/ath10k/mac.c
> > +++ b/drivers/net/wireless/ath/ath10k/mac.c
> > @@ -2973,7 +2973,8 @@ static int ath10k_update_channel_list(struct
> > ath10k
> > *ar)
> > ch->chan_radar =
> > !!(channel->flags &
> > IEEE80211_CHAN_RADAR);
> >
> > - passive = channel->flags & IEEE80211_CHAN_NO_IR;
> > + passive = channel->flags & (IEEE80211_CHAN_NO_IR
> |
> > +
> > + IEEE80211_CHAN_RADAR);
> > ch->passive = passive;
> >
> > ch->freq = channel->center_freq;
> >
> > --
> > (by Jouni Malinen)
> >
> >>
> >> _______________________________________________
> >> ath10k mailing list
> >> ath10k@lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/ath10k
> >
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-01-24 16:12 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 [this message]
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
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='00d601d27651$ae648ee0$0b2daca0$@acksys.fr' \
--to=jp.tosoni@acksys.fr \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=cedric.voncken@acksys.fr \
/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.