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: Sun, 31 Jan 2010 20:53:14 +0100	[thread overview]
Message-ID: <1264967594.3597.6.camel@johannes.local> (raw)
In-Reply-To: <4B65D51F.1090903@lwfinger.net>

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

Larry,

> I finally sorted this out. The patch in question (c7ab5ef) is the bad one, but
> not the basic response rate part.
> 
> Going back to the code that worked, I discovered that the routines
> b43_short_slot_timing_enable/disable() were never called. Once the new code
> touched the shared memory location 0x0010, the transmit performance dropped way
> off. If I let the new code adjust the Interframe Slot time in MMIO space, but
> not the shared memory location, the transmit rate in my BCM4311/2 went from a
> maximum of 18 to 22 Mb/s. This problem did not affect the 0x4315 device as the
> memory was changed only for G PHYs. I think that should be for 2GHz, and have
> made that adjustment. I have not yet tested that with the LP PHY. Once I do, I
> will post a patch for comment and testing.

Cool, thanks for looking into it and the detailed analysis!

> Thanks for helping me understand the basic response rates.

Any time.

johannes

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

      reply	other threads:[~2010-01-31 19:53 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
2010-01-30 22:39       ` Larry Finger
2010-01-31 19:08       ` Larry Finger
2010-01-31 19:53         ` Johannes Berg [this message]

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=1264967594.3597.6.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