Search Linux Wireless

RE: Problems with regulatory domain support and BCM43224

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

 



I think there is to it more than SW.
Where ever you get this card, is the card tested and regulatory approved for those countries, DFS or not?

It is possible that this card is only regulatory tested for non DFS channels, but now you enable them for passive. This means that yes, you are save and not violate DFS rules because you are in passive mode. However, you are in complete violation if the STA finds an AP on that DFS channel and then connects and transmits as this STA is not allow to transmit on that channel since it is not approved.

David


-----Original Message-----
From: mcgrof@xxxxxxxxx [mailto:mcgrof@xxxxxxxxx] On Behalf Of Luis R. Rodriguez
Sent: Thursday, March 08, 2012 11:36 AM
To: Quan, David
Cc: Seth Forshee; Green, Michael; linux-wireless@xxxxxxxxxxxxxxx; Johannes Berg
Subject: Re: Problems with regulatory domain support and BCM43224

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
��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f



[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