From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: voncken <cedric.voncken@acksys.fr>, linux-wireless@vger.kernel.org
Subject: Re: Atheros ETSI DFS pattern
Date: Wed, 30 Nov 2016 11:54:11 +0100 [thread overview]
Message-ID: <2fe8be5d-9f34-7a2f-d825-ca39e5facaae@neratec.com> (raw)
In-Reply-To: <012101d24af3$40bb97f0$c232c7d0$@acksys.fr>
On 11/30/2016 11:19 AM, voncken wrote:
> In the file drivers/net/wireless/ath/dfs_pattern_detector.c we can found the
> ETSI pattern definition.
>
> In this definition we can found 7 patterns (0 to 6).
>
> The ETSI standard EN 301893 Annex D only specifies 6 patterns. Only the
> pattern 1 to 6 defined in the ath dfs pattern match with the ETSI standard.
>
> Why the pattern 0 is defined?
>
> Is it possible to remove this pattern and keep compliant with the ETSI
> standard?
>
> Thanks for your help.
>
> Cedric.
>
Hi,
pattern 0 is the 'reference DFS test signal', the 700Hz pattern with 18 pulses
each 1us wide.
At implementation time, EN301893 v1.5 was the current revision and the reference
pattern is defined in Table D.3. I double checked that v1.8.1 has this one still
defined, so it remains required.
Given that most basic DFS features in certification labs are tested with this
pattern, I don't expect it to be obsoleted any time.
Out of curiosity: why would you like it removed? From the false-detection
probability, pattern 0 is uncritical (the tricky one is pattern 1).
Cheers,
Zefir
prev parent reply other threads:[~2016-11-30 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 10:19 Atheros ETSI DFS pattern voncken
2016-11-30 10:54 ` Zefir Kurtisi [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=2fe8be5d-9f34-7a2f-d825-ca39e5facaae@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=cedric.voncken@acksys.fr \
--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