2009/11/14 Matthew Garrett mj...@srcf.ucam.org:
On Sat, Nov 14, 2009 at 12:41:49AM +, Andrew Benton wrote:
And it seems to be working well. No errors so far. I've just downloaded
a kernel, browsed slashdot a bit. I'll test it some more tomorrow but
this is a BIG step in the right
On 14/11/09 07:29, Matthew Garrett wrote:
I should emphasise that this patch works by effectively disabling deep C
states on your CPU, which in turn will increase your power consumption.
It's very much either a workaround for broken hardware or something that
covers up a more subtle bug
On 11/13/2009 08:20 PM, Larry Finger wrote:
On 11/13/2009 11:46 AM, Oncaphillis wrote:
Thanks for the tip. But it still hangs
We still need to know where it hangs. If you boot to console mode (type a 3 on
the option line in GRUB), does it boot? If it does not, what is the last line
shown
On Sat, 14 Nov 2009 09:52:15 +
Andrew Benton b3n...@gmail.com wrote:
It was working fine last night but I can't get that kernel to connect
today. Nothing has changed, I can see no reason why it was working
and isn't working now. It feels like a hardware problem.
I'm recompiling with a
On 14/11/09 11:24, Chris Vine wrote:
Be aware that if you have been using the proprietary wl driver to send
on your bug reports, you must do a cold boot before testing b43, as if
you warm boot after having initialised the wireless device with the wl
driver then the DMA bug disappears.
That
Hello group,
I managed to get AP with my bcm4306 rev 2 running using b43legacy and hostapd.
I'm using compat-wireless-2009-11-13 with patches from openwrt trunk for my
b43legacy driver. I use libnl HEAD version und hostapd 0.6.9.
Now I have two issues.
1)
I'm using Miktorik RB/14 4miniPCI =
On 11/14/2009 12:24 PM, Oncaphillis wrote:
On 11/13/2009 08:20 PM, Larry Finger wrote:
On 11/13/2009 11:46 AM, Oncaphillis wrote:
Thanks for the tip. But it still hangs
We still need to know where it hangs. If you boot to console mode (type a 3
on
the option line in GRUB), does it
On 11/14/2009 07:37 AM, Oncaphillis wrote:
So it seems to me it doesn't even reach the loading of p43.ko
but gets stuck in the cfg80211 layer.
We can test that hypothesis. Generate a kernel without b43. Once it boots, enter
the following commands as root:
modprobe -v rfkill
modprobe -v
On 11/14/2009 04:42 PM, Larry Finger wrote:
On 11/14/2009 07:37 AM, Oncaphillis wrote:
So it seems to me it doesn't even reach the loading of p43.ko
but gets stuck in the cfg80211 layer.
We can test that hypothesis. Generate a kernel without b43. Once it boots,
enter
the following commands
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
On 11/14/2009 08:45 PM, Michael Buesch wrote:
On Saturday 14 November 2009 12:24:24 Oncaphillis wrote:
On 11/13/2009 08:20 PM, Larry Finger wrote:
On 11/13/2009 11:46 AM, Oncaphillis wrote:
Thanks for the tip. But it still hangs
We still need to know where it hangs. If you boot to
On Saturday 14 November 2009 12:24:24 Oncaphillis wrote:
On 11/13/2009 08:20 PM, Larry Finger wrote:
On 11/13/2009 11:46 AM, Oncaphillis wrote:
Thanks for the tip. But it still hangs
We still need to know where it hangs. If you boot to console mode (type a 3
on
the option line
On Saturday 14 November 2009 21:03:09 Oncaphillis wrote:
On 11/14/2009 08:45 PM, Michael Buesch wrote:
On Saturday 14 November 2009 12:24:24 Oncaphillis wrote:
On 11/13/2009 08:20 PM, Larry Finger wrote:
On 11/13/2009 11:46 AM, Oncaphillis wrote:
Thanks for the tip. But it still
On 11/14/2009 12:51 PM, William Bourque wrote:
Ok, I tried with value of 150, 100 already and I'm recompiling to see
the result with 175 and 125.
150us seems to give me the best result. As with 200 I could use the
wireless for several minutes and insert/remove the module. However it
Michael,
I now have MMIO traces after modprobe of wl and b43, both after a fresh cold
reboot. There are many similaries (of course), but some differences that could
be important in the DMA errors.
In both dumps, I see the code advancing through the cores. I don't see the PCI
configuration
On Saturday 14 November 2009 23:29:38 Larry Finger wrote:
Michael,
I now have MMIO traces after modprobe of wl and b43, both after a fresh cold
reboot. There are many similaries (of course), but some differences that could
be important in the DMA errors.
In both dumps, I see the code
On 11/14/2009 07:31 PM, Michael Buesch wrote:
I guess the patch misses some curly brackets.
So it does. V2 attached.
Larry
Index: wireless-testing/drivers/net/wireless/b43legacy/rfkill.c
===
---
I guess the patch misses some curly brackets.
--
Greetings, Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
18 matches
Mail list logo
