On Fri, Jul 2, 2010 at 9:48 AM, John W. Linville <linville@xxxxxxxxxxxxx> wrote: > On Fri, Jul 02, 2010 at 09:42:54AM -0700, Ben Greear wrote: >> On 07/02/2010 07:12 AM, John W. Linville wrote: > >> >The ath9k driver is setting its own regulatory restrictions based on >> >its EEPROM. Setting the domain from userland can only further restrict >> >the regulatory settings. The '98' value represents a synthesized >> >regulatory domain, based on the intersection of the available source >> >of regulatory information (which can include the EEPROM, the userland >> >setting, and a country IE from your AP). >> >> Is there any way to get/set these raw settings (like, whatever it has in EEPROM)? >> >> I expect we may ship some of these systems overseas, and would like the flexibility >> to set the country-code for testing purposes, if nothing else. > > I'll leave it to the Atheros guys to address this. Your "expectation" of having the freedom to modify the EEPROM is valid as I agree with it too but current legislation does not allow for it. So to support upstream drivers we just cannot allow for those type of changes. You won't get any support if you try to mess with that stuff unless we get a change in legislation that says otherwise. Please refer to: http://wireless.kernel.org/en/vendors/VendorSupport http://wireless.kernel.org/en/developers/Regulatory/statement http://wireless.kernel.org/en/developers/Regulatory Luis >> Is there any documentation as to what '98' really means, or do we just ignore that >> value and look at the info printed out after that? > > '98' pretty much means "look at the info" :-) Maybe userspace should be changed to interpret these. I'm on vacation right now though, patch welcomed for iw. 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
