On Thu, 2011-03-31 at 18:49 -0700, Thomas Pedersen wrote: > NL80211_CMD_GET_WIPHY now returns a flag NL80211_SUPPORT_MESH_AUTH if > the wiphy's mesh implementation supports routing of mesh auth frames to > userspace. This is useful for forward compatibility between old kernels > and new userspace tools. Patch looks good, but you should check whether mesh auth is supported in join_mesh when it is requested, and refuse otherwise, so that we force drivers to correctly advertise it. > Thanks for your comments, I've tried to implement the necessary changes below. > wiphy->flags now gets a WIPHY_FLAG_MESH_AUTH flag in case the mesh > implementation supports routing of mesh auth frames to userspace. If you know > of a better place to put this (rdev maybe?), please let me know. Also, it would > be nice if all you have is the ifindex; not having to send a command to > nl80211, parse the response, then get the wiphy index so you can request > capabilities from the stack. I'd like to be able to get capabilities directly > from an interface, should this happen in CMD_GET_MESH_CONFIG, > CMD_GET_INTERFACE, or maybe somewhere else? iw can't do this because it overloads the command line, but in nl80211 you can always use an ifindex instead of a wiphy index to identify a device. johannes -- 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
