From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Seth Forshee <seth.forshee@canonical.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
wireless-regdb@lists.infradead.org,
Jean-Pierre TOSONI <jp.tosoni@acksys.fr>
Subject: Re: [wireless-regdb] CAC time syntax in regdb.txt
Date: Mon, 30 Mar 2015 23:10:18 +0200 [thread overview]
Message-ID: <20150330211018.GU5622@wotan.suse.de> (raw)
In-Reply-To: <1427702614.26117.1.camel@sipsolutions.net>
On Mon, Mar 30, 2015 at 10:03:34AM +0200, Johannes Berg wrote:
> On Thu, 2015-03-26 at 21:42 +0100, Luis R. Rodriguez wrote:
>
> > This would require generating two binary files and supporting that. This was
> > never done. We could also try to somehow mesh both versions together with one
> > larger file that has both and try to remain compatible. That's the ideal
> > solution IMHO.
>
> Given the file format, I don't think this will be possible.
>
> > Instead of sticking to CRDA updates to rely on this for support what we really
> > need to do is mesh in CRDA support upstream into the kernel since the kernel
> > now supports the cryptographic needs that CRDA had. I was planning on doing
> > this during the upcoming Hackweek at SUSE but if anyone else wants to try that
> > before please feel free.
>
> And given that we want this direction anyway, I'm not sure that the
> multi-file-format CRDA solution will really be economical.
>
> For the kernel, we should probably define an extensible file format
> anyway, and then just do it once.
Ack. I can try to address both then during Hackweek unless someone wants
to jump on it sooner.
Luis
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2015-03-30 21:10 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
2015-03-26 20:42 ` Luis R. Rodriguez
2015-03-30 8:03 ` Johannes Berg
2015-03-30 21:10 ` Luis R. Rodriguez [this message]
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=20150330211018.GU5622@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=johannes@sipsolutions.net \
--cc=jp.tosoni@acksys.fr \
--cc=mcgrof@do-not-panic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox