From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC v2 2/2] ath9k: integrate initial DFS module
Date: Thu, 03 Nov 2011 19:15:17 +0100 [thread overview]
Message-ID: <4EB2DA35.3040708@openwrt.org> (raw)
In-Reply-To: <4EB2D6DE.3050207@neratec.com>
On 2011-11-03 7:01 PM, Zefir Kurtisi wrote:
> Hi Felix,
>
> while I was waiting for your feedback on my related patch, I assumed
> you're okay with having those rx filter flags preserved in ath_calcrxfilter.
I did send some feedback on the rx filter preserve patch. I think it's
unnecessary and should be left out. If calcrxfilter properly returns the
ATH9K_RX_FILTER_PHYRADAR flag where necessary, then no preserve logic is
needed.
> I'll check your proposal for v3.
>
> BTW, as the comment says, it is TODO enable radar detection only for
> DFS channels. Beside the lack of the management module to provide the
> relevant information, it comes handy to test pulse detection on non-DFS
> channels without the need to modify hostapd ;)
Yeah, but it would be nice to split hardware capability from runtime
state early on.
- Felix
WARNING: multiple messages have this Message-ID (diff)
From: Felix Fietkau <nbd@openwrt.org>
To: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
rodrigue@qca.qualcomm.com
Subject: Re: [RFC v2 2/2] ath9k: integrate initial DFS module
Date: Thu, 03 Nov 2011 19:15:17 +0100 [thread overview]
Message-ID: <4EB2DA35.3040708@openwrt.org> (raw)
In-Reply-To: <4EB2D6DE.3050207@neratec.com>
On 2011-11-03 7:01 PM, Zefir Kurtisi wrote:
> Hi Felix,
>
> while I was waiting for your feedback on my related patch, I assumed
> you're okay with having those rx filter flags preserved in ath_calcrxfilter.
I did send some feedback on the rx filter preserve patch. I think it's
unnecessary and should be left out. If calcrxfilter properly returns the
ATH9K_RX_FILTER_PHYRADAR flag where necessary, then no preserve logic is
needed.
> I'll check your proposal for v3.
>
> BTW, as the comment says, it is TODO enable radar detection only for
> DFS channels. Beside the lack of the management module to provide the
> relevant information, it comes handy to test pulse detection on non-DFS
> channels without the need to modify hostapd ;)
Yeah, but it would be nice to split hardware capability from runtime
state early on.
- Felix
next prev parent reply other threads:[~2011-11-03 18:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 13:55 [ath9k-devel] [RFC v2 0/2] ath9k: DFS radar detection Zefir Kurtisi
2011-11-03 13:55 ` Zefir Kurtisi
2011-11-03 13:55 ` [ath9k-devel] [RFC v2 1/2] ath9k: add DFS radar pulse processing Zefir Kurtisi
2011-11-03 13:55 ` Zefir Kurtisi
2011-11-03 15:54 ` [ath9k-devel] " Mohammed Shafi
2011-11-03 15:54 ` Mohammed Shafi
2011-11-03 16:25 ` [ath9k-devel] " Zefir Kurtisi
2011-11-03 16:25 ` Zefir Kurtisi
2011-11-03 15:56 ` [ath9k-devel] " Mohammed Shafi
2011-11-03 15:56 ` Mohammed Shafi
2011-11-03 16:26 ` [ath9k-devel] " Zefir Kurtisi
2011-11-03 16:26 ` Zefir Kurtisi
2011-11-03 13:55 ` [ath9k-devel] [RFC v2 2/2] ath9k: integrate initial DFS module Zefir Kurtisi
2011-11-03 13:55 ` Zefir Kurtisi
2011-11-03 15:11 ` [ath9k-devel] " Felix Fietkau
2011-11-03 15:11 ` Felix Fietkau
2011-11-03 18:01 ` [ath9k-devel] " Zefir Kurtisi
2011-11-03 18:01 ` Zefir Kurtisi
2011-11-03 18:15 ` Felix Fietkau [this message]
2011-11-03 18:15 ` Felix Fietkau
2011-11-03 15:27 ` [ath9k-devel] " Mohammed Shafi
2011-11-03 15:27 ` Mohammed Shafi
2011-11-03 16:45 ` [ath9k-devel] " Zefir Kurtisi
2011-11-03 16:45 ` Zefir Kurtisi
2011-11-03 16:57 ` [ath9k-devel] " Mohammed Shafi
2011-11-03 16:57 ` Mohammed Shafi
2011-11-03 15:51 ` [ath9k-devel] " Christian Lamparter
2011-11-03 15:51 ` Christian Lamparter
2011-11-03 17:25 ` [ath9k-devel] " Zefir Kurtisi
2011-11-03 17:25 ` Zefir Kurtisi
2011-11-03 17:30 ` [ath9k-devel] " Felix Fietkau
2011-11-03 17:30 ` Felix Fietkau
2011-11-03 17:46 ` [ath9k-devel] " Zefir Kurtisi
2011-11-03 17:46 ` Zefir Kurtisi
2011-11-04 3:00 ` [ath9k-devel] " Peter Stuge
2011-11-04 3:00 ` Peter Stuge
2011-11-04 9:47 ` Zefir Kurtisi
2011-11-04 9:47 ` 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=4EB2DA35.3040708@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.