Re: About at76c50XX based devices.

[Dan Williams <dcbw redhat com>]

On Mon, 2006-06-19 at 22:04 +0400, Maxim Grechkin wrote:
> The problem is that it is not working with NM. If problems you
> mentioned are simple interface problems I think I will try to fix
> them. But before it I want to get NM working with it.

Ok; does it work with straight wpa_supplicant using the _wext_ driver
for what you'd like to do?  If that doesn't work, then the driver likely
needs to be fixed.  NM uses wpa_supplicant underneath for all
connections.

Dan

> On 6/19/06, Dan Williams <dcbw redhat com> wrote:
> > On Mon, 2006-06-19 at 18:03 +0400, Maxim Grechkin wrote:
> > > Why are at76c50xx based devices are unsupported? There is good driver
> > > for it (at76c503a.berlios.de). The driver mentioned on wiki page (from
> > > sf.net) is bad, but from berlios is better.
> >
> > I wasn't aware of this driver, actually.
> >
> > Some random notes about it:
> >
> > 1) it's got a private ioctl() for passive vs. active scanning; this is
> > now a WE standardized thing and should be integrated into the
> > SIOCSIWSCAN handler in WE >= 20
> >
> > 2) at76c503_iw_handler_set_wap() doesn't handle the OFF case (where AP
> > BSSID is 00:00:00:00:00:00); should be done pretty much like the ANY
> > case which this function already handles
> >
> > 3) at76c503_iw_handler_set_essid() handles the old WE case for SSID
> > being NULL terminated and length incremented by 1; but doesn't handle
> > new case.  If the driver is compiled to WE >= 21, the client-passed SSID
> > length is 100% correct, even if there is a \0 at the end.
> >
> > All in all, it looks pretty good; and I don't see any specific issues
> > that NM would dislike.  Have you been able to get it to work with NM?
> >
> > Dan
> >
> >
> 
>