Search Linux Wireless

Re: [PATCH v2 5/5] cfg80211: allow beaconing after DFS CAC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6 November 2013 11:11, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote:
> On Tue, 2013-11-05 at 14:48 +0100, Janusz Dziedzic wrote:
>> After going throught the Channel Availability Check (CAC)
>> required by DFS enable beaconing. Channels that have
>> gone through a CAC will be in the NL80211_DFS_AVAILABLE
>> state. Without this change APs don't start beaconing
>> after a successful CAC.
>> Change also cfg80211_secondary_chans_ok() where handle
>> prohibited_flags as prohibited.
>
> I can't really understand this commit message - can you please rephrase
> it?
>

Allow beaconing after we pass Channel Availability Check (CAC).
Allow non-DFS and DFS channels mix. All DFS channels have to
be in NL80211_DFS_AVAILABLE state (have to pass CAC).

BR
Janusz
--
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




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux