Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Replace ocf-linux with cryptodev-linux
Date: Fri, 28 Mar 2014 13:34:36 -0400	[thread overview]
Message-ID: <20140328173436.GK3370@denix.org> (raw)
In-Reply-To: <CADkTA4MxeTfzCY6YT4657jZy3btMN=wDDcUAaktzE=85SvunOA@mail.gmail.com>

On Fri, Mar 28, 2014 at 01:18:32PM -0400, Bruce Ashfield wrote:
> On Fri, Mar 28, 2014 at 1:13 PM, Denys Dmytriyenko <denis@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.kang@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


  reply	other threads:[~2014-03-28 17:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 10:15 [PATCH 0/3] Replace ocf-linux with cryptodev-linux Kai Kang
2014-03-26 10:15 ` [PATCH 1/3] cryptodev-linux: add recipe Kai Kang
2014-03-26 14:40   ` Otavio Salvador
2014-03-28 17:11   ` Denys Dmytriyenko
2014-03-26 10:15 ` [PATCH 2/3] openssl: replace dependency ocf-linux with cryptodev-linux Kai Kang
2014-03-26 10:15 ` [PATCH 3/3] ocf-linux: remove recipe Kai Kang
2014-03-26 14:42 ` [PATCH 0/3] Replace ocf-linux with cryptodev-linux Otavio Salvador
2014-03-28  3:03   ` Kang Kai
2014-03-28 17:13   ` Denys Dmytriyenko
2014-03-28 17:18     ` Bruce Ashfield
2014-03-28 17:34       ` Denys Dmytriyenko [this message]
2014-03-28 17:42         ` Bruce Ashfield
2014-03-28 17:22     ` Richard Purdie
2014-03-28 17:37       ` Denys Dmytriyenko
2014-03-28  9:50 ` Richard Purdie
2014-03-31  3:02   ` Kang Kai

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=20140328173436.GK3370@denix.org \
    --to=denis@denix.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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