From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: 
 <wireless-regdb-bounces+johannes=sipsolutions.net@lists.infradead.org>
Received: from cantor2.suse.de ([195.135.220.15] helo=mx2.suse.de)
 by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux))
 id 1YcgxH-00029Q-Uj
 for wireless-regdb@lists.infradead.org; Mon, 30 Mar 2015 21:10:48 +0000
Date: Mon, 30 Mar 2015 23:10:18 +0200
From: "Luis R. Rodriguez" <mcgrof@suse.com>
Message-ID: <20150330211018.GU5622@wotan.suse.de>
References: <773DB8A82AB6A046AE0195C68612A319019FF13E@sbs2003.acksys.local>
 <20150326192532.GB61113@ubuntu-hedt>
 <20150326204221.GD5622@wotan.suse.de>
 <1427702614.26117.1.camel@sipsolutions.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <1427702614.26117.1.camel@sipsolutions.net>
Subject: Re: [wireless-regdb] CAC time syntax in regdb.txt
List-Unsubscribe: 
 <http://lists.infradead.org/mailman/options/wireless-regdb>, 
 <mailto:wireless-regdb-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/wireless-regdb/>
List-Post: <mailto:wireless-regdb@lists.infradead.org>
List-Help: <mailto:wireless-regdb-request@lists.infradead.org?subject=help>
List-Subscribe: 
 <http://lists.infradead.org/mailman/listinfo/wireless-regdb>, 
 <mailto:wireless-regdb-request@lists.infradead.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Sender: "wireless-regdb" <wireless-regdb-bounces@lists.infradead.org>
Errors-To: 
 wireless-regdb-bounces+johannes=sipsolutions.net@lists.infradead.org
Content-Transfer-Encoding: 8bit
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>
List-ID: <wireless-regdb@lists.infradead.org>

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