On Thu, 2009-08-13 at 18:46 +0800, Jouni Malinen wrote: > It is not about whether it would be possible to use connect or not; it > is about whether the additional features provided by separate auth/assoc > commands are of use--and they are. wpa_supplicant will provide more > functionality, e.g., FT, when using these commands. Any change to add > support for the new NL80211_CMD_CONNECT must not break this existing > mechanism; it is only to add support for drivers that cannot support the > auth/assoc interface that provides more control to user space. Ah, I see. This makes sense to me. I ignored the 11r code when I wrote the code. Now I realized what it is used for (i.e. sme_event_auth). I'm not sure if it can be done in cfg80211 SME easily, but it doesn't help for connect API anyway. I'll send V2 according to your suggestion. Johannes, I think we need a way in cfg80211 to tell connect vs. auth/assoc. The current capability method (nl80211_send_wiphy) cannot do this. For example, if (dev->ops->connect || dev->ops->auth) NLA_PUT_U32(msg, i, NL80211_CMD_CONNECT); We need to either make NL80211_CMD_CONNECT only depends on ops->connect or make NL80211_CMD_AUTH depends on ops->auth. Johannes, which one do you prefer? Thanks, -yi -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
