Return-path: Received: from he.sipsolutions.net ([78.46.109.217] helo=sipsolutions.net) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1Tfyjw-000210-Bn for wireless-regdb@lists.infradead.org; Tue, 04 Dec 2012 20:05:13 +0000 Received: by sipsolutions.net with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Tfyju-0006Uw-Sj for wireless-regdb@lists.infradead.org; Tue, 04 Dec 2012 21:05:11 +0100 Message-ID: <1354651535.9608.22.camel@jlt4.sipsolutions.net> From: Johannes Berg Date: Tue, 04 Dec 2012 21:05:35 +0100 In-Reply-To: <1354651410.9608.21.camel@jlt4.sipsolutions.net> References: <1354648499.9608.19.camel@jlt4.sipsolutions.net> <1354651357.9608.20.camel@jlt4.sipsolutions.net> <1354651410.9608.21.camel@jlt4.sipsolutions.net> Mime-Version: 1.0 Subject: Re: [wireless-regdb] [PATCH] dbparse: remove usable bandwidth check List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: wireless-regdb-bounces@lists.infradead.org Errors-To: wireless-regdb-bounces+johannes=sipsolutions.net@lists.infradead.org Content-Transfer-Encoding: 8bit To: wireless-regdb@lists.infradead.org List-ID: On Tue, 2012-12-04 at 21:03 +0100, Johannes Berg wrote: > On Tue, 2012-12-04 at 21:02 +0100, Johannes Berg wrote: > > On Tue, 2012-12-04 at 20:14 +0100, Johannes Berg wrote: > > > From: Johannes Berg > > > > > > The kernel uses the bandwidth this way: any frequency > > > rule that is required for any of the 20 MHz subchannels > > > of a given channel must allow the total bandwidth. > > > Therefore, this check is wrong -- a frequency rule may > > > need to be specified with higher bandwidth than it has > > > to allow to form e.g. HT40 out of subchannels. > > > > This patch, and the other patch, are because we currently interpret the > > rules this way: > > > > http://johannes.sipsolutions.net/files/chans-old.pdf > > Let me attach that for the archives ... And give an example :-) HT40+ on channel 9 uses the range covered by channels 9 and 13. Channel 13 falls into the second freqband, so that must have @40 because in the kernel we currently check that any freqband that is required for channel 9 or 13 (in this example) allows enough bandwidth for the whole channel. johannes _______________________________________________ wireless-regdb mailing list wireless-regdb@lists.infradead.org http://lists.infradead.org/mailman/listinfo/wireless-regdb