All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jean-Pierre Tosoni <jp.tosoni@acksys.fr>,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [RFC] [PATCH] crda: enforce ETSI CAC timer of 600s on the weather band
Date: Mon, 13 Apr 2015 14:18:18 -0500	[thread overview]
Message-ID: <20150413191818.GA3025@ubuntu-xps13> (raw)
In-Reply-To: <1428951396.2355.15.camel@sipsolutions.net>

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.

Seth

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


  reply	other threads:[~2015-04-13 19:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 15:31 [wireless-regdb] [RFC] [PATCH] crda: enforce ETSI CAC timer of 600s on the weather band Jean-Pierre Tosoni
2015-04-13 16:23 ` Seth Forshee
2015-04-13 18:56   ` Johannes Berg
2015-04-13 19:18     ` Seth Forshee [this message]
2015-04-13 19:36       ` Johannes Berg
2015-04-13 19:54         ` Seth Forshee
2015-04-14  7:16           ` Johannes Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150413191818.GA3025@ubuntu-xps13 \
    --to=seth.forshee@canonical.com \
    --cc=johannes@sipsolutions.net \
    --cc=jp.tosoni@acksys.fr \
    --cc=mcgrof@suse.com \
    --cc=wireless-regdb@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.