linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Chr <chunkeey@web.de>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	John W Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] p54: Fix for TX sequence number problem that resulted from commit 741b4fbc44
Date: Fri, 15 Aug 2008 21:26:15 +0200	[thread overview]
Message-ID: <1218828375.3197.0.camel@localhost> (raw)
In-Reply-To: <200808152034.46346.chunkeey@web.de>

On Fri, 2008-08-15 at 20:34 +0200, Chr wrote:
> Hmm, or there's something else can't count?!??
> 
> Anyway, the firmware will always assign (as in overwrite) the
> sequence number for every transmitted frame... unfortunatly
> there isn't a uniform way to disable this behaviour. 

If it always does that, then it cannot be implementing QoS properly.

johannes


  reply	other threads:[~2008-08-15 19:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 16:23 [PATCH] p54: Fix for TX sequence number problem that resulted from commit 741b4fbc44 Larry Finger
2008-08-08  8:26 ` Chr
2008-08-08 14:29   ` Larry Finger
2008-08-08 18:38     ` Chr
2008-08-09 16:02       ` Larry Finger
2008-08-09 16:43         ` Chr
2008-08-09 18:11           ` Larry Finger
2008-08-10 14:19       ` Larry Finger
2008-08-10 22:27         ` Chr
2008-08-10 23:04           ` Larry Finger
2008-08-13 22:15             ` Chr
2008-08-15 18:34         ` Chr
2008-08-15 19:26           ` Johannes Berg [this message]
2008-08-15 20:15             ` Chr
2008-08-15 20:17               ` Johannes Berg
2008-08-15 21:06                 ` Chr
2008-08-15 21:13                   ` Johannes Berg
2008-08-16  0:34           ` Larry Finger
2008-08-16  2:21             ` Chr
2008-08-16 14:00               ` Larry Finger
2008-08-16 14:38                 ` Chr

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=1218828375.3197.0.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=chunkeey@web.de \
    --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).