On Tue, Dec 21, 2010 at 5:53 AM, Johannes Berg
<johannes@xxxxxxxxxxxxxxxx> wrote:
> On Mon, 2010-12-20 at 12:02 -0500, Luis R. Rodriguez wrote:
>> This grants drivers access to the DFS region that a
>> regulatory domain belongs to.
>>
>> Signed-off-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx>
>> ---
>> Âinclude/net/regulatory.h | Â Â5 +++++
>> Ânet/wireless/reg.c    |  Â4 ++++
>> Â2 files changed, 9 insertions(+), 0 deletions(-)
>>
>> diff --git a/include/net/regulatory.h b/include/net/regulatory.h
>> index 9fcb603..3ed16c5 100644
>> --- a/include/net/regulatory.h
>> +++ b/include/net/regulatory.h
>> @@ -40,6 +40,10 @@ enum environment_cap {
>> Â * Â 99 - built by driver but a specific alpha2 cannot be determined
>> Â * Â 98 - result of an intersection between two regulatory domains
>> Â * Â 97 - regulatory domain has not yet been configured
>> + * @dfs_region: If CRDA responded with a regulatory domain that requires
>> + * Â DFS master operation on a known DFS region (NL80211_CFLAG_DFS_*),
>> + * Â dfs_region represents that region. Drivers can use this and the
>> + * Â @alpha2 to adjust their device's DFS parameters as they wish.
>
> The alpha2 is pretty useless -- I don't think you should advocate using
> it. I think it can even be "99" or something at this point.
The alpha2 here is for the request, not what is set though.
Luis
--
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
