On Thu, 2011-09-08 at 17:39 +0300, Victor Goldenshtein wrote:
> > No, I don't think you can advertise wiphy.flags since those flags are
> > internal -- you'll have to map single wiphy flags to single capability
> > flags which are also defined in nl80211.h.
> >
> > I'd call it "NL80211_ATTR_CAPABILITIES" to sidestep the issue of it
> > being a driver of HW or whatever capability.
> Sorry, I'm not sure that I'm entirely understand, you mean to create
> *nested* "NL80211_ATTR_CAPABILITIES" attribute which will contain all
> new capability flags, mapped from wiphy.flags? and to do it within
> existing nl80211_send_wiphy() function?
No, I mean just add a U32 NL80211_ATTR_CAPABILITIES and put new flags
there, like this in nl80211.h:
enum nl80211_device_capabilities {
NL80211_DEV_CAPA_XXX = (1<<0);
etc...
};
Just don't use wiphy.flags directly since that's internal flags.
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
