On Fri, Sep 05, 2008 at 07:33:14PM -0700, Marcel Holtmann wrote: > can we get a small document in Documentation/ that describes what has to > be done for CRDA. That would help to ease the adaption and would allow > us to point people to it. Nothing fancy, but some quick notes where to > find it and what to put where. Sure, I'm putting this together now. > > 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. > > Do we have an example for all the possible ways? I think about something > to help driver maintainers to move over and use the infrastructure the > right way. The only case I didn't test was the case for Intel's drivers, all other drivers would use regulatory_hint() based on an alpha2 and that worked swell. I found some issues with the case of providing a built regulatory domain so I'm updating it now and am also updating some other parts of the code for the old regulatory infrastructure, it seems there were a few obvious issues we didn't catch there yet. I hope to have the new doc for you with a few fixes and an example as to what Intel drivers can do soon. I was hoping to get it all done by today but that didn't happen. 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
