From: Larry Finger <Larry.Finger@lwfinger.net>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: William Bourque <william.bourque@polymtl.ca>,
wireless <linux-wireless@vger.kernel.org>,
bcm43xx-dev@lists.berlios.de
Subject: Re: Fatal DMA error problem with netbook and BCM4312
Date: Fri, 20 Nov 2009 14:05:25 -0600 [thread overview]
Message-ID: <4B06F685.1020405@lwfinger.net> (raw)
In-Reply-To: <20091120195834.334d8bc0@boulder.homenet>
On 11/20/2009 01:58 PM, Chris Vine wrote:
> On Fri, 20 Nov 2009 06:43:05 -0600
> Larry Finger <Larry.Finger@lwfinger.net> wrote:
>> One last check. I would appreciate receiving answers to the following
>> questions. These questions apply to anyone else with this problem.
>>
>> Does the pm_qos patch help your "fatal DMA error" problem,
>> particularly when booted from power-off?
>>
>> If you warm-boot after loading the wl driver, does the patch make any
>> difference?
>
> What's the date/time of the last patch you posted for this and what
> kernel does it apply to?
Friday 11/13 ar 22:38 CET. The link is at
https://lists.berlios.de/pipermail/bcm43xx-dev/2009-November/006338.html.
The patch is written for wireless-testing, but it should apply on mainline
kernels as well.
Larry
next prev parent reply other threads:[~2009-11-20 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AFA09C8.4060602@gmail.com>
[not found] ` <200911131216.43704.mb@bu3sch.de>
[not found] ` <4AFD83CA.2050508@lwfinger.net>
[not found] ` <200911131836.26857.mb@bu3sch.de>
[not found] ` <4AFD9E20.3060501@gmail.com>
[not found] ` <4AFDD1C9.4050402@lwfinger.net>
[not found] ` <4AFDF68C.4040804@polymtl.ca>
[not found] ` <4AFE1E5F.9040009@lwfinger.net>
[not found] ` <4AFEFC2C.5030704@polymtl.ca>
2009-11-20 12:43 ` Fatal DMA error problem with netbook and BCM4312 Larry Finger
2009-11-20 19:58 ` Chris Vine
2009-11-20 20:05 ` Larry Finger [this message]
2009-11-21 0:15 ` Chris Vine
2009-11-22 19:03 ` Chris Vine
2009-11-23 1:52 ` Larry Finger
2009-11-23 10:18 ` 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=4B06F685.1020405@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.