ath10k: set channel by command "iw" not from hostapd and DFS support of firmware-2.bin_10.1.467.2-1

[Bartosz Markowski]

On 16 May 2014 10:03, Vu Hai NGUYEN <vh.nguyen at actiasodielec.fr> wrote:
>>> Seems CONFIG_ATH10K_DFS_CERTIFIED is not set.
>>> You can simply check this during compilation adding eg. to mac.c
>>> #ifndef CONFIG_ATH10K_DFS_CERTIFIED
>>> #error DFS_NOT_SET
>>> #endif
>
> I'm quite sure that CONFIG_ATH10K_DFS_CERTIFIED is enabled because the 3 debug file dfs_block_radar_events, dfs_simulate_radar, dfs_stats is
> only created if CONFIG_ATH10K_DFS_CERTIFIED=y ? And I had these 3 files in my folder debug fs but "dfs_stats" show "DFS not enabled"
>
>>> I am not sure but could be if you kernel is old and didn't have this
>>> option (which is available in backports) then will  be not set.
>>> @Bartosz didn't we have same problem, do you remember how this was solved?
>
>>I assume you are using backports, right? I think I hit something
>>similar when I was compiling my own backports package (under openwrt).
>>The backports were generated from ath.git. I think the root cause for
>>me those days was outdated .local-symbols file from the backports and
>>lack of 'ATH10K_DFS_CERTIFIED=' there (I 'mixed' the original
>>comapt-wireless from openwrt and my own backports). But I have no idea
>>if you are facing something similar, since I do not know your build setup..
>
> Yes I'm using backport v3.15 (latest) to build ath10k for my kernel 3.2.36 (provided by Marvell for my Marvell Armada 370 chipset).
> I also download the folder ath from ath10k master branch (I got problem with seeing information of fw_stats from the version ath10k in backport).
> Any suggestion? Please feel free to ask me more information if you need :D

Did you just replace it under your backports folder? Maybe you still
have CONFIG_ATH10K_DFS_CERTIFIED instead of
CPTCFG_ATH10K_DFS_CERTIFIED there?

-- 
Bartosz