All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Seth Forshee <seth.forshee@canonical.com>
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: Tue, 14 Apr 2015 09:16:06 +0200	[thread overview]
Message-ID: <1428995766.3019.0.camel@sipsolutions.net> (raw)
In-Reply-To: <20150413195426.GB3025@ubuntu-xps13>

On Mon, 2015-04-13 at 14:54 -0500, Seth Forshee wrote:

> > > 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?
> 
> Just to be clear, I'm not arguing for or against the patch at all. I'm
> only trying to explain why Jean-Pierre is proposing to change CRDA
> rather than db.txt. Maybe I should just let him speak for himself ...
> 
> As I understand it Jean-Pierre is looking for a stop-gap to get CAC
> times into the kernel until such time as we have a file format which
> allows getting them from regulatory.bin. Chaning CRDA can accomplish
> this, whereas modifying db.txt cannot.

Ah, yes, I got confused here. The regdb binary format doesn't support
it, but the kernel does.

johannes


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


      reply	other threads:[~2015-04-14  7:16 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
2015-04-13 19:36       ` Johannes Berg
2015-04-13 19:54         ` Seth Forshee
2015-04-14  7:16           ` Johannes Berg [this message]

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=1428995766.3019.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jp.tosoni@acksys.fr \
    --cc=mcgrof@suse.com \
    --cc=seth.forshee@canonical.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.