[Prism54-devel] Attempting to assoc with hostap-driven AP
Luis R. Rodriguez
mcgrof@ruslug.rutgers.edu
Wed, 4 Feb 2004 17:07:33 -0500
Just use any of these:
http://prism54.org/pub/linux/snapshot/tars/prism54-cvs-latest.tar.bz2
http://prism54.org/pub/linux/snapshot/kernel/v2.4/patch-2.4-prism54-cvs-latest.bz2
http://prism54.org/pub/linux/snapshot/kernel/v2.6/patch-2.6-prism54-cvs-latest.bz2
In your case, it seems you'd like to use the last link.
The DRV_VERSION hasn't changed and that's just because we havn't
released any testing/stable driver. If you want to see the changes since
the driver version you were using read the ChangeLog.
Luis
On Wed, Feb 04, 2004 at 11:36:19PM +0200, vda@port.imtp.ilyichevsk.odessa.ua wrote:
> On Wednesday 04 February 2004 19:37, Luis R. Rodriguez wrote:
> > I see some oid messages in the logs, these have been removed from
> > standard verbose setup. Are you using an old driver?
> >
> > Luis
>
> My running kernel is patched with 'latest' driver which
> contained:
>
> #define DRV_VERSION "1.0.2.2"
>
> I just downloaded today's latest CVS patch and it is
> too 1.0.2.2. However I suspect this one is newer.
>
> In future I'll download and use timestamped patches from
> http://prism54.org/pub/linux/snapshot/kernel/v2.6/YYYY-MM
> to remove all confusion.
>
> Maybe it makes sense to add YYYY-MM-DD to module startup
> message?
>
> I'll patch 2.6.2 now with patch-2.6.2-prism54-cvs20040204.bz2
> and retest.
>
> Meanwhile I veriried that two SMCs seem to work fine as AP and STA
> both with and without WEP.
>
> I reached 2.4 megabyte/s throughput with netcat in both cases.
> Good job guys! :)
> --
> vda
>
> _______________________________________________
> Prism54-devel mailing list
> Prism54-devel@prism54.org
> http://prism54.org/mailman/listinfo/prism54-devel