Hi Luis, > 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 module parameter > * all rules were 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 > through udev allowing distributions to update regulatory rules > without updating the kernel. > > 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. thanks for the write-up and examples. I like it a lot and gives driver maintainers a nice understanding what to do. While reading through it, I came to think about regulatory_hint(). So is there a use case where would give it the alpha2 code and the domain itself at the same time? If not, then it would make more sense to split this into two functions. Maybe something regulatory_alpha2_hint() and regulatory_domain_hint(). Just a thought. Regards Marcel -- 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
