On Fri, 26 Aug 2005 11:07:07 -0400, Michael Wu wrote: > http://aluminum.sourmilk.net/adm8211/index.php?path=netdev/
Looks good for the first view. Unfortunately I won't have enough time to look closely until next week. > - adm8211 supports shared key authentication, rtl8180-sa2400 only supports > open authentication. (which is kinda okay when you consider that 802.11i > doesn't use shared key) > - Both drivers do not support LEAP authentication. > - adm8211 supports WE18/WPA (partly via SIWGENIE, it doesn't generate WPA/RSN > IEs itself) > - rtl8180-sa2400 supports a really simple master mode. (should something like > hostapd be used instead for master mode?) > - rtl8180-sa2400 supports sending probe responses. adm8211 lets the hardware > do it, though newer adm8211 cards can be told to hand it off to the software. > - rtl8180-sa2400 creates a completely random bssid in adhoc. adm8211 keeps > the > first 3 octets from the MAC addr. > - adm8211 supports sending & handling deauthentication and disassociation > frames. I did not see definitions for those frames, so I assume there's no > support there. > - adm8211 needs many hooks in scanning/authentication/association to set > BSSID/SSID/AID/etc. in hardware. > - rtl8180-sa2400 doesn't seem to convert to little endian in a number of > places. (not really major..) Many thanks for the comparison. You mentioned problem with hooks in scanning/association/etc. Probably everybody involved in this discussion knows it but I think it is worth saying it: This is one of the most important things in a new ieee80211 layer. Unfortunately, it seems that every driver developer concentrates on the aspects of his device (this include ieee80211 layer from ipw as well as from rtl8180). But every device (or more precisely firmware) provides different set of features - some takes care of almost everything, other can do basic things only. So the amount of work that needs to be done in the ieee80211 layer is different for different devices. The layer has to be generic. It has to cope e.g. with authentication/association performed fully by itself as well as with auth/assoc performed automatically by the device, etc. I'm convinced this is the first goal we have to reach before we start to implement WPA, QoS and so. -- Jiri Benc SUSE Labs - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
