On Tue, 2009-02-03 at 20:53 +0100, Michael Buesch wrote:
>
> So well.
> b43 in AP mode does actually work properly.
Indeed, I found it functional, even with WPA2. Just not performing well
on throughput.
> Atheros is the best bet, I'd say. But _first_ check to buy a supported card.
Indeed. On
On Tuesday 03 February 2009 20:41:06 Brian J. Murrell wrote:
> On Tue, 2009-02-03 at 20:16 +0100, Michael Buesch wrote:
> > On Tuesday 03 February 2009 05:44:42 Brian J. Murrell wrote:
> > > The bad news is that throughput still sucks rocks.
>
> Sorry if that sounded harsh. It didn't seem as hars
On Tue, 2009-02-03 at 20:16 +0100, Michael Buesch wrote:
> On Tuesday 03 February 2009 05:44:42 Brian J. Murrell wrote:
> > The bad news is that throughput still sucks rocks.
Sorry if that sounded harsh. It didn't seem as harsh when I was writing
it as it did just now reading it. I meant no ill-
On Tuesday 03 February 2009 05:44:42 Brian J. Murrell wrote:
> The bad news is that throughput still sucks rocks.
This is unlikely to change ever, except if broadcom releases the sources.
Go and buy a device that's actually vendor supported, if you want full
throughput.
--
Greetings, Michael.
_
So, I decided to give b43 in AP mode a go on my ASUS wl500gp with r14139
(kernel 2.6.25.20). The results are both good and bad.
First the good news. The problems I was seeing with b43/AP mode on my
Linksys WRT54GS are gone. I don't see the CPU saturated with ksoftirqd.
Yay.
The bad news is tha