On Thursday 19 November 2009 06:21:45 William Bourque wrote:
Michael Buesch wrote:
Enforce all device constraints on the descriptor memory region.
There are several constraints on the descriptor memory, as documented
in the specification. The current code does not enforce them and/or
Hello All!
The reporter is encountering kernel crashes while downloading at high
speed using openfwwf firmware. He claims in a separate post, that if
he switches to proprietary firmware, the problem is gome.
What additional information should I ask him?
-- Forwarded message --
So I'm at a loss here, but if someone comes up with a bright
idea to test or needs more informations I'm willing to test
the resulting code on my machine.
Sebastian
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
On Thursday 19 November 2009 12:07:30 Oncaphillis wrote:
So I'm at a loss here, but if someone comes up with a bright
idea to test or needs more informations I'm willing to test
the resulting code on my machine.
Erm, no. Can you please answer the questions that you didn't answer, yet?
On 11/19/2009 12:09 PM, Michael Buesch wrote:
On Thursday 19 November 2009 12:07:30 Oncaphillis wrote:
So I'm at a loss here, but if someone comes up with a bright
idea to test or needs more informations I'm willing to test
the resulting code on my machine.
Erm, no. Can you please
Erm, no. Can you please answer the questions that you didn't answer, yet?
Especially the request for the original vendor driver.
oh sorry. I did that, but the mail only went to larry -- stupid me -- the
device didn't come with a CD/DVD and I killed Windows XP right away.
Sorry
Can you please try the following patch?
http://bu3sch.de/patches/wireless-testing/20091119-1349/patches/002-ssb-rewrite-sprom-fallback-mechanism.patch
--
Greetings, Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https
On 11/19/2009 01:49 PM, Michael Buesch wrote:
Can you please try the following patch?
http://bu3sch.de/patches/wireless-testing/20091119-1349/patches/002-ssb-rewrite-sprom-fallback-mechanism.patch
That seems to freeze my kernel. I tell you more in a couple of hours
On Thursday 19 November 2009 14:26:42 Oncaphillis wrote:
On 11/19/2009 01:49 PM, Michael Buesch wrote:
Can you please try the following patch?
http://bu3sch.de/patches/wireless-testing/20091119-1349/patches/002-ssb-rewrite-sprom-fallback-mechanism.patch
That seems to freeze my kernel
On Thursday 19 November 2009 16:27:01 Michael Buesch wrote:
On Thursday 19 November 2009 14:26:42 Oncaphillis wrote:
On 11/19/2009 01:49 PM, Michael Buesch wrote:
Can you please try the following patch?
http://bu3sch.de/patches/wireless-testing/20091119-1349/patches/002-ssb-rewrite-sprom
Hello All!
Here is tthe additional information about the issue.
-- Forwarded message --
From: bugzi...@redhat.com
Date: 2009/11/19
Subject: [Bug 538579] Kernel dead, when with the default b43
Firmware, a while full speed downloading
To: lemen...@gmail.com
Please do not reply
On Thursday 19 November 2009 16:41:12 Michael Buesch wrote:
Wait, that still can't work. I'll fix it soon...
Ok, here's the updated version. Please test this:
http://bu3sch.de/patches/wireless-testing/20091119-1842/patches/002-ssb-rewrite-sprom-fallback-mechanism.patch
--
Greetings, Michael
With open firmware being distributed by some distros, the problem
of a duplicate skb returned to b43_dma_handle_txstatus() is being
reported. (See Bug #538579 at bugzi...@redhat.com.)
When this problem occurs, A BUG_ON() is encountered - the kernel
panic yields little information. This patch
At present, the results of an SSB core scan are only logged when
CONFIG_SSB_DEBUG is y. As this may not be set in a distro kernel,
it is difficult interpret many problems posted in bug reports or in
help forums.
Signed-off-by: Larry Finger larry.fin...@lwfinger.net
---
Index:
On Thursday 19 November 2009 20:43:54 Larry Finger wrote:
At present, the results of an SSB core scan are only logged when
CONFIG_SSB_DEBUG is y. As this may not be set in a distro kernel,
it is difficult interpret many problems posted in bug reports or in
help forums.
Signed-off-by: Larry
At present, the results of an SSB core scan are only logged when
CONFIG_SSB_DEBUG is y. As this may not be set in a distro kernel,
it is difficult interpret many problems posted in bug reports or in
help forums.
Signed-off-by: Larry Finger larry.fin...@lwfinger.net
---
V2 - Change from KERN_INFO
This rewrites the error handling policies in the TX status handler.
It tries to be error-tolerant as in try hard to not crash the machine.
It won't recover from errors (that are bugs in the firmware or driver),
because that's impossible. However, it will return a more or less useful
error message
On 11/19/2009 06:44 PM, Michael Buesch wrote:
On Thursday 19 November 2009 16:41:12 Michael Buesch wrote:
Wait, that still can't work. I'll fix it soon...
Ok, here's the updated version. Please test this:
http://bu3sch.de/patches/wireless-testing/20091119-1842/patches/002-ssb-rewrite-sprom
On 11/18/2009 11:21 PM, William Bourque wrote:
Also, just saying, but it seems Larry's pm_qos_update_requirement
patch had some good effects; I can hardly get any connectivity without
it. With the patch, the wireless seems to be stable for a few minutes
before generating DMA errors...
/20091119-1842/patches/002-ssb-rewrite-sprom-fallback-mechanism.patch
Heureka -- seems like I'm the first linux user on the planet with a
WLAN connection on that device. The MAC address is random which
of course is a pain for DHCP but it seems to work. Appears a little
bit slow though.
Ok
20 matches
Mail list logo
