On Monday 15 October 2007 11:05:26 Richard Purdie wrote:
On Sun, 2007-10-14 at 11:42 +0200, Johannes Berg wrote:
On Sat, 2007-10-13 at 17:26 +0200, Michael Buesch wrote:
I also saw this sometimes, but I have absolutely no idea how that happens.
Someone any idea?
Nope, but adding
On Monday 15 October 2007 11:05:26 am Richard Purdie wrote:
It appears to be having a problem in the strcmp in
led_trigger_set_default() which is odd. Code above that checks if one of
the options is NULL so all I can think it either the default_trigger
string being passed in is invalid or
On Sat, 2007-10-13 at 17:26 +0200, Michael Buesch wrote:
I also saw this sometimes, but I have absolutely no idea how that happens.
Someone any idea?
Nope, but adding more CCs :) I briefly looked at the code and couldn't
track it. Got a powerpc oops with disassembly?
b43-phy0 debug: Loading
Hi all,
I tried (I think) latest b43 driver on a bcm4318. It works quite well, but on
a series of connect/reconnect I had attached stack in dmesg.
Any idea?
Chris
FYI (normal dmesg output)
b43-phy0: Broadcom 4318 WLAN found
b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy0
On Saturday 13 October 2007 18:23:33 Christian Hoffmann wrote:
Hi all,
I tried (I think) latest b43 driver on a bcm4318. It works quite well, but on
a series of connect/reconnect I had attached stack in dmesg.
Any idea?
Chris
FYI (normal dmesg output)
b43-phy0: Broadcom 4318 WLAN
