Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-31 Thread Bruce Ashfield
On Tue, Oct 30, 2012 at 2:50 PM, McClintock Matthew-B29882 b29...@freescale.com wrote: On Thu, Oct 18, 2012 at 8:33 AM, Bruce Ashfield bruce.ashfi...@gmail.com wrote: On Thu, Oct 18, 2012 at 5:57 AM, Yashpal Dutta yashpal.du...@freescale.com wrote: This is a /dev/crypto device driver,

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-31 Thread McClintock Matthew-B29882
On Wed, Oct 31, 2012 at 12:11 PM, Bruce Ashfield bruce.ashfi...@gmail.com wrote: On Tue, Oct 30, 2012 at 2:50 PM, McClintock Matthew-B29882 b29...@freescale.com wrote: On Thu, Oct 18, 2012 at 8:33 AM, Bruce Ashfield bruce.ashfi...@gmail.com wrote: On Thu, Oct 18, 2012 at 5:57 AM, Yashpal

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-30 Thread McClintock Matthew-B29882
On Thu, Oct 18, 2012 at 8:33 AM, Bruce Ashfield bruce.ashfi...@gmail.com wrote: On Thu, Oct 18, 2012 at 5:57 AM, Yashpal Dutta yashpal.du...@freescale.com 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

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-30 Thread McClintock Matthew-B29882
On Thu, Oct 18, 2012 at 3:16 PM, Darren Hart dvh...@linux.intel.com wrote: +++ 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 =

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-19 Thread Andreas Oberritter
On 19.10.2012 03:47, McClintock Matthew-B29882 wrote: On Thu, Oct 18, 2012 at 3:38 PM, Darren Hart dvh...@linux.intel.com wrote: +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?

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-19 Thread Khem Raj
On Fri, Oct 19, 2012 at 2:43 AM, Andreas Oberritter o...@opendreambox.org wrote: That's not an option for cryptodev, though, because unlike most recipes inheriting module.bbclass, cryptodev not only installs modules, but also header files. for such exceptions you can always use

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread Khem Raj
On Oct 18, 2012, at 2:57 AM, Yashpal Dutta yashpal.du...@freescale.com wrote: +-install: ++modules_install: + make -C $(KERNEL_DIR) SUBDIRS=`pwd` modules_install +-@echo Installing cryptodev.h in /usr/include/crypto ... +-@install -D crypto/cryptodev.h

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread Khem Raj
] cryptodev kernel module recipe On Oct 18, 2012, at 2:57 AM, Yashpal Dutta yashpal.du...@freescale.com wrote: +-install: ++modules_install: + make -C $(KERNEL_DIR) SUBDIRS=`pwd` modules_install +- @echo Installing cryptodev.h in /usr/include/crypto ... +- @install -D crypto

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread Bruce Ashfield
On Thu, Oct 18, 2012 at 5:57 AM, Yashpal Dutta yashpal.du...@freescale.com 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

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread Darren Hart
On 10/18/2012 02:14 AM, Khem Raj wrote: On Oct 18, 2012, at 2:57 AM, Yashpal Dutta yashpal.du...@freescale.com wrote: +-install: ++modules_install: +make -C $(KERNEL_DIR) SUBDIRS=`pwd` modules_install +- @echo Installing cryptodev.h in /usr/include/crypto ... +- @install -D

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread McClintock Matthew-B29882
On Thu, Oct 18, 2012 at 2:59 PM, Darren Hart dvh...@linux.intel.com wrote: On 10/18/2012 02:14 AM, Khem Raj wrote: On Oct 18, 2012, at 2:57 AM, Yashpal Dutta yashpal.du...@freescale.com wrote: +-install: ++modules_install: +make -C $(KERNEL_DIR) SUBDIRS=`pwd` modules_install +-

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread Darren Hart
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:

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread Darren Hart
On 10/18/2012 04:06 PM, McClintock Matthew-B29882 wrote: On Thu, Oct 18, 2012 at 2:59 PM, Darren Hart dvh...@linux.intel.com wrote: On 10/18/2012 02:14 AM, Khem Raj wrote: On Oct 18, 2012, at 2:57 AM, Yashpal Dutta yashpal.du...@freescale.com wrote: +-install: ++modules_install: +

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread McClintock Matthew-B29882
On Thu, Oct 18, 2012 at 3:16 PM, Darren Hart dvh...@linux.intel.com wrote: 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

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread Darren Hart
On 10/18/2012 04:33 PM, McClintock Matthew-B29882 wrote: On Thu, Oct 18, 2012 at 3:16 PM, Darren Hart dvh...@linux.intel.com wrote: 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

Re: [OE-core] [PATCH] cryptodev kernel module recipe

2012-10-18 Thread McClintock Matthew-B29882
On Thu, Oct 18, 2012 at 3:38 PM, Darren Hart dvh...@linux.intel.com wrote: +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? cryptodev Makefile does not use these it uses KERNEL_DIR in

[OE-core] [PATCH] cryptodev kernel module recipe

2012-10-17 Thread Yashpal Dutta
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.du...@freescale.com ---