On Thu, Aug 13, 2009 at 05:29:37PM +0800, Zhu Yi wrote: > The connect API wraps auth/assoc commands in cfg80211 SME. For example, > when cfg80211 receives NL80211_CMD_CONNECT (cfg80211_connect), it checks > if connect API is supported or not. If it is not supported (for all > mac80211 based drivers), it uses the common cfg80211_conn_do_work() to > do auth/assoc the same way as it handles NL80211_CMD_AUTHENTICATE. So > from user space point of view, if connect API is supported, it can use > it directly and let cfg80211 to maintain the state of auth and assoc. 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. -- Jouni Malinen PGP id EFC895FA -- 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
