From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Tim Harvey <tharvey@gateworks.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
linux-wireless@vger.kernel.org
Subject: Re: FCC DFS support
Date: Mon, 19 Oct 2015 11:10:12 +0200 [thread overview]
Message-ID: <5624B374.5080209@neratec.com> (raw)
In-Reply-To: <CAJ+vNU2q1kLBs8wXRN++62bn24ohthFr=0htDMBh7qxsqmeodg@mail.gmail.com>
On 10/16/2015 06:53 PM, Tim Harvey wrote:
> Greetings,
>
> Is FCC DFS support (from the updated rules released in Aug 2014) fully
> supported in ath10k by the driver/firmware/cards?
>
> The linux-wireless DFS page [1] has some great info but doesn't really
> list what is currently in place and working and doesn't mention ath10k
> specifically and I didn't see anything on the ath10k page either [2].
>
> Thanks for any info!
>
> Regards,
>
> Tim
>
> [1] - https://wireless.wiki.kernel.org/en/developers/dfs
> [2] - https://wireless.wiki.kernel.org/en/users/drivers/ath10k
> --
>
Hi Tim,
you're right, unfortunately the DFS documentation in [1] is quite outdated -
basically in its initial state from 2011 when ath10k was unknown. It took around
four years to get the work done, and since numerous parties contributed at
different times and different modules (driver, mac/cfg, hostapd), the
documentation has not always been updated accordingly.
But the more important fact is: yes, ath10 and ath9k today fully support FCC.
We certified one of our ath9k based products for FCC and ETSI some months ago, and
I got confirmations that ath10k also passed certification testing for FCC.
It is relevant to note that both drivers use the same radar pattern detector (and
all upper layers anyway), so that if ath9k passed, ath10k most probably will also
do (and vice versa).
Hth,
Zefir
next prev parent reply other threads:[~2015-10-19 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 16:53 FCC DFS support Tim Harvey
2015-10-19 9:10 ` Zefir Kurtisi [this message]
2015-10-19 13:31 ` Tim Harvey
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=5624B374.5080209@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tharvey@gateworks.com \
/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).