Hello
Marc Haber wrote:
Hi,
when the broadcom-sta driver didn't compile with 2.6.33 I decided to
give b43 a new try. I have a Lenovo Ideapad S12, which has a BCM4312
with LP Phy (14e4:4315). I am using Debian unstable.
When I load the module, a new interface wlan0 appears, but iwlist
Michael Buesch wrote:
On Tuesday 02 March 2010 23:25:48 William Bourque wrote:
So if I get this right, this code is responsible of handling the b43
devices, as well as several other PCI-E devices, correct?
Nah, this is a broadcom specific thing of the on-chip SSB bus.
Ok, sorry
Chris Vine wrote:
On Sun, 28 Feb 2010 00:44:58 +0100
Gábor Stefanik netrolller...@gmail.com wrote:
2010/2/28 Nathan Schulte rekl...@gmail.com:
2010/2/27 Gábor Stefanik netrolller...@gmail.com:
OK, I whipped up a quick test patch with changes found so far
implemented. Please test if this
New test patch attached.
Please CC linux-wirel...@vger.kernel.org on further e-mails,
bcm43xx-dev appears to be having problems.
Hmm... I don't know if it is only coincidence, but this one seems to
help somehow.
The driver raised the DMA error again, but instead of being as soon as I
Chris Vine wrote:
On Sun, 28 Feb 2010 19:58:11 +0100
Michael Buesch m...@bu3sch.de wrote:
It says 8k for all of my devices there. So an MMIO write to 0x2000
and above writes to completely random memory.
My BCM4312 device is 16K:
Region 0: Memory at f800 (64-bit, non-prefetchable)
Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error might occur. In doing so, I found that 3 slots in the
DMA header cache cross a page boundary. Such a situation is allowed on
my system, but it might be forbidden on Atom processors.
Larry Finger wrote:
Hi,
If possible, please test this patch starting from a cold boot. It is a
variation of something we tried earlier, but enough different to try it.
Thanks,
Larry
A little late but I just tested and I have the same bug.
However, unlike Andrew, the error keep
Larry Finger wrote:
Please try this patch without the pm_qos patch to see if it helps. The
Broadcom
wl driver does this during the setup.
The DMA error is still there. There is something strange about the wl
driver, it seems to perform some action on the card that are only done
after the
Chris Vine wrote:
On Mon, 23 Nov 2009 22:58:36 -0500
William Bourque william.bour...@polymtl.ca wrote:
Larry Finger 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
Chris Vine wrote:
On Tue, 24 Nov 2009 10:50:13 -0500
William Bourque william.bour...@polymtl.ca wrote:
[snip]
I was using the B43 (GPL) driver but with the proprietary firmware
extracted from Broadcom crap with bfwcutter.
The proprietary driver provided by Broadcom (what you refer as wl
Chris Vine wrote:
On Tue, 24 Nov 2009 10:50:13 -0500
William Bourque william.bour...@polymtl.ca wrote:
[snip]
I was using the B43 (GPL) driver but with the proprietary firmware
extracted from Broadcom crap with bfwcutter.
The proprietary driver provided by Broadcom (what you refer as wl
Larry Finger wrote:
On 11/24/2009 11:54 AM, William Bourque wrote:
Chris Vine wrote:
On Tue, 24 Nov 2009 10:50:13 -0500
William Bourque william.bour...@polymtl.ca wrote:
[snip]
I was using the B43 (GPL) driver but with the proprietary firmware
extracted from Broadcom crap with bfwcutter
Nothing changed... Again, the Broadcom driver is helpless.
Also note all of this was made after a _warm_ boot. Do you want me to
try everything from a cold boot?
Just an update, cold booting didn't help.
- William
___
Bcm43xx-dev mailing
Well well... While looking to activate SSB_DEBUG, I found out that SSB
was _included_ in my old 2.6.32-rc5 kernel.
I recompiled with SSB as module and the Broadcom wl driver seems to
claim the card correctly... look like ssb was claiming the PCI device
from it.
I don't remember I played in the
Larry Finger wrote:
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
Larry Finger 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
Larry Finger 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
Larry Finger wrote:
On 11/13/2009 06:15 PM, William Bourque wrote:
Larry Finger wrote:
Based on a suggestion by Matthew Garrett, please try the patch below.
Thanks,
Larry
=
Index: wireless-testing/drivers/net/wireless/b43/main.c
Oncaphillis wrote:
On 11/13/2009 05:12 PM, Larry Finger wrote:
On 11/13/2009 09:33 AM, Oncaphillis wrote:
Hi,
I have a Acer One D250 which is equipped with a BCM4312 for
which on the homepage the support is marked as in progress.
Whenever the kernel tries to insert b43.ko it freezes. If've
Michael Buesch wrote:
Please test the following patch. It changes more stuff related to the
descriptor ring handling (remove the old patch first before applying this
one).
http://bu3sch.de/patches/wireless-testing/20091113-1834/patches/001-b43-rewrite-dma-ring-alloc.patch
Hi
Here is the
Larry Finger wrote:
Based on a suggestion by Matthew Garrett, please try the patch below.
Thanks,
Larry
=
Index: wireless-testing/drivers/net/wireless/b43/main.c
===
---
Michael Buesch wrote:
On Thursday 12 November 2009 19:45:45 Andrew Benton wrote:
On 12/11/09 17:14, Larry Finger wrote:
I guess I'm a failure at writing diagnostic patches. Until there is a DMA
error,
the only effect of the patch is to add a little extra time to the routine
that
fills in
Michael Buesch wrote:
On Thursday 12 November 2009 20:32:32 William Bourque wrote:
Sorry for the late reply... I seem to have the exact same bug here. Do
you need more people to run the diagnostic patch?
Well, it doesn't hurt.
Here we go.
I think we can observe the same problem
Michael Buesch wrote:
On Thursday 12 November 2009 22:34:00 William Bourque wrote:
Michael Buesch wrote:
On Thursday 12 November 2009 20:32:32 William Bourque wrote:
Sorry for the late reply... I seem to have the exact same bug here. Do
you need more people to run the diagnostic patch?
Well
24 matches
Mail list logo
