2. And then if userspace sends a wiphy idx to the NL80211_CMD_GET_REG,
we'll return wiphy-regd for that case as well?
That's right, for now we'd be able to send the regd when either
NL80211_ATTR_WIPHY_SELF_MANAGED_REG is set or when
NL80211_ATTR_WIPHY_SELF_MANAGED_REG is not set but
On Wed, Nov 5, 2014 at 1:12 AM, Arik Nemtsov a...@wizery.com wrote:
On Wed, Nov 5, 2014 at 5:23 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov a...@wizery.com wrote:
+ * @NL80211_ATTR_WIPHY_SELF_MANAGED_REG: flag attribute indicating the
+
On Wed, Nov 5, 2014 at 5:23 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov a...@wizery.com wrote:
+ * @NL80211_ATTR_WIPHY_SELF_MANAGED_REG: flag attribute indicating the
+ * regulatory information came from the driver and not from the
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov a...@wizery.com wrote:
+ * @NL80211_ATTR_WIPHY_SELF_MANAGED_REG: flag attribute indicating the
+ * regulatory information came from the driver and not from the global
+ * cfg80211 regulatory domain information.
Awesome, can you also add
From: Jonathan Doron j...@wizery.com
Allow usermode to query wiphy-specific regd info, for drivers that use
wiphy-specific regulatory management.
Use the existing API for sending regdomain info to usermode, but return
the wiphy-specific regd in case wiphy index is provided and the driver
employs
