Search Linux Wireless

Re: Problems with regulatory domain support and BCM43224

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

 



On Thu, Mar 8, 2012 at 11:07 AM, Quan, David <dquan@xxxxxxxxxxxxxxxx> wrote:
> 1) Depending on which WW sku number you selected, it may and may not support the DFS channels. So this is not true that we do not support DFS channels in WW mode.

David, sorry I should have clarified, this is not for ath9k. This is
for other drivers which do not have custom regulatory domains nor do
they have any regulatory hint obtainable from their EEPROM. For those
cards that do not have anything like this we make them use the world
regulatory domain by default.

> 2) Today, I do not believe ath9k code supports DFS detection. If that is what you mean. Therefore STA mode will not support DFS detection. However, STA does support DFS channels. DFS channel support vs DFS detection support is two different things. DFS channel support as a slave device, only has to do passive scanning.
>
> Let me know if that answers your questions.

It does, but would like your advice / review on the idea of enabling
DFS channels as passive scan, no-ibss (or any radiation enabled) for
cards that use the static default world regulatory domain in the
kernel. This would not in any way affect ath9k, ath6kl, or any of our
cards, but just help other cards that do not have anything
implemented.

  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


[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