From: "Rafał Miłecki" <zajec5@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: b43-dev <b43-dev@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Interesting development regarding b43 DMA ERROR
Date: Fri, 6 Aug 2010 18:31:11 +0200 [thread overview]
Message-ID: <AANLkTi=-Jc9XjD-gqwtUyUnM768wvv3GzzwhJNtkwYKK@mail.gmail.com> (raw)
In-Reply-To: <4C5B27BE.8010708@lwfinger.net>
2010/8/5 Larry Finger <Larry.Finger@lwfinger.net>:
> Yesterday, I had to go back to kernel 2.6.34 for a test of code to avoid ssb
> load freezeups on my HP Mini 110 Netbook, which has the SPROM at offset 0x0800,
> not 0x1000. As I had been using b43 for this BCM4312 (14e4:4315) card in DMA
> mode without any problems, I was quite surprised to see the dreaded DMA errors.
> I had attributed the lack of errors with wireless testing to be due to the AMI,
> not Phoenix, BIOS in this machine. When I switched to mainline ('git describe'
> reports it as v2.6.35-3370-gcdd854b), again it works.
>
> AFAIK, none of any fixes that were put into wt to try to solve this problem had
> any affect, yet the device now works here.
>
> Is anyone else that had/has the DMA problem running 2.6.35 + updates from the
> linux-2.6.git tree? If so, does your BCM4312 now work with b43, or is my box
> special?
Interesting. It means some patch that gone mainline fixed it and it
was submitted using other tree than w-t, right?
Would you care to bisect this?
--
Rafał
next prev parent reply other threads:[~2010-08-06 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:06 Interesting development regarding b43 DMA ERROR Larry Finger
2010-08-06 16:31 ` Rafał Miłecki [this message]
2010-08-06 17:37 ` Larry Finger
2010-08-08 5:08 ` Kalle Valo
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='AANLkTi=-Jc9XjD-gqwtUyUnM768wvv3GzzwhJNtkwYKK@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).