From: Darren Hart <dvhart@linux.intel.com>
To: Yashpal Dutta <yashpal.dutta@freescale.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] cryptodev kernel module recipe
Date: Thu, 18 Oct 2012 16:16:47 -0400 [thread overview]
Message-ID: <508063AF.9030400@linux.intel.com> (raw)
In-Reply-To: <1350554279-8975-1-git-send-email-yashpal.dutta@freescale.com>
On 10/18/2012 05:57 AM, Yashpal Dutta wrote:
> This is a /dev/crypto device driver, equivalent to those in OpenBSD or FreeBSD.
> The main idea is to access of existing ciphers in kernel space from userspace,
> thus enabling re-use of a hardware implementation of a cipher.
>
> Signed-off-by: Yashpal Dutta <yashpal.dutta@freescale.com>
> ---
> meta/recipes-kernel/cryptodev/cryptodev_1.5.bb | 18 +++++++++++++
> .../cryptodev/files/makefile_fixup.patch | 26 ++++++++++++++++++++
> 2 files changed, 44 insertions(+), 0 deletions(-)
> create mode 100644 meta/recipes-kernel/cryptodev/cryptodev_1.5.bb
> create mode 100644 meta/recipes-kernel/cryptodev/files/makefile_fixup.patch
>
> diff --git a/meta/recipes-kernel/cryptodev/cryptodev_1.5.bb b/meta/recipes-kernel/cryptodev/cryptodev_1.5.bb
> new file mode 100644
> index 0000000..5125710
> --- /dev/null
> +++ b/meta/recipes-kernel/cryptodev/cryptodev_1.5.bb
> @@ -0,0 +1,18 @@
> +SECTION = "devel"
> +SUMMARY = "Linux Cryptodev KERNEL MODULE"
> +DESCRIPTION = "The Cryptodev package contains the kernel /dev/crypto module"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> +
> +DEPENDS = "virtual/kernel"
This DEPENDS in inherited from the module.bbclass, no need to duplicate
> +
> +inherit module
> +
> +SRCREV = "1c24a0aa996630518d47826a2e3fea129ea094c7"
> +
> +SRC_URI = "git://repo.or.cz/cryptodev-linux.git;protocol=git \
> + file://makefile_fixup.patch"
Tabs to indent, spaces to align. Spaces here please.
> +
> +EXTRA_OEMAKE='KERNEL_DIR="${STAGING_KERNEL_DIR}" PREFIX="${D}"'
modules.bbclass already sets KERNEL_PATH and KERNEL_SRC, perhaps you
could use one of those?
If you just use ${includedir} in your install I believe you can skip
PREFIX here and get the /usr part right there.
> +
> +S = "${WORKDIR}/git"
> diff --git a/meta/recipes-kernel/cryptodev/files/makefile_fixup.patch b/meta/recipes-kernel/cryptodev/files/makefile_fixup.patch
> new file mode 100644
> index 0000000..323aacd
> --- /dev/null
> +++ b/meta/recipes-kernel/cryptodev/files/makefile_fixup.patch
> @@ -0,0 +1,26 @@
> +diff --git a/Makefile b/Makefile
> +index 2be8825..b36d68c 100644
> +--- a/Makefile
> ++++ b/Makefile
> +@@ -1,6 +1,7 @@
> + KBUILD_CFLAGS += -I$(src)
> + KERNEL_DIR = /lib/modules/$(shell uname -r)/build
> + VERSION = 1.5
> ++PREFIX =
> +
> + cryptodev-objs = ioctl.o main.o cryptlib.o authenc.o zc.o util.o
> +
> +@@ -12,10 +13,10 @@ build: version.h
> + version.h: Makefile
> + @echo "#define VERSION \"$(VERSION)\"" > version.h
> +
> +-install:
> ++modules_install:
> + make -C $(KERNEL_DIR) SUBDIRS=`pwd` modules_install
Current kernels recommend using M= instead of SUBDIRS=:
SRC := $(shell pwd)
make -C $(KERNEL_SRC) M=$(SRC) modules_install
See the hello-mod example in meta-skeleton/recipes-kernel/hello-mod for
a minimal example.
> +- @echo "Installing cryptodev.h in /usr/include/crypto ..."
> +- @install -D crypto/cryptodev.h /usr/include/crypto/cryptodev.h
> ++ @echo "Installing cryptodev.h in $(PREFIX)/usr/include/crypto ..."
> ++ @install -D crypto/cryptodev.h $(PREFIX)/usr/include/crypto/cryptodev.h
Use ${includedir} here
> +
> + clean:
> + make -C $(KERNEL_DIR) SUBDIRS=`pwd` clean
>
M=
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2012-10-18 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 9:57 [PATCH] cryptodev kernel module recipe Yashpal Dutta
2012-10-18 6:14 ` Khem Raj
[not found] ` <DD178F3D66989248ABAC4C14253F477F11E36C@039-SN2MPN1-021.039d.mgd.msft.net>
2012-10-18 6:35 ` Khem Raj
2012-10-18 19:59 ` Darren Hart
2012-10-18 20:06 ` McClintock Matthew-B29882
2012-10-18 20:21 ` Darren Hart
2012-10-18 13:33 ` Bruce Ashfield
2012-10-30 18:50 ` McClintock Matthew-B29882
2012-10-31 17:11 ` Bruce Ashfield
2012-10-31 19:21 ` McClintock Matthew-B29882
2012-10-18 20:16 ` Darren Hart [this message]
2012-10-18 20:33 ` McClintock Matthew-B29882
2012-10-18 20:38 ` Darren Hart
2012-10-19 1:47 ` McClintock Matthew-B29882
2012-10-19 9:43 ` Andreas Oberritter
2012-10-19 14:45 ` Khem Raj
2012-10-30 18:53 ` McClintock Matthew-B29882
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=508063AF.9030400@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yashpal.dutta@freescale.com \
/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