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 <[email protected]>
> ---
>  .../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
> [email protected]
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to