On Fri, Aug 12, 2011 at 02:30:28PM +0200, Johannes Berg wrote: > On Wed, 2011-08-10 at 23:55 +0300, Jouni Malinen wrote: > > The NL80211_CMD_NEW_BEACON command is, in practice, requesting AP mode > > operations to be started. Add new attributes to provide extra IEs > > (e.g., WPS IE, P2P IE) for drivers that build Beacon, Probe Response, > > and (Re)Association Response frames internally (likely in firmware). > > Out of curiosity, how would such a driver implement WPS to start with? These new attributes are provided to allow that to be done easily, i.e., the driver will request the firmware to add the extra IEs (WPS/P2P IE) to the frames that need them. Whenever the IEs change, a _SET_BEACON command is used to update the IE contents (just like we do with the full Beacon template). I'm assuming here that the driver (or well, firmware) is building rest of the IEs both based on internal knowledge of the channel and security policy (the newly added attributes). This is similar to how WPS is normally run with many drivers that use private WEXT ioctls and the new attributes allow them to move to nl80211 more easily. -- 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
