From: bruno randolf <bruno@thinktube.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: ath5k-devel@lists.ath5k.org, mcgrof@gmail.com,
jirislaby@gmail.com, mickflemm@gmail.com,
linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH 2/3] ath5k: use SWBA to detect IBSS HW merges
Date: Fri, 25 Jan 2008 15:07:17 +0900 [thread overview]
Message-ID: <200801251507.17814.bruno@thinktube.com> (raw)
In-Reply-To: <1201166295.3454.52.camel@johannes.berg>
On Thursday 24 January 2008 18:18:15 Johannes Berg wrote:
> On Sat, 2008-01-19 at 18:18 +0900, Bruno Randolf wrote:
> > time und check if a HW merge (automatic TSF update) has happened on every
> > received beacon with the same BSSID.
>
> I don't know who is smoking what (I suspect Atheros folks...), but
> calling a TSF adoption a "merge" is pretty out of line IMHO when you
> also describe some non-standard BSSID changes as "merge".
hmm, i agree, that calling that a "merge" is a bit over the top. i was using
this term as somebody mentioned it in
http://madwifi.org/wiki/DevDocs/AdhocMerge, but i agree that "TSF update" is
more to the point and clearer.
bruno
next prev parent reply other threads:[~2008-01-25 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 9:17 [PATCH 1/3] ath5k: better beacon timer calculation Bruno Randolf
2008-01-19 9:18 ` [PATCH 2/3] ath5k: use SWBA to detect IBSS HW merges Bruno Randolf
2008-01-22 1:32 ` Nick Kossifidis
2008-01-24 9:18 ` Johannes Berg
2008-01-25 6:07 ` bruno randolf [this message]
2008-01-19 9:18 ` [PATCH 3/3] ath5k: configure backoff for IBSS beacon queue Bruno Randolf
2008-01-19 19:33 ` Nick Kossifidis
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=200801251507.17814.bruno@thinktube.com \
--to=bruno@thinktube.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@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).