On 05/22/2014 09:50 AM, Ben Greear wrote: > Hello! > > I'm having issues where when we add several ath10k NICs to a system, > the regulatory domain goes quite restricted.. There is an ath9k NIC > with eeprom over-ride hack, and user-space sets regdomain to 'US'. > > Later, when registering ath10k, at least one of those NICs registeres > as 'TW'. The ending domain looks like this: > > [root@lf1011-13060017 ~]# iw reg get > country 98: DFS-UNSET > (2402 - 2472 @ 40), (N/A, 30) > (5270 - 5330 @ 40), (N/A, 17), DFS > (5735 - 5835 @ 80), (N/A, 30) > > > I tried adding a hack to ath10k to zero out the ar->ath_common.regulatory.current_rd, > but in fact it seems to be reported as zero to begin with. > > I am obviously missing something. Either my hacks to ath10k are not > sufficient, or possibly the system is getting regulatory info from > somewhere else? > > Any ideas where else it might be getting the idea it should be in TW > domain? Can it get this from beacons from other systems? Ahh, sneaky nasty code....it was being set based on the timezone of all things! Looks like you can override this behaviour with the command below if you are of a mind to do so: echo COUNTRY=US > /etc/sysconfig/regdomain Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- 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
