On 10/24/06, Anand Kumria <[EMAIL PROTECTED]> wrote:
On Mon, 23 Oct 2006 18:47:25 -0400, Luis R. Rodriguez wrote:> ieee80211_regdomains > > Breaks down regulatory domains into data structures which allow > drivers to share channel and power contraints based on stack > regulatory domain. This driver adds in-kernel support for common > regulatory domains (such as FCC and ETSI), makes updating the [snip] +/* Stack regulatory domain values. Atheros seems to have started this + * convention and most hardware vendors followed their example. + * Although these are *very* common we allow for a hw-specific + * map between stack and device regdomain values. */ +enum stack_regdomain { + REGDOMAIN_WORLD = 0x00, /* World compliance, minimum set */ + REGDOMAIN_FCC = 0x10, /* USA */ + REGDOMAIN_IC = 0x20, /* Canada */ + REGDOMAIN_ETSI = 0x30, /* Europe */ + REGDOMAIN_SPAIN = 0x31, /* Spain */ + REGDOMAIN_FRANCE = 0x32, /* France */ + REGDOMAIN_MKK = 0x40, /* Japan */ +}; + Why not pick either the country name or the organisation within the country that determines the frequency guidelines?
Ultimately I think this is the way this should work and this is why I provide a alpha3 country code --> stack regulatory domain map. Userpace should just let the user pick the country at say, distribution install time, and the map then used to determine the regulatory domain. Regulatory domains are what dictate the subband restrictions and as such these are ultimately what we need in the stack to decide what goes and what doesn't. Luis - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
