From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 8 13:31:30 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E88E106566B; Mon, 8 Aug 2011 13:31:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 06EF68FC13; Mon, 8 Aug 2011 13:31:29 +0000 (UTC) Received: by vws18 with SMTP id 18so2667301vws.13 for ; Mon, 08 Aug 2011 06:31:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=csc12jsJsRVrzGDSwkAZmyPgTLQj5Tkma4Mwnl+betg=; b=mXzx55RV9FzAojYXniBfZWoeR2aKOLjBI/c960lg4C81QMdh0DhUQiYEkHkWzYp1LY rQXJymIA9zBOkUNwfiyO2u5eXhSG84K/avVeIoentyf38qXLVz9m4CSQ4lO+1hXCehoa 6LVIKyKXP+Ot2QU+5A/n/ynfusM6Gta12ypM4= MIME-Version: 1.0 Received: by 10.52.94.139 with SMTP id dc11mr3513467vdb.28.1312810289304; Mon, 08 Aug 2011 06:31:29 -0700 (PDT) Received: by 10.52.157.193 with HTTP; Mon, 8 Aug 2011 06:31:29 -0700 (PDT) In-Reply-To: <201108081525.21563.bschmidt@freebsd.org> References: <201108081525.21563.bschmidt@freebsd.org> Date: Mon, 8 Aug 2011 21:31:29 +0800 Message-ID: From: Adrian Chadd To: bschmidt@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFQ] net80211 regulatory changes: what I'd like to see before 9.0-RELEASE X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2011 13:31:30 -0000 On 8 August 2011 21:25, Bernhard Schmidt wrote: > We've discussed this on IRC already, though to mention it again what I > > really like to get rid of is all the SKU stuff from the regdomain.xml. This > is > > specific to ath(4) and ath(4) only. Yup, I agree. ath/ath_hal can export a default country code for the given SKU. The only reason I'd maintain the SKU is so tools that currently expose that value keep working (ie, to read the EEPROM value from the NIC.) But it won't be used anywhere else for configuration/ > Using the isocc as the index is correct and really the way to go, but it > > might not serve some corner cases that well. Imagine someone wants > > to set a regdomain and not a country (we DO support this currently), > > how do want to express that in regdomain.xml? Adding a dummy isocc > > for each regdomain (FCC, ETSI, ..)? Maybe we should use (isocc,regdomain) > > as the index, so it is possible to use issoc=0,regdomain={FCC,ETSI,..} > > for the mentioned case. You'd just create or use a NONE ISOCC, and set your regulatory domain to whatever. The ISO CC is just a key to find a default regulatory domain. Some countries may share the same regulatory domain because they (for example) implement 100% of the USA FCC rules. But many won't, so I think we'll likely see something more like CRDA where each country gets enumerated. There'll also (for now) be custom SKUs/regulatory domains - specifically to drive the net80211ath/ath_hal GSM configuration (900mhz.) net80211 handles 900mhz frequencies. The SKU choice "tells" the ath/hal code to use the relevant channel mapping. That's the main reason I don't want to yet get rid of SKUs. I can worry about that part later. Adrian