On Tue, Mar 30, 2010 at 4:41 AM, Krzysztof Halasa <khc@xxxxxxxxx> wrote: > "Luis R. Rodriguez" <mcgrof@xxxxxxxxx> writes: > >>> So what exactly do I change? Can the regulatory.bin change the default >>> country? >> >> Huh? >> >>> Remember I need to be compliant to the US freq sets as well - when the >>> regdomain is set to US. IOW I can't allow the user operating the device >>> to set e.g. channel 12 when the user selects country=US (so there is a >>> big difference between country 0=US and the real country=US). >> >> Huh? > > Not sure what do you mean. Are my expectations unrealistic? > >>> But the driver says: >>> ath: EEPROM regdomain: 0x0 >>> ath: EEPROM indicates default country code should be used >>> ath: doing EEPROM country->regdmn map search >>> ath: country maps to regdmn code: 0x3a >>> ath: Country alpha2 being used: US >>> ath: Regpair used: 0x3a >>> >>> At least for the driver 0 doesn't mean US, it means "default country". >>> Perhaps the meaning of "default country" depends on maybe location of >>> the hw and/or sw manufacturer? >> >> I just pointed to some documentation for you which indicated 0x0 means >> "US". > > Yes, but the meaning depends on the POV. What is important to me is what > does that mean to a) the software I use, b) the hardware I use (cards). > The driver doesn't say 0=US, perhaps it should? Then things would be > very different. My point was that this is not something meant to be interpreted by anyone for what "default country" means, the documentation I pointed out clearly states that 0x0 is designed to mean to match the "US" by Atheros hardware as per hardware documentation provided to ODMs. 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
