On 25 June 2014 19:34, Ben Greear <greearb at candelatech.com> wrote: > On 06/25/2014 10:20 AM, Luis R. Rodriguez wrote: >> On Wed, Jun 25, 2014 at 9:48 AM, Ben Greear <greearb at candelatech.com> wrote: >>> I started trying to do some more DFS testing on a 3.14.8+ kernel, >>> and from what I can tell, the US region is configured for >>> DFS-Unset. I was assuming this should be set to DFS_FCC. >>> >>> I tried installing the latest regulatory.bin. crda is whatever >>> is standard on Fedora 19. >>> >>> Do you know if DFS is supposed to work at all in the 3.14 kernel? >> >> DFS region support was added upstream via 8b60b07805 >> >> mcgrof at ergon ~/linux (git::master)$ git describe --contains 8b60b07805 >> v3.3-rc1~182^2~44^2~384 >> >> Now, that doesn't mean a driver will have DFS support of course. I'm >> not going to treasure hunt that for you. > > The driver (ath10k) works, and if I manually force the 'US' regulatory domain > to use DFS-FCC in set_regdom in reg.c, then it shows up as DFS-FCC in 'iw reg get' > and hostapd & driver properly detects radar since airport is nearby, hostapd > chooses a different channel, and things go on working. > >>> I'm certain I had this working earlier on this machine, >>> but I was on a somewhat patched linux.ath tree at the >>> time it seems.... >> >> There's an issue Krishna reported about internal db now parsing the >> new db.txt format properly after the antenna gain removal but a patch >> is supposed to be on the way. You don't seem to be using that though >> so you may want to debug things a bit further. > > Is the 'regulatory.bin' from today's wireless-regdb repository > correct? I did not try regenerating it..I just did a git pull... > Best get latest regdb, crda: wireless-regd/ make; make install crda/ make ; make install (skip warning about world regulatory domain - I think we will fix this soon). Next: modprobe cfg80211 iw reg set US dmesg (check reg messages) iw reg get You should get correct DFS region. BR Janusz
