From: Sujith <m.sujith@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Jouni.Malinen@Atheros.com
Subject: Re: [PATCH] mac80211: Update IBSS beacon timestamp properly
Date: Sun, 8 Mar 2009 18:34:30 +0530 [thread overview]
Message-ID: <18867.49758.741918.767411@gargle.gargle.HOWL> (raw)
In-Reply-To: <1236516770.4205.17.camel@johannes.local>
Johannes Berg wrote:
> On Tue, 2009-03-03 at 10:15 +0530, Sujith wrote:
> > In IBSS mode, the beacon timestamp has to be filled with the
> > BSS's timestamp when joining, and set to zero when creating
> > a new BSS.
>
> I don't quite understand why, do we read it out again at any point?
>
Drivers do, when they do a beacon_get(). And the timestamp in the
beacon is used to calculate TBTT.
Sujith
next prev parent reply other threads:[~2009-03-08 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 4:45 [PATCH] mac80211: Update IBSS beacon timestamp properly Sujith
2009-03-08 12:52 ` Johannes Berg
2009-03-08 13:04 ` Sujith [this message]
2009-03-08 13:08 ` 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=18867.49758.741918.767411@gargle.gargle.HOWL \
--to=m.sujith@gmail.com \
--cc=Jouni.Malinen@Atheros.com \
--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