From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Adrien Decostre <ad.decostre@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Questions regarding ath9k and new EN 300 328 regulation
Date: Mon, 27 Oct 2014 11:43:32 +0100 [thread overview]
Message-ID: <544E21D4.9020401@neratec.com> (raw)
In-Reply-To: <CAOtFK_Ue0xjEaYY3qm0n2Tj=Hnu1dbphupmdZmiouVuGLnktoA@mail.gmail.com>
On 10/24/2014 05:23 PM, Adrien Decostre wrote:
>
> I am looking for information about the compliancy of the ath9k driver
> to the EN 300 328 ETSI regulation.
>
> Would someone know if ath9k has already been tested for this regulation?
>
> Is it needed to enable any specific flag in ath9k to guarantee
> compliancy to the adaptivity tests described in EN 300 328?
>
>
The pattern detector currently used in ath was initially developed for ath9k when
EN 300.328 v1.5.1 was released. It passed the ETSI certification in a German lab
and the source code (besides moving it up in the tree to be also available for
10k) was basically not touched ever since.
I did not track all the DFS requirement changes up to the latest v1.9.1 draft, but
afaik the sole difference relevant for the detector is the reduction of the
shortest pulses width in the test pattern specification from 0.7 to 0.5us. With
that, the chance of the current implementation to pass a v1.8 certification
depends on ath9k's ability to detect the shorter pulses. I did some initial
measurements years ago to get a rough picture, which showed that the ath9k is
losing like 30% of the 0.5us pulses (as compared to .7us).
With the patches you referred, YMMV - you would need to perform thorough
statistical analyses to get an estimate on whether it would pass.
As for the adaptivity tests, they are not part of DFS (see note in 4.9.1) and
maybe would best fit within the ACS module
(http://wireless.kernel.org/en/users/Documentation/acs). The current DFS support
available in ath9k is limited to bare radar detection, which is enabled through
CONFIG_CFG80211_CERTIFICATION_ONUS.
Cheers,
Zefir
next prev parent reply other threads:[~2014-10-27 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 15:23 Questions regarding ath9k and new EN 300 328 regulation Adrien Decostre
2014-10-27 10:43 ` Zefir Kurtisi [this message]
2014-10-27 14:18 ` Adrien Decostre
2014-10-27 14:50 ` Zefir Kurtisi
2014-10-27 18:23 ` Adrien Decostre
2014-10-30 12:55 ` Zefir Kurtisi
2014-11-05 9:07 ` Adrien Decostre
2014-11-05 8:33 ` voncken
2014-11-05 9:35 ` Adrien Decostre
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=544E21D4.9020401@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=ad.decostre@gmail.com \
--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 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).