Search Linux Wireless

Re: Getting random regulatory domains on boot-up with ath9k

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

 



On Fri, Nov 6, 2009 at 8:21 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote:

>  * The fix for the regression would be to either use an alpha2 which
> does have an entry and put that first in the array *or* (my
> preference) to check first the alpha2 set on cfg80211 and see if that
> maps to a country allowed by your region code and if so get cfg80211
> to request that regulatory domain to CRDA.

I just thought of another possible solution for region code stuff --
just make them static world roaming regulatory domains. But to do this
it means we'd enable the world roaming features on cfg80211 and
channels which would typically be disabled would then just become
passive-scan/no-ibss. I'd have to get buy-in through our internal
regulatory guys first. This also seems like a clean solution but it
would mean more static tables define for each major region code we
have and I am not sure how many of those we have.

  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 Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux