On Fri, 2013-02-15 at 09:56 +0100, Dennis H Jensen wrote:
> On Thu, 2013-02-14 at 16:40 +0100, Johannes Berg wrote:
> > On Thu, 2013-02-14 at 16:34 +0100, Johannes Berg wrote:
> > > From: Johannes Berg <johannes.berg@xxxxxxxxx>
> > >
> > > This adds support for the new split wiphy dump,
> > > it only uses it for "iw list", not for "info"
> > > though, so far. Using it for "info" would mean
> > > querying the kernel capability first and then
> > > using get/dump (with filter) depending on that.
> >
> > Dennis, are you up for implementing this in wpa_supplicant?
>
> Great, this will solve it. I can handle the wpa_supplicant; give me a
> couple of days to get it sorted.
FWIW, I think for wpa_s there are two possibilities:
1) simply always use NL_F_DUMP with NL80211_CMD_GET_WIPHY, and include
the filter & split attributes; this will mean on old kernels it will
retrieve information for all devices so you have to filter it
2) query the nl80211 global features first when initialising the
nl80211 sockets, and then use NL_F_DUMP with the filter only if the
feature is supported in the kernel
Both are about the same difficulty because for 2) you need the extra
feature command (once at init) while for 1) you need an extra command to
get the wiphy index for the device you care about for filtering. For 1)
that command would be NL80211_CMD_GET_INTERFACE.
> What's the procedure, do I post to both lists or just the hostap?
Just hostap is fine.
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
