linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: "Chadd, Adrian" <achadd@qca.qualcomm.com>
Cc: linville@tuxdriver.com, ath9k-devel@lists.ath9k.org,
	linux-wireless@vger.kernel.org, rodrigue@qca.qualcomm.com,
	achadd@qca.qualcomm.com, nbd@openwrt.org
Subject: Re: [PATCH 1/3] ath9k: add DFS pattern detector
Date: Tue, 10 Apr 2012 12:09:52 +0200	[thread overview]
Message-ID: <4F8406F0.9090900@neratec.com> (raw)
In-Reply-To: <CAJ-Vmon-kgy8kM=Q=4jBJFfMuMxprwjrj6Za_UyLWLEwYtMTEw@mail.gmail.com>

On 04/06/2012 01:35 AM, Adrian Chadd wrote:
> [top post]
> 
> I think this is a good starting point. Let's aim to get this into the
> tree and then start working on some further testing and debugging
> APIs.
> 
> Thanks so much for working on this!
> 
> 
> 
> Adrian
> 
Thanks for looking at it, Adrian.

As for the APIs, I have some debugfs based statistics used for pulse and
pattern detection evaluation that I'll post as soon as the detector
module gets accepted.

Since DFS testing is a new topic anyhow, if you have some existing APIs
used in your QCA test-lab, I'd suggest to adopt them for ath9k.
Otherwise let's pool together and develop some sane and easy-to-use test
framework to share the enormous testing and/or certification efforts
(though realistically DFS testing will never be plug-and-playable to be
performed by common developers outside full-blown testing labs :-().


Thanks, Zefir


  reply	other threads:[~2012-04-10 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 15:15 [PATCH 0/3] ath9k: DFS pattern detector Zefir Kurtisi
2012-04-03 15:15 ` [PATCH 1/3] ath9k: add " Zefir Kurtisi
2012-04-05 23:35   ` Adrian Chadd
2012-04-10 10:09     ` Zefir Kurtisi [this message]
2012-04-03 15:15 ` [PATCH 2/3] ath9k: add DFS pattern detector instance to ath_softc Zefir Kurtisi
2012-04-03 15:15 ` [PATCH 3/3] ath9k: update to DFS pattern detector interface Zefir Kurtisi

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=4F8406F0.9090900@neratec.com \
    --to=zefir.kurtisi@neratec.com \
    --cc=achadd@qca.qualcomm.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nbd@openwrt.org \
    --cc=rodrigue@qca.qualcomm.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).