Re: [PATCH 2/3] ath5k: use SWBA to detect IBSS HW merges

[PATCH 1/3] ath5k: better beacon timer calculation · Bruno Randolf <hidden> · 2008-01-19
[PATCH 2/3] ath5k: use SWBA to detect IBSS HW merges · Bruno Randolf <hidden> · 2008-01-19
Re: [PATCH 2/3] ath5k: use SWBA to detect IBSS HW merges · "Nick Kossifidis" <mickflemm@gmail.com> · 2008-01-22
Re: [PATCH 2/3] ath5k: use SWBA to detect IBSS HW merges · Johannes Berg <johannes@sipsolutions.net> · 2008-01-24
Re: [PATCH 2/3] ath5k: use SWBA to detect IBSS HW merges · bruno randolf <hidden> · 2008-01-25
[PATCH 3/3] ath5k: configure backoff for IBSS beacon queue · Bruno Randolf <hidden> · 2008-01-19
Re: [PATCH 3/3] ath5k: configure backoff for IBSS beacon queue · "Nick Kossifidis" <mickflemm@gmail.com> · 2008-01-19

From: Johannes Berg <johannes@sipsolutions.net>
Date: 2008-01-24 14:48:16

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".

johannes

Attachments

signature.asc [application/pgp-signature] 828 bytes

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help