The latest linux-wlan-ng is 0.1.15pre8, Looking at the changelog
[ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/CHANGES], a few updates have
happened that I noticed since 0.1.13
- Applied pizza's patch to remove the pb_t structure and make all
802.11<->ether conversions happen in-place. Noticeably reduces
cpu load. Also includes a few misc bugfixes to the conversion code.
- Partial rewrite of the PCI/PLX/USB driver internals
- Fix an alignment bug in the rx path.
- Partial rewrite of copy_to_bap.
- More cleanups/deletions/fixes in wlan_compat.h
- Updates to hfa384x.h to reflect latest documentation
and David Gibson [the author and maintainer of the orinoco linux driver] has
a sept 13 update [http://ozlabs.org/people/dgibson/dldwd/]
Hope this helps out. :)
----- Original Message -----
From: "Michael Brown" <mb...@fe...>
To: "Boris" <bo...@th...>
Cc: <eth...@li...>
Sent: Thursday, September 19, 2002 2:39 AM
Subject: Re: [Etherboot-developers] Prism2 driver update?
> On Wed, 18 Sep 2002, Boris wrote:
> > What was the prism2 driver derrived from? The linux kernel? If so,
> > what version was it extracted from? I read that the linux driver has
> > been updated because it had some allocation problems. Make we should
> > take the latest linux driver and get that one working in etherboot.
> > Just in case the older driver had problems [which even I had with
> > larger then 20mb images].
>
> It was taken from 2.4.18-6mdk (Mandrake 8.2 release), which I think
> corresponds to linux-wlan-ng-0.1.13. If you can point me towards the
> relevant changelog message and patches for the Linux kernel, I'll try to
> map them into the Etherboot driver.
>
> The Etherboot Prism2 driver comprises three header files (hfa384x.h,
> p80211hdr.h and wlan_compat.h), one main C file (prism2.c) and two wrapper
> C files (prism2_pci.c and prism2_plx.c). The header files were lifted
> straight from the Linux kernel source without modifications, in order to
> make it easier to upgrade them, so that's a simple job. In prism2.c,
> there are very few nontrivial routines:
> hfa384x_docmd_wait
> hfa384x_prepare_bap
> hfa384x_copy_from_bap
> hfa384x_copy_to_bap
> hfa384x_cmd_access
> hfa384x_drvr_getconfig
> hfa384x_drvr_setconfig
> hfa384x_wait_for_event
> prism2_poll
> prism2_transmit
> most of which have direct equivalents in the Linux kernel source, so it
> should be fairly straightforward to see which changes should be applied to
> which routines.
>
> Michael Brown
> http://www.fensystems.co.uk
>
>
|
