From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Jonathan Bither <jonbither@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: New DFS pattern detector
Date: Tue, 24 Apr 2012 10:50:40 +0200 [thread overview]
Message-ID: <4F966960.20700@neratec.com> (raw)
In-Reply-To: <4F965B47.1080000@gmail.com>
Hi Jonathan,
an earlier proposal for the DFS pattern detector posted at [1] was in
fact located in the common ath layer and meant to be used by all DFS
capable Atheros devices.
For the sake of simplicity and based on assumptions that ath9k will be
the first driver to use it, the detector was finally moved into ath9k.
So far, it is independent of the underlying HW and if there was a
consensus that it could be used by ath5k or other drivers, I'll take
care to move it back to the ath layer.
FYI, the initial plans were even to have the detector fully abstracted
from the underlying driver and provide it as part of mac80211. With no
further feedback from other chip-manufacturers the generic approach was
dropped and became Atheros specific.
Feel free to ask for further details, though I'm out of office right now
and will respond delayed.
HTH, Zefir
[1] http://article.gmane.org/gmane.linux.kernel.wireless.general/84402
On 24.04.2012 09:50, Jonathan Bither wrote:
> Hey List,
> With the new DFS pattern detector that was added for ath9k, I was curious if this would be beneficial for the ath5k and possibly other drivers as well. Was there any interest in perhaps making this a common API?
>
> Thanks,
> Jonathan Bither
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-24 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 7:50 New DFS pattern detector Jonathan Bither
2012-04-24 8:50 ` Zefir Kurtisi [this message]
2012-04-24 9:26 ` Jonathan Bither
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=4F966960.20700@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=jonbither@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).