All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janusz Dziedzic <janusz.dziedzic@tieto.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "wireless-regdb@lists.infradead.org"
	<wireless-regdb@lists.infradead.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless-regdb: add DFS CAC time parameter
Date: Tue, 20 May 2014 15:26:48 +0200	[thread overview]
Message-ID: <CALhHN=rLpBt-aTNDSbO6BO-TwFYuHf79=rpsTetysBrW_D47cA@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6UuZFDLdA-KW=ohaFwXjj_3wSY84cj3-KPO7HoKREPHOA@mail.gmail.com>

On 20 May 2014 09:33, Luis R. Rodriguez <mcgrof@do-not-panic.com> wrote:
> On Fri, May 9, 2014 at 1:40 AM, Janusz Dziedzic
> <janusz.dziedzic@tieto.com> wrote:
>> Introduce support for setting DFS CAC time
>> in milliseconds.
>>
>> Eg.
>> (5250 - 5330 @ AUTO), (20), (60000), DFS
>>
>> will setup CAC 60 seconds CAC time.
>
> Can you elaborate whether or not this will require a bump on CRDA  and
> issuing of two new wireless-regdb files for the different versions on
> the commit log?
>
Yes, sure - will add this.

BTW, probably you know, why we decide to split usermode regulatory
code into crda, regdb? This required binary interface between them and
a lot of "not needed" code? Why we don't simply zip/sign db.tx code
and parse this direrctly in crda and use just one user mode project
for that.
What was the reason for have regulatory in binary file?

BR
Janusz

WARNING: multiple messages have this Message-ID (diff)
From: Janusz Dziedzic <janusz.dziedzic@tieto.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	"wireless-regdb@lists.infradead.org"
	<wireless-regdb@lists.infradead.org>
Subject: Re: [wireless-regdb] [PATCH] wireless-regdb: add DFS CAC time parameter
Date: Tue, 20 May 2014 15:26:48 +0200	[thread overview]
Message-ID: <CALhHN=rLpBt-aTNDSbO6BO-TwFYuHf79=rpsTetysBrW_D47cA@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6UuZFDLdA-KW=ohaFwXjj_3wSY84cj3-KPO7HoKREPHOA@mail.gmail.com>

On 20 May 2014 09:33, Luis R. Rodriguez <mcgrof@do-not-panic.com> wrote:
> On Fri, May 9, 2014 at 1:40 AM, Janusz Dziedzic
> <janusz.dziedzic@tieto.com> wrote:
>> Introduce support for setting DFS CAC time
>> in milliseconds.
>>
>> Eg.
>> (5250 - 5330 @ AUTO), (20), (60000), DFS
>>
>> will setup CAC 60 seconds CAC time.
>
> Can you elaborate whether or not this will require a bump on CRDA  and
> issuing of two new wireless-regdb files for the different versions on
> the commit log?
>
Yes, sure - will add this.

BTW, probably you know, why we decide to split usermode regulatory
code into crda, regdb? This required binary interface between them and
a lot of "not needed" code? Why we don't simply zip/sign db.tx code
and parse this direrctly in crda and use just one user mode project
for that.
What was the reason for have regulatory in binary file?

BR
Janusz

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


  reply	other threads:[~2014-05-20 13:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09  8:40 [PATCH] wireless-regdb: add DFS CAC time parameter Janusz Dziedzic
2014-05-09  8:40 ` [wireless-regdb] " Janusz Dziedzic
2014-05-09  8:40 ` [PATCH] crda: add DFS CAC time support Janusz Dziedzic
2014-05-09  8:40   ` [wireless-regdb] " Janusz Dziedzic
2014-05-20  7:33 ` [PATCH] wireless-regdb: add DFS CAC time parameter Luis R. Rodriguez
2014-05-20  7:33   ` [wireless-regdb] " Luis R. Rodriguez
2014-05-20 13:26   ` Janusz Dziedzic [this message]
2014-05-20 13:26     ` Janusz Dziedzic
2014-05-20 14:24   ` John W. Linville
2014-05-20 14:24     ` [wireless-regdb] " John W. Linville
2014-05-20 18:01     ` Janusz Dziedzic
2014-05-20 18:01       ` [wireless-regdb] " Janusz Dziedzic
2014-05-20 18:08       ` John W. Linville
2014-05-20 18:08         ` [wireless-regdb] " John W. Linville
2014-05-20 18:24         ` Johannes Berg
2014-05-20 18:24           ` [wireless-regdb] " Johannes Berg
2014-05-20 18:48           ` Luis R. Rodriguez
2014-05-20 18:48             ` [wireless-regdb] " Luis R. Rodriguez
2014-05-21 16:03             ` Johannes Berg
2014-05-21 16:03               ` [wireless-regdb] " Johannes Berg
2014-05-21 18:00               ` John W. Linville
2014-05-21 18:00                 ` [wireless-regdb] " John W. Linville
2014-05-21 19:09                 ` Johannes Berg
2014-05-21 19:09                   ` [wireless-regdb] " Johannes Berg
2014-06-09  7:33                   ` Janusz Dziedzic
2014-06-09  7:33                     ` [wireless-regdb] " Janusz Dziedzic
2014-06-10 16:45                     ` Johannes Berg
2014-06-10 16:45                       ` [wireless-regdb] " Johannes Berg
2014-06-09  8:00               ` Felix Fietkau
2014-06-09  8:00                 ` [wireless-regdb] " Felix Fietkau
2014-06-09 10:22                 ` Janusz Dziedzic
2014-06-09 10:22                   ` [wireless-regdb] " Janusz Dziedzic
2014-06-09 12:27                   ` Janusz Dziedzic
2014-06-09 12:27                     ` [wireless-regdb] " Janusz Dziedzic
2014-06-10 16:46                 ` Johannes Berg
2014-06-10 16:46                   ` [wireless-regdb] " Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2014-02-12 18:54 [PATCH 1/4] cfg80211: regulatory, introduce DFS CAC time Janusz Dziedzic
2014-02-12 18:54 ` [PATCH] wireless-regdb: add DFS CAC time parameter Janusz Dziedzic

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='CALhHN=rLpBt-aTNDSbO6BO-TwFYuHf79=rpsTetysBrW_D47cA@mail.gmail.com' \
    --to=janusz.dziedzic@tieto.com \
    --cc=linux-wireless@vger.kernel.org \
    --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 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.