Wireless-regdb Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Jean-Pierre TOSONI <jp.tosoni@acksys.fr>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] CAC time syntax in regdb.txt
Date: Thu, 26 Mar 2015 14:25:32 -0500	[thread overview]
Message-ID: <20150326192532.GB61113@ubuntu-hedt> (raw)
In-Reply-To: <773DB8A82AB6A046AE0195C68612A319019FF13E@sbs2003.acksys.local>

On Thu, Mar 26, 2015 at 06:19:02PM +0100, Jean-Pierre TOSONI wrote:
> Hi list,
> 
> I saw that the library in crda was updated to handle the CAC time.
> AFAICT the format is
>       (freq - freq @ bw), (eirp [mW]), [(CACtime)] [flags...]
> 
> but the conversion of the database from text format to bin format is
> still using a python script that crashes with this format.
> I used the
> https://git.kernel.org/cgit/linux/kernel/git/sforshee/wireless-regdb.git
> repo.
> 
> Is there an updated python script out there? Or a replacement tool? Or
> am I missing a something?

CRDA was updated to understand db.txt files with DFS CAC times, but the
binary format doesn't include them. The best that could be done then is
to make dbparse.py ignore CAC times. But the only purpose for the python
scripts is to convert wireless-regdb's db.txt to binary format, and it
would be a bit misleading to include CAC times in db.txt if they can't
be included in regulatory.bin. So I don't really see much of a point in
updating dbparse.py until the binary format supports CAC times.

Luis - Any thoughts? Are there plans to add DFS CAC times to the binary
format?

Seth

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


  reply	other threads:[~2015-03-26 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 17:19 [wireless-regdb] CAC time syntax in regdb.txt Jean-Pierre TOSONI
2015-03-26 19:25 ` Seth Forshee [this message]
2015-03-26 20:42   ` Luis R. Rodriguez
2015-03-30  8:03     ` Johannes Berg
2015-03-30 21:10       ` Luis R. Rodriguez
2015-04-03  5:26         ` Janusz Dziedzic
2015-04-07  7:35           ` Jean-Pierre Tosoni

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=20150326192532.GB61113@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=jp.tosoni@acksys.fr \
    --cc=mcgrof@do-not-panic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox