Return-path: Received: from s3.sipsolutions.net ([144.76.43.152]:59814 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753138AbaBTH7S (ORCPT ); Thu, 20 Feb 2014 02:59:18 -0500 Message-ID: <1392883153.5073.4.camel@jlt4.sipsolutions.net> (sfid-20140220_085935_245625_6226F25B) Subject: Re: [PATCH] crda: handle AUTO bw setting in db2rd From: Johannes Berg To: Janusz Dziedzic Cc: "Luis R. Rodriguez" , Janusz Dziedzic , linux-wireless , "John W. Linville" Date: Thu, 20 Feb 2014 08:59:13 +0100 In-Reply-To: (sfid-20140220_085709_664222_A73B5F37) References: <1392226988-3878-1-git-send-email-janusz.dziedzic@tieto.com> <1392882691.5073.3.camel@jlt4.sipsolutions.net> (sfid-20140220_085709_664222_A73B5F37) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, 2014-02-20 at 08:57 +0100, Janusz Dziedzic wrote: > >> Yes, seems we should send this even this is 0. > >> Next for old kernel, all channels where BW=0 will be HT20 only. > > > > Is that really a good idea? > > > > Maybe crda should just get the logic to determine maximum bandwidth, > > like you did in the kernel, and then we can even revert the kernel code > > again? > > > Yes, this is possible to calculate this in crda (or even set this manually). Ok. Would that help older kernels? How would we handle genregdb.awk? johannes