On Sat, Nov 7, 2009 at 11:02 AM, Jeffrey Baker <jwbaker@xxxxxxxxx> wrote: > On Fri, Nov 6, 2009 at 8:21 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: >> On Fri, Nov 6, 2009 at 12:04 AM, Jeffrey Baker <jwbaker@xxxxxxxxx> wrote: >> So one way or another user intervention is required to alter current >> regulatory solutions. For Linux though the best solution *as an end >> user* to enable AP mode is not to alter wireless-regdb but instead to >> report your issue. In your case you have a non-trivial regression >> which does indeed need to be addressed. > > Thanks, your email(s) explained a great number of issues. I don't > have the expertise to contribute here, so I leave it in your capable > hands. I would say, however, that from the _user's_ perspective, the > best thing is if a wifi card bought in the USA from a USA retailer > automagically conformed to USA regulations, even if that's an issue to > be taken up with the card manufacturer and not with the driver > authors. Agreed, however how devices get programmed is a little complex than just a country code. So one option is to use a direct country code and that's it, another option is to use a world regulatory domain when you want to target a few countries and want to have passive scanning enabled -- typically business laptop SKUs. Then you have the region codes as your card has which is targetted for a few set of countries on a region, for example a european region code. What we have learned from implementing a solution on Linux is this wasn't easy to manage but that we can make it simpler. At Atheros at least we might stop using the region codes and just stick to the world roaming options and direct country codes. The Linux implementation we have done has helped to re-evaluate current implementations and has helped us adapt to better more reasonable solutions. These things just take time to change. 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
