From: Mattias Nissler <mattias.nissler@gmx.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Wu <flamingice@sourmilk.net>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: include MAC timestamp in radiotap header
Date: Sat, 24 Nov 2007 10:27:41 +0100 [thread overview]
Message-ID: <1195896461.8231.3.camel@localhost> (raw)
In-Reply-To: <1195893283.4149.188.camel@johannes.berg>
On Sat, 2007-11-24 at 09:34 +0100, Johannes Berg wrote:
> On Sat, 2007-11-24 at 00:21 -0500, Michael Wu wrote:
> > On Friday 23 November 2007 05:45:54 Johannes Berg wrote:
> > > This makes mac80211 include the low-level MAC timestamp
> > > in the radiotap header.
> > >
> > No thanks. Not every driver supports reporting the timestamp and supporting
> > timestamp/no timestamp in the default radiotap rx code makes it not so simple
> > anymore.
>
> Uh, so how am I supposed to get the timestamp? Copy all the code into
> b43 and make it generate the exact same radiotap header? That's pretty
> crappy too.
On rt2x00, we've just added a facility that dumps information about all
frames received and transmitted at a very low level. We dump general
information about the frame, the tx/rx descriptors and the packet. Maybe
something similar would also be useful for b43?
Mattias
next prev parent reply other threads:[~2007-11-24 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 10:45 [PATCH] mac80211: include MAC timestamp in radiotap header Johannes Berg
2007-11-24 5:21 ` Michael Wu
2007-11-24 8:34 ` Johannes Berg
2007-11-24 9:27 ` Mattias Nissler [this message]
2007-11-24 9:36 ` bruno randolf
2007-11-24 13:38 ` Mattias Nissler
2007-11-25 6:21 ` Kalle Valo
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=1195896461.8231.3.camel@localhost \
--to=mattias.nissler@gmx.de \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).