I'd like to catch up to recent MadWiFi driver code and am asking for
advice on how I'm approaching this.
? The bottom line is: How crazy is it to attempt to get MadWiFI + Hostap
to work with MontaVista 2.4.17 ?
What I have is:
MontaVista (2.4.17 kernel)
Atheros 5212 (Netgear 311, Wistron ?)
A circa-2003 MadWifi Driver (with changes parallel to MadWiFi
(Both WiFi cards currently work with this old, but modified, MadWiFi
My plan of action is:
1) using RH9 on an x86 PC (2.4.20 or possibly a .24,.25 kernel
a. add Wireless Extensions as needed
b. add Crypto as needed
c. add hostap as needed
d. add MadWiFi from the CVS branch (assumed to be more stable than
e. validate the driver's functionality relative to our needs (WDS,
2) If that all works out, then do the same for our MontaVista
2.4.17 embedded system
a. I'm unsure of the challenges of mixing and matching 2.4.17 with
newer crypto, etc.
3) If (2) is problematic, then upgrade the MV 2.4.17 kernel to .20
...or... .25 and retry
a. Note that this could adversely affect other components of our
If anyone has any thoughts on whether this approach is doomed or
unnecessarily complex, please let me know.
I'll write up anything useful I discover along the way.
P.S. I'm taking over one of Henry Qian's roles at Amperion
From: Michael Renzmann <madwifi@no...> - 2005-12-14 08:48:57
On Thu, 2005-11-17 at 17:18 -0500, Jeff Vandegrift wrote:
> d. add MadWiFi from the CVS branch (assumed to be more stable
> than NG)
You're asking for madwifi-old, which you should get out of our
Subversion repository rather than out of the old CVS. madwifi-old has
seen some changes which are not available in CVS.