linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>,
	Tim Gardner <tim.gardner@canonical.com>,
	bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org,
	Greg KH <greg@kroah.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH V2] b43legacy: Fix failure in rate-adjustment mechanism
Date: Sun, 7 Sep 2008 00:40:04 +0200	[thread overview]
Message-ID: <200809070040.04300.mb@bu3sch.de> (raw)
In-Reply-To: <48c2fb5a.JqLELi8PJxjxmDaY%Larry.Finger@lwfinger.net>

On Saturday 06 September 2008 23:51:22 Larry Finger wrote:
> A coding error present since b43legacy was incorporated into the
> kernel has prevented the driver from using the rate-setting mechanism
> of mac80211. The driver has been forced to remain at a 1 Mb/s rate.
> 
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@kernel.org>		[2.6.26], [2.6.25]

Reviewed-by: Michael Buesch <mb@bu3sch.de>

> ---
> 
> John,
> 
> This is a bug, not a regression. I guess under the new rules that it
> is 2.6.28 material.

I wonder what the -stable rules are.
It seems really screwed to me to avoid applying the fix to 2.6.27,
but still apply it to 2.6.25/26-stable.

I'd like to see this patch in .25, .26 and .27, however I'm not sure
what the rules are.

For reference:
Three people agree on the correctness of the patch, it's a oneliner
and it's tested to fix the bug. However it is not a regression. The
bug is in there since day-0 of b43legacy. But this fix improves
TX rates a lot.

> Index: wireless-testing/drivers/net/wireless/b43legacy/xmit.c
> ===================================================================
> --- wireless-testing.orig/drivers/net/wireless/b43legacy/xmit.c
> +++ wireless-testing/drivers/net/wireless/b43legacy/xmit.c
> @@ -624,7 +624,7 @@ void b43legacy_handle_hwtxstatus(struct
>  	tmp = hw->count;
>  	status.frame_count = (tmp >> 4);
>  	status.rts_count = (tmp & 0x0F);
> -	tmp = hw->flags;
> +	tmp = hw->flags << 1;
>  	status.supp_reason = ((tmp & 0x1C) >> 2);
>  	status.pm_indicated = !!(tmp & 0x80);
>  	status.intermediate = !!(tmp & 0x40);

-- 
Greetings Michael.

  reply	other threads:[~2008-09-06 22:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06 21:51 [PATCH V2] b43legacy: Fix failure in rate-adjustment mechanism Larry Finger
2008-09-06 22:40 ` Michael Buesch [this message]
2008-09-08  5:31   ` Greg KH
2008-09-08 12:53     ` Michael Buesch
2008-09-08 16:22     ` Larry Finger
2008-09-08 20:54       ` John W. Linville
2008-09-10  6:40         ` Otto Solares
2008-09-10 13:21           ` John W. Linville
2008-09-10  5:19       ` Greg KH

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=200809070040.04300.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=greg@kroah.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tim.gardner@canonical.com \
    --cc=torvalds@linux-foundation.org \
    /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).