b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Request for testing b43 & Broadcom 14e4:4315 cards for DMA ERRORs (Linux 3.0)
Date: Mon, 30 May 2011 09:45:49 +0200	[thread overview]
Message-ID: <BANLkTikNq-nkOA8V04ymOzU-6E89w9SCUA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=fgGTvjdQ0Ghd15CBoYzd9TLU2CQ@mail.gmail.com>

W dniu 30 maja 2011 09:22 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?:
> I believe we've fixed that errors in Linux 3.0-rc1. Can you give it a
> chance and report back?

I'd like to say (and you should too) big thanks to Juan, who gave me
access to his affected machine and spent a lot of time testing. He
even bisected kernel on his Atom pointing us to hrtimers regression.


If this is going to work, I've some annoying info for Larry.

I can not tell which of the recent b43/ssb commits were really needed
for solving this issue the final one was "b43: implement timeouts
workaround". The tricky part is we got very similar patch ready 1,5
year ago [0], by Larry!

The mistake done by Larry was applying workaround on PCI(e) core
instead of 80211 core. I've noticed that when comparing
"ssb_read32(SSB_IMCFGLO);" after cold boot between ssb&b43 and wl.
Drivers read different values from hardware, so it was a hint we were
doing this on a wrong core.

[0] http://lists.berlios.de/pipermail/bcm43xx-dev/2009-December/006592.html

-- 
Rafa?

  reply	other threads:[~2011-05-30  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  7:22 Request for testing b43 & Broadcom 14e4:4315 cards for DMA ERRORs (Linux 3.0) Rafał Miłecki
2011-05-30  7:45 ` Rafał Miłecki [this message]
2011-05-31 23:29 ` Chris Vine
2011-06-01  9:17   ` Rafał Miłecki
2011-06-02  3:40 ` William Bourque

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=BANLkTikNq-nkOA8V04ymOzU-6E89w9SCUA@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=b43-dev@lists.infradead.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).