From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 17:15:34 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42CFB106564A for ; Fri, 12 Dec 2008 17:15:34 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 083318FC1E for ; Fri, 12 Dec 2008 17:15:33 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id mBCHFVes086305 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Dec 2008 09:15:31 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49429C33.9030300@freebsd.org> Date: Fri, 12 Dec 2008 09:15:31 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Andrew Atrens References: <493418EA.7020602@freebsd.org> <4942879F.1040601@atrens.ca> In-Reply-To: <4942879F.1040601@atrens.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP: r185522 - in head: . share/man/man4 sys/amd64/conf sys/arm/conf sys/conf sys/contrib/dev/ath sys/dev/ath sys/dev/ath/ath_rate/amrr sys/dev/ath/ath_rate/onoe sys/dev/ath/ath_rate/sample ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 17:15:34 -0000 Andrew Atrens wrote: > Hi Sam, > > I'm noticing that regdomain support for 'FCCB' appears to be included > but is not hooked in to a countrycode yet. I've made the (very simple) > changes myself and the kernel appears to be sane though I haven't yet > attempted a connection at 10 or 5 Mhz, 20Mhz definitely still works .. > > $ ifconfig -v ath0 list channels > Channel 1 : 2412 Mhz 11b Channel 6 : 2437 Mhz 11g/10Mhz > Channel 1 : 2412 Mhz 11g Channel 6 : 2437 Mhz 11g/5Mhz > Channel 1 : 2412 Mhz 11g/10Mhz Channel 7 : 2442 Mhz 11b > Channel 1 : 2412 Mhz 11g/5Mhz Channel 7 : 2442 Mhz 11g > Channel 2 : 2417 Mhz 11b Channel 7 : 2442 Mhz 11g/10Mhz > Channel 2 : 2417 Mhz 11g Channel 7 : 2442 Mhz 11g/5Mhz > Channel 2 : 2417 Mhz 11g/10Mhz Channel 8 : 2447 Mhz 11b > Channel 2 : 2417 Mhz 11g/5Mhz Channel 8 : 2447 Mhz 11g > Channel 3 : 2422 Mhz 11b Channel 8 : 2447 Mhz 11g/10Mhz > Channel 3 : 2422 Mhz 11g Channel 8 : 2447 Mhz 11g/5Mhz > Channel 3 : 2422 Mhz 11g/10Mhz Channel 9 : 2452 Mhz 11b > Channel 3 : 2422 Mhz 11g/5Mhz Channel 9 : 2452 Mhz 11g > Channel 4 : 2427 Mhz 11b Channel 9 : 2452 Mhz 11g/10Mhz > Channel 4 : 2427 Mhz 11g Channel 9 : 2452 Mhz 11g/5Mhz > Channel 4 : 2427 Mhz 11g/10Mhz Channel 10 : 2457 Mhz 11b > Channel 4 : 2427 Mhz 11g/5Mhz Channel 10 : 2457 Mhz 11g > Channel 5 : 2432 Mhz 11b Channel 10 : 2457 Mhz 11g/10Mhz > Channel 5 : 2432 Mhz 11g Channel 10 : 2457 Mhz 11g/5Mhz > Channel 5 : 2432 Mhz 11g/10Mhz Channel 11 : 2462 Mhz 11b > Channel 5 : 2432 Mhz 11g/5Mhz Channel 11 : 2462 Mhz 11g > Channel 6 : 2437 Mhz 11b Channel 11 : 2462 Mhz 11g/10Mhz > Channel 6 : 2437 Mhz 11g Channel 11 : 2462 Mhz 11g/5Mhz > Channel 6 : 2437 Mhz 11g Turbo > > Since it appears that everything is in place to support it, I'm > curious whether there is some technical or regulatory/legal reason > that this hasn't yet been done .. > > I'm not sure of all of the tradeoffs of 5Mhz/10Mhz channels @2GHz, I > know that one downside is that likely only ofdm modulations will work, > an obvious one is that you'd lose half the bandwidth. > > On the positive side I suspect (as is the case for 900Mhz) one's noise > immunity may change (improve?), and perhaps my signal may get a bit > more 'punch' as on the access side I'm firing through a fair bit of > foliage. > FCCB was added solely for testing 1/2 and 1/4 width channel support in 2.4G; hence the lack of a public hookup. I can't advise you on regulatory issues. Given the shortage of spectrum in the 2.4 band I can imagine folks doing outdoor applications might find this useful. Sam