From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Janusz Dziedzic <janusz.dziedzic@tieto.com>,
"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: Mon, 09 Jun 2014 10:00:06 +0200 [thread overview]
Message-ID: <53956986.8070603@openwrt.org> (raw)
In-Reply-To: <1400688233.4136.8.camel@jlt4.sipsolutions.net>
On 2014-05-21 18:03, Johannes Berg wrote:
> On Tue, 2014-05-20 at 11:48 -0700, Luis R. Rodriguez wrote:
>
>> > I think we should, but if we can't then at least can we cut to an
>> > extensible format?
>
> I don't see any way to extend the format right now.
>
> There's a wrinkle with making it more extensible too though - if we do
> that then we must be extremely careful that future older crda versions
> (i.e. the next version that we're about to write) will not parse a newer
> extended file more permissively, so our extensions are limited anyway.
>
> Looks like the format update really is needed, which probably means we
> should change the scripts to generate two databases and change the
> filename, or so?
How about making the format properly extensible by reusing what we're
already doing to keep the kernel ABI stable? For example, we could store
the database in a netlink-like attribute format, with some changes to
make it fixed endian.
I'm already doing just that for a few things in OpenWrt, so I have
working C code for writing and parsing such a format.
Another nice feature would be to indicate in the attributes if crda is
required to understand them, or if it can just continue with a warning.
If done right, I think we can probably make this the last time we change
the format version.
- Felix
next prev parent reply other threads:[~2014-06-09 8:00 UTC|newest]
Thread overview: 19+ 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 ` [PATCH] crda: add DFS CAC time support Janusz Dziedzic
2014-05-20 7:33 ` [PATCH] wireless-regdb: add DFS CAC time parameter Luis R. Rodriguez
2014-05-20 13:26 ` Janusz Dziedzic
2014-05-20 14:24 ` John W. Linville
2014-05-20 18:01 ` Janusz Dziedzic
2014-05-20 18:08 ` John W. Linville
2014-05-20 18:24 ` Johannes Berg
2014-05-20 18:48 ` Luis R. Rodriguez
2014-05-21 16:03 ` Johannes Berg
2014-05-21 18:00 ` John W. Linville
2014-05-21 19:09 ` Johannes Berg
2014-06-09 7:33 ` Janusz Dziedzic
2014-06-10 16:45 ` Johannes Berg
2014-06-09 8:00 ` Felix Fietkau [this message]
2014-06-09 10:22 ` Janusz Dziedzic
2014-06-09 12:27 ` Janusz Dziedzic
2014-06-10 16:46 ` 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=53956986.8070603@openwrt.org \
--to=nbd@openwrt.org \
--cc=janusz.dziedzic@tieto.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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;
as well as URLs for NNTP newsgroup(s).