linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: bcm43xx devel <Bcm43xx-dev@lists.berlios.de>,
	wireless <linux-wireless@vger.kernel.org>
Cc: Michael Buesch <mb@bu3sch.df>,
	William Bourque <william.bourque@polymtl.ca>,
	Chris Vine <chris@cvine.freeserve.co.uk>
Subject: DMA errors with BCM4312 - an update
Date: Tue, 24 Nov 2009 13:06:43 -0600	[thread overview]
Message-ID: <4B0C2EC3.5010408@lwfinger.net> (raw)

This E-mail is to summarize what I have learned to date.

The pm_qos change does nothing useful. It may have helped a little, but the side
effects are far worse than the benefits.

Most systems work better with b43 when warm booted after Broadcom's wl driver
was loaded. The conclusion is that wl is making some change in the setup that
b43 is not.

(3) Based on the above, I have done MMIO and PCI-E configuration tracing for the
two drivers and found some real differences. After seeing these, I did more RE
work, and found some setup for the PCI-E core that was missed earlier. I am
still working on the changes. What I have completed is found at

http://bcm-v4.sipsolutions.net/PCI-E#PCI-E_Setup

I doubt that most of these new routines will affect the problem interfaces as
they apply only to PCI-E core revisions 7 and 8. My BCM4312 has rev 9. I do not
know what versions are giving the trouble. With SSB_DEBUG enabled, it will be in
a log line as follows:

ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)

If you are seeing the DMA error, please supply the above info.

The "PCI-E Miscellaneous Configuration" routine that is not yet finished does
run on my system and is the source of the tracing differences. If the problem
cards has a revision newer than 9, I will probably need an MMIO trace for your
device.

Larry


             reply	other threads:[~2009-11-24 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 19:06 Larry Finger [this message]
2009-11-24 21:15 ` DMA errors with BCM4312 - an update Chris Vine
2009-11-24 21:20   ` Michael Buesch
2009-11-25  0:39     ` Larry Finger

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=4B0C2EC3.5010408@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=chris@cvine.freeserve.co.uk \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.df \
    --cc=william.bourque@polymtl.ca \
    /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).