From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@cozybit.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: support RX_FLAG_MACTIME_END
Date: Mon, 12 Nov 2012 21:42:39 +0100 [thread overview]
Message-ID: <1352752959.12957.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1352745513-1265-1-git-send-email-thomas@cozybit.com> (sfid-20121112_193850_215866_5571BA38)
On Mon, 2012-11-12 at 10:38 -0800, Thomas Pedersen wrote:
> + if (ieee80211_have_rx_timestamp(rx_status))
> + /* time when timestamp field was received */
> + t_r = ieee80211_calculate_rx_timestamp(local, rx_status,
> + 24 + 12 +
> + elems->total_len + 4,
> + 24);
This doesn't seem quite right, the FCS isn't accounted for correctly?
I think it might be wortwhile to pass the SKB to the function instead of
rx_status though, then it could get skb->len and check whether or not
FCS was before the timestamp (which, btw, you should mention in the
documentation for the new flag!)
And then I suspect the check for IEEE80211_HW_RX_INCLUDES_FCS is also
incorrect -- even if the driver didn't report the FCS maybe the
timestamping semantic was such that it was after the FCS?
This seems to need a little fixing up, but other than that looks good.
johannes
next prev parent reply other threads:[~2012-11-12 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 18:38 [PATCH] mac80211: support RX_FLAG_MACTIME_END Thomas Pedersen
2012-11-12 20:11 ` Javier Cardona
2012-11-12 21:56 ` Thomas Pedersen
2012-11-13 0:48 ` Adrian Chadd
2012-11-13 7:56 ` Johannes Berg
2012-11-12 20:42 ` Johannes Berg [this message]
2012-11-12 21:52 ` Thomas Pedersen
2012-11-13 8:04 ` Johannes Berg
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=1352752959.12957.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@cozybit.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).