From: Denys Dmytriyenko <denis@denix.org>
To: Kai Kang <kai.kang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] cryptodev-linux: add recipe
Date: Fri, 28 Mar 2014 13:11:11 -0400 [thread overview]
Message-ID: <20140328171111.GH3370@denix.org> (raw)
In-Reply-To: <a1ff6a91da21f19e5365114dca7ae942803efcd6.1395825881.git.kai.kang@windriver.com>
On Wed, Mar 26, 2014 at 06:15:57PM +0800, Kai Kang wrote:
> Yocto kernel linux-yocto uses cryptodev-linux to use device /dev/crypto.
> So add cryptodev-linux which is one alternative of ocf-linux and then
> remove ocf-linux later.
Quick question - is it native-only recipe? Does it expect cryptodev module to
be patched into kernel? Is this what the above description implies -
"linux-yocto uses cryptodev-linux"?
From the looks of it, the recipe only installs a header and doesn't even build
the out-of-tree module for cryptodev, that cryptodev-linux provides...
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> .../openssl/cryptodev-linux_1.6.bb | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
> create mode 100644 meta/recipes-connectivity/openssl/cryptodev-linux_1.6.bb
>
> diff --git a/meta/recipes-connectivity/openssl/cryptodev-linux_1.6.bb b/meta/recipes-connectivity/openssl/cryptodev-linux_1.6.bb
> new file mode 100644
> index 0000000..320716d
> --- /dev/null
> +++ b/meta/recipes-connectivity/openssl/cryptodev-linux_1.6.bb
> @@ -0,0 +1,22 @@
> +SUMMARY = "A /dev/crypto device driver"
> +HOMEPAGE = "http://cryptodev-linux.org/"
> +
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> +
> +SRC_URI = "http://download.gna.org/cryptodev-linux/${BPN}-${PV}.tar.gz"
> +
> +SRC_URI[md5sum] = "eade38998313c25fd7934719cdf8a2ea"
> +SRC_URI[sha256sum] = "75f1425c8ea1f8cae523905a5a046a35092327a6152800b0b86efc4e56fb3e2f"
> +
> +do_compile() {
> + :
> +}
> +
> +# Just install cryptodev.h which is the only header file needed to be exported
> +do_install() {
> + install -D ${S}/crypto/cryptodev.h ${D}${includedir}/crypto/cryptodev.h
> +}
> +
> +ALLOW_EMPTY_${PN} = "1"
> +BBCLASSEXTEND = "native nativesdk"
> --
> 1.8.1.2
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2014-03-28 17:11 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 [this message]
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
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=20140328171111.GH3370@denix.org \
--to=denis@denix.org \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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