Re: rt2x00/rt2500 support

[Dan Williams <dcbw redhat com>]

On Wed, 2006-07-12 at 09:32 +1200, Eion Robb wrote:
> On Wed, 12 Jul 2006 09:08:01 +1200, Dan Williams <dcbw redhat com> wrote:
> 
> >
> > I just pulled the nightly CVS from here:
> > http://rt2x00.serialmonkey.com/wiki/index.php/Downloads
> >
> > http://rt2x00.serialmonkey.com/rt2500-cvs-daily.tar.gz
> >
> > for the rt2500.  I can find nowhere the driver actually supports WEXT.
> > I thought some bits of the rt2x00 driver used the devicescape 80211
> > stack, which means they _would_ actually support some stuff for WEXT.
> > But I can't find anywhere in the driver that does.
> 
> You were on the right page, but the link for the rt2x00 driver is
> http://rt2x00.serialmonkey.com/rt2x00-cvs-daily.tar.gz
> The driver you downloaded was the old legacy (ralink supplied) driver

Ok, this makes a lot more sense.  However I'd suggest to the rt2x00
people to make that link a _LOT_ more prominent than it is, otherwise
people aren't going to know which driver is which and they are going to
download the wrong one.

For example, madwifi does "madwifi" and "madwifi-ng", and it's quite
clear from their site which driver is newer and better.  I couldn't
figure that out at all from the rt2x00 site.  But I digress...

The rt2x00-cvs-daily driver does appear to properly support WEXT since
it uses the ieee80211 layer.  But until the sourceforge site gets
updated to reflect which driver people should actually use, I'd be
hesitant to say that rt2x00 is actually WEXT compliant since most people
would likely make the same mistake I did, and download the older driver.

Dan

> > Furthermore, it doesn't look like the scan results function actually
> > returns the BSSID's WPA or RSN generic information element.  Which is
> > pretty much necessary.
> I'm guessing this is from using the old driver right?  Just to check, what  
> command are you running and whats an example of correct results (just in  
> case it isn't working now, I can look out for it in the future)
> 
> >
> > So if it does actually work for you with -Dwext for WPA, where did you
> > get the driver from?
> 
> As above
> 
> > Dan
> >
> >
> 
> So is there any reason for it not to be detected by NetworkManager?
> 
> --Eion
> 
>