Re: Asus EeePC

[Dan Williams <dcbw redhat com>]

On Thu, 2007-12-27 at 12:39 -0500, Pat Suwalski wrote:
> On Thu, 27 Dec 2007, Ryan Novosielski wrote:
> > Well, I'll try to take a good look at this thing when I get it. Maybe
> > the information can be of help in some way.
> 
> Having worked on this part of the eeePC, I have some useful information.
> 
> The atl2 driver on the unit works great, the upstream source "just works" 
> with it.

Ok, good to know; The reason I though it wasn't quite working was that I
saw a huge atl2 driver RFC patch go through lkml about 3 weeks ago that
I thought was applicable to this.  If stuff works, great :)

> The problem with the wireless is that Atheros was very insistent on 
> shipping their version of madwifi as default (surprise).

Yeah, sucks.  There's historically been problems with madwifi because
the WEXT implementation for stuff like signal quality and WPA was late
to the game, and some parts just seem to work differently than every
other driver out there.  The WEXT support of drivers needs to get more
harmonized.

> Nonetheless, my experimentation with 2.6.24, the latest madwifi, and the 
> latest wpa-supplicant were very positive.

With the WEXT driver of the madwifi driver for wpa_supplicant?  The
ideal case is that stuff works with the WEXT driver exclusively.

Dan