From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>,
"John W. Linville" <linville@tuxdriver.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bruno Randolf <bruno@thinktube.com>
Subject: Re: pull request: wireless-2.6 2008-08-26
Date: Wed, 27 Aug 2008 16:31:03 -0700 [thread overview]
Message-ID: <20080827233103.GE5927@tesla> (raw)
In-Reply-To: <1ba2fa240808271611v382631ecn2a24e2816562d434@mail.gmail.com>
On Wed, Aug 27, 2008 at 04:11:15PM -0700, Tomas Winkler wrote:
> if (beacon_timestamp > rx_timestamp)
> merge
>
> The patch from Assaf just disable reporting RX timestamp to mac and
> thus disabling merging which gives incorrect spec behavior but smooth
> traffic.
We *should follow the spec*.
> Actually we've checked few cards including broadcom and various
> windows NICs
What are windows NICs?
> and non of them implements this correctly so this WA is
> probably the solution.
Disagreed! If there is hardware which is not capable of handling this
we should simply have a HW flag which specifies this to handle this as a
work around (WA). Just because some cards are not capable it doesn't
mean it should impose that on the rest.
> Other solution would be to mark leader with highest TSF and not
> reconnecting to the same station again and again.
>
> Last solution would be to remove this merging all together but then
> I'm not sure if Bruno added this code just implement the spec or
> really tested it with any hardware. I'm not sure if any vendor
> implements PS in IBSS so this merging is probably not important
> anyway.
Absolutely not! IBSS merge is per spec, otherwise you don't really have
a real IBSS.
Luis
next prev parent reply other threads:[~2008-08-27 23:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 1:30 pull request: wireless-2.6 2008-08-26 John W. Linville
2008-08-27 7:38 ` Tomas Winkler
2008-08-27 8:40 ` David Miller
2008-08-27 9:13 ` Tomas Winkler
2008-08-27 11:10 ` Marcel Holtmann
2008-08-27 10:05 ` Tomas Winkler
2008-08-27 10:10 ` Johannes Berg
2008-08-27 10:33 ` David Miller
2008-08-27 11:34 ` Tomas Winkler
2008-08-27 11:45 ` David Miller
2008-08-27 12:26 ` Tomas Winkler
2008-08-27 13:10 ` Michael Buesch
2008-08-27 14:55 ` Tomas Winkler
2008-08-27 15:22 ` Michael Buesch
2008-08-27 15:45 ` Tomas Winkler
2008-08-27 10:32 ` David Miller
2008-08-27 11:42 ` Tomas Winkler
2008-08-27 13:57 ` Arjan van de Ven
2008-08-27 11:39 ` David Miller
2008-08-27 19:26 ` Tomas Winkler
2008-08-27 20:25 ` Michael Buesch
2008-08-27 23:11 ` Tomas Winkler
2008-08-27 23:31 ` Luis R. Rodriguez [this message]
2008-08-28 0:19 ` Tomas Winkler
2008-08-28 1:30 ` Luis R. Rodriguez
2008-08-28 7:59 ` Tomas Winkler
2008-08-28 10:35 ` Bruno Randolf
2008-08-28 10:52 ` Tomas Winkler
2008-08-28 11:13 ` Bruno Randolf
2008-08-28 8:31 ` Michael Buesch
2008-08-28 9:29 ` Tomas Winkler
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=20080827233103.GE5927@tesla \
--to=lrodriguez@atheros.com \
--cc=bruno@thinktube.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=tomasw@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).