On Sun, 2011-04-10 at 19:16 +0100, Anton Ivanov wrote: > On 04/10/11 16:23, Stefan Lippers-Hollmann wrote: > > Hi > > > > On Sunday 10 April 2011, Anton Ivanov wrote: > > > >> On 04/10/11 00:55, Ben Hutchings wrote: > >> > >>> On Fri, 2011-04-08 at 13:39 +0100, Anton Ivanov wrote: > >>> > > [...] > > > >>>> ath driver ignores reg domain setting passed via cfg80211 and uses one > >>>> from EEPROM instead. This setting a lot of cheap cards is CN. As a result > >>>> the reg domain is set incorrectly (and for some countries illegally). > >>>> > > [...] > > > >>> What do you mean by 'passed via cfg80211'? Are you setting the > >>> ieee80211_regdom module parameter? > >>> > > [...] > > > >> Yes. No effect. ath still reads from eeprom. > >> > > The EEPROM settings are authoritative, you can only restrict the > > regulatory settings further to aid regulatory compliance in different > > regions, but never relax them. Tools like crda always intersect the > > EEPROM's (OTP in newer chipset generations) with the chosen regulatory > > domain as provided by wireless-regdb or the in-kernel regdb; regulatory > > hints like IEEE 802.11d may also restrict the allowed frequencies even > > further. > > > > http://wireless.kernel.org/en/users/Drivers/ath#Regulatory > > > > This is intended beaviour and required for FCC compliance (keep in mind > > that calibration data is also only validated for the given regdomain), > > not a bug. > > > > So a card that returns only CN from EEPROM is basically intended to be > sold _ONLY_ in China. Right? Yes. It is probably illegal to sell these cards in some countries. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part