Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Armin Kuster <akuster@mvista.com>
Subject: Re: [meta-networking][PATCH] netmap: add new package
Date: Thu, 30 Jul 2015 17:26:54 -0700	[thread overview]
Message-ID: <55BAC0CE.4030101@gmail.com> (raw)
In-Reply-To: <20150729145808.GB12478@jama>


Martin,


On 07/29/2015 07:58 AM, Martin Jansa wrote:
> On Wed, Jul 22, 2015 at 08:08:13PM -0700, Armin Kuster wrote:
>> From: Armin Kuster <akuster@mvista.com>
>>
>> this adds netmap, the fast packet I/O framework
>> http://info.iet.unipi.it/~luigi/netmap/
>
> Fails to build on jenkins log in:
> http://errors.yoctoproject.org/Errors/Build/7660/
>

I have a lame typo in the configure parameter that my local build didn't 
show. As I try this on other arch's it is barfing in other areas.

I am going to traveling for the next two weeks so you can remove this or 
black list it until I can resolve the issues. I do hate cause you more work.

my apologizes,
Armin
>>
>> Signed-off-by: Armin Kuster <akuster@mvista.com>
>> ---
>>   .../recipes-kernel/netmap/netmap-modules_git.bb    | 33 ++++++++++++++++++++++
>>   meta-networking/recipes-kernel/netmap/netmap.inc   | 14 +++++++++
>>   .../recipes-kernel/netmap/netmap_git.bb            | 32 +++++++++++++++++++++
>>   3 files changed, 79 insertions(+)
>>   create mode 100644 meta-networking/recipes-kernel/netmap/netmap-modules_git.bb
>>   create mode 100644 meta-networking/recipes-kernel/netmap/netmap.inc
>>   create mode 100644 meta-networking/recipes-kernel/netmap/netmap_git.bb
>>
>> diff --git a/meta-networking/recipes-kernel/netmap/netmap-modules_git.bb b/meta-networking/recipes-kernel/netmap/netmap-modules_git.bb
>> new file mode 100644
>> index 0000000..63ca50f
>> --- /dev/null
>> +++ b/meta-networking/recipes-kernel/netmap/netmap-modules_git.bb
>> @@ -0,0 +1,33 @@
>> +require netmap.inc
>> +
>> +DEPENDS = "virtual/kernel"
>> +do_configure[depends] += "virtual/kernel:do_shared_workdir"
>> +
>> +inherit module
>> +
>> +COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips|arm).*-linux'
>> +
>> +CLEANBROKEN = "1"
>> +
>> +export INSTALL_MOD_DIR="kernel/netmap-modules"
>> +
>> +EXTRA_OECONF = "--kernel-dir=${STAGING_KERNEL_BUILDDIR} \
>> +                --kernel-sources=${STAGING_KERNEL_DIR} \
>> +                --install-mod-path=${D} \
>> +                --driver-suffix="-netmap" \
>> +                "
>> +
>> +do_configure () {
>> +    cd ${S}/LINUX
>> +    ./configure ${EXTRA_OECONF}
>> +}
>> +
>> +do_compile () {
>> +    cd ${S}/LINUX
>> +    make
>> +}
>> +
>> +do_install () {
>> +    cd ${S}/LINUX
>> +    oe_runmake install
>> +}
>> diff --git a/meta-networking/recipes-kernel/netmap/netmap.inc b/meta-networking/recipes-kernel/netmap/netmap.inc
>> new file mode 100644
>> index 0000000..4a101a1
>> --- /dev/null
>> +++ b/meta-networking/recipes-kernel/netmap/netmap.inc
>> @@ -0,0 +1,14 @@
>> +SUMMARY = "netmap and VALE - very fast packet I/O from userspace (FreeBSD/Linux)"
>> +DESCRIPTION= "NETMAP is a framework for very fast packet I/O from userspace.  VALE is an equally fast in-kernel software switch using the netmap API.  Both are implemented as a single kernel module for FreeBSD and Linux, and can deal with line rate on real or emulated 10 Gbit ports."
>> +SECTION = "networking"
>> +HOMEPAGE = "http://code.google.com/p/netmap/"
>> +LICENSE = "GPLv2+"
>> +
>> +LIC_FILES_CHKSUM = "file://README;beginline=13;endline=14;md5=f64f2b172fe6903ff7b6272c6edde588"
>> +
>> +SRCREV = "a14a35b839fe7ab6855f25f1e86e306ee7ad8123"
>> +PV = "master+git${SRCPV}"
>> +
>> +SRC_URI = "git://github.com/luigirizzo/netmap.git"
>> +
>> +S = "${WORKDIR}/git"
>> diff --git a/meta-networking/recipes-kernel/netmap/netmap_git.bb b/meta-networking/recipes-kernel/netmap/netmap_git.bb
>> new file mode 100644
>> index 0000000..da80bad
>> --- /dev/null
>> +++ b/meta-networking/recipes-kernel/netmap/netmap_git.bb
>> @@ -0,0 +1,32 @@
>> +require netmap.inc
>> +
>> +DEPENDS = "netmap-modules"
>> +
>> +EXTRA_OECONF = "--kernel-dir=${STAGING_KERNEL_BUILDDIR} \
>> +                --kernel-sources=${STAGING_KERNEL_DIR} \
>> +                --install-mod-path=${D} \
>> +                --no-drivers \
>> +                --prefix=${prefix} \
>> +                --destir=${D} \
>> +                --cc='${CC}' \
>> +                --ld='${LD}' \
>> +                "
>> +
>> +do_configure () {
>> +    cd ${S}/LINUX
>> +    ./configure ${EXTRA_OECONF}
>> +}
>> +
>> +do_compile () {
>> +    cd ${S}/LINUX
>> +    make  apps
>> +}
>> +
>> +do_install () {
>> +    cd ${S}/LINUX
>> +    make install-apps DESTDIR=${D}
>> +}
>> +
>> +FILES_${PN} += "${bindir}"
>> +RDEPENDS_${PN} = "kernel-module-netmap"
>> +RRECOMMENDS_${PN} = "kernel-module-netmap"
>> --
>> 2.3.5
>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>
>


      reply	other threads:[~2015-07-31  0:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23  3:08 [meta-networking][PATCH] netmap: add new package Armin Kuster
2015-07-29 14:58 ` Martin Jansa
2015-07-31  0:26   ` akuster808 [this message]

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=55BAC0CE.4030101@gmail.com \
    --to=akuster808@gmail.com \
    --cc=akuster@mvista.com \
    --cc=openembedded-devel@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