Hi,
The version of madwifi in debian is *not* madwifi-ng, it is from the
madwifi-old branch. It is totally working correctly with the
wpasupplicant package in debian.
Since the old driver is not supported anymore, is less stable than
the new one, lacks some features and does not work with newer cards,
the madwifi team urges most users to switch to the new driver.
Huh! This is absolutely not true.
I am responsible for madwifi in debian (along with team members) and
also heavily involved with upstream development and support of madwifi.
Tonight I asked in irc if these facts are correct:-
<kelmo_lap> otaku42, did you make a public anouncement about
distributions adopting the madwifi-ng code?
<otaku42> kelmo_lap: not yet, apart from what i've replied in one or two
mails on the lists.
<kelmo_lap> someone states this:
<kelmo_lap> Since the old driver is not supported anymore, is less
stable than the new
<kelmo_lap> one, lacks some features and does not work with newer cards,
the madwifi
<kelmo_lap> team urges most users to switch to the new driver.
<otaku42> kelmo_lap: that's new to me. do you have a chance to ask the
person where this information comes from?
<kelmo_lap> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354388
otaku42 is Michael Renzmann, the Madwifi project leader.
madwifi-ng is *not* as stable as madwifi-old. Yes it does support more
stuff, but that is not the point. wpasupplicant is compatible with the
madwifi package provided by debian. When madwifi-ng is tagged as "stable
for distributions to use" by the majority of the Madwifi developers, I
will organise the upload of it, and make sure wpasupplicant is updated
with the relevant headers (unless someone thinks of a better solution).
madwifi-old *is* supported, I even applied a maintenance patch to it
recently. However, it is not currently developed any further, only bugs
are fixed.
Out of curiosity, does madwifi-ng not implement WE19 completely? If
it does, then it should work with the 'wext' interface of wpasupplicant.
madwifi-ng does not use the wext driver ioctl's, but its own, btw :-)
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
