On Fri, Mar 28, 2014 at 01:18:32PM -0400, Bruce Ashfield wrote: > On Fri, Mar 28, 2014 at 1:13 PM, Denys Dmytriyenko <de...@denix.org> wrote: > > On Wed, Mar 26, 2014 at 11:42:39AM -0300, Otavio Salvador wrote: > >> Hello Kai, > >> > >> On Wed, Mar 26, 2014 at 7:15 AM, Kai Kang <kai.k...@windriver.com> wrote: > >> > Replace ocf-linux with cryptodev-linux because linux-yocto use > >> > cryptodev-linux to implement /dev/crypto. > >> > >> Thanks for handling it; I was going to address same issue this week so > >> we could have it upstreamed and drop the Freescale bbappends for it. > > > > So, we also have a recipe of cryptodev for TI builds. But it's not just a > > header file and we need the actual module to be built and packaged... > > As long as something out of tree can co-exist with in-tree implementations, > I don't see a problem with an incremental update that builds the module > as well.
Thanks. So, I already have cryptodev-tests as a separate recipe that builds some tests from the same source, as main cryptodev. I guess I can look into separating module part into cryptodev-module recipe, which can be optional for kernels like linux-yocto that have it already patched in. Will that work? -- Denys -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
