From: Simon Wunderlich <sw@simonwunderlich.de>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Jean-Pierre Tosoni <jp.tosoni@acksys.fr>,
Cedric VONCKEN <cedric.voncken@acksys.fr>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath9k/ath10k DFS testing / certification
Date: Tue, 24 Jan 2017 16:10:55 +0100 [thread overview]
Message-ID: <9646101.djguVEVbIO@prime> (raw)
In-Reply-To: <CAJ-Vmo=WYvi5ZL_VDr623cFkp0oocDYkui346_mtb91cthsXMA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2004 bytes --]
Hi Adrian,
On Tuesday, January 24, 2017 7:05:58 AM CET Adrian Chadd wrote:
> hi!
>
> On 24 January 2017 at 03:16, Simon Wunderlich <sw@simonwunderlich.de> wrote:
> > Hi Adrian,
> >
> > I've been doing DFS pre-tests back in December 2016. We did AP tests for a
> > 9880 based AP for ETSI and FCC region. We had two small patches for making
> > the>
> > tests less painful (in hostapd and mac80211):
> > * disable CSA on incoming radar, that is keep on staying on the operating
> >
> > channels. That makes continouos testing of radar signals much easier
> > (usually you test like 10 radars in a row), since we don't had to reboot
> > the device all the time.
> >
> > * shorten CAC to 3 seconds, because waiting 60 seconds is also taking
> > some
> >
> > time
>
> Do you have those patches available somewhere?
>
not sure if I can release them, so no. :)
But both were rather trivial, the first one is a change in hostapd, the latter
in mac80211.
> > All FCC tests pass, at least from the radar detection point. ETSI had a
> > problem with one of the patterns. We used iperf UDP tests to generate
> > load,
> > but will probably switch to another tool in the next round (or tune it),
> > since it seems to send packets too bursty, which could be the cause for
> > the failed ETSI test.
>
> Ok. What are you using to generate radar patterns for testing?
>
We used 300k+ EUR Rohde&Schwarz equipment of the certification lab. :)
I don't have a pattern generation available at my home, but I remember
discussions that it's possible to get something useful and cheap using SDRs
(with cheap I mean in the <5k$ range). I believe Zefir had tried this route
...
> > Thanks for the info on the scan bug, we discovered that too, but thought
> > we
> > could fix it in mac80211 (but never really followed up). Please keep me in
> > the loop when this is fixed. :)
> :
> :) I'll punt this to QCA if/when the right time arises and see if
>
> they'll fix ath10k firmware.
Excellent!
Simon
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-01-24 15:11 UTC|newest]
Thread overview: 13+ 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 [this message]
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
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=9646101.djguVEVbIO@prime \
--to=sw@simonwunderlich.de \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=cedric.voncken@acksys.fr \
--cc=jp.tosoni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox