public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Regression in b43 with BCM4311/2
Date: Sat, 30 Jan 2010 22:58:19 +0100	[thread overview]
Message-ID: <1264888699.3546.208.camel@johannes.local> (raw)
In-Reply-To: <4B64AAEB.9020806@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

On Sat, 2010-01-30 at 15:55 -0600, Larry Finger wrote:
> On 01/30/2010 03:30 PM, Johannes Berg wrote:

> My AP returns the following in the scan output:
> 
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
>           24 Mb/s; 36 Mb/s; 54 Mb/s
> Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
> 
> I don't see any * markings.

Check with iw, instead of iwlist, I think?

> >> Is b43 missing something needed to set the basic_rates member of struct
> >> ieee80211_bxx_conf to a more reasonable value when b43_op_bss_info_changed() is
> >> entered? I think it should be 0xFFF, not 0xF. I have tested with the larger
> >> value and found that this change did not improve transmit rates.
> > 
> > So you're saying it doesn't help anyway?
> 
> Yes, it does not help. Since my previous message, I have also tested the short
> slot logic. Inverting the test made no difference.

Strange. can the patch be reverted as a whole and then it's ok again?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2010-01-30 21:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30 21:21 Regression in b43 with BCM4311/2 Larry Finger
2010-01-30 21:30 ` Johannes Berg
2010-01-30 21:55   ` Larry Finger
2010-01-30 21:58     ` Johannes Berg [this message]
2010-01-30 22:39       ` Larry Finger
2010-01-31 19:08       ` Larry Finger
2010-01-31 19:53         ` Johannes Berg

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=1264888699.3546.208.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.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