Re: ath/regd.c: regdomain 0x8000 fails to retrieve a regulatory domain pair

["Luis R. Rodriguez" <lrodriguez@atheros.com>]

On Thu, May 21, 2009 at 11:19:02AM -0700, Gábor Stefanik wrote:
> On Thu, May 21, 2009 at 7:16 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> >> On Mon, May 11, 2009 at 03:49:20AM -0700, Joerg Albert wrote:
> >> > Plugging in a WNDA3100 (ar9170usb) I get the error
> >> >
> >> > ath: No regulatory domain pair found, cannot continue
> >> >
> >> > Seems like the EEPROM of the stick initializes regulatory.current_rd
> >> > to 0x8000, current_rd_ext to 0. Is this a valid setting?
> >> >
> >> > Looked into ath/regd.c, ath_regd_init():
> >> >
> >> > ath_get_regpair(regdmn)
> >> >
> >> > is called with regdmn == 0x8000 and returns NULL.
> >> >
> >> > Shall that regdmn value be dealt with by
> >> >
> >> >          if (reg->country_code == CTRY_DEFAULT &&
> >> >              regdmn == CTRY_DEFAULT)
> >> >                  reg->country_code = CTRY_UNITED_STATES;
> >> > ?
> 
> Why CTRY_UNITED_STATES?

Well, that's just the way the regulatory infrastructure is designed, I suppose
that we inform vendors they can program their EEPROM with with 0x8000 as an
option to use CTRY_UNITED_STATES.

> Is there no CTRY_WORLD?

If (regdm & 0x60) then you have a world regualtory domain. Atheros devices
have 12 world regulatory domains today. They are all built-in to ath.ko.

> Or is 0x8000 US-specific?

That's what I believe.

  Luis