On 28/12/09 04:49, Larry Finger wrote:
Hi,
In the latest Broadcom driver, I found code that sets the timeout field of the
SSB configuration for some BCM4311 and all BCM4312 devices. Please test this
patch following a cold boot.
Sadly it does not work. Tested with the mainline kernel. The
On 12/28/2009 09:52 AM, Andrew Benton wrote:
Sadly it does not work. Tested with the mainline kernel. The DMA errors
persist.
Shucks!!! I was hoping for a late Christmas present. Unfortunately, more coal in
my stocking.
As usual, thanks for testing.
Larry
On Monday 28 December 2009 05:49:14 Larry Finger wrote:
+ tmp = ~(SSB_IMCFGLO_SERTO | SSB_IMCFGLO_REQTO_SHIFT);
This does not make any sense.
Did you mean:
+ tmp = ~(SSB_IMCFGLO_SERTO | SSB_IMCFGLO_REQTO);
+ tmp |= 3;
So you set
On 12/28/2009 12:33 PM, Michael Buesch wrote:
On Monday 28 December 2009 05:49:14 Larry Finger wrote:
+tmp = ~(SSB_IMCFGLO_SERTO | SSB_IMCFGLO_REQTO_SHIFT);
This does not make any sense.
Did you mean:
+ tmp = ~(SSB_IMCFGLO_SERTO | SSB_IMCFGLO_REQTO);
On Monday 28 December 2009 20:09:05 Larry Finger wrote:
I did get that wrong. The Broadcom code does the equivalent of
tmp = tmp ~0x77 | 3
Ok, so you need my version of the masking.
which is what my code ended up doing by accident, but REQ is set to zero.
Yeah, OK to me. It's a workaround
Hi,
In the latest Broadcom driver, I found code that sets the timeout field of the
SSB configuration for some BCM4311 and all BCM4312 devices. Please test this
patch following a cold boot.
Thanks,
Larry
Index: wireless-testing/drivers/ssb/driver_pcicore.c
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. Please try
this really ugly
On Monday 21 December 2009 22:31:10 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
On 12/21/2009 03:47 PM, Michael Buesch wrote:
On Monday 21 December 2009 22:31:10 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
On Monday 21 December 2009 23:02:39 Larry Finger wrote:
On 12/21/2009 03:47 PM, Michael Buesch wrote:
On Monday 21 December 2009 22:31:10 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
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.
On 12/21/2009 04:11 PM, Michael Buesch wrote:
On Monday 21 December 2009 23:02:39 Larry Finger wrote:
On 12/21/2009 03:47 PM, Michael Buesch wrote:
On Monday 21 December 2009 22:31:10 Larry Finger wrote:
Hi,
I placed a number of test prints in my system trying to find where a
DMA data error
On 12/21/2009 04:18 PM, William Bourque wrote:
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
On Monday 21 December 2009 23:20:06 Larry Finger wrote:
Here, it was slot 74 that crossed the page boundary. At 110 bytes per
every 2 slots, that works out to 4070 bytes for 0 - 73. From that, I
infer that the cache starts on a page boundary.
Yeah well. For you.
--
Greetings, Michael.
On Mon, 21 Dec 2009 17:18:01 -0500
William Bourque william.bour...@polymtl.ca wrote:
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.
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
In exploring the cause of DMA errors for BCM4312 devices on Atom
processors, other drivers that work write to PCI configuration
On Sat, 19 Dec 2009 10:43:29 -0600
Larry Finger larry.fin...@lwfinger.net 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
I applied this to 2.6.32.2 and it didn't
On 19/12/09 19:55, Chris Vine wrote:
On Sat, 19 Dec 2009 10:43:29 -0600
Larry Fingerlarry.fin...@lwfinger.net 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
I
On 12/19/2009 05:11 PM, Andrew Benton wrote:
On 19/12/09 19:55, Chris Vine wrote:
I applied this to 2.6.32.2 and it didn't help with the DMA errors I am
afraid.
Chris
Same here, the patch didn't prevent the DMA errors, however, I did
notice that it only reported the error once, it
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
On 12/19/2009 10:15 PM, William Bourque wrote:
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
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 your fatal DMA
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
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?)
fails to even detect
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?)
On 11/24/2009 10:58 AM, William Bourque wrote:
I did tried before, it succesfully built, it was loading (modprobe)
correctly but no new interface was registered by it.
However, I might have done something wrong, I will try it again to make
sure it wasn't a PEBKAC problem.
Are you certain that
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?)
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.
The proprietary driver
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
On 11/24/2009 01:35 PM, William Bourque wrote:
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
On Tue, 24 Nov 2009 11:43:32 -0600
Larry Finger larry.fin...@lwfinger.net wrote:
On 11/24/2009 10:58 AM, William Bourque wrote:
I did tried before, it succesfully built, it was loading (modprobe)
correctly but no new interface was registered by it.
However, I might have done something
On 24/11/09 20:25, Chris Vine wrote:
For the record, and in case someone else needs it, I had to apply this
one: one glue file didn't include sched.h as it should have done
(presumably one of the other included headers happened to include it in
kernel= 2.6.31 but not after). I don't know why
On 24/11/09 18:05, Larry Finger wrote:
The wl driver needs lib80211 as a module. Check your .config for
CONFIG_LIB80211.
Larry
The wl driver works well for me with a monolithic kernel. The only
module I have is wl
andy:~$ lsmod
Module Size Used by
wl
On Sun, 2009-11-22 at 19:52 -0600, Larry Finger wrote:
We know that the wl driver does something to the interface that persists
across
a warm boot - we just do not know what. It does not appear to be done in any
of
the MMIO traffic - at least I have not seen it in the mmio-trace output. If
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
On Sat, 21 Nov 2009 00:15:12 +
Chris Vine ch...@cvine.freeserve.co.uk wrote:
WARM BOOT FROM KERNEL WITH WL MODULE INSTALLED
The patched kernel makes no change on a warm boot in the sense that
if I warm boot after initialising the wireless device with the wl
module then the b43 module
On 11/22/2009 01:03 PM, Chris Vine wrote:
On Sat, 21 Nov 2009 00:15:12 +
Chris Vine ch...@cvine.freeserve.co.uk wrote:
WARM BOOT FROM KERNEL WITH WL MODULE INSTALLED
The patched kernel makes no change on a warm boot in the sense that
if I warm boot after initialising the wireless device
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
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
On Fri, 20 Nov 2009 06:43:05 -0600
Larry Finger larry.fin...@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
42 matches
Mail list logo
