From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ath9k-devel@lists.ath9k.org, rodrigue@qca.qualcomm.com,
nbd@openwrt.org
Subject: Re: [PATCH 2/2] ath9k: integrate initial DFS module
Date: Tue, 15 Nov 2011 16:52:28 +0100 [thread overview]
Message-ID: <4EC28ABC.70307@neratec.com> (raw)
In-Reply-To: <CAD2nsn1a7rgvGGNYGjVsCdfGXVVzOYK-dM6ojV1+P5dsL6yYvA@mail.gmail.com>
On 11/15/2011 04:24 PM, Mohammed Shafi wrote:
> Hi Zefir,
>
> just few doubt, sorry for the late reply
>
> On Tue, Nov 8, 2011 at 10:04 PM, Zefir Kurtisi
> <zefir.kurtisi@neratec.com> wrote:
>> This patch integrates the DFS module into ath9k, including
>> * build the module into ath9k_hw
>> * set up DFS debugfs
>> @@ -1855,11 +1858,6 @@ int ath_rx_tasklet(struct ath_softc *sc, int flush, bool hp)
>> if (sc->sc_flags & SC_OP_RXFLUSH)
>> goto requeue_drop_frag;
>>
>> - retval = ath9k_rx_skb_preprocess(common, hw, hdr, &rs,
>> - rxs, &decrypt_error);
>> - if (retval)
>> - goto requeue_drop_frag;
>> -
>> rxs->mactime = (tsf & ~0xffffffffULL) | rs.rs_tstamp;
>> if (rs.rs_tstamp > tsf_lower &&
>> unlikely(rs.rs_tstamp - tsf_lower > 0x10000000))
>> @@ -1869,6 +1867,17 @@ int ath_rx_tasklet(struct ath_softc *sc, int flush, bool hp)
>> unlikely(tsf_lower - rs.rs_tstamp > 0x10000000))
>> rxs->mactime += 0x100000000ULL;
>>
>> + if ((rs.rs_status & ATH9K_RXERR_PHY) &&
>> + (rs.rs_phyerr == ATH9K_PHYERR_RADAR)) {
>> + /* DFS: check for radar pulse */
>> + ath9k_dfs_process_phyerr(sc, hdr, &rs, rxs->mactime);
>> + }
>> +
>> + retval = ath9k_rx_skb_preprocess(common, hw, hdr, &rs,
>> + rxs, &decrypt_error);
>> + if (retval)
>> + goto requeue_drop_frag;
>
> does the above fixes any bug related to mactime displayed in sniffer
>
>
Hi Mohammed,
no, like all other modifications within this patch the above does not fix anything (at least not intentionally) ;)
What it does is moving the calculation of rxs->mactime before ath9k_rx_skb_preprocess(), since the mactime is needed to stamp the radar event. So, the five lines marked as removals are actually moved further down which shouldn't have any side effects.
Thanks
Zefir
next prev parent reply other threads:[~2011-11-15 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 16:34 [PATCH 0/2] ath9k: DFS radar detection Zefir Kurtisi
2011-11-08 16:34 ` [PATCH 1/2] ath9k: add DFS radar pulse processing Zefir Kurtisi
2011-11-08 16:34 ` [PATCH 2/2] ath9k: integrate initial DFS module Zefir Kurtisi
2011-11-15 15:24 ` Mohammed Shafi
2011-11-15 15:52 ` Zefir Kurtisi [this message]
2011-11-15 16:27 ` Luis R. Rodriguez
2011-11-16 4:16 ` Mohammed Shafi
2011-11-15 16:45 ` Luis R. Rodriguez
2011-11-16 14:50 ` Zefir Kurtisi
2011-11-15 14:37 ` [PATCH 0/2] ath9k: DFS radar detection John W. Linville
2011-11-15 16:46 ` Luis R. Rodriguez
2011-11-23 16:11 ` Zefir Kurtisi
2011-11-24 8:40 ` Adrian Chadd
2011-11-24 9:04 ` 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=4EC28ABC.70307@neratec.com \
--to=zefir.kurtisi@neratec.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 \
--cc=shafi.wireless@gmail.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).