If a wiphy-idx is specified, the kernel will return the wiphy specific regdomain, if such exists. Otherwise return the global regdom. When no wiphy-idx is specified, return the global regdomain as well as all wiphy-specific regulatory domains in the system, via a new nested list of attributes. Add a new attribute for each wiphy-specific regdomain, for usermode to identify it as such.
Showing the changes to include/uapi/linux (1 of 4 files). Show all
Unified · Split
| @@ -252,7 +252,15 @@ · 251 unmodified lines | ||
| 252 | 252 | * %NL80211_ATTR_IFINDEX. |
| 253 | 253 | * |
| 254 | 254 | * @NL80211_CMD_GET_REG: ask the wireless core to send us its currently set |
| 255 | − * regulatory domain. | |
| 255 | + * regulatory domain. If %NL80211_ATTR_WIPHY is specified and the device | |
| 256 | + * has a private regulatory domain, it will be returned. Otherwise, the | |
| 257 | + * global regdomain will be returned. | |
| 258 | + * A device will have a private regulatory domain if it uses the | |
| 259 | + * regulatory_hint() API. Even when a private regdomain is used the channel | |
| 260 | + * information will still be mended according to further hints from | |
| 261 | + * the regulatory core to help with compliance. A dump version of this API | |
| 262 | + * is now available which will returns the global regdomain as well as | |
| 263 | + * all private regdomains of present wiphys (for those that have it). | |
| 256 | 264 | * @NL80211_CMD_SET_REG: Set current regulatory domain. CRDA sends this command |
| 257 | 265 | * after being queried by the kernel. CRDA replies by sending a regulatory |
| 258 | 266 | * domain structure which consists of %NL80211_ATTR_REG_ALPHA set to our |