On Fri, 2008-09-05 at 12:43 -0700, Luis R. Rodriguez wrote: > This adds the new wireless regulatory infrastructure. The > main motiviation behind this was to centralize regulatory > code as each driver was implementing their own regulatory solution, > and to replace the initial centralized code we have where: > > * only 3 regulatory domains are supported: US, JP and EU > * regulatory domains can only be changed through a module parameter > * all rules are built statically in the kernel > > We now have support for regulatory domains for many countries > and regulatory domains are now queried through a userspace agent > (CRDA) through udev allowing distributions to update regulatory rules > without updating the kernel. Updates on regulatory rules can > now be left as an independent effort. > > Each driver can regulatory_hint() a regulatory domain > based on either their EEPROM mapped regulatory domain value to a > respective ISO/IEC 3166-1 country code or pass an internally built > regulatory domain. We also add support to let the user set the > regulatory domain through userspace in case of faulty EEPROMs to > further help compliance. > > Support for world roaming will be added soon for cards capable of > this. > > For more information see: > > http://wireless.kernel.org/en/developers/Regulatory/CRDA > > For now we leave an option to enable the old module parameter, > ieee80211_regdom, and to build the 3 old regdomains statically > (US, JP and EU). This option is CONFIG_WIRELESS_OLD_REGULATORY. > These old static definitions and the module parameter is being > scheduled for removal for 2.6.29. > > Signed-off-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> Looks fine to me now, as far as I've looked, I guess there'll be some odd fixes required etc. but we can figure that out. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
