From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from s3.sipsolutions.net ([5.9.151.49] helo=sipsolutions.net) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1YhkAD-0002G0-Dc for wireless-regdb@lists.infradead.org; Mon, 13 Apr 2015 19:36:58 +0000 Message-ID: <1428953793.2355.16.camel@sipsolutions.net> From: Johannes Berg Date: Mon, 13 Apr 2015 21:36:33 +0200 In-Reply-To: <20150413191818.GA3025@ubuntu-xps13> References: <000601d075fe$e10e0600$a32a1200$@acksys.fr> <20150413162317.GA21761@ubuntu-xps13> <1428951396.2355.15.camel@sipsolutions.net> <20150413191818.GA3025@ubuntu-xps13> Mime-Version: 1.0 Subject: Re: [wireless-regdb] [RFC] [PATCH] crda: enforce ETSI CAC timer of 600s on the weather band List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: "wireless-regdb" Errors-To: wireless-regdb-bounces+johannes=sipsolutions.net@lists.infradead.org Content-Transfer-Encoding: 8bit To: Seth Forshee Cc: Jean-Pierre Tosoni , "Luis R. Rodriguez" , wireless-regdb@lists.infradead.org List-ID: On Mon, 2015-04-13 at 14:18 -0500, Seth Forshee wrote: > On Mon, Apr 13, 2015 at 08:56:36PM +0200, Johannes Berg wrote: > > On Mon, 2015-04-13 at 11:23 -0500, Seth Forshee wrote: > > > On Mon, Apr 13, 2015 at 05:31:14PM +0200, Jean-Pierre Tosoni wrote: > > > > A really weird patch that splits the U-NII-2e band into 1, 2 or 3 > > > > sub-bands to enforce a CAC time of 10 minutes in the range 5600-5650 MHz. > > > > > > Wrong maintainer / list. CRDA patches should be directed to Luis and the > > > linux-wireless list (feel free to Cc wireless-regdb if you like). > > > > However, I'm not convinced that this actually *belongs* into the crda > > code? That seems like the wrong approach - shouldn't these rules be > > captured in the database? We do have AUTO-BW now so it should be > > possible, no? > > > > And if the timings aren't captured in the db.txt file they really should > > be. > > Yeah with AUTO-BW the bands could be broken up in db.txt, and we could > even put in the CAC times. But we still can't get the CAC times into the > current regulatory.bin format, so it doesn't really accomplish anything. But then there's also little point in putting any code for it into the crda binary, no? johannes _______________________________________________ wireless-regdb mailing list wireless-regdb@lists.infradead.org http://lists.infradead.org/mailman/listinfo/wireless-regdb