Re: [meta-intel] Unable to build yocto for Intel Mohon Peak CRB
Hi Dhanasekar, The document that you are referring to is having the steps to build the BSP by using Yocto Project Dylan which is very old by now. Let’s me loop in Raymond who was supporting Intel comms platform. Let’s see whether the BSP has newer version that you should start with. BL From: Dhanasekar Jaganathan [mailto:jdhanasekar...@gmail.com] Sent: Thursday, August 2, 2018 7:20 PM To: Burton, Ross Cc: Ong, Boon Leong ; meta-intel@yoctoproject.org Subject: Re: [meta-intel] Unable to build yocto for Intel Mohon Peak CRB Hi Burton, After changing my host machine to ubuntu, I am not seeing "Permission denied" issue. Previously, I was working in Fedora host machine. Currently, I am getting below error, user@ubuntu:~/dhanasekar/yocto/poky/build$ bitbake core-image-sato-sdk Pseudo is not present but is required, building this first before the main build ERROR: Unable to parse conf/bitbake.conf: ParseError at /home/user/dhanasekar/yocto/poky/meta-intel/conf/machine/include/intel-corei7-64-common.inc:6: Could not include required file conf/machine/include/tune-corei7.inc For Atom CPU, Do you need tune-corei7.inc?. Please correct me if I am wrong. How to include "tun-corei7.inc" ? Thanks, Dhanasekar On Thu, Aug 2, 2018 at 3:44 AM, Burton, Ross mailto:ross.bur...@intel.com>> wrote: On 1 August 2018 at 15:13, Dhanasekar Jaganathan mailto:jdhanasekar...@gmail.com>> wrote: > OSError: [Errno 13] Permission denied: > '/home/server/Dhanasekar/Server-BIOS/yocto/poky/build/cache' For whatever reason you don't have permission to write to this folder, but the build can't even start without that. Check your permissions. Ross -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] OpenCV-3.0 integrate on yocto
Try http://layers.openembedded.org/layerindex/recipe/39865/ From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of vamsi krishna gattupalli Sent: Wednesday, January 13, 2016 9:41 PM To: meta-intel@yoctoproject.org Subject: [meta-intel] OpenCV-3.0 integrate on yocto Hi, Can anyone help how to integrate opencv-3.0 version in yocto. And how to get .bb files for opencv3.0 version. thanks, Vamsi -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [master & jethro][PATCH 0/2] Added support for dpdk v2.2.0
>> > -Original Message- >> > From: Wold, Saul >> > Sent: Thursday, December 31, 2015 3:06 AM >> > To: Gupta, Rahul KumarXX ; meta- >> > in...@yoctoproject.org >> > Cc: Wu, Chia Chuan >> > Subject: Re: [meta-intel] [master & jethro][PATCH 0/2] Added support >> > for dpdk v2.2.0 >> > >> > On Thu, 2015-12-31 at 00:01 +0800, Rahul Kumar Gupta wrote: >> > > Dear Maintainer(s), >> > > >> > > These two patches introduces the recipe to build dpdk v2.2.0. >> > > >> > Is there any reason we can not remove the older versions of DPDK >> > from master (and possibly jethro)? >> > >> > Are the older versions required to be kept? >> >> I will send out a separate patch to remove the older versions from >> master and Jethro. >> >It really should be part of the same patch, as a "git mv" to preserve as much >of >the git history of the original recipe as possible, at least that is the >practice in OE- >Core. Chia Chuan et. al. I suggest that you look into having dpdk_git.bb and a dpdk_.bb. That will benefit the community. Ya, older dpdk on master and potentially Jethro can be removed since they may not be needed for comms product line. Cheers -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 2/2] meta-isg: dpdk: fix v1.8.0 build with kernel 4.1
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of Anuj Mittal >Sent: Monday, October 5, 2015 10:02 PM >To: meta-intel@yoctoproject.org >Subject: [meta-intel] [PATCH 2/2] meta-isg: dpdk: fix v1.8.0 build with kernel >4.1 > >Backported fixes from upstream dpdk sources to ensure dpdk 1.8.0 compiles >against kernel 4.1. > >Signed-off-by: Anuj Mittal >--- > ...dpdk-1.8.0-kni-fix-build-with-kernel-3.19.patch | 69 + > ...cc-version-detection-to-permit-versions-n.patch | 149 > > .../common/recipes-extended/dpdk/dpdk_1.8.0.bb |9 +- > 3 files changed, 226 insertions(+), 1 deletion(-) create mode 100644 meta- >isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-kni-fix-build-with-kernel- >3.19.patch > create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk- >1.8.0-mk-rework-gcc-version-detection-to-permit-versions-n.patch > >diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-kni-fix- >build-with-kernel-3.19.patch b/meta-isg/common/recipes- >extended/dpdk/dpdk/dpdk-1.8.0-kni-fix-build-with-kernel-3.19.patch >new file mode 100644 >index 000..508a139 >--- /dev/null >+++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-kni-fix-buil >+++ d-with-kernel-3.19.patch >@@ -0,0 +1,69 @@ >+From 5f461166ffbdfff038c7fe118037bf50ad51e722 Mon Sep 17 00:00:00 2001 >+From: Pablo de Lara >+Date: Sun, 22 Mar 2015 18:02:16 + >+Subject: [PATCH] kni: fix build with kernel 3.19 >+ >+Upstream-Status: Backport [2.1.0] >+ >+Due to API changes in functions ndo_dflt_bridge_getlink (commit >+2c3c031c) and ndo_fdb_add (commit f6f6424b) in kernel 3.19, DPDK would >+not build. >+ >+This patch solves the problem, by checking the kernel version and >+adding the necessary new parameters. >+ >+Mind that function igb_ndo_fdb_add does not need the extra parameter if >+USE_CONST_DEV_UC_CHAR is not set, since that macro is only defined when >+kernel is greater or equal than 3.7 >+ >+Signed-off-by: Pablo de Lara >+Acked-by: Thomas Monjalon (cherry picked >+from commit 98f255ed0a4a73bf785e884dc2069405de840546) >+Signed-off-by: Rahul Kumar Gupta >+--- >+ lib/librte_eal/linuxapp/kni/ethtool/igb/igb_main.c | 7 +++ >+lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat.h | 4 >+ 2 files changed, 11 insertions(+) >+ >+diff --git a/lib/librte_eal/linuxapp/kni/ethtool/igb/igb_main.c >+b/lib/librte_eal/linuxapp/kni/ethtool/igb/igb_main.c >+index a802a02..24b147d 100644 >+--- a/lib/librte_eal/linuxapp/kni/ethtool/igb/igb_main.c > b/lib/librte_eal/linuxapp/kni/ethtool/igb/igb_main.c >+@@ -2103,6 +2103,9 @@ static int igb_set_features(struct net_device >+*netdev, static int igb_ndo_fdb_add(struct ndmsg *ndm, struct nlattr *tb[], >+ struct net_device *dev, >+ const unsigned char *addr, >++#ifdef HAVE_NDO_FDB_ADD_VID >++u16 vid, >++#endif >+ u16 flags) >+ #else >+ static int igb_ndo_fdb_add(struct ndmsg *ndm, @@ -2259,7 +2262,11 @@ >+static int igb_ndo_bridge_getlink(struct sk_buff *skb, u32 pid, u32 seq, >+ else >+ mode = BRIDGE_MODE_VEPA; >+ >++#ifdef HAVE_NDO_FDB_ADD_VID >++ return ndo_dflt_bridge_getlink(skb, pid, seq, dev, mode, 0, 0); #else >+ return ndo_dflt_bridge_getlink(skb, pid, seq, dev, mode); >++#endif /* HAVE_NDO_FDB_ADD_VID */ >+ } >+ #endif /* HAVE_BRIDGE_ATTRIBS */ >+ #endif /* NTF_SELF */ >+diff --git a/lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat.h >+b/lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat.h >+index 1213cc6..2e7e714 100644 >+--- a/lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat.h > b/lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat.h >+@@ -3881,4 +3881,8 @@ skb_set_hash(struct sk_buff *skb, __u32 hash, >+__always_unused int type) #define HAVE_VF_MIN_MAX_TXRATE 1 #endif /* >+>= 3.16.0 */ >+ >++#if ( LINUX_VERSION_CODE >= KERNEL_VERSION(3,19,0) ) #define >++HAVE_NDO_FDB_ADD_VID #endif /* >= 3.19.0 */ >++ >+ #endif /* _KCOMPAT_H_ */ >+-- >+1.9.1 >+ Back-port patch looks ok and can be found at http://www.dpdk.org/browse/dpdk/commit/?id=98f255ed0a4a73bf785e884dc2069405de840546 >diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-mk- >rework-gcc-version-detection-to-permit-versions-n.patch b/meta- >isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-mk-rework-gcc-version- >detection-to-permit-versions-n.patch >new file mode 100644 >index 000..032fed5 >--- /dev/null >+++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-mk-rework-gc >+++ c-version-detection-to-permit-versions-n.patch >@@ -0,0 +1,149 @@ >+From 8b1709d58a7015279161e4c61b4f22e06b8263d3 Mon Sep 17 00:00:00 >2001 >+From: Panu Matilainen >+Date: Mon, 23 Feb 2015 16:53:56 +0200 >+Subject: [PATCH] mk: rework gcc version detection to permit versions >+newer than 4.x >+ >+Upstream-Status: Backport [2.1.0] >+ >+Separately comparing major and minor versions become
Re: [meta-intel] [PATCH 1/2] meta-isg: dpdk: fix v2.0.0 build with kernel 4.1
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of Anuj Mittal
>Sent: Monday, October 5, 2015 10:02 PM
>To: meta-intel@yoctoproject.org
>Subject: [meta-intel] [PATCH 1/2] meta-isg: dpdk: fix v2.0.0 build with kernel
>4.1
>
>Backported fixes from upstream dpdk sources to ensure dpdk 2.0.0 compiles
>against kernel 4.1.
>
>Signed-off-by: Anuj Mittal
>---
> ...ix-a-build-warning-being-treated-as-error.patch | 45 +
> .../dpdk-2.0.0-kni-fix-build-with-kernel-4.0.patch | 58
> ...k-2.0.0-kni-fix-igb-build-with-kernel-4.1.patch | 70
> ...k-2.0.0-kni-net-fix-build-with-kernel-4.1.patch | 54 +++
> .../common/recipes-extended/dpdk/dpdk_2.0.0.bb |4 ++
> 5 files changed, 231 insertions(+)
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-
>1.8.0-and-2.0.0-ixgbe-fix-a-build-warning-being-treated-as-error.patch
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-
>2.0.0-kni-fix-build-with-kernel-4.0.patch
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-
>2.0.0-kni-fix-igb-build-with-kernel-4.1.patch
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-
>2.0.0-kni-net-fix-build-with-kernel-4.1.patch
>
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-
>ixgbe-fix-a-build-warning-being-treated-as-error.patch b/meta-
>isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-ixgbe-fix-a-build-
>warning-being-treated-as-error.patch
>new file mode 100644
>index 000..66edb1d
>--- /dev/null
>+++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-ix
>+++ gbe-fix-a-build-warning-being-treated-as-error.patch
>@@ -0,0 +1,45 @@
>+From b212cb3d806093399d51a49a6b4205a400cec510 Mon Sep 17 00:00:00
>2001
>+From: Rahul Kumar Gupta
>+Date: Thu, 1 Oct 2015 22:27:16 +0800
>+Subject: [PATCH] ixgbe: fix a build warning being treated as error
>+
>+Upstream-Status: Backport [2.1.0]
>+
>+Initialize the data byte to avoid warnings like:
>+
>+ lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c: In function
>'ixgbe_read_i2c_combined_generic':
>+ lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c:2101:9: error: 'low_bits' may be
>used
>+ uninitialized in this function [-Werror=maybe-uninitialized]
>+ *data |= bit << i;
>+^
>+ dpdk/2.0.0-r0/dpdk-2.0.0/lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c:120:5:
>note:
>+ 'low_bits' was declared here
>+ u8 low_bits;
>+ ^
>+ lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c:2101:9: error: 'high_bits' may be
>used
>+ uninitialized in this function [-Werror=maybe-uninitialized]
>+ *data |= bit << i;
>+^
>+ lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c:119:5: note: 'high_bits' was
>declared
>here
>+ u8 high_bits;
>+
>+Signed-off-by: Anuj Mittal
>+---
>+ lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c | 1 +
>+ 1 file changed, 1 insertion(+)
>+
>+diff --git a/lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c
>+b/lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c
>+index 2305448..4774adb 100644
>+--- a/lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c
> b/lib/librte_pmd_ixgbe/ixgbe/ixgbe_phy.c
>+@@ -2096,6 +2096,7 @@ STATIC s32 ixgbe_clock_in_i2c_byte(struct
>+ixgbe_hw *hw, u8 *data)
>+
>+ DEBUGFUNC("ixgbe_clock_in_i2c_byte");
>+
>++ *data = 0;
>+ for (i = 7; i >= 0; i--) {
>+ ixgbe_clock_in_i2c_bit(hw, &bit);
>+ *data |= bit << i;
>+--
>+1.9.1
You mentioned that this patch is back-ported from dpdk upstream.
I looked up in http://www.dpdk.org/browse/dpdk/log/ and search for
commit b212cb3d806093399d51a49a6b4205a400cec510 or author "Rahul Kumar Gupta",
http://www.dpdk.org/browse/dpdk/commit/?id=b212cb3d806093399d51a49a6b4205a400cec510
shows that the commit is bad commit reference.
Something looks very wrong here... where is this patch collected from?
It does not seem from dpdk upstream.
>+
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-kni-fix-
>build-with-kernel-4.0.patch b/meta-isg/common/recipes-
>extended/dpdk/dpdk/dpdk-2.0.0-kni-fix-build-with-kernel-4.0.patch
>new file mode 100644
>index 000..625f014
>--- /dev/null
>+++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-kni-fix-buil
>+++ d-with-kernel-4.0.patch
>@@ -0,0 +1,58 @@
>+From 54117da1c945c046c6e3959db81511c78f876426 Mon Sep 17 00:00:00
>2001
>+From: Pablo de Lara
>+Date: Tue, 28 Apr 2015 18:37:42 +0100
>+Subject: [PATCH] kni: fix build with kernel 4.0
>+
>+Upstream-Status: Backport [2.1.0]
>+
>+Due to API changes in function pointer ndo_bridge_setlink (commit
>+ad41faa8) and the rename of functions vlan_tx_* (commit df8a39de) in
>+kernel 4.0, DPDK would not build.
>+
>+This patch adds the properly checks to fix the compilation.
>+
>+Reported-by: Stephen Hemminger
>+Signed-off-by: Pablo de Lara
>+Signed-off-by: Anuj Mittal
>+---
>+ lib/librte_eal/li
Re: [meta-intel] [master][PATCH 0/3] meta-isg:relocate meta-crystalforest and update PREFERRED_VERSION of linux-yocto
>-Original Message- >From: Wu, Chia Chuan >Sent: Friday, October 2, 2015 7:29 PM >To: meta-intel@yoctoproject.org >Cc: Wu, Chia Chuan; Ong, Boon Leong >Subject: [meta-intel][master][PATCH 0/3] meta-isg:relocate meta- >crystalforest and update PREFERRED_VERSION of linux-yocto > >From: Wu Chia Chuan > >Dear Maintainer(s), > >This patch series relocate the meta-crystalforest layer from meta- >crystalforest to meta-isg/meta-crystalforest. >This is in support of BSP consoildation of all Intel platforms into meta-isg >layer. > >This patch series also update the PREFERRED_VERSION of linux-yocto-3.14 to >4.1 for MACHINES:crystalforest, >mohonpeak32 and mohonpeak64. > >I have build-tested for this patch series, please review and consider merging >into master branch if you don't have any concern on this patches. Saul, This what we discussed in PDT earlier. The team has checked the upgrade and sanity test on actual boards. Looks good. Thanks Ong Boon Leong -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [master][PATCH 3/3] meta-mohonpeak: update the PREFERRED_VERSION of linux-yocto-3.14 to 4.1
>-Original Message- >From: Wu, Chia Chuan >Sent: Friday, October 2, 2015 7:29 PM >To: meta-intel@yoctoproject.org >Cc: Wu, Chia Chuan; Ong, Boon Leong >Subject: [meta-intel][master][PATCH 3/3] meta-mohonpeak: update the >PREFERRED_VERSION of linux-yocto-3.14 to 4.1 > >From: Wu Chia Chuan > >Update the PREFERRED_VERSION of linux-yocto-3.14 to 4.1 for >mohonpeak32 and mohonpeak64 machines. > >Signed-off-by: Wu Chia Chuan Acked-by: Ong Boon Leong -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [master][PATCH 2/3] meta-crystalforest: update the PREFERRED_VERSION of linux-yocto-3.14 to 4.1
>-Original Message- >From: Wu, Chia Chuan >Sent: Friday, October 2, 2015 7:29 PM >To: meta-intel@yoctoproject.org >Cc: Wu, Chia Chuan; Ong, Boon Leong >Subject: [meta-intel][master][PATCH 2/3] meta-crystalforest: update the >PREFERRED_VERSION of linux-yocto-3.14 to 4.1 > >From: Wu Chia Chuan > >Update the PREFERRED_VERSION of linux-yocto-3.14 to 4.1 for crystalforest >BSP. > >Signed-off-by: Wu Chia Chuan Acked-by: Ong Boon Leong -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [master][PATCH 1/3] meta-crystalforest: relocate meta-crystalforest layer into meta-isg layer
>-Original Message- >From: Wu, Chia Chuan >Sent: Friday, October 2, 2015 7:29 PM >To: meta-intel@yoctoproject.org >Cc: Wu, Chia Chuan; Ong, Boon Leong >Subject: [meta-intel][master][PATCH 1/3] meta-crystalforest: relocate meta- >crystalforest layer into meta-isg layer > >From: Wu Chia Chuan > >This is in support of BSP consolidation of all Intel platforms in to meta-isg >common layer. >The "MAINTAINERS file" and "meta-isg/MAINTAINERS file" are updated to >reflect the changed. > >Signed-off-by: Wu Chia Chuan Acked-by: Ong Boon Leong >--- > MAINTAINERS|4 - > meta-crystalforest/COPYING.MIT | 17 -- > meta-crystalforest/README | 240 > meta-crystalforest/README.sources | 17 -- > meta-crystalforest/conf/layer.conf | 12 - > meta-crystalforest/conf/machine/crystalforest.conf | 40 > .../formfactor/crystalforest-gladden/machconfig|3 - > .../formfactor/crystalforest-server/machconfig |3 - > .../recipes-bsp/formfactor/formfactor_0.0.bbappend |1 - > meta-isg/MAINTAINERS |4 + > meta-isg/meta-crystalforest/COPYING.MIT| 17 ++ > meta-isg/meta-crystalforest/README | 240 > > meta-isg/meta-crystalforest/README.sources | 17 ++ > meta-isg/meta-crystalforest/conf/layer.conf| 12 + > .../conf/machine/crystalforest.conf| 40 > .../formfactor/crystalforest-gladden/machconfig|3 + > .../formfactor/crystalforest-server/machconfig |3 + > .../recipes-bsp/formfactor/formfactor_0.0.bbappend |1 + > 18 files changed, 337 insertions(+), 337 deletions(-) delete mode 100644 >meta-crystalforest/COPYING.MIT delete mode 100644 meta- >crystalforest/README delete mode 100644 meta- >crystalforest/README.sources delete mode 100644 meta- >crystalforest/binary/.gitignore > delete mode 100644 meta-crystalforest/conf/layer.conf > delete mode 100644 meta-crystalforest/conf/machine/crystalforest.conf > delete mode 100644 meta-crystalforest/recipes- >bsp/formfactor/formfactor/crystalforest-gladden/machconfig > delete mode 100644 meta-crystalforest/recipes- >bsp/formfactor/formfactor/crystalforest-server/machconfig > delete mode 100644 meta-crystalforest/recipes- >bsp/formfactor/formfactor_0.0.bbappend > create mode 100644 meta-isg/meta-crystalforest/COPYING.MIT > create mode 100644 meta-isg/meta-crystalforest/README > create mode 100644 meta-isg/meta-crystalforest/README.sources > create mode 100644 meta-isg/meta-crystalforest/binary/.gitignore > create mode 100644 meta-isg/meta-crystalforest/conf/layer.conf > create mode 100644 meta-isg/meta- >crystalforest/conf/machine/crystalforest.conf > create mode 100644 meta-isg/meta-crystalforest/recipes- >bsp/formfactor/formfactor/crystalforest-gladden/machconfig > create mode 100644 meta-isg/meta-crystalforest/recipes- >bsp/formfactor/formfactor/crystalforest-server/machconfig > create mode 100644 meta-isg/meta-crystalforest/recipes- >bsp/formfactor/formfactor_0.0.bbappend > >diff --git a/MAINTAINERS b/MAINTAINERS >index 79a021d..443041d 100644 >--- a/MAINTAINERS >+++ b/MAINTAINERS >@@ -31,10 +31,6 @@ COMMON > M:Saul Wold > F:common/ > >-CRYSTALFOREST >-M: Wu Chia Chuan >-F: meta-crystalforest/ >- > TLK > M:Saul Wold > F:meta-tlk/ >diff --git a/meta-crystalforest/COPYING.MIT b/meta- >crystalforest/COPYING.MIT deleted file mode 100644 index >fb950dc..000 >--- a/meta-crystalforest/COPYING.MIT >+++ /dev/null >@@ -1,17 +0,0 @@ >-Permission is hereby granted, free of charge, to any person obtaining a copy >-of this software and associated documentation files (the "Software"), to deal >-in the Software without restriction, including without limitation the rights >-to >use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies >of the Software, and to permit persons to whom the Software is -furnished to >do so, subject to the following conditions: >- >-The above copyright notice and this permission notice shall be included in - >all copies or substantial portions of the Software. >- >-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, >EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF >MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND >NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT >HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, >WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, >-OUT OF OR IN CONNECTION WITH THE
[meta-intel] meta-romley BSP layer retirement communication
Dear mailing-list, We are planning to retire meta-romley BSP layer from meta-intel master branch which is targeting YP2.0. This is in support of BSP consolidation of all intel platforms to intel common machine - intel-corei7-64 and intel-core2-32 starting from YP2.0. For romley platform, the meta-romley BSP layer that has been validated with Linux kernel v3.14 and will continue to be maintained in YPv1.8. If you have concern on this proposal, please tell us. If we have not heard any response from mailing-list, we will delete meta-romley BSP from YP2.0 meta-intel branch starting from 11/9/2015 onwards Thank you very much Ong Boon Leong Intel Corporation -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update meta branch SRCREV
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of Saul Wold >Sent: Tuesday, September 1, 2015 11:31 PM >To: Mittal, AnujX; meta-intel@yoctoproject.org >Cc: Wu, Chia Chuan >Subject: Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update >meta branch SRCREV > >On 08/31/2015 08:35 PM, Anuj Mittal wrote: >> From: Wu Chia Chuan >> >> Enable i40e network driver for Intel Ethernet Controller >> XL710/X710 on Intel common BSP so that the NIC card is discoverable >> under River Forest platform. >> >Since master still contains a 3.14 kernel is there a reason that this is not >provided >as a second patch set so that they match even if the kernel-cache data is >split? Make sense. Let's update this SRCREV on both master and fido branch for linux-yocto_3.14.bbappend. That will make sure it is 1:1 mapping as many as possible. -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 1/1] meta-valleyisland: Add linux-firmware-pcie8897 support in valleyisland-32.conf and valleyisland-64.conf
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of wei.tee...@intel.com
>Sent: Thursday, July 30, 2015 1:30 PM
>To: meta-intel@yoctoproject.org
>Subject: [meta-intel] [PATCH 1/1] meta-valleyisland: Add linux-firmware-
>pcie8897 support in valleyisland-32.conf and valleyisland-64.conf
>
>From: Ng Wei Tee
>
>Add linux-firmware-pcie8897 support for both valleyisland-32.conf and
>valleyisland-64.conf in order to enable the Marvell 8897 card.
>
>Signed-off-by: Ng Wei Tee
Acked-by: Ong Boon Leong
I am giving you my acked as I believe that Marvell card is essential to be
a package needed for booting the system. So, that is why instead of using
MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS below, you intentionally are
using MACHINE_EXTRA_RRECOMMENDS
BL
>---
> .../conf/machine/valleyisland-32.conf |2 ++
> .../conf/machine/valleyisland-64.conf |1 +
> 2 files changed, 3 insertions(+)
>
>diff --git a/meta-isg/meta-valleyisland/conf/machine/valleyisland-32.conf
>b/meta-isg/meta-valleyisland/conf/machine/valleyisland-32.conf
>index 6bbae7a..f989e7d 100644
>--- a/meta-isg/meta-valleyisland/conf/machine/valleyisland-32.conf
>+++ b/meta-isg/meta-valleyisland/conf/machine/valleyisland-32.conf
>@@ -14,6 +14,8 @@ require conf/machine/include/meta-intel.inc
>
> MACHINE_FEATURES += "pcbios efi"
>
>+MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-pcie8897"
>+
> XSERVER ?= "${XSERVER_X86_BASE} \
> ${XSERVER_X86_EXT} \
> ${XSERVER_X86_FBDEV} \
>diff --git a/meta-isg/meta-valleyisland/conf/machine/valleyisland-64.conf
>b/meta-isg/meta-valleyisland/conf/machine/valleyisland-64.conf
>index a13cc17..9158232 100644
>--- a/meta-isg/meta-valleyisland/conf/machine/valleyisland-64.conf
>+++ b/meta-isg/meta-valleyisland/conf/machine/valleyisland-64.conf
>@@ -15,6 +15,7 @@ require conf/machine/include/meta-intel.inc
>
> MACHINE_FEATURES += "pcbios efi"
>
>+MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-pcie8897"
>
> XSERVER ?= "${XSERVER_X86_BASE} \
> ${XSERVER_X86_EXT} \
>--
>1.7.9.5
>
>--
>___
>meta-intel mailing list
>meta-intel@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-intel
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 1/1] meta-valleyisland: recipes-core to include hostapd, iw, dhcp and linux-firmware-pcie8897
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of wei.tee...@intel.com >Sent: Wednesday, July 29, 2015 4:29 PM >To: meta-intel@yoctoproject.org >Subject: [meta-intel] [PATCH 1/1] meta-valleyisland: recipes-core to include >hostapd, iw, dhcp and linux-firmware-pcie8897 > >From: Ng Wei Tee > >A new recipes-core directory is created to include hostapd, iw, linux- >firmware- >pcie8897, dhcp features for enabling Marvell 8897 wifi and bluetooth support >in Valley Island BSP. Hostapd and iw is used to enable AP mode and STA mode >functionality. > >Signed-off-by: Ng Wei Tee >--- > .../recipes-core/images/core-image-sato.bbappend |1 + > 1 file changed, 1 insertion(+) > create mode 100644 meta-isg/meta-valleyisland/recipes-core/images/core- >image-sato.bbappend > >diff --git a/meta-isg/meta-valleyisland/recipes-core/images/core-image- >sato.bbappend b/meta-isg/meta-valleyisland/recipes-core/images/core-image- >sato.bbappend >new file mode 100644 >index 000..f32eb5a >--- /dev/null >+++ b/meta-isg/meta-valleyisland/recipes-core/images/core-image-sato.bba >+++ ppend >@@ -0,0 +1 @@ >+IMAGE_INSTALL += "hostapd iw linux-firmware-pcie8897 dhcp-server dhcp- >client" Usually, this line is set part of local.conf and does not need a bbappend creation. -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [meta-isg][fido][master][PATCH] meta-isg: dpdk: fix incorrect config fix-up patch and also tidy up dpdk.inc
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of Darren Hart >Sent: Tuesday, July 28, 2015 1:47 AM >To: Wu, Chia Chuan >Cc: meta-intel@yoctoproject.org >Subject: Re: [meta-intel] [meta-isg][fido][master][PATCH] meta-isg: dpdk: fix >incorrect config fix-up patch and also tidy up dpdk.inc > > > >On 7/27/15 4:14 AM, chia.chuan...@intel.com wrote: >> From: Ong Boon Leong >> >> This patch fixes issue in build configuration variables that were not >> correctly parsed by do_configure() task. The environment variables >> introduced by below patches, $(DPDK_TARGET_MACH) & >> $(CONFIG_VHOST_ENABLED) are not evaluated because the config files >> under dpdk/config/ folder are not parsed by Makefile but instead by cpp >compiler. >> >> >> dpdk/dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-type.patch >> >> dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-conf >> ig.patch >> dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in- >common_linux >> app.patch >> >> Thanks to Anuj Mittal for detecting the issue above. >> >> So, we fix the above issues by using sed command to fix-up the right >> values as follow >> >> 1) Override the value of CONFIG_RTE_MACHINE based on MACHINE_ARCH at >>config/defconfig_x86_64-native-linuxapp-gcc >>config/defconfig_i686-native-linuxapp-gcc >> >> 2) Override the value of CONFIG_RTE_KNI_VHOST, >CONFIG_RTE_KNI_VHOST_VNET_HDR_EN and >>CONFIG_RTE_LIBRTE_VHOST based on PACKAGECONFIG[vhost] at >>config/common_linuxapp >> >> Since we are here, we also take opportunity to tidy up dpdk.inc by >> integrating common recipe from dpdk_1.8.0.bb & dpdpk_2.0.0.bb > >This is at least 2 distinct functional changes and should be made as separate >commits. At the very least, please separate the .inc common changes into their >own patch. Darren, Chia Chuan will make the changes for DPDK, collect the patches from Anuj on The zlib-qat and dpdk dependency on the "virtual/qat" thread and sent in one single patch-series to you. He will be using a different subject title so that you are aware that you can merge that patch-series instead of merging from two other submits. Thanks Boon Leong -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 3/3] libva-intel-driver: Update to 1.6.0
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of Lim, Siew Hoon >Sent: Monday, July 27, 2015 8:26 PM >To: Burton, Ross >Cc: meta-intel@yoctoproject.org >Subject: Re: [meta-intel] [PATCH 3/3] libva-intel-driver: Update to 1.6.0 > > >> All patches need to contain an Upstream-Status annotation to say what the >state of the patch is: a backport from upstream, a fix that's been submitted >upstream, a change that is inappropriate for upstream (with rationale), and so >on. > >Hi Ross, > >Thanks for the advice. Noted. >Ok, I will add in the upstream status inside original commit message from >libva- >intel-driver before generate the patch. > Siew Hoon, please refer to http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [master, fido, dizzy][PATCH] meta-crystalforest: add in clarity around how to pick the right QAT version
>-Original Message- >From: Darren Hart [mailto:dvh...@linux.intel.com] >Sent: Saturday, July 25, 2015 2:28 AM >To: Ong, Boon Leong >Cc: meta-intel@yoctoproject.org; Wu, Chia Chuan >Subject: Re: [meta-intel] [master, fido, dizzy][PATCH] meta-crystalforest: add >in >clarity around how to pick the right QAT version > >On 7/23/15 4:48 PM, Ong Boon Leong wrote: >> Add explanation on how to override the default setting under >> crystalforest.conf on PREFERRED_PROVIDER_virtual/qat. > >Unfortunatley, this documentation is not correct for master and fido as they >don't have qat15, nor do they have the notion of virtual/qat. Would you like >these applied only to dizzy? On another patchseries submitted by Anuj, I mentioned that we should make qat16 to indeed provides virtual/qat so that DPDK recipes under meta-isg/common can have dpdk_qat example depends on virtual/qat instead of qat16. If you agree to that approach, this the documentation update can be applied to all dizzy, fido and master branches. Thanks Boon Leong -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [master & fido][PATCH 1/4] meta-isg: fix dpdk_qat example for dpdk v2.0.0
Thanks for the fix.
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of Anuj Mittal
>Sent: Saturday, July 25, 2015 1:08 AM
>To: meta-intel@yoctoproject.org
>Subject: [meta-intel] [master & fido][PATCH 1/4] meta-isg: fix dpdk_qat
>example for dpdk v2.0.0
>
>Make sure that the dpdk_qat example builds. Added
>the patch to point to right libs and headers.
>
>Signed-off-by: Anuj Mittal
Acked-by: Ong Boon Leong
>---
> meta-isg/common/recipes-extended/dpdk/dpdk.inc |1 +
> ...0-point-to-the-right-include-and-lib-path.patch | 43
>
> .../common/recipes-extended/dpdk/dpdk_2.0.0.bb |1 +
> 3 files changed, 45 insertions(+)
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-
>1.8.0-and-2.0.0-point-to-the-right-include-and-lib-path.patch
>
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc b/meta-
>isg/common/recipes-extended/dpdk/dpdk.inc
>index 85b88fa..1603158 100644
>--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
>+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
>@@ -20,6 +20,7 @@ export RTE_KERNELDIR_OUT =
>"${STAGING_KERNEL_BUILDDIR}"
> export INSTALL_PATH = "${prefix}/dpdk"
> export SYSROOTPATH = "--sysroot=${STAGING_DIR_HOST}"
> export DPDK_TARGET_MACH = "${@get_dpdk_target_mach(bb,d)}"
>+export ICP_LAC_API_DIR = "${STAGING_DIR_TARGET}${includedir}/lac"
>
> # The list of intel Comms platforms and their target machine
> # process mapping. The supported target machine is listed under
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-
>2.0.0-point-to-the-right-include-and-lib-path.patch b/meta-
>isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-point-to-the-
>right-include-and-lib-path.patch
>new file mode 100644
>index 000..75bb517
>--- /dev/null
>+++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-
>point-to-the-right-include-and-lib-path.patch
>@@ -0,0 +1,43 @@
>+From 928595c80ae28d19861d7e76ed898a8fb3f2c1dc Mon Sep 17 00:00:00
>2001
>+From: Anuj Mittal
>+Date: Fri, 24 Jul 2015 23:57:17 +0800
>+Subject: [PATCH] dpdk: point to the right include and lib path
>+
>+Upstream-Status: Inappropriate [Configuration]
>+
>+Make sure that we point to the right location of qat
>+lac headers and library.
>+
>+Signed-off-by: Anuj Mittal
>+---
>+ examples/dpdk_qat/Makefile |7 ++-
>+ 1 file changed, 2 insertions(+), 5 deletions(-)
>+
>+diff --git a/examples/dpdk_qat/Makefile b/examples/dpdk_qat/Makefile
>+index f1e06a1..5b906f7 100644
>+--- a/examples/dpdk_qat/Makefile
> b/examples/dpdk_qat/Makefile
>+@@ -66,18 +66,15 @@ SRCS-y := main.c crypto.c
>+
>+ CFLAGS += -O3
>+ CFLAGS += $(WERROR_FLAGS)
>+-CFLAGS += -I$(ICP_ROOT)/quickassist/include \
>+- -I$(ICP_ROOT)/quickassist/include/lac \
>+- -I$(ICP_ROOT)/quickassist/lookaside/access_layer/include
>++CFLAGS += -I$(ICP_LAC_API_DIR)
>+
>+ # From CRF 1.2 driver, library was renamed to libicp_qa_al.a
>+ ifneq ($(wildcard $(ICP_ROOT)/build/icp_qa_al.a),)
>+ ICP_LIBRARY_PATH = $(ICP_ROOT)/build/icp_qa_al.a
>+ else
>+-ICP_LIBRARY_PATH = $(ICP_ROOT)/build/libicp_qa_al.a
>++ICP_LIBRARY_PATH = $(ICP_LIB_ROOT)/libicp_qa_al.a
>+ endif
>+
>+-LDLIBS += -L$(ICP_ROOT)/build
>+ LDLIBS += $(ICP_LIBRARY_PATH) \
>+ -lz \
>+ -losal \
>+--
>+1.7.9.5
>+
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb b/meta-
>isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
>index cb158b9..0cadba7 100644
>--- a/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
>+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
>@@ -6,6 +6,7 @@ SRC_URI = "http://dpdk.org/browse/dpdk/snapshot/dpdk-
>${PV}.tar.gz;name=dpdk \
> file://dpdk-1.8.0-and-2.0.0-add-RTE_KERNELDIR_OUT-to-split-kernel-
>bu.patch \
> file://dpdk-1.8.0-and-2.0.0-add-sysroot-option-within-app-
>makefile.patch \
> file://dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-
>type.patch \
>+ file://dpdk-1.8.0-and-2.0.0-point-to-the-right-include-and-lib-
>path.patch \
> "
>
> SRC_URI[dpdk.md5sum] = "e9e7935c9eec920841ad373949514934"
>--
>1.7.9.5
>
>--
>___
>meta-intel mailing list
>meta-intel@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-intel
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [master & fido][PATCH 2/4] meta-isg: fix dpdk_qat example for dpdk v1.8.0
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of Anuj Mittal
>Sent: Saturday, July 25, 2015 1:08 AM
>To: meta-intel@yoctoproject.org
>Subject: [meta-intel] [master & fido][PATCH 2/4] meta-isg: fix dpdk_qat
>example for dpdk v1.8.0
>
>Make sure that the dpdk_qat example builds.
>
>Signed-off-by: Anuj Mittal
Acked-by: Ong Boon Leong
>---
> .../common/recipes-extended/dpdk/dpdk_1.8.0.bb |1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb b/meta-
>isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
>index 5265a9c..5122324 100644
>--- a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
>+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
>@@ -6,6 +6,7 @@ SRC_URI = "http://dpdk.org/browse/dpdk/snapshot/dpdk-
>${PV}.tar.gz;name=dpdk \
> file://dpdk-1.8.0-and-2.0.0-add-RTE_KERNELDIR_OUT-to-split-kernel-
>bu.patch \
> file://dpdk-1.8.0-and-2.0.0-add-sysroot-option-within-app-
>makefile.patch \
> file://dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-
>type.patch \
>+ file://dpdk-1.8.0-and-2.0.0-point-to-the-right-include-and-lib-
>path.patch \
> "
>
> SRC_URI[dpdk.md5sum] = "11ad8785aaa869cc87265bcb8d828f22"
>--
>1.7.9.5
>
>--
>___
>meta-intel mailing list
>meta-intel@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-intel
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [master & fido][PATCH 3/4] meta-isg: point to right qat package for dpdk v2.0.0
>-PACKAGECONFIG[dpdk_qat] = ",,qat" >+PACKAGECONFIG[dpdk_qat] = ",,qat16" For fido and master, qat16 is the only supported QAT under meta-crystralforest For River Forest which only has Coleto Creek chipset. Dpdk recipes under meta-isg/common/recipes-extended/dpdk can support multiple platforms e.g river forest, romley+walnut hill card and mohon-peak and future product line. So, we should NOT restrict the build dependency on qat16 because that will defeat the purpose of putting dpdk recipes under meta-isg/common. I would think that qat16 should provides virtual/qat and make the above for both dpdk 1.8 & dpdk2.0 depends on virtual/qat instead. -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master, fido, dizzy][PATCH] add clarity for QAT selection under crystalforest
Darren, This patch add better clarity about how to pick the right 'qat15' or 'qat16' for various platforms (crystalforest, highlandforest & river forest) that shares the common crystalforest.conf machine definition. Please help merge the patch into master, fido and dizzy. Many thanks for the quick turn-around! Boon Leong Ong Boon Leong (1): meta-crystalforest: add in clarity around how to pick the right QAT version meta-crystalforest/README | 25 + 1 file changed, 25 insertions(+) -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master, fido, dizzy][PATCH] meta-crystalforest: add in clarity around how to pick the right QAT version
Add explanation on how to override the default setting under crystalforest.conf on PREFERRED_PROVIDER_virtual/qat. Signed-off-by: Ong Boon Leong --- meta-crystalforest/README | 25 + 1 file changed, 25 insertions(+) diff --git a/meta-crystalforest/README b/meta-crystalforest/README index 2053a3c..f549f90 100644 --- a/meta-crystalforest/README +++ b/meta-crystalforest/README @@ -204,12 +204,37 @@ Note: qat16 recipe is meant for platform with Coleto Creek chipset. qat15 recipe is meant for platform with Cave Creek chipset. +conf/machine/crystalforest.conf is the common machine configuration +to support Crystal Forest/server, Crystal Forest/gladden, Highland Forest and +River Forest. In order to generate the right binary for these platforms which +have different QAT technology, user could change the default config accordingly +within crystalforest.conf as below: + +For Coleto Creek chipset: +PREFERRED_PROVIDER_virtual/qat ?= "qat16" + +For Cave Creek chipset: +PREFERRED_PROVIDER_virtual/qat ?= "qat15" + +Another option and preferred approach for above setting is to override +configuration under build/conf/local.conf as follow: + +For Coleto Creek chipset: +PREFERRED_PROVIDER_virtual/qat = "qat16" + +For Cave Creek chipset: +PREFERRED_PROVIDER_virtual/qat = "qat15" + By default, the machine configuration does not assume that the above ingredients are pre-installed onto the BSP. Developers are required to either use smart tool to install those software packages or configure IMAGE_INSTALL under build/conf/local.conf, for example. +For Coleto Creek chipset: IMAGE_INSTALL += "dpdk qat16 zlib-qat" +For Cavecreek Creek chipset: +IMAGE_INSTALL += "dpdk qat15 zlib-qat" + The list of packages can be searched under tmp/deploy/ folder. -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 2/3] meta-crystalforest: add qat preferred provider
>Your cover letter said crystal forest depends on qat15. Why are we setting it >to >qat16 here? Crystal-forest depends on qat15 Highland-forest depends on qat16 Qat16 is chosen as default because that is to support coleto creek which is newer chipset. > >Is there a reason we are doing this as qat15 and qat16 instead of just having >two qat recipes with different versions and setting the >PREFERRED_VERSION_qat in the machine config? > >e.g. > >qat_15-1.7.0-30.bb >qat_16-2.2.0-30.bb > >PREFERRED_VERSION_qat ?= "15-%" > >There shouldn't be a need for a virtual/qat at all. This is from discussion in the past with Saul on splitting the recipe into qat15 and qat16 so that we can have those named folders containing versioned patches accordingly. meta-crystalforest/recipes-extended/qat/qat15 meta-crystalforest/recipes-extended/qat/qat16 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 0/2] meta-crystalforest readme and maintainer update
>>You can do this and submit the patches in this way to dizzy and it >>preserves the cherry-pick meta-data. I will apply these to dizzy from my >cherry-pick this time. > >Sure since now it is merged into master. I could resend. I didn't read correct. Thanks for helping the cherry-pick from your end. -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 0/2] meta-crystalforest readme and maintainer update
>$ git log -2 >commit d7c2305f2b6b1025985e1f71110ffa4b094de63b (HEAD, >refs/heads/dizzy) >Author: Ong Boon Leong >Date: 2015-07-23 > >meta-crystalforest: update README to include support for River Forest > >This adds further clarification on how various Intel Communication > platforms >that are supported across different branches within meta-crystalforest > layer. > >Signed-off-by: Ong Boon Leong >Signed-off-by: Darren Hart >(cherry picked from commit 9aa6c066ebf44aecef40caec333772cd970f6842) > >commit 2d731523cc0130c0e12c70957ff1fa048f179a6d >Author: Ong Boon Leong >Date: 2015-07-23 > >MAINTAINERS: update name for romley and crystal forest BSP > >This patch updates the maintainer for these two platforms >to Wu Chia Chuan. > >Signed-off-by: Ong Boon Leong >(cherry picked from commit >a2b4e15a181728692b1da5808e1690cee9912ce6) >[dvh...@linux.intel.com: Applied to dizzy] >Signed-off-by: Darren Hart > >You can do this and submit the patches in this way to dizzy and it preserves >the >cherry-pick meta-data. I will apply these to dizzy from my cherry-pick this >time. Sure since now it is merged into master. I could resend. -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 3/3] meta-crystalforest: zlib-qat depends on virtual/qat
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of Anuj Mittal
>Sent: Friday, July 24, 2015 12:39 AM
>To: meta-intel@yoctoproject.org
>Subject: [meta-intel] [dizzy][PATCH 3/3] meta-crystalforest: zlib-qat depends
>on
>virtual/qat
>
>Made zlib-qat DEPENDS on virtual/qat. This allows us to switch between
>highland forest and crystal forest platforms.
>
>Signed-off-by: Anuj Mittal
Acked-by: Ong Boon Leong
>---
> .../zlib-qat/zlib-qat_0.4.7-002.bb |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat_0.4.7-002.bb
>b/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat_0.4.7-002.bb
>index 4400696..1869f32 100644
>--- a/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat_0.4.7-002.bb
>+++ b/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat_0.4.7-002.bb
>@@ -14,7 +14,7 @@ LIC_FILES_CHKSUM = "file://${WORKDIR}/zlib-
>${ZLIB_VERSION}/zlib.h;beginline=4;en
>
> # For target side versions of openssl enable support for OCF Linux driver #
> if
>they are available.
>-DEPENDS += "cryptodev-linux pkgconfig qat16"
>+DEPENDS += "cryptodev-linux pkgconfig virtual/qat"
>
> SRC_URI = "http://www.zlib.net/zlib-${ZLIB_VERSION}.tar.gz;name=zlib \
> https://01.org/sites/default/files/page/zlib_shim_0.4.7-
>002_withdocumentation.zip;name=zlibqat \
>--
>1.7.9.5
>
>--
>___
>meta-intel mailing list
>meta-intel@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-intel
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 2/3] meta-crystalforest: add qat preferred provider
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of Anuj Mittal >Sent: Friday, July 24, 2015 12:39 AM >To: meta-intel@yoctoproject.org >Subject: [meta-intel] [dizzy][PATCH 2/3] meta-crystalforest: add qat preferred >provider > >Added the qat preferred provider to be qat16. > >Signed-off-by: Anuj Mittal Acked-by: Ong Boon Leong >--- > meta-crystalforest/conf/machine/crystalforest.conf |2 ++ > 1 file changed, 2 insertions(+) > >diff --git a/meta-crystalforest/conf/machine/crystalforest.conf b/meta- >crystalforest/conf/machine/crystalforest.conf >index 44b9bb2..84a6df2 100644 >--- a/meta-crystalforest/conf/machine/crystalforest.conf >+++ b/meta-crystalforest/conf/machine/crystalforest.conf >@@ -18,6 +18,8 @@ > PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" > PREFERRED_VERSION_linux-yocto ?= "3.10%" > >+PREFERRED_PROVIDER_virtual/qat ?= "qat16" >+ > require conf/machine/include/intel-corei7-64-common.inc > require conf/machine/include/intel-common-pkgarch.inc > require conf/machine/include/meta-intel.inc >-- >1.7.9.5 > >-- >___ >meta-intel mailing list >meta-intel@yoctoproject.org >https://lists.yoctoproject.org/listinfo/meta-intel -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 1/3] meta-crystalforest: add virtual/qat provider
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of Anuj Mittal
>Sent: Friday, July 24, 2015 12:39 AM
>To: meta-intel@yoctoproject.org
>Subject: [meta-intel] [dizzy][PATCH 1/3] meta-crystalforest: add virtual/qat
>provider
>
>Changed qat to PROVIDES "virtual/qat" so we can switch between qat15 and
>qat16 for highland forest and crystalforest.
>
>Signed-off-by: Anuj Mittal
Acked-by: Ong Boon Leong
>---
> meta-crystalforest/recipes-extended/qat/qat.inc |1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/meta-crystalforest/recipes-extended/qat/qat.inc b/meta-
>crystalforest/recipes-extended/qat/qat.inc
>index 0053204..6a2ceff 100644
>--- a/meta-crystalforest/recipes-extended/qat/qat.inc
>+++ b/meta-crystalforest/recipes-extended/qat/qat.inc
>@@ -6,6 +6,7 @@ LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-
>2.0;md5=801f80980d171dd6425610833a22dbe6"
> COMPATIBLE_MACHINE = "crystalforest"
> DEPENDS += "cryptodev-linux pkgconfig zlib"
>+PROVIDES += "virtual/qat"
>
> MODULE_DIR =
>"${D}${base_libdir}/modules/${KERNEL_VERSION}/kernel/drivers"
> ICP_TOOLS = "accelcomp"
>--
>1.7.9.5
>
>--
>___
>meta-intel mailing list
>meta-intel@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-intel
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [dizzy][PATCH 2/2] meta-crystalforest: update README to include support for River Forest
This adds further clarification on how various Intel Communication platforms that are supported across different branches within meta-crystalforest layer. Signed-off-by: Ong Boon Leong --- meta-crystalforest/README | 100 - 1 file changed, 62 insertions(+), 38 deletions(-) diff --git a/meta-crystalforest/README b/meta-crystalforest/README index 210df56..2053a3c 100644 --- a/meta-crystalforest/README +++ b/meta-crystalforest/README @@ -2,34 +2,38 @@ This README file contains information on building the meta-crystalforest BSP layer, and booting the images contained in the /binary directory. Please see the corresponding sections below for details. -The 'Crystal Forest' platform consists of two versions. -1. GLADDEN -2. SERVER +Overview of Intel Communication Product Offering + -The Gladden Platform consists of Intel Xeon E3-1125C/E3-1105C Processor, -plus the Intel Communication Chipset 89xx for Smaller Form Factor -Communication Infrastructure. -(Gladden + Cave Creek) also known as CrystalForest-Gladden +The following platforms are supported on meta-intel dizzy branch ONLY: -The Server Platform consists of Intel Xeon E5-2600 and E5-2400 Processors, -plus the Intel Communication Chipset 89xx for Large-Scale Communications -Infrastructure. -(Ivy Bridge-EP/EN + Coleto Creek) also known as HighlandForest -(Sandy Bridge-EP/EN + Cave Creek) also known as CrystalForest-Server +Crystal Forest/Server - Shumway reference platform configurations: +processor: Intel Xeon E5-2600/E5-2400 (Sandy Bridge-based) or + Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based) +chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek) +url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview -Both Platforms use Matrox graphics Card. +Crystal Forest/Gladden - Stargo reference platform configurations: +processor: Intel Xeon E3-1125C/E3-1105C (Sandy Bridge-based) or + Intel Xeon E3-1125v2/E3-1105v2 (Ivy Bridge-based) +chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek) +url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview -Further information about the Crystal Forest Gladden platform supported -by this BSP can be found here: +Highland Forest (Crystal Forest/Server Refresh) - Shumway reference platform configurations: +processor: Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based) +chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek) +url: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/crystal-forest-server/xeon-e5-v2-89xx-chipset-ibd.html - http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview +The following platform is supported on meta-intel fido branch and beyond. -Further information about the Crystal Forest server platform supported -by this BSP can be found here: +River Forest - Long Brook reference platform configurations: +processor: Intel Xeon E5-2600v3/E5-2400v3 (Haswell EP-based) +chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek) +url: https://www-ssl.intel.com/content/www/my/en/embedded/products/river-forest/overview.html?wapkw=coleto - http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview +All above four platforms use PCIe-based Matrox graphics card for display. -Information on all Intel® embedded platforms can be found here: +More Information on all Intel® embedded platforms can be found here: http://www.intel.com/p/en_US/embedded/hwsw/hardware @@ -65,7 +69,7 @@ Patches Please submit any patches against this BSP to the meta-intel mailing list (meta-intel@yoctoproject.org) and cc: the maintainer: -Maintainer: Chan Wei Sern +Maintainer: Wu Chia Chuan Please see the meta-intel/MAINTAINERS file for more details. @@ -114,6 +118,8 @@ At the end of a successful build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section 'Booting the images from /binary'). +The live image is located within build/tmp/deploy/images/ folder. + As an alternative to downloading the BSP tarball, you can also work directly from the meta-intel git repository. For each BSP in the 'meta-intel' repository, there are multiple branches, one @@ -131,15 +137,26 @@ II. Booting the images in /binary This BSP contains bootable live images, which can be used to directly boot Yocto off of a USB flash drive. -Under Linux, insert a USB flash drive. Assuming the USB flash drive -takes device /dev/sdf, use dd to copy the live image to it. For -example: +You can deploy the hddimg image to a USB or SATA device. You will +need to know the device name on your host as well as the device name on +the target. Be careful with this step as using the wrong host device can +result in
[meta-intel] [dizzy][PATCH 1/2] MAINTAINERS: update name for romley and crystal forest BSP
This patch updates the maintainer for these two platforms to Wu Chia Chuan. Signed-off-by: Ong Boon Leong --- MAINTAINERS |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index b7cd2a3..2f77f45 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -36,7 +36,7 @@ M:Nitin A Kamble F: meta-crownbay/ CRYSTALFOREST -M: Ong Boon Leong +M: Wu Chia Chuan F: meta-crystalforest/ EMENLOW @@ -52,7 +52,7 @@ M:Nitin A Kamble F: meta-jasperforest/ ROMLEY -M: Haw Foo Chien +M: Wu Chia Chuan F: meta-romley/ SUGARBAY -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [dizzy][PATCH 0/2] meta-crystalforest readme and maintainer update
Darren, This patch-series is meant for dizzy branch ONLY. These two patches do the following: 1) update the maintainer list for crystalforest and romley to Wu Chia Chuan the resource funded by Intel Comms group to focus on those product lines. 2) Add clarity on how crystal forest, highland forest and river forest platforms are supported within meta-intel as requested by Intel Comms group. If you don't have concern, please help apply these 2 patches onto to DIZZY. Many thanks Boon Leong Ong Boon Leong (2): MAINTAINERS: update name for romley and crystal forest BSP meta-crystalforest: update README to include support for River Forest MAINTAINERS |4 +- meta-crystalforest/README | 100 - 2 files changed, 64 insertions(+), 40 deletions(-) -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido & master][PATCH 1/2] MAINTAINERS: update name for romley and crystal forest BSP
This patch updates the maintainer for these two platforms to Wu Chia Chuan. Signed-off-by: Ong Boon Leong --- MAINTAINERS |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 9c3b3af..6401963 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -36,7 +36,7 @@ M:Saul Wold F: meta-crownbay/ CRYSTALFOREST -M: Saul Wold +M: Wu Chia Chuan F: meta-crystalforest/ EMENLOW @@ -52,7 +52,7 @@ M:Saul Wold F: meta-jasperforest/ ROMLEY -M: Haw Foo Chien +M: Wu Chia Chuan F: meta-romley/ SUGARBAY -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido & master][PATCH 2/2] meta-crystalforest: update README to include support for River Forest
This adds further clarification on how various Intel Communication platforms that are supported across different branches within meta-crystalforest layer. Signed-off-by: Ong Boon Leong --- meta-crystalforest/README | 100 - 1 file changed, 62 insertions(+), 38 deletions(-) diff --git a/meta-crystalforest/README b/meta-crystalforest/README index 210df56..2053a3c 100644 --- a/meta-crystalforest/README +++ b/meta-crystalforest/README @@ -2,34 +2,38 @@ This README file contains information on building the meta-crystalforest BSP layer, and booting the images contained in the /binary directory. Please see the corresponding sections below for details. -The 'Crystal Forest' platform consists of two versions. -1. GLADDEN -2. SERVER +Overview of Intel Communication Product Offering + -The Gladden Platform consists of Intel Xeon E3-1125C/E3-1105C Processor, -plus the Intel Communication Chipset 89xx for Smaller Form Factor -Communication Infrastructure. -(Gladden + Cave Creek) also known as CrystalForest-Gladden +The following platforms are supported on meta-intel dizzy branch ONLY: -The Server Platform consists of Intel Xeon E5-2600 and E5-2400 Processors, -plus the Intel Communication Chipset 89xx for Large-Scale Communications -Infrastructure. -(Ivy Bridge-EP/EN + Coleto Creek) also known as HighlandForest -(Sandy Bridge-EP/EN + Cave Creek) also known as CrystalForest-Server +Crystal Forest/Server - Shumway reference platform configurations: +processor: Intel Xeon E5-2600/E5-2400 (Sandy Bridge-based) or + Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based) +chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek) +url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview -Both Platforms use Matrox graphics Card. +Crystal Forest/Gladden - Stargo reference platform configurations: +processor: Intel Xeon E3-1125C/E3-1105C (Sandy Bridge-based) or + Intel Xeon E3-1125v2/E3-1105v2 (Ivy Bridge-based) +chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek) +url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview -Further information about the Crystal Forest Gladden platform supported -by this BSP can be found here: +Highland Forest (Crystal Forest/Server Refresh) - Shumway reference platform configurations: +processor: Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based) +chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek) +url: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/crystal-forest-server/xeon-e5-v2-89xx-chipset-ibd.html - http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview +The following platform is supported on meta-intel fido branch and beyond. -Further information about the Crystal Forest server platform supported -by this BSP can be found here: +River Forest - Long Brook reference platform configurations: +processor: Intel Xeon E5-2600v3/E5-2400v3 (Haswell EP-based) +chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek) +url: https://www-ssl.intel.com/content/www/my/en/embedded/products/river-forest/overview.html?wapkw=coleto - http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview +All above four platforms use PCIe-based Matrox graphics card for display. -Information on all Intel® embedded platforms can be found here: +More Information on all Intel® embedded platforms can be found here: http://www.intel.com/p/en_US/embedded/hwsw/hardware @@ -65,7 +69,7 @@ Patches Please submit any patches against this BSP to the meta-intel mailing list (meta-intel@yoctoproject.org) and cc: the maintainer: -Maintainer: Chan Wei Sern +Maintainer: Wu Chia Chuan Please see the meta-intel/MAINTAINERS file for more details. @@ -114,6 +118,8 @@ At the end of a successful build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section 'Booting the images from /binary'). +The live image is located within build/tmp/deploy/images/ folder. + As an alternative to downloading the BSP tarball, you can also work directly from the meta-intel git repository. For each BSP in the 'meta-intel' repository, there are multiple branches, one @@ -131,15 +137,26 @@ II. Booting the images in /binary This BSP contains bootable live images, which can be used to directly boot Yocto off of a USB flash drive. -Under Linux, insert a USB flash drive. Assuming the USB flash drive -takes device /dev/sdf, use dd to copy the live image to it. For -example: +You can deploy the hddimg image to a USB or SATA device. You will +need to know the device name on your host as well as the device name on +the target. Be careful with this step as using the wrong host device can +result in
[meta-intel] [fido & master][PATCH 0/2] crystalforest maintainer and readme update
Darren, This two patches do the following: 1) update the maintainer list for crystalforest and romley to Wu Chia Chuan the resource funded by Intel Comms group to focus on those product lines. 2) Add clarity on how crystal forest, highland forest and river forest platforms are supported within meta-intel as requested by Intel Comms group. If you don't have concern, please help apply these 2 patches onto to fido and master. I will be sending another series just to be applied on dizzy branch because this series does not apply neatly onto dizzy branch. Many thanks Boon Leong Ong Boon Leong (2): MAINTAINERS: update name for romley and crystal forest BSP meta-crystalforest: update README to include support for River Forest MAINTAINERS |4 +- meta-crystalforest/README | 100 - 2 files changed, 64 insertions(+), 40 deletions(-) -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [met-intel-quark] Enable stack-protector defense support for SPI image
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of Ramajayam, Yugeraj >Sent: Thursday, July 9, 2015 3:36 PM >To: Le Foll, Brendan >Cc: meta-intel@yoctoproject.org >Subject: Re: [meta-intel] [met-intel-quark] Enable stack-protector defense >support for SPI image > >Hi Brian, > >I followed as you said. I ran, > >1. $ bitbake -c menuconfig uclibc >2. Selected fstack-protector option >3. Copied the .config file from build/tmp-spi/work/i586-poky-linux- >uclibc/uclibc/0.9.33+gitAUTOINC+48a0006012-r9/git/.config >4. I replaced ../meta/recipes-core/uclibc/uclibc-git/uClibc.distro with >.config and >renamed it as uClibc.distro and did a $ bitbake uclibc 5. After compilation, I >checked the build/tmp-spi/work/i586-poky-linux- >uclibc/uclibc/0.9.33+gitAUTOINC+48a0006012-r9. The Uclibc.distro there is the >same as I changed in ../meta/recipes-core/uclibc/uclibc-git/uClibc.distro with >all >the SSP (stack-protector) related configs built in. >6. But, when I checked .config file at build/tmp-spi/work/i586-poky-linux- >uclibc/uclibc/0.9.33+gitAUTOINC+48a0006012-r9/git/.config, the SSP configs >are disabled as in my previous build. Somehow the stack-protector features >were not passed over to the final .config > >Is there any other way for me to check if those stack-protector options are >enabled ? >Or did I missing some steps ?? > Took a look at this topic. We just need to declare DISTRO_FEATURES_append = "ssp" under local.conf for enabling stack smashing protection for uclibc I have confirmed that the merged.config under work/i586-poky-linux-uclibc/uclibc/0.9.33+gitAUTOINC+48a0006012-r9/git has UCLIBC_HAS_SSP=y. Test performed as shown below against the uclibc binary on tmp/work/.../packages-split/uclibc/lib/ will reveal that with and without the "ssp" settings, the library C is built with and without stack protector. objdump -d libuClibc-0.9.34-git.so | grep __stack_chk_fail Cheers. BL -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 0/2] zlib-qat fixes for Highland Forest
> >I'll merge this to master as is. > You meant dizzy right... ;-) -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 0/2] zlib-qat fixes for Highland Forest
>When you apply backports, please do so using:
>
>$ git cherry-pick -x COMMIT
>
>This will identify the patch as a backport and include the master commit in the
>commit message, making it clear. Please resubmit the patches using this
>method.
>
Darren,
I think that Anuj may not present the case clear enough.
Let me explain on his behalf so we understand what is the gap here.
The event happened in this sequence:
1) Zlib-qat has been merged into dizzy here
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?h=dizzy&id=3ee02a36e0d1126fda0c6ea6a1bef4db08b8be7a
This commit has a defect in the kernel module compilation ${CC}.
2) Then, when Anuj took over to enable zlib-qat for master and fido for River
Forest platform, he cherry-pick the dizzy version
and add in some fixed as recorded in the commit below.
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=9511d5564160384b4e9f8a88f59d6f90f6ca0e0e
So, it is only possible to do git cherry-pick -x from master back to dizzy if
we first do git revert commit "3ee02a36".
Darren, which do you prefer?
1) Git revert than git cherry-pick from master
2) send an incremental git commit to fix this ${CC} issue
I must admit that we should have focus on master from start but implementation
has slipped due to turn-over.
We are looking at having this patch accepted by tomorrow so that we can
generate BSP release this Friday for
Crystal Forest and Highland Forest for dizzy branch.
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 1/2] meta-crystalforest: use correct compiler for zlib
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of Anuj Mittal
>Sent: Thursday, July 16, 2015 12:54 PM
>To: meta-intel@yoctoproject.org
>Subject: [meta-intel] [dizzy][PATCH 1/2] meta-crystalforest: use correct
>compiler for zlib
>
>Changed the qat_mem makefile to use $(CC) instead of gcc directly. This avoids
>build errors and makes sure that right options are being passed for cross-
>compile.
>
>Signed-off-by: Anuj Mittal
Acked-by: Ong Boon Leong
>---
> .../recipes-extended/zlib-qat/zlib-qat.bb |2 ++
> .../zlib-qat-qat_mem-use-the-right-compiler.patch | 31
>
> 2 files changed, 33 insertions(+)
> create mode 100644 meta-crystalforest/recipes-extended/zlib-qat/zlib-
>qat/zlib-qat-qat_mem-use-the-right-compiler.patch
>
>diff --git a/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat.bb b/meta-
>crystalforest/recipes-extended/zlib-qat/zlib-qat.bb
>index a9cc1d7..4400696 100644
>--- a/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat.bb
>+++ b/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat.bb
>@@ -19,6 +19,7 @@ DEPENDS += "cryptodev-linux pkgconfig qat16"
> SRC_URI = "http://www.zlib.net/zlib-${ZLIB_VERSION}.tar.gz;name=zlib \
> https://01.org/sites/default/files/page/zlib_shim_0.4.7-
>002_withdocumentation.zip;name=zlibqat \
> file://0001-Fix-for-Zlib-qat-Compilation-issue.patch \
>+ file://zlib-qat-qat_mem-use-the-right-compiler.patch \
> "
>
> SRC_URI[zlib.md5sum] = "44d667c142d7cda120332623eab69f40"
>@@ -65,6 +66,7 @@ do_patch() {
> cd ${S}
> patch -p1 < ${WORKDIR}/zlib-1.2.8-qat.patch
> patch -p1 < ${WORKDIR}/0001-Fix-for-Zlib-qat-Compilation-issue.patch
>+ patch -p1 < ${WORKDIR}/zlib-qat-qat_mem-use-the-right-
>compiler.patch
> }
>
> do_configure() {
>diff --git a/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat/zlib-qat-
>qat_mem-use-the-right-compiler.patch b/meta-crystalforest/recipes-
>extended/zlib-qat/zlib-qat/zlib-qat-qat_mem-use-the-right-compiler.patch
>new file mode 100644
>index 000..7b9af29
>--- /dev/null
>+++ b/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat/zlib-qat-qat
>+++ _mem-use-the-right-compiler.patch
>@@ -0,0 +1,31 @@
>+From 22a4ef23792251c284d9766ab5ee87cbeeef2ec4 Mon Sep 17 00:00:00
>2001
>+From: Anuj Mittal
>+Date: Thu, 16 Jul 2015 11:05:38 +0800
>+Subject: [PATCH] qat_mem: use the right compiler
>+
>+Upstream-Status: Inappropriate [Configuration]
>+
>+Use $(CC) instead of gcc directly. Makes sure that the right options
>+are being passed for cross-compile.
>+
>+Signed-off-by: Anuj Mittal
>+---
>+ contrib/qat/qat_mem/Makefile |2 +-
>+ 1 file changed, 1 insertion(+), 1 deletion(-)
>+
>+diff --git a/contrib/qat/qat_mem/Makefile
>+b/contrib/qat/qat_mem/Makefile index 0a521f2..2c7c8dc 100644
>+--- a/contrib/qat/qat_mem/Makefile
> b/contrib/qat/qat_mem/Makefile
>+@@ -64,7 +64,7 @@ MODULENAME := qat_mem
>+ KDIR := $(KERNEL_SOURCE_ROOT)
>+ PWD := $(shell pwd)
>+
>+-CC := gcc -Wall -imacros
>$(KERNEL_SOURCE_ROOT)/include/generated/autoconf.h
>++CC := $(CC) -Wall -imacros
>$(KERNEL_SOURCE_ROOT)/include/generated/autoconf.h
>+
>+ ifeq ($(KERNELRELEASE),)
>+ all: $(MODULENAME)_test
>+--
>+1.7.9.5
>+
>--
>1.7.9.5
>
>--
>___
>meta-intel mailing list
>meta-intel@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-intel
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [dizzy][PATCH 2/2] meta-crystalforest: rename zlib-qat recipe
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of Anuj Mittal
>Sent: Thursday, July 16, 2015 12:54 PM
>To: meta-intel@yoctoproject.org
>Subject: [meta-intel] [dizzy][PATCH 2/2] meta-crystalforest: rename zlib-qat
>recipe
>
>Rename zlib-qat recipe to include version info.
>
>Signed-off-by: Anuj Mittal
Acked-by: Ong Boon Leong
>---
> .../{zlib-qat.bb => zlib-qat_0.4.7-002.bb} |0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename meta-crystalforest/recipes-extended/zlib-qat/{zlib-qat.bb => zlib-
>qat_0.4.7-002.bb} (100%)
>
>diff --git a/meta-crystalforest/recipes-extended/zlib-qat/zlib-qat.bb b/meta-
>crystalforest/recipes-extended/zlib-qat/zlib-qat_0.4.7-002.bb
>similarity index 100%
>rename from meta-crystalforest/recipes-extended/zlib-qat/zlib-qat.bb
>rename to meta-crystalforest/recipes-extended/zlib-qat/zlib-qat_0.4.7-002.bb
>--
>1.7.9.5
>
>--
>___
>meta-intel mailing list
>meta-intel@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/meta-intel
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 12/16] meta-isg: dpdk: rearrange common meta-data from dpdk_1.8.0.bb into dpdk.inc
Extract out common meta-data from dpdk_1.8.0.bb into dpdk.inc for better
scalability into future dpdk.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc | 24 +++
.../common/recipes-extended/dpdk/dpdk_1.8.0.bb | 32
2 files changed, 24 insertions(+), 32 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index e1670c5..4125126 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -18,6 +18,25 @@ export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
export RTE_KERNELDIR_OUT = "${STAGING_KERNEL_BUILDDIR}"
export INSTALL_PATH = "${prefix}/dpdk"
+export SYSROOTPATH = "--sysroot=${STAGING_DIR_HOST}"
+export DPDK_TARGET_MACH = "${@get_dpdk_target_mach(bb,d)}"
+
+# The list of intel Comms platforms and their target machine
+# process mapping. The supported target machine is listed under
+# dpdk/mk/machine
+def get_dpdk_target_mach(bb, d):
+target_arch = d.getVar('MACHINE_ARCH', True)
+multiarch_options = {
+"mohonpeak64":"atm",
+"mohonpeak32":"atm",
+"crystalforest": "ivb",
+"romley": "snd",
+"romley-ivb": "ivb",
+}
+
+if target_arch in multiarch_options :
+return multiarch_options[target_arch]
+return ""
do_configure () {
#
@@ -38,6 +57,11 @@ do_compile () {
EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
CROSS="${TARGET_PREFIX}" \
prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
+
+ cd ${S}/examples/
+ oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR}" \
+ EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
+ CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
}
do_install () {
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
index 7a278b6..a0f8d8a 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
@@ -24,38 +24,6 @@ PACKAGECONFIG[dpdk_qat] = ",,qat"
PACKAGECONFIG[vhost] = ",,fuse"
PACKAGECONFIG[libvirt] = ",,libvirt"
-# The list of intel Comms platforms and their target machine
-# process mapping. The supported target machine is listed under
-# dpdk/mk/machine
-def get_dpdk_target_mach(bb, d):
-target_arch = d.getVar('MACHINE_ARCH', True)
-multiarch_options = {
-"mohonpeak64":"atm",
-"mohonpeak32":"atm",
-"crystalforest": "ivb",
-"romley": "snd",
-"romley-ivb": "ivb",
-}
-
-if target_arch in multiarch_options :
-return multiarch_options[target_arch]
-return ""
-
export CONFIG_EXAMPLE_DPDK_QAT = "${@base_contains('PACKAGECONFIG',
'dpdk_qat', 'y', 'n', d)}"
export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@base_contains('PACKAGECONFIG',
'libvirt', 'y', 'n', d)}"
export CONFIG_VHOST_ENABLED = "${@base_contains('PACKAGECONFIG', 'vhost', 'y',
'n', d)}"
-export SYSROOTPATH = "--sysroot=${STAGING_DIR_HOST}"
-export DPDK_TARGET_MACH = "${@get_dpdk_target_mach(bb,d)}"
-
-do_compile_append () {
-
- cd ${S}/examples/
-
- ###
- # In order to make use of dpdk.inc for example app installation
- # without failure, override the default build directory
- ###
- oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR}" \
- EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
- CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
-}
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 14/16] meta-isg: dpdk: renaming patches which are common to DPDK v1.8 and DPDK v2.0
From: WU CHIA CHUAN For patches which are common to DPDK v1.8 and DPDK v2.0, they are renamed to following file naming format for clarity dpdk-1.8.0-and-2.0.0*.patch. Signed-off-by: WU CHIA CHUAN Signed-off-by: Ong Boon Leong --- ...-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch | 52 0-add-sysroot-option-within-app-makefile.patch | 33 - ...-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch | 52 0-add-sysroot-option-within-app-makefile.patch | 33 + 0-dpdk-defconfig-select-RTE_MACHINE-type.patch | 48 ++ ...dd-config-variable-to-enable-disable-dpdk.patch | 44 + 0-dpdk-defconfig-select-RTE_MACHINE-type.patch | 48 -- ...d-config-variable-to-enable-disable-dpdk_.patch | 44 - .../common/recipes-extended/dpdk/dpdk_1.8.0.bb |8 +-- 9 files changed, 181 insertions(+), 181 deletions(-) delete mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch delete mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-add-sysroot-option-within-app-makefile.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-type.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-examples-add-config-variable-to-enable-disable-dpdk.patch delete mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch delete mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch deleted file mode 100644 index bfef221..000 --- a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch +++ /dev/null @@ -1,52 +0,0 @@ -From 69238a0b910bca43ef13154718a7a6c9b0dabe8a Mon Sep 17 00:00:00 2001 -From: Ong Boon Leong -Date: Thu, 25 Jun 2015 15:39:38 +0800 -Subject: [PATCH] dpdk v1.8.0: add RTE_KERNELDIR_OUT to split kernel build - artifact - -Introduce RTE_KERNELDIR_OUT to be the path to which kernel build -artifacts are located. This is for matching the workflow change -since Yocto Project v1.8 onwards whereby tmp/work-shared contains -separate directories for kernel source and kernel artifacts. - -Upstream-Status: Inappropriate [configuration] - -Signed-off-by: Ong Boon Leong - mk/rte.module.mk |6 +++--- - 1 file changed, 3 insertions(+), 3 deletions(-) - -diff --git a/mk/rte.module.mk b/mk/rte.module.mk -index 7bf77c1..d4253a5 100644 a/mk/rte.module.mk -+++ b/mk/rte.module.mk -@@ -77,7 +77,7 @@ build: _postbuild - # build module - $(MODULE).ko: $(SRCS_LINKS) - @if [ ! -f $(notdir Makefile) ]; then ln -nfs $(SRCDIR)/Makefile . ; fi -- @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) \ -+ @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) \ - CC=$(KERNELCC) CROSS_COMPILE=$(CROSS) V=$(if $V,1,0) - - # install module in $(RTE_OUTPUT)/kmod -@@ -88,7 +88,7 @@ $(RTE_OUTPUT)/kmod/$(MODULE).ko: $(MODULE).ko - - # install module - modules_install: -- @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) \ -+ @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) \ - modules_install - - .PHONY: clean -@@ -98,7 +98,7 @@ clean: _postclean - .PHONY: doclean - doclean: - @if [ ! -f $(notdir Makefile) ]; then ln -nfs $(SRCDIR)/Makefile . ; fi -- $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) clean -+ $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) clean - @$(foreach FILE,$(SRCS-y) $(SRCS-n) $(SRCS-),\ - if [ -h $(notdir $(FILE)) ]; then rm -f $(notdir $(FILE)) ; fi ;) - @if [ -h $(notdir Makefile) ]; then rm -f $(notdir Makefile) ; fi --- -1.7.9.5 - diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch deleted file mode 100644 index 02c7dc3..000 --- a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch +++ /dev/null @@ -1,33 +0,0 @@ -From 3112250f6452215890fc7db73c8127e111af956f Mon Sep 17 00:00:00 2001 -From: Ong Boon Leong -Date: Thu, 2 Jul 2015 23:51:01 +0800 -Subject: [PATCH
[meta-intel] [master & fido][PATCH 11/16] meta-isg: dpdk: intro recipe for DPDK v1.8.0
This patch adds the support for DPDK v1.8.0 from dpdk.org.
It introduces PACKAGECONFIG options for enabling Virtualization Technology
and QuickAssiste Technology with DPDK.
There is couple of additional DPDK Makefile & config patches to enable
PACKAGECONFIG said above.
Signed-off-by: Ong Boon Leong
---
.../common/recipes-extended/dpdk/dpdk_1.8.0.bb | 61
1 file changed, 61 insertions(+)
create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
new file mode 100644
index 000..7a278b6
--- /dev/null
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
@@ -0,0 +1,61 @@
+include dpdk.inc
+
+SRC_URI = "http://dpdk.org/browse/dpdk/snapshot/dpdk-${PV}.tar.gz;name=dpdk \
+
file://dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch \
+
file://dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch
\
+ file://dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch \
+ file://dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch \
+ file://dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch \
+ "
+
+SRC_URI[dpdk.md5sum] = "11ad8785aaa869cc87265bcb8d828f22"
+SRC_URI[dpdk.sha256sum] =
"9f5386830bd999355182e20408f3fc2cfa0802a4497fdded8d43202feede1939"
+
+export EXAMPLES_BUILD_DIR = "${RTE_TARGET}"
+export ARCHDIR = "generic"
+
+# dpdk example apps dpdk_qat and vhost have dependancy on fuse and qat.
+# fuse is in meta-filesystems and qat is not yet upstreamed.
+# So adding mechanism to explicitly disable the use of fuse and qat.
+# To enable, uncomment the below line or include in .bbappend.
+# PACKAGECONFIG ?= " dpdk_qat vhost libvirt"
+
+PACKAGECONFIG[dpdk_qat] = ",,qat"
+PACKAGECONFIG[vhost] = ",,fuse"
+PACKAGECONFIG[libvirt] = ",,libvirt"
+
+# The list of intel Comms platforms and their target machine
+# process mapping. The supported target machine is listed under
+# dpdk/mk/machine
+def get_dpdk_target_mach(bb, d):
+target_arch = d.getVar('MACHINE_ARCH', True)
+multiarch_options = {
+"mohonpeak64":"atm",
+"mohonpeak32":"atm",
+"crystalforest": "ivb",
+"romley": "snd",
+"romley-ivb": "ivb",
+}
+
+if target_arch in multiarch_options :
+return multiarch_options[target_arch]
+return ""
+
+export CONFIG_EXAMPLE_DPDK_QAT = "${@base_contains('PACKAGECONFIG',
'dpdk_qat', 'y', 'n', d)}"
+export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@base_contains('PACKAGECONFIG',
'libvirt', 'y', 'n', d)}"
+export CONFIG_VHOST_ENABLED = "${@base_contains('PACKAGECONFIG', 'vhost', 'y',
'n', d)}"
+export SYSROOTPATH = "--sysroot=${STAGING_DIR_HOST}"
+export DPDK_TARGET_MACH = "${@get_dpdk_target_mach(bb,d)}"
+
+do_compile_append () {
+
+ cd ${S}/examples/
+
+ ###
+ # In order to make use of dpdk.inc for example app installation
+ # without failure, override the default build directory
+ ###
+ oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR}" \
+ EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
+ CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
+}
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 10/16] meta-isg: dpdk v1.8: introduce target machine selection for DPDK.
DPDK default config set the TARGET machine type to native which is incorrect. The SDK assumes that the DPDK package is built and installed natively. So, to support cross-compilation uses, we add DPDK_TARGET_MACH option here. This variable should be defined at either dpdk bb or bbappend file. Signed-off-by: Ong Boon Leong --- 0-dpdk-defconfig-select-RTE_MACHINE-type.patch | 48 1 file changed, 48 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch new file mode 100644 index 000..979541e --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch @@ -0,0 +1,48 @@ +From 6eaf6b1a61321acb824f9672c12d0e30a2110f52 Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Mon, 16 Mar 2015 11:10:43 +0800 +Subject: [PATCH] DPDK: defconfig: add selectable RTE_MACHINE option + +In order to make sure that DPDK build environment config can handle the +package being built on different build machine for different target machine +which will have different x86 architecture intrinsics than the build machine, +we introduce DPDK_TARGET_MACH to be tunable from dpdk recipe. The machine +type can be under mk/machine folder. + +Upstream-Status: Inappropriate [configuration] + +Signed-off-by: Ong Boon Leong +--- + config/defconfig_i686-native-linuxapp-gcc |2 +- + config/defconfig_x86_64-native-linuxapp-gcc |2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/config/defconfig_i686-native-linuxapp-gcc b/config/defconfig_i686-native-linuxapp-gcc +index a90de9b..c9a74a5 100644 +--- a/config/defconfig_i686-native-linuxapp-gcc b/config/defconfig_i686-native-linuxapp-gcc +@@ -32,7 +32,7 @@ + + #include "common_linuxapp" + +-CONFIG_RTE_MACHINE="native" ++CONFIG_RTE_MACHINE=$(DPDK_TARGET_MACH) + + CONFIG_RTE_ARCH="i686" + CONFIG_RTE_ARCH_I686=y +diff --git a/config/defconfig_x86_64-native-linuxapp-gcc b/config/defconfig_x86_64-native-linuxapp-gcc +index 60baf5b..0e4802d 100644 +--- a/config/defconfig_x86_64-native-linuxapp-gcc b/config/defconfig_x86_64-native-linuxapp-gcc +@@ -32,7 +32,7 @@ + + #include "common_linuxapp" + +-CONFIG_RTE_MACHINE="native" ++CONFIG_RTE_MACHINE=$(DPDK_TARGET_MACH) + + CONFIG_RTE_ARCH="x86_64" + CONFIG_RTE_ARCH_X86_64=y +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 13/16] meta-isg: dpdk: move the do_install hostapp directory from dpdk.inc to dpdk_1.8.0.bb
From: WU CHIA CHUAN
dpdk.inc is common to dpdk_1.8.0.bb and dpdk_2.0.0.bb, since DPDK v2.0 is no
longer have
hostapp directory, so we only perform hostapp installation for DPDK v1.8.
Signed-off-by: WU CHIA CHUAN
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc |2 --
.../common/recipes-extended/dpdk/dpdk_1.8.0.bb |6 ++
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 4125126..85b88fa 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -71,7 +71,6 @@ do_install () {
${D}/${INSTALL_PATH}/tools \
${D}/${INSTALL_PATH}/${RTE_TARGET} \
${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
- ${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp \
${D}${includedir} \
${D}${includedir}/${ARCHDIR} \
${D}${includedir}/exec-env \
@@ -90,7 +89,6 @@ do_install () {
# Install applications
install -m 0755 ${S}/${RTE_TARGET}/app/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/app/
- install -m 0755 ${S}/${RTE_TARGET}/hostapp/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp/
# Install examples
for dirname in ${S}/examples/*
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
index a0f8d8a..cab76cc 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
@@ -27,3 +27,9 @@ PACKAGECONFIG[libvirt] = ",,libvirt"
export CONFIG_EXAMPLE_DPDK_QAT = "${@base_contains('PACKAGECONFIG',
'dpdk_qat', 'y', 'n', d)}"
export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@base_contains('PACKAGECONFIG',
'libvirt', 'y', 'n', d)}"
export CONFIG_VHOST_ENABLED = "${@base_contains('PACKAGECONFIG', 'vhost', 'y',
'n', d)}"
+
+do_install_append () {
+
+ install -m 0755 -d ${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp
+ install -m 0755 ${S}/${RTE_TARGET}/hostapp/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp/
+}
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 16/16] meta-isg: dpdk v2.0.0: initial DPDK v2.0.0 enabling recipe
From: WU CHIA CHUAN
This patch makes reference to early dpdk meta-data implementation
and extends it to support DPDK v2.0.0.
Signed-off-by: WU CHIA CHUAN
Signed-off-by: Ong Boon Leong
---
.../common/recipes-extended/dpdk/dpdk_2.0.0.bb | 29
1 file changed, 29 insertions(+)
create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
b/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
new file mode 100644
index 000..cb158b9
--- /dev/null
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
@@ -0,0 +1,29 @@
+include dpdk.inc
+
+SRC_URI = "http://dpdk.org/browse/dpdk/snapshot/dpdk-${PV}.tar.gz;name=dpdk \
+
file://dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch
\
+
file://dpdk-1.8.0-and-2.0.0-examples-add-config-variable-to-enable-disable-dpdk.patch
\
+
file://dpdk-1.8.0-and-2.0.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch \
+
file://dpdk-1.8.0-and-2.0.0-add-sysroot-option-within-app-makefile.patch \
+
file://dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-type.patch \
+ "
+
+SRC_URI[dpdk.md5sum] = "e9e7935c9eec920841ad373949514934"
+SRC_URI[dpdk.sha256sum] =
"643789a3be5ba44dd84d6b248cdf5471b260f8736dada177dadf076aebfbff3f"
+
+export EXAMPLES_BUILD_DIR = "${RTE_TARGET}"
+export ARCHDIR = "generic"
+
+# dpdk example apps dpdk_qat and vhost have dependancy on fuse and qat.
+# fuse is in meta-filesystems and qat is not yet upstreamed.
+# So adding mechanism to explicitly disable the use of fuse and qat.
+# To enable, uncomment the below line or include in .bbappend.
+# PACKAGECONFIG ?= " dpdk_qat vhost libvirt"
+
+PACKAGECONFIG[dpdk_qat] = ",,qat"
+PACKAGECONFIG[vhost] = ",,fuse"
+PACKAGECONFIG[libvirt] = ",,libvirt"
+
+export CONFIG_EXAMPLE_DPDK_QAT = "${@base_contains('PACKAGECONFIG',
'dpdk_qat', 'y', 'n', d)}"
+export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@base_contains('PACKAGECONFIG',
'libvirt', 'y', 'n', d)}"
+export CONFIG_VHOST_ENABLED = "${@base_contains('PACKAGECONFIG', 'vhost', 'y',
'n', d)}"
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 07/16] meta-isg: dpdk v1.8: add patches for qat, vhost and libvirt PACKAGECONFIG
Introduce two patches to enable DPDK config file to support PACKAGECONFIG options for QAT, vhost and libvirt. Signed-off-by: Ong Boon Leong --- ...ld-config-VHOST-in-common_linuxapp-config.patch | 43 +++ ...d-config-variable-to-enable-disable-dpdk_.patch | 44 2 files changed, 87 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch new file mode 100644 index 000..e8ded8d --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch @@ -0,0 +1,43 @@ +From c1a59d62f2aa7656060d8ebcc8e45e852d931ff1 Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Tue, 17 Feb 2015 00:23:12 +0800 +Subject: [PATCH] dpdk: enable VHOST build config in common_linuxapp config + +Introduce CONFIG_VHOST_ENABLED for package config selection purpose in +building vhost feature. + +Upstream-Status: Inappropriate [configuration] + +Signed-off-by: Ong Boon Leong +--- + config/common_linuxapp |6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/config/common_linuxapp b/config/common_linuxapp +index 2f9643b..67f5edb 100644 +--- a/config/common_linuxapp b/config/common_linuxapp +@@ -361,9 +361,9 @@ CONFIG_RTE_LIBRTE_PIPELINE=y + # + CONFIG_RTE_LIBRTE_KNI=y + CONFIG_RTE_KNI_KO_DEBUG=n +-CONFIG_RTE_KNI_VHOST=n ++CONFIG_RTE_KNI_VHOST=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_KNI_VHOST_MAX_CACHE_SIZE=1024 +-CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=n ++CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_KNI_VHOST_DEBUG_RX=n + CONFIG_RTE_KNI_VHOST_DEBUG_TX=n + +@@ -372,7 +372,7 @@ CONFIG_RTE_KNI_VHOST_DEBUG_TX=n + # fuse-devel is needed to run vhost. + # fuse-devel enables user space char driver development + # +-CONFIG_RTE_LIBRTE_VHOST=n ++CONFIG_RTE_LIBRTE_VHOST=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_LIBRTE_VHOST_DEBUG=n + + # +-- +1.7.9.5 + diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch new file mode 100644 index 000..c86c1a1 --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch @@ -0,0 +1,44 @@ +From 54c95ca8f76f412c94a9f61e3756420ac554310b Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Thu, 12 Feb 2015 16:33:49 +0800 +Subject: [PATCH] examples: add config variable to enable/disable dpdk_qat + +Upstream-Status: Inappropriate [configuration] + +This patch adss following example build configs: + +1) CONFIG_EXAMPLE_DPDK_QAT is used to control dpdk_qat example + by PACKAGECONFIG. + +2) CONFIG_EXAMPLE_VM_POWER_MANAGER is used to control vm_power_manager + example by PACKAGECONFIG. + +Signed-off-by: Ong Boon Leong +--- + examples/Makefile |4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/examples/Makefile b/examples/Makefile +index 81f1d2f..7e9c7bd 100644 +--- a/examples/Makefile b/examples/Makefile +@@ -40,7 +40,7 @@ include $(RTE_SDK)/mk/rte.vars.mk + DIRS-y += cmdline + DIRS-$(CONFIG_RTE_LIBRTE_DISTRIBUTOR) += distributor + ifneq ($(ICP_ROOT),) +-DIRS-y += dpdk_qat ++DIRS-$(CONFIG_EXAMPLE_DPDK_QAT) += dpdk_qat + endif + DIRS-y += exception_path + DIRS-y += helloworld +@@ -68,6 +68,6 @@ DIRS-$(CONFIG_RTE_LIBRTE_VHOST) += vhost + DIRS-$(CONFIG_RTE_LIBRTE_XEN_DOM0) += vhost_xen + DIRS-y += vmdq + DIRS-y += vmdq_dcb +-DIRS-y += vm_power_manager ++DIRS-$(CONFIG_EXAMPLE_VM_POWER_MANAGER) += vm_power_manager + + include $(RTE_SDK)/mk/rte.extsubdir.mk +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 08/16] meta-isg: dpdk: fix GCC compiler LDFLAG and CFLAG issue
DPDK v1.8.0 has some change made on app makefile that breaks dpdk.inc
may on passing in EXTRA_CFLAGS AND EXTRA_LDFLAGS. So this patch
re-tune the dpdk.inc to align to the change.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 61b3259..e1670c5 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -34,8 +34,8 @@ do_compile () {
unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
cd ${S}/${RTE_TARGET}
- oe_runmake EXTRA_LDFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
- EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
+ oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR}" \
+ EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
CROSS="${TARGET_PREFIX}" \
prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
}
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 06/16] meta-isg: dpdk v1.8.0: add makefile patches to support split kernel output
Starting form YPv1.8.y onwards, the kernel build output is separately kept under work-shared. Signed-off-by: Ong Boon Leong --- ...-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch | 52 1 file changed, 52 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch new file mode 100644 index 000..bfef221 --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch @@ -0,0 +1,52 @@ +From 69238a0b910bca43ef13154718a7a6c9b0dabe8a Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Thu, 25 Jun 2015 15:39:38 +0800 +Subject: [PATCH] dpdk v1.8.0: add RTE_KERNELDIR_OUT to split kernel build + artifact + +Introduce RTE_KERNELDIR_OUT to be the path to which kernel build +artifacts are located. This is for matching the workflow change +since Yocto Project v1.8 onwards whereby tmp/work-shared contains +separate directories for kernel source and kernel artifacts. + +Upstream-Status: Inappropriate [configuration] + +Signed-off-by: Ong Boon Leong +--- + mk/rte.module.mk |6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/mk/rte.module.mk b/mk/rte.module.mk +index 7bf77c1..d4253a5 100644 +--- a/mk/rte.module.mk b/mk/rte.module.mk +@@ -77,7 +77,7 @@ build: _postbuild + # build module + $(MODULE).ko: $(SRCS_LINKS) + @if [ ! -f $(notdir Makefile) ]; then ln -nfs $(SRCDIR)/Makefile . ; fi +- @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) \ ++ @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) \ + CC=$(KERNELCC) CROSS_COMPILE=$(CROSS) V=$(if $V,1,0) + + # install module in $(RTE_OUTPUT)/kmod +@@ -88,7 +88,7 @@ $(RTE_OUTPUT)/kmod/$(MODULE).ko: $(MODULE).ko + + # install module + modules_install: +- @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) \ ++ @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) \ + modules_install + + .PHONY: clean +@@ -98,7 +98,7 @@ clean: _postclean + .PHONY: doclean + doclean: + @if [ ! -f $(notdir Makefile) ]; then ln -nfs $(SRCDIR)/Makefile . ; fi +- $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) clean ++ $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) clean + @$(foreach FILE,$(SRCS-y) $(SRCS-n) $(SRCS-),\ + if [ -h $(notdir $(FILE)) ]; then rm -f $(notdir $(FILE)) ; fi ;) + @if [ -h $(notdir Makefile) ]; then rm -f $(notdir Makefile) ; fi +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 15/16] meta-isg: dpdk v2.0.0: add patch to handle vhost and ip_fragmentation applications
From: WU CHIA CHUAN Introduce a patch to enable/disable the vhost and ip_fragmentation examples applications under common_linuxapp config file. The flag introduce is controlled by PACKAGECONFIG. Signed-off-by: WU CHIA CHUAN Signed-off-by: Ong Boon Leong --- ...T-and-ip_fragmentation-in-common_linuxapp.patch | 50 1 file changed, 50 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch new file mode 100644 index 000..45ce5e0 --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch @@ -0,0 +1,50 @@ +From 3d3c03d947394696565b3bb7bed8c900de057a28 Mon Sep 17 00:00:00 2001 +From: WU CHIA CHUAN +Date: Thu, 2 Jul 2015 15:59:18 +0800 +Subject: [PATCH] dpdk enable VHOST and ip_fragmentation in common_linuxapp config + +Introduce CONFIG_VHOST_ENABLED for package config selection purpose in +building vhost feature. + +Upstream-Status: Inappropriate [configuration] + +Signed-off-by: WU CHIA CHUAN +--- + config/common_linuxapp | 11 --- + 1 file changed, 8 insertions(+), 3 deletions(-) + +diff --git a/config/common_linuxapp b/config/common_linuxapp +index 0b25f34..000f950 100644 +--- a/config/common_linuxapp b/config/common_linuxapp +@@ -406,19 +406,24 @@ CONFIG_RTE_LIBRTE_PIPELINE=y + CONFIG_RTE_LIBRTE_KNI=y + CONFIG_RTE_KNI_PREEMPT_DEFAULT=y + CONFIG_RTE_KNI_KO_DEBUG=n +-CONFIG_RTE_KNI_VHOST=n ++CONFIG_RTE_KNI_VHOST=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_KNI_VHOST_MAX_CACHE_SIZE=1024 +-CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=n ++CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_KNI_VHOST_DEBUG_RX=n + CONFIG_RTE_KNI_VHOST_DEBUG_TX=n + + # ++# Compile ip_fragmentation ++# ++CONFIG_RTE_IP_FRAG=y ++ ++# + # Compile vhost library + # fuse-devel is needed to run vhost-cuse. + # fuse-devel enables user space char driver development + # vhost-user is turned on by default. + # +-CONFIG_RTE_LIBRTE_VHOST=n ++CONFIG_RTE_LIBRTE_VHOST=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_LIBRTE_VHOST_USER=y + CONFIG_RTE_LIBRTE_VHOST_DEBUG=n + +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 09/16] meta-isg: dpdk v1.8: add app makefile patch to enable sysroot setting
DPDK v1.8.0 app Makefile does not support "--sysroot=" option in LDFLAGS because of Makefile internal logic that always add -Wl, before. This causes poky GNU linker search path issue for target machine sysroot usr/lib. Signed-off-by: Ong Boon Leong --- 0-add-sysroot-option-within-app-makefile.patch | 33 1 file changed, 33 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch new file mode 100644 index 000..02c7dc3 --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch @@ -0,0 +1,33 @@ +From 3112250f6452215890fc7db73c8127e111af956f Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Thu, 2 Jul 2015 23:51:01 +0800 +Subject: [PATCH] dpdk v1.8.0: add --sysroot option within app makefile + +Upstream-Status: Inappropriate [configuration] + +in DPDK v1.8.0, rte.app.mk has been changed to add -Wl, to +all items listed under EXTRA_LDFLAGS. It causes --sysroot= + to not setup correctly when we depends on gcc to setup +for GNU ld. + +Signed-off-by: Ong Boon Leong +--- + mk/rte.app.mk |2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/mk/rte.app.mk b/mk/rte.app.mk +index e1a0dbf..9528588 100644 +--- a/mk/rte.app.mk b/mk/rte.app.mk +@@ -259,7 +259,7 @@ ifeq ($(LINK_USING_CC),1) + override EXTRA_LDFLAGS := $(call linkerprefix,$(EXTRA_LDFLAGS)) + O_TO_EXE = $(CC) $(CFLAGS) $(LDFLAGS_$(@)) \ + -Wl,-Map=$(@).map,--cref -o $@ $(OBJS-y) $(call linkerprefix,$(LDFLAGS)) \ +- $(EXTRA_LDFLAGS) $(call linkerprefix,$(LDLIBS)) ++ $(EXTRA_LDFLAGS) $(SYSROOTPATH) $(call linkerprefix,$(LDLIBS)) + else + O_TO_EXE = $(LD) $(LDFLAGS) $(LDFLAGS_$(@)) $(EXTRA_LDFLAGS) \ + -Map=$(@).map --cref -o $@ $(OBJS-y) $(LDLIBS) +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 05/16] meta-isg: dpdk: add external kernel module build handling for tmp/work-shared
DPDK software builds external kernel modules igb_uio.ko, rte_kni.ko & etc that
depend on the availability of kernel source. With splitting of kernel source
and artifacts into separate fodlers under tmp/work-shared, we need to handle
this by introducing do_configure[depends] += "virtual/kernel:do_shared_workdir"
to ensure build dependency is satisfied.
Refer to poky 46cdaf1 kernel: move source and build output to work-shared
This patch also introduces RTE_KERNELDIR_OUT variable to be used to setup
the kernel build artifact path. RTE_KERNELDIR remains as the kernel source path.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc |3 +++
1 file changed, 3 insertions(+)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 1d985ff..61b3259 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -4,6 +4,8 @@ LICENSE = "BSD & LGPLv2 & GPLv2"
LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe"
RDEPENDS_${PN} += "python-subprocess"
+DEPENDS = "virtual/kernel"
+do_configure[depends] += "virtual/kernel:do_shared_workdir"
inherit module
@@ -14,6 +16,7 @@ export RTE_TARGET="${@bb.utils.contains("TUNE_FEATURES",
"corei7", "x86_64-ivshm
export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
+export RTE_KERNELDIR_OUT = "${STAGING_KERNEL_BUILDDIR}"
export INSTALL_PATH = "${prefix}/dpdk"
do_configure () {
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 04/16] meta-isg: dpdk: introduce ARCHDIR variable to dpdk.inc
Starting from DPDK v1.8 onwards, there is name change from
include/arch to include/generic under build directory. So to cater
for such change, we introduce ARCHDIR variable. This variable should
be set under individual version of dpdk recipe.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 910feb4..1d985ff 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -46,7 +46,7 @@ do_install () {
${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp \
${D}${includedir} \
- ${D}${includedir}/arch \
+ ${D}${includedir}/${ARCHDIR} \
${D}${includedir}/exec-env \
${D}${libdir} \
${D}${MODULE_DIR}
@@ -57,7 +57,7 @@ do_install () {
install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
- install -m 640 ${S}/${RTE_TARGET}/include/arch/*.h
${D}${includedir}/arch/
+ install -m 640 ${S}/${RTE_TARGET}/include/${ARCHDIR}/*.h
${D}${includedir}/${ARCHDIR}/
install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*.h
${D}${includedir}/exec-env/
install -m 0755 ${S}/tools/*.py
${D}/${INSTALL_PATH}/tools/
@@ -94,7 +94,7 @@ FILES_${PN}-doc += "\
FILES_${PN}-dev += " \
${INSTALL_PATH}/${RTE_TARGET}/.config \
${includedir} \
- ${includedir}/arch \
+ ${includedir}/${ARCHDIR} \
${includedir}/exec-env \
"
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 03/16] meta-isg: dpdk: improve software installation task
do_install() has been non-scalable due to different DPDK SW releases
offer increasingly more examples. So, this patch is intended to make
the do_install() simplified by using regular expression technique to
extract out executables name that are built.
Tested this patch with DPDK v1.6.0r2 and v1.7.0 and the software packages
look intact.
Signed-off-by: Ong Boon Leong
Signed-off-by: Saul Wold
(cherry picked from commit a43871c39ae462647ebe58679b92cd34c8ae48a6)
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc | 83
1 file changed, 26 insertions(+), 57 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 5e7d52b..910feb4 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -9,13 +9,13 @@ inherit module
export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
export RTE_SDK = "${S}"
-export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
+export RTE_TARGET="${@bb.utils.contains("TUNE_FEATURES", "corei7",
"x86_64-ivshmem-linuxapp-gcc", "i686-native-linuxapp-gcc", d)}"
+
export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
export INSTALL_PATH = "${prefix}/dpdk"
-
do_configure () {
#
### default value for prefix is "usr", unsetting it, so it
@@ -25,10 +25,8 @@ do_configure () {
unset prefix
make O=$RTE_TARGET T=$RTE_TARGET config
-
}
-
do_compile () {
unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
@@ -37,10 +35,8 @@ do_compile () {
EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
CROSS="${TARGET_PREFIX}" \
prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
-
}
-
do_install () {
install -m 0755 -d ${D}/${INSTALL_PATH} \
@@ -48,70 +44,36 @@ do_install () {
${D}/${INSTALL_PATH}/tools \
${D}/${INSTALL_PATH}/${RTE_TARGET} \
${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
+ ${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp \
${D}${includedir} \
${D}${includedir}/arch \
${D}${includedir}/exec-env \
${D}${libdir} \
${D}${MODULE_DIR}
- install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
${D}${MODULE_DIR}/
- install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
${D}${MODULE_DIR}/
+ install -m 0755 ${S}/${RTE_TARGET}/kmod/*.ko${D}${MODULE_DIR}/
install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
- install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
- install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/exec-env/
+ install -m 640 ${S}/${RTE_TARGET}/include/arch/*.h
${D}${includedir}/arch/
+ install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*.h
${D}${includedir}/exec-env/
install -m 0755 ${S}/tools/*.py
${D}/${INSTALL_PATH}/tools/
+ # Install applications
+ install -m 0755 ${S}/${RTE_TARGET}/app/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/app/
+ install -m 0755 ${S}/${RTE_TARGET}/hostapp/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp/
- #Install test applications
- install -m 0755 ${S}/${RTE_TARGET}/app/test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/testpmd
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/dump_cfg
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/cmdline_test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
-
-
- # Install example applications
- # It is expected that user of this include file should define
EXAMPLES_BUILD_DIR
- for app in ${S}/examples/*
+ # Install examples
+ for dirname in ${S}/examples/*
do
- case `basename ${app}` in
- "dpdk_qat" | "vhost" | "vhost_xen" | "Makefile" ) continue
- ;;
- "l2fwd-ivshmem")
- install -
[meta-intel] [master & fido][PATCH 01/16] meta-isg: Making meta-isg as a layer
From: venkatasubramanian pattu
This layer provides additional common recipes to be used by all IOTG maintained
platforms.
Signed-off-by: venkatasubramanian pattu
Signed-off-by: Saul Wold
(cherry picked from commit 6a334428e1b92de2b6c322654ae6f64d3ff55ab6)
Signed-off-by: Ong Boon Leong
---
meta-isg/conf/layer.conf | 12
1 file changed, 12 insertions(+)
create mode 100644 meta-isg/conf/layer.conf
diff --git a/meta-isg/conf/layer.conf b/meta-isg/conf/layer.conf
new file mode 100644
index 000..48ad0c3
--- /dev/null
+++ b/meta-isg/conf/layer.conf
@@ -0,0 +1,12 @@
+# We have a conf and classes directory, add to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have recipes-* directories, add to BBFILES
+BBFILES += "${LAYERDIR}/common/recipes-*/*/*.bb \
+${LAYERDIR}/common/recipes-*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "isg"
+BBFILE_PATTERN_isg := "^${LAYERDIR}/common/"
+BBFILE_PRIORITY_isg = "5"
+
+LAYERDEPENDS_isg = "intel"
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [master & fido][PATCH 02/16] meta-isg: Add include file for DPDK
From: venkatasubramanian pattu
Added include file dpdk.inc to share common functionality based on
dpdk_1.6.0r2
Added a new variable EXAMPLE_BUILD_DIR. This points to apps build
directory which is different in dpdk v1.6.0r2 and v1.7.0.
Users of dpdk.inc have to define EXAMPLE_BUILD_DIR for the
installation of example apps.
This recipe is cherry-picked from branch dizzy and the commit ID:
1c825a06095178c0c51f28d5867549feac8a47f4:meta-intel/common: Add include file
for DPDK
Signed-off-by: venkatasubramanian pattu
Signed-off-by: Saul Wold
(cherry picked from commit 578494c0c4715bb8d24972fa52850e89c36410a1)
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc | 138
1 file changed, 138 insertions(+)
create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk.inc
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
new file mode 100644
index 000..5e7d52b
--- /dev/null
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -0,0 +1,138 @@
+DESCRIPTION = "Intel(r) Data Plane Development Kit"
+HOMEPAGE = "http://dpdk.org";
+LICENSE = "BSD & LGPLv2 & GPLv2"
+LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe"
+
+RDEPENDS_${PN} += "python-subprocess"
+
+inherit module
+
+export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
+export RTE_SDK = "${S}"
+export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
+export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
+export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
+export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
+export INSTALL_PATH = "${prefix}/dpdk"
+
+
+do_configure () {
+ #
+ ### default value for prefix is "usr", unsetting it, so it
+ ### will not be concatenated in ${RTE_TARGET}/Makefile
+ ### which will cause compilation failure
+ #
+ unset prefix
+
+ make O=$RTE_TARGET T=$RTE_TARGET config
+
+}
+
+
+do_compile () {
+ unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
+
+ cd ${S}/${RTE_TARGET}
+ oe_runmake EXTRA_LDFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
+ EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
+ CROSS="${TARGET_PREFIX}" \
+ prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
+
+}
+
+
+do_install () {
+
+ install -m 0755 -d ${D}/${INSTALL_PATH} \
+ ${D}/${INSTALL_PATH}/doc \
+ ${D}/${INSTALL_PATH}/tools \
+ ${D}/${INSTALL_PATH}/${RTE_TARGET} \
+ ${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
+ ${D}${includedir} \
+ ${D}${includedir}/arch \
+ ${D}${includedir}/exec-env \
+ ${D}${libdir} \
+ ${D}${MODULE_DIR}
+
+ install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
${D}${MODULE_DIR}/
+ install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
${D}${MODULE_DIR}/
+
+ install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
+
+ install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
+ install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
+ install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
+ install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/exec-env/
+ install -m 0755 ${S}/tools/*.py
${D}/${INSTALL_PATH}/tools/
+
+
+ #Install test applications
+ install -m 0755 ${S}/${RTE_TARGET}/app/test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+ install -m 0755 ${S}/${RTE_TARGET}/app/testpmd
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+ install -m 0755 ${S}/${RTE_TARGET}/app/dump_cfg
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+ install -m 0755 ${S}/${RTE_TARGET}/app/cmdline_test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+
+
+ # Install example applications
+ # It is expected that user of this include file should define
EXAMPLES_BUILD_DIR
+ for app in ${S}/examples/*
+ do
+ case `basename ${app}` in
+ "dpdk_qat" | "vhost" | "vhost_xen" | "Makefile" ) continue
+ ;;
+ "l2fwd-ivshmem")
+ install -m 0755 ${app}/guest/${EXAMPLES_BUILD_DIR}/app/guest
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+
[meta-intel] [master & fido][PATCH 00/16] add DPDK v1.8 & v2.0 to meta-isg common
Dear maintainers, We have confirmed that the following patchseries applied on both master and fido branch on meta-isg/common folder. The build test on both branches appear satisfactory to us and the packages-split content have been validate to be healthy too. We have also run sanity test of DPDK on River Forest platform to confirm the packages installed are good. So, we are recommending that this series be merged into both master and fido branches to enabling DPDK v1.8.0 and DPDKv2.0.0. This patchseries are the same patch content as the series that was sent with title "DPDK v1.8.0 & v2.0.0 for CID platforms" that was sent early this week. So, you could choose to pick this series or the older series. We just mark here as both master and fido for your convenience. Thanks Chia Chuan and Anuj for helping on running actual test on River Forest platform. Many thanks, Ong Boon Leong Ong Boon Leong (10): meta-isg: dpdk: improve software installation task meta-isg: dpdk: introduce ARCHDIR variable to dpdk.inc meta-isg: dpdk: add external kernel module build handling for tmp/work-shared meta-isg: dpdk v1.8.0: add makefile patches to support split kernel output meta-isg: dpdk v1.8: add patches for qat, vhost and libvirt PACKAGECONFIG meta-isg: dpdk: fix GCC compiler LDFLAG and CFLAG issue meta-isg: dpdk v1.8: add app makefile patch to enable sysroot setting meta-isg: dpdk v1.8: introduce target machine selection for DPDK. meta-isg: dpdk: intro recipe for DPDK v1.8.0 meta-isg: dpdk: rearrange common meta-data from dpdk_1.8.0.bb into dpdk.inc WU CHIA CHUAN (4): meta-isg: dpdk: move the do_install hostapp directory from dpdk.inc to dpdk_1.8.0.bb meta-isg: dpdk: renaming patches which are common to DPDK v1.8 and DPDK v2.0 meta-isg: dpdk v2.0.0: add patch to handle vhost and ip_fragmentation applications meta-isg: dpdk v2.0.0: initial DPDK v2.0.0 enabling recipe venkatasubramanian pattu (2): meta-isg: Making meta-isg as a layer meta-isg: Add include file for DPDK meta-isg/common/recipes-extended/dpdk/dpdk.inc | 132 ...-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch | 52 0-add-sysroot-option-within-app-makefile.patch | 33 + 0-dpdk-defconfig-select-RTE_MACHINE-type.patch | 48 +++ ...dd-config-variable-to-enable-disable-dpdk.patch | 44 +++ ...ld-config-VHOST-in-common_linuxapp-config.patch | 43 +++ ...T-and-ip_fragmentation-in-common_linuxapp.patch | 50 .../common/recipes-extended/dpdk/dpdk_1.8.0.bb | 35 ++ .../common/recipes-extended/dpdk/dpdk_2.0.0.bb | 29 + meta-isg/conf/layer.conf | 12 ++ 10 files changed, 478 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk.inc create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-add-sysroot-option-within-app-makefile.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-type.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-examples-add-config-variable-to-enable-disable-dpdk.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb create mode 100644 meta-isg/conf/layer.conf -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [fido][PATCH 00/16] DPDK v1.8.0 & v2.0.0 for CID platforms
>-Original Message- >From: Saul Wold [mailto:s...@linux.intel.com] >Sent: Thursday, July 9, 2015 11:54 PM >To: Ong, Boon Leong >Cc: meta-intel@yoctoproject.org; chia.chuah...@intel.com >Subject: Re: [meta-intel][fido][PATCH 00/16] DPDK v1.8.0 & v2.0.0 for CID >platforms > >On 07/07/2015 04:20 PM, Ong Boon Leong wrote: >> Dear maintainers, >> >> Firstly, the patch add a layer for meta-isg just like dizzy branch. >> >> Then, the patchseries add the capabillity of DPDKv1.8.0 and DPDKv2.0.0 >> on meta-intel fido branch. It reuses DPDK ingredients from dizzy >> branch as base and further customizes dpdk.inc to handle several build change >across DPDK v1.8.0 & v2.0.0. >> >> Wu, Chia Chuan has contributed the enhancement for DPDK v2.0.0 and I >> have checked and signed-off his contributions. I have validated both >> versions are building fine and the ingredients under packages-split look >> healthy >to my best knowledge. >> >> Chia Chuan has helped in testing the ingredients on CID platforms. >> >> Although it is a long series, but a lot of the commits are >> incrementally small for review. Hope that is fine with you. >> >> Appreciate your help and effort in reviewing this patchseries. >> >> If you find them good, please kindly help to merge them into fido branch. >> >Something I realized would make things much better, can these patches and along >with the QAT and zlib patches actually go into master and then be backported >into >fido? > >This will then keep master current and allow easier update/upgrade pathes for >dpdk, qat and associated work. This is the get stuff in master upstream first >and >then backport? > >Would this be possible? Saul, ok. We will make sure that the patches are sent to be master then considered to be back-ported Into Fido. We were doing catch-up and with this that will safe effort in keeping "upgrading". -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [fido][PATCH v2 2/2] meta-crystalforest: qat makefile patches
>-Original Message- >From: Saul Wold [mailto:s...@linux.intel.com] >Sent: Thursday, July 9, 2015 11:00 PM >To: Ong, Boon Leong >Cc: Mittal, AnujX; meta-intel@yoctoproject.org >Subject: Re: [meta-intel] [fido][PATCH v2 2/2] meta-crystalforest: qat makefile >patches > >On 07/08/2015 10:46 PM, Ong, Boon Leong wrote: >>> -Original Message- >>> From: Saul Wold [mailto:s...@linux.intel.com] >>> Sent: Thursday, July 9, 2015 1:29 PM >>> To: Ong, Boon Leong >>> Cc: Mittal, AnujX; meta-intel@yoctoproject.org >>> Subject: Re: [meta-intel] [fido][PATCH v2 2/2] meta-crystalforest: >>> qat makefile patches >>> >>> On 07/08/2015 03:35 PM, Ong, Boon Leong wrote: >>>>>> I do think that 2/2 --> 1/2 and 1/2 -> 2/2 in this patch-series to >>>>>> avoid partially update the patchseries and have build issue. >>>>>> >>>>> That would have been one option, but since this was a new recipe >>>>> and the patches are required to start with I would prefer to see >>>>> them as one patch, future changes could such as improving or >>>>> modifying a given patch or part of the recipe should be individual >>>>> patches as they they are >>> incremental changes to a given patch. >>>> >>>> Got it. If you find issue in the DPDK series, I will re-format the >>>> patch-series to follow the above principles for the first time >>>> submission of new recipe. Thanks for guidance above. >>>> >>> >>> I think I understand what you are trying to do with the dpdk series, >>> I started looking at it today and began wondering if it would not >>> have been easier to have them collapsed, but I understand that you >>> cherry-picked and then updated, and introduced the patches before the final >recipes. >> >> I opined that a cherry-picked should be a clean pick with no content >> change unless conflict changes is required. Followed by another commit to >> fix the >fido build issue to be explicitly. >> >>> So, when I saw and understood your intent there, having multiple >>> smaller ones is OK. I honestly reviewed the finished product since >>> that was easier than trying to decipher the individual patches though! >> Ya, I understand the difficulty there because collapsing some patches >> may lost the evolution of the dpdk series. I may collapse them in the >> 2nd series (if required), just want to make sure that it is made >> easier for your review and merge. Sorry but thank you for your time and >> effort! >> >> On separate matter, Anuj just shared with me his zlib-qat patch that cherry- >picked patch from dizzy into fido. >> He took the path of "in the same cherry-picked commit, he swapped a >> patch that is zlib-qat is not building on fido, i.e. doing a patch content >> changes on >cherry-picked patch." >> I was not really in favor of such process because I like cherry-picked patch >> to be >as in-tact as possible as the source of it. >> This gives assurance that there is additional hidden ingredients added >> mid-way >that I am not aware of. >> > >So your saying that the cherry-picked version is broken? Ya. It is broken when Anuj pick from dizzy to fido. > >> What is your preference here? We will try to follow what suits your best. >> A) clean cherry-picked then a commit to fix build error >> B) a single commit that has both commits in (A). >> >I think that cherry-picking the patch and then having the minimal change to >make >it work should be 1 patch, this can be done with an interactive rebase and a >squash, but ensure that the commit message reflects this change. > >I think having working patches is important. > Thanks for the advice. Much appreciated. I will pay attention on this. -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [fido][PATCH v2 2/2] meta-crystalforest: qat makefile patches
>-Original Message- >From: Saul Wold [mailto:s...@linux.intel.com] >Sent: Thursday, July 9, 2015 1:29 PM >To: Ong, Boon Leong >Cc: Mittal, AnujX; meta-intel@yoctoproject.org >Subject: Re: [meta-intel] [fido][PATCH v2 2/2] meta-crystalforest: qat makefile >patches > >On 07/08/2015 03:35 PM, Ong, Boon Leong wrote: >>>> I do think that 2/2 --> 1/2 and 1/2 -> 2/2 in this patch-series to >>>> avoid partially update the patchseries and have build issue. >>>> >>> That would have been one option, but since this was a new recipe and >>> the patches are required to start with I would prefer to see them as >>> one patch, future changes could such as improving or modifying a >>> given patch or part of the recipe should be individual patches as they they >>> are >incremental changes to a given patch. >> >> Got it. If you find issue in the DPDK series, I will re-format the >> patch-series to follow the above principles for the first time >> submission of new recipe. Thanks for guidance above. >> > >I think I understand what you are trying to do with the dpdk series, I started >looking at it today and began wondering if it would not have been easier to >have >them collapsed, but I understand that you cherry-picked and then updated, and >introduced the patches before the final recipes. I opined that a cherry-picked should be a clean pick with no content change unless conflict changes is required. Followed by another commit to fix the fido build issue to be explicitly. >So, when I saw and understood your intent there, having multiple smaller ones >is >OK. I honestly reviewed the finished product since that was easier than >trying to >decipher the individual patches though! Ya, I understand the difficulty there because collapsing some patches may lost the evolution of the dpdk series. I may collapse them in the 2nd series (if required), just want to make sure that it is made easier for your review and merge. Sorry but thank you for your time and effort! On separate matter, Anuj just shared with me his zlib-qat patch that cherry-picked patch from dizzy into fido. He took the path of "in the same cherry-picked commit, he swapped a patch that is zlib-qat is not building on fido, i.e. doing a patch content changes on cherry-picked patch." I was not really in favor of such process because I like cherry-picked patch to be as in-tact as possible as the source of it. This gives assurance that there is additional hidden ingredients added mid-way that I am not aware of. What is your preference here? We will try to follow what suits your best. A) clean cherry-picked then a commit to fix build error B) a single commit that has both commits in (A). Thanks -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [fido][PATCH v2 2/2] meta-crystalforest: qat makefile patches
>> I do think that 2/2 --> 1/2 and 1/2 -> 2/2 in this patch-series to >> avoid partially update the patchseries and have build issue. >> >That would have been one option, but since this was a new recipe and the >patches >are required to start with I would prefer to see them as one patch, future >changes >could such as improving or modifying a given patch or part of the recipe >should be >individual patches as they they are incremental changes to a given patch. Got it. If you find issue in the DPDK series, I will re-format the patch-series to follow the above principles for the first time submission of new recipe. Thanks for guidance above. > >> I would like to hear your commend here so that I don't get "dinged' by >> you in future ... =-) >> >I don't mean to be harsh, just trying to be consistent. Nay, you are not harsh, honestly. I should have use 'advised' instead of 'dinged' ... =-) Thanks again. -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 1/2] intel-quark: Introduce new BSP for Quark/X1000 SOC
>+EFI_PROVIDER = "gummiboot" Just curious, is there a switch now from the legacy GRUB v0.97 + secure boot patch now to gummiboot? -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [fido][PATCH v2 2/2] meta-crystalforest: qat makefile patches
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of Saul Wold >Sent: Wednesday, July 8, 2015 4:53 AM >To: Mittal, AnujX; meta-intel@yoctoproject.org >Subject: Re: [meta-intel] [fido][PATCH v2 2/2] meta-crystalforest: qat makefile >patches > > >These patches should be part of the actual recipe patch since they are >referenced >in that recipe. > >Think one logical unit, such that if we tried to bisect we would not get >failures, >with 2 patches, this will cause a failure between the 2 patches if bisect lands >there. > Saul, Speaking of this matter, I have seen maintainer from other community prefer smaller commits than one single logical unit. So, I asked Anuj & others here to make it smaller so that it is easier to keep track of the changes instead one single large commit. It seems that you put more emphasis on single unit commit that helps in term of git bisect. Is that your preference? I do think that 2/2 --> 1/2 and 1/2 -> 2/2 in this patch-series to avoid partially update the patchseries and have build issue. I would like to hear your commend here so that I don't get "dinged' by you in future ... =-) -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 16/16] meta-isg: dpdk v2.0.0: initial DPDK v2.0.0 enabling recipe
From: WU CHIA CHUAN
This patch makes reference to early dpdk meta-data implementation
and extends it to support DPDK v2.0.0.
Signed-off-by: WU CHIA CHUAN
Signed-off-by: Ong Boon Leong
---
.../common/recipes-extended/dpdk/dpdk_2.0.0.bb | 29
1 file changed, 29 insertions(+)
create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
b/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
new file mode 100644
index 000..cb158b9
--- /dev/null
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb
@@ -0,0 +1,29 @@
+include dpdk.inc
+
+SRC_URI = "http://dpdk.org/browse/dpdk/snapshot/dpdk-${PV}.tar.gz;name=dpdk \
+
file://dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch
\
+
file://dpdk-1.8.0-and-2.0.0-examples-add-config-variable-to-enable-disable-dpdk.patch
\
+
file://dpdk-1.8.0-and-2.0.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch \
+
file://dpdk-1.8.0-and-2.0.0-add-sysroot-option-within-app-makefile.patch \
+
file://dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-type.patch \
+ "
+
+SRC_URI[dpdk.md5sum] = "e9e7935c9eec920841ad373949514934"
+SRC_URI[dpdk.sha256sum] =
"643789a3be5ba44dd84d6b248cdf5471b260f8736dada177dadf076aebfbff3f"
+
+export EXAMPLES_BUILD_DIR = "${RTE_TARGET}"
+export ARCHDIR = "generic"
+
+# dpdk example apps dpdk_qat and vhost have dependancy on fuse and qat.
+# fuse is in meta-filesystems and qat is not yet upstreamed.
+# So adding mechanism to explicitly disable the use of fuse and qat.
+# To enable, uncomment the below line or include in .bbappend.
+# PACKAGECONFIG ?= " dpdk_qat vhost libvirt"
+
+PACKAGECONFIG[dpdk_qat] = ",,qat"
+PACKAGECONFIG[vhost] = ",,fuse"
+PACKAGECONFIG[libvirt] = ",,libvirt"
+
+export CONFIG_EXAMPLE_DPDK_QAT = "${@base_contains('PACKAGECONFIG',
'dpdk_qat', 'y', 'n', d)}"
+export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@base_contains('PACKAGECONFIG',
'libvirt', 'y', 'n', d)}"
+export CONFIG_VHOST_ENABLED = "${@base_contains('PACKAGECONFIG', 'vhost', 'y',
'n', d)}"
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 15/16] meta-isg: dpdk v2.0.0: add patch to handle vhost and ip_fragmentation applications
From: WU CHIA CHUAN Introduce a patch to enable/disable the vhost and ip_fragmentation examples applications under common_linuxapp config file. The flag introduce is controlled by PACKAGECONFIG. Signed-off-by: WU CHIA CHUAN Signed-off-by: Ong Boon Leong --- ...T-and-ip_fragmentation-in-common_linuxapp.patch | 50 1 file changed, 50 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch new file mode 100644 index 000..45ce5e0 --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch @@ -0,0 +1,50 @@ +From 3d3c03d947394696565b3bb7bed8c900de057a28 Mon Sep 17 00:00:00 2001 +From: WU CHIA CHUAN +Date: Thu, 2 Jul 2015 15:59:18 +0800 +Subject: [PATCH] dpdk enable VHOST and ip_fragmentation in common_linuxapp config + +Introduce CONFIG_VHOST_ENABLED for package config selection purpose in +building vhost feature. + +Upstream-Status: Inappropriate [configuration] + +Signed-off-by: WU CHIA CHUAN +--- + config/common_linuxapp | 11 --- + 1 file changed, 8 insertions(+), 3 deletions(-) + +diff --git a/config/common_linuxapp b/config/common_linuxapp +index 0b25f34..000f950 100644 +--- a/config/common_linuxapp b/config/common_linuxapp +@@ -406,19 +406,24 @@ CONFIG_RTE_LIBRTE_PIPELINE=y + CONFIG_RTE_LIBRTE_KNI=y + CONFIG_RTE_KNI_PREEMPT_DEFAULT=y + CONFIG_RTE_KNI_KO_DEBUG=n +-CONFIG_RTE_KNI_VHOST=n ++CONFIG_RTE_KNI_VHOST=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_KNI_VHOST_MAX_CACHE_SIZE=1024 +-CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=n ++CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_KNI_VHOST_DEBUG_RX=n + CONFIG_RTE_KNI_VHOST_DEBUG_TX=n + + # ++# Compile ip_fragmentation ++# ++CONFIG_RTE_IP_FRAG=y ++ ++# + # Compile vhost library + # fuse-devel is needed to run vhost-cuse. + # fuse-devel enables user space char driver development + # vhost-user is turned on by default. + # +-CONFIG_RTE_LIBRTE_VHOST=n ++CONFIG_RTE_LIBRTE_VHOST=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_LIBRTE_VHOST_USER=y + CONFIG_RTE_LIBRTE_VHOST_DEBUG=n + +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 14/16] meta-isg: dpdk: renaming patches which are common to DPDK v1.8 and DPDK v2.0
From: WU CHIA CHUAN For patches which are common to DPDK v1.8 and DPDK v2.0, they are renamed to following file naming format for clarity dpdk-1.8.0-and-2.0.0*.patch. Signed-off-by: WU CHIA CHUAN Signed-off-by: Ong Boon Leong --- ...-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch | 52 0-add-sysroot-option-within-app-makefile.patch | 33 - ...-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch | 52 0-add-sysroot-option-within-app-makefile.patch | 33 + 0-dpdk-defconfig-select-RTE_MACHINE-type.patch | 48 ++ ...dd-config-variable-to-enable-disable-dpdk.patch | 44 + 0-dpdk-defconfig-select-RTE_MACHINE-type.patch | 48 -- ...d-config-variable-to-enable-disable-dpdk_.patch | 44 - .../common/recipes-extended/dpdk/dpdk_1.8.0.bb |8 +-- 9 files changed, 181 insertions(+), 181 deletions(-) delete mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch delete mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-add-sysroot-option-within-app-makefile.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-type.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-examples-add-config-variable-to-enable-disable-dpdk.patch delete mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch delete mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch deleted file mode 100644 index bfef221..000 --- a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch +++ /dev/null @@ -1,52 +0,0 @@ -From 69238a0b910bca43ef13154718a7a6c9b0dabe8a Mon Sep 17 00:00:00 2001 -From: Ong Boon Leong -Date: Thu, 25 Jun 2015 15:39:38 +0800 -Subject: [PATCH] dpdk v1.8.0: add RTE_KERNELDIR_OUT to split kernel build - artifact - -Introduce RTE_KERNELDIR_OUT to be the path to which kernel build -artifacts are located. This is for matching the workflow change -since Yocto Project v1.8 onwards whereby tmp/work-shared contains -separate directories for kernel source and kernel artifacts. - -Upstream-Status: Inappropriate [configuration] - -Signed-off-by: Ong Boon Leong - mk/rte.module.mk |6 +++--- - 1 file changed, 3 insertions(+), 3 deletions(-) - -diff --git a/mk/rte.module.mk b/mk/rte.module.mk -index 7bf77c1..d4253a5 100644 a/mk/rte.module.mk -+++ b/mk/rte.module.mk -@@ -77,7 +77,7 @@ build: _postbuild - # build module - $(MODULE).ko: $(SRCS_LINKS) - @if [ ! -f $(notdir Makefile) ]; then ln -nfs $(SRCDIR)/Makefile . ; fi -- @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) \ -+ @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) \ - CC=$(KERNELCC) CROSS_COMPILE=$(CROSS) V=$(if $V,1,0) - - # install module in $(RTE_OUTPUT)/kmod -@@ -88,7 +88,7 @@ $(RTE_OUTPUT)/kmod/$(MODULE).ko: $(MODULE).ko - - # install module - modules_install: -- @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) \ -+ @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) \ - modules_install - - .PHONY: clean -@@ -98,7 +98,7 @@ clean: _postclean - .PHONY: doclean - doclean: - @if [ ! -f $(notdir Makefile) ]; then ln -nfs $(SRCDIR)/Makefile . ; fi -- $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) clean -+ $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) clean - @$(foreach FILE,$(SRCS-y) $(SRCS-n) $(SRCS-),\ - if [ -h $(notdir $(FILE)) ]; then rm -f $(notdir $(FILE)) ; fi ;) - @if [ -h $(notdir Makefile) ]; then rm -f $(notdir Makefile) ; fi --- -1.7.9.5 - diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch deleted file mode 100644 index 02c7dc3..000 --- a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch +++ /dev/null @@ -1,33 +0,0 @@ -From 3112250f6452215890fc7db73c8127e111af956f Mon Sep 17 00:00:00 2001 -From: Ong Boon Leong -Date: Thu, 2 Jul 2015 23:51:01 +0800 -Subject: [PATCH
[meta-intel] [fido][PATCH 12/16] meta-isg: dpdk: rearrange common meta-data from dpdk_1.8.0.bb into dpdk.inc
Extract out common meta-data from dpdk_1.8.0.bb into dpdk.inc for better
scalability into future dpdk.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc | 24 +++
.../common/recipes-extended/dpdk/dpdk_1.8.0.bb | 32
2 files changed, 24 insertions(+), 32 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index e1670c5..4125126 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -18,6 +18,25 @@ export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
export RTE_KERNELDIR_OUT = "${STAGING_KERNEL_BUILDDIR}"
export INSTALL_PATH = "${prefix}/dpdk"
+export SYSROOTPATH = "--sysroot=${STAGING_DIR_HOST}"
+export DPDK_TARGET_MACH = "${@get_dpdk_target_mach(bb,d)}"
+
+# The list of intel Comms platforms and their target machine
+# process mapping. The supported target machine is listed under
+# dpdk/mk/machine
+def get_dpdk_target_mach(bb, d):
+target_arch = d.getVar('MACHINE_ARCH', True)
+multiarch_options = {
+"mohonpeak64":"atm",
+"mohonpeak32":"atm",
+"crystalforest": "ivb",
+"romley": "snd",
+"romley-ivb": "ivb",
+}
+
+if target_arch in multiarch_options :
+return multiarch_options[target_arch]
+return ""
do_configure () {
#
@@ -38,6 +57,11 @@ do_compile () {
EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
CROSS="${TARGET_PREFIX}" \
prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
+
+ cd ${S}/examples/
+ oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR}" \
+ EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
+ CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
}
do_install () {
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
index 7a278b6..a0f8d8a 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
@@ -24,38 +24,6 @@ PACKAGECONFIG[dpdk_qat] = ",,qat"
PACKAGECONFIG[vhost] = ",,fuse"
PACKAGECONFIG[libvirt] = ",,libvirt"
-# The list of intel Comms platforms and their target machine
-# process mapping. The supported target machine is listed under
-# dpdk/mk/machine
-def get_dpdk_target_mach(bb, d):
-target_arch = d.getVar('MACHINE_ARCH', True)
-multiarch_options = {
-"mohonpeak64":"atm",
-"mohonpeak32":"atm",
-"crystalforest": "ivb",
-"romley": "snd",
-"romley-ivb": "ivb",
-}
-
-if target_arch in multiarch_options :
-return multiarch_options[target_arch]
-return ""
-
export CONFIG_EXAMPLE_DPDK_QAT = "${@base_contains('PACKAGECONFIG',
'dpdk_qat', 'y', 'n', d)}"
export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@base_contains('PACKAGECONFIG',
'libvirt', 'y', 'n', d)}"
export CONFIG_VHOST_ENABLED = "${@base_contains('PACKAGECONFIG', 'vhost', 'y',
'n', d)}"
-export SYSROOTPATH = "--sysroot=${STAGING_DIR_HOST}"
-export DPDK_TARGET_MACH = "${@get_dpdk_target_mach(bb,d)}"
-
-do_compile_append () {
-
- cd ${S}/examples/
-
- ###
- # In order to make use of dpdk.inc for example app installation
- # without failure, override the default build directory
- ###
- oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR}" \
- EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
- CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
-}
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 09/16] meta-isg: dpdk v1.8: add app makefile patch to enable sysroot setting
DPDK v1.8.0 app Makefile does not support "--sysroot=" option in LDFLAGS because of Makefile internal logic that always add -Wl, before. This causes poky GNU linker search path issue for target machine sysroot usr/lib. Signed-off-by: Ong Boon Leong --- 0-add-sysroot-option-within-app-makefile.patch | 33 1 file changed, 33 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch new file mode 100644 index 000..02c7dc3 --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch @@ -0,0 +1,33 @@ +From 3112250f6452215890fc7db73c8127e111af956f Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Thu, 2 Jul 2015 23:51:01 +0800 +Subject: [PATCH] dpdk v1.8.0: add --sysroot option within app makefile + +Upstream-Status: Inappropriate [configuration] + +in DPDK v1.8.0, rte.app.mk has been changed to add -Wl, to +all items listed under EXTRA_LDFLAGS. It causes --sysroot= + to not setup correctly when we depends on gcc to setup +for GNU ld. + +Signed-off-by: Ong Boon Leong +--- + mk/rte.app.mk |2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/mk/rte.app.mk b/mk/rte.app.mk +index e1a0dbf..9528588 100644 +--- a/mk/rte.app.mk b/mk/rte.app.mk +@@ -259,7 +259,7 @@ ifeq ($(LINK_USING_CC),1) + override EXTRA_LDFLAGS := $(call linkerprefix,$(EXTRA_LDFLAGS)) + O_TO_EXE = $(CC) $(CFLAGS) $(LDFLAGS_$(@)) \ + -Wl,-Map=$(@).map,--cref -o $@ $(OBJS-y) $(call linkerprefix,$(LDFLAGS)) \ +- $(EXTRA_LDFLAGS) $(call linkerprefix,$(LDLIBS)) ++ $(EXTRA_LDFLAGS) $(SYSROOTPATH) $(call linkerprefix,$(LDLIBS)) + else + O_TO_EXE = $(LD) $(LDFLAGS) $(LDFLAGS_$(@)) $(EXTRA_LDFLAGS) \ + -Map=$(@).map --cref -o $@ $(OBJS-y) $(LDLIBS) +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 13/16] meta-isg: dpdk: move the do_install hostapp directory from dpdk.inc to dpdk_1.8.0.bb
From: WU CHIA CHUAN
dpdk.inc is common to dpdk_1.8.0.bb and dpdk_2.0.0.bb, since DPDK v2.0 is no
longer have
hostapp directory, so we only perform hostapp installation for DPDK v1.8.
Signed-off-by: WU CHIA CHUAN
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc |2 --
.../common/recipes-extended/dpdk/dpdk_1.8.0.bb |6 ++
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 4125126..85b88fa 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -71,7 +71,6 @@ do_install () {
${D}/${INSTALL_PATH}/tools \
${D}/${INSTALL_PATH}/${RTE_TARGET} \
${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
- ${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp \
${D}${includedir} \
${D}${includedir}/${ARCHDIR} \
${D}${includedir}/exec-env \
@@ -90,7 +89,6 @@ do_install () {
# Install applications
install -m 0755 ${S}/${RTE_TARGET}/app/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/app/
- install -m 0755 ${S}/${RTE_TARGET}/hostapp/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp/
# Install examples
for dirname in ${S}/examples/*
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
index a0f8d8a..cab76cc 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
@@ -27,3 +27,9 @@ PACKAGECONFIG[libvirt] = ",,libvirt"
export CONFIG_EXAMPLE_DPDK_QAT = "${@base_contains('PACKAGECONFIG',
'dpdk_qat', 'y', 'n', d)}"
export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@base_contains('PACKAGECONFIG',
'libvirt', 'y', 'n', d)}"
export CONFIG_VHOST_ENABLED = "${@base_contains('PACKAGECONFIG', 'vhost', 'y',
'n', d)}"
+
+do_install_append () {
+
+ install -m 0755 -d ${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp
+ install -m 0755 ${S}/${RTE_TARGET}/hostapp/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp/
+}
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 11/16] meta-isg: dpdk: intro recipe for DPDK v1.8.0
This patch adds the support for DPDK v1.8.0 from dpdk.org.
It introduces PACKAGECONFIG options for enabling Virtualization Technology
and QuickAssiste Technology with DPDK.
There is couple of additional DPDK Makefile & config patches to enable
PACKAGECONFIG said above.
Signed-off-by: Ong Boon Leong
---
.../common/recipes-extended/dpdk/dpdk_1.8.0.bb | 61
1 file changed, 61 insertions(+)
create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
new file mode 100644
index 000..7a278b6
--- /dev/null
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb
@@ -0,0 +1,61 @@
+include dpdk.inc
+
+SRC_URI = "http://dpdk.org/browse/dpdk/snapshot/dpdk-${PV}.tar.gz;name=dpdk \
+
file://dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch \
+
file://dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch
\
+ file://dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch \
+ file://dpdk-1.8.0-add-sysroot-option-within-app-makefile.patch \
+ file://dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch \
+ "
+
+SRC_URI[dpdk.md5sum] = "11ad8785aaa869cc87265bcb8d828f22"
+SRC_URI[dpdk.sha256sum] =
"9f5386830bd999355182e20408f3fc2cfa0802a4497fdded8d43202feede1939"
+
+export EXAMPLES_BUILD_DIR = "${RTE_TARGET}"
+export ARCHDIR = "generic"
+
+# dpdk example apps dpdk_qat and vhost have dependancy on fuse and qat.
+# fuse is in meta-filesystems and qat is not yet upstreamed.
+# So adding mechanism to explicitly disable the use of fuse and qat.
+# To enable, uncomment the below line or include in .bbappend.
+# PACKAGECONFIG ?= " dpdk_qat vhost libvirt"
+
+PACKAGECONFIG[dpdk_qat] = ",,qat"
+PACKAGECONFIG[vhost] = ",,fuse"
+PACKAGECONFIG[libvirt] = ",,libvirt"
+
+# The list of intel Comms platforms and their target machine
+# process mapping. The supported target machine is listed under
+# dpdk/mk/machine
+def get_dpdk_target_mach(bb, d):
+target_arch = d.getVar('MACHINE_ARCH', True)
+multiarch_options = {
+"mohonpeak64":"atm",
+"mohonpeak32":"atm",
+"crystalforest": "ivb",
+"romley": "snd",
+"romley-ivb": "ivb",
+}
+
+if target_arch in multiarch_options :
+return multiarch_options[target_arch]
+return ""
+
+export CONFIG_EXAMPLE_DPDK_QAT = "${@base_contains('PACKAGECONFIG',
'dpdk_qat', 'y', 'n', d)}"
+export CONFIG_EXAMPLE_VM_POWER_MANAGER = "${@base_contains('PACKAGECONFIG',
'libvirt', 'y', 'n', d)}"
+export CONFIG_VHOST_ENABLED = "${@base_contains('PACKAGECONFIG', 'vhost', 'y',
'n', d)}"
+export SYSROOTPATH = "--sysroot=${STAGING_DIR_HOST}"
+export DPDK_TARGET_MACH = "${@get_dpdk_target_mach(bb,d)}"
+
+do_compile_append () {
+
+ cd ${S}/examples/
+
+ ###
+ # In order to make use of dpdk.inc for example app installation
+ # without failure, override the default build directory
+ ###
+ oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR}" \
+ EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
+ CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
+}
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 08/16] meta-isg: dpdk: fix GCC compiler LDFLAG and CFLAG issue
DPDK v1.8.0 has some change made on app makefile that breaks dpdk.inc
may on passing in EXTRA_CFLAGS AND EXTRA_LDFLAGS. So this patch
re-tune the dpdk.inc to align to the change.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 61b3259..e1670c5 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -34,8 +34,8 @@ do_compile () {
unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
cd ${S}/${RTE_TARGET}
- oe_runmake EXTRA_LDFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
- EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
+ oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR}" \
+ EXTRA_CFLAGS="--sysroot=${STAGING_DIR_HOST}
-I${STAGING_INCDIR}" \
CROSS="${TARGET_PREFIX}" \
prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
}
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 03/16] meta-isg: dpdk: improve software installation task
do_install() has been non-scalable due to different DPDK SW releases
offer increasingly more examples. So, this patch is intended to make
the do_install() simplified by using regular expression technique to
extract out executables name that are built.
Tested this patch with DPDK v1.6.0r2 and v1.7.0 and the software packages
look intact.
Signed-off-by: Ong Boon Leong
Signed-off-by: Saul Wold
(cherry picked from commit a43871c39ae462647ebe58679b92cd34c8ae48a6)
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc | 83
1 file changed, 26 insertions(+), 57 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 5e7d52b..910feb4 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -9,13 +9,13 @@ inherit module
export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
export RTE_SDK = "${S}"
-export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
+export RTE_TARGET="${@bb.utils.contains("TUNE_FEATURES", "corei7",
"x86_64-ivshmem-linuxapp-gcc", "i686-native-linuxapp-gcc", d)}"
+
export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
export INSTALL_PATH = "${prefix}/dpdk"
-
do_configure () {
#
### default value for prefix is "usr", unsetting it, so it
@@ -25,10 +25,8 @@ do_configure () {
unset prefix
make O=$RTE_TARGET T=$RTE_TARGET config
-
}
-
do_compile () {
unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
@@ -37,10 +35,8 @@ do_compile () {
EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
CROSS="${TARGET_PREFIX}" \
prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
-
}
-
do_install () {
install -m 0755 -d ${D}/${INSTALL_PATH} \
@@ -48,70 +44,36 @@ do_install () {
${D}/${INSTALL_PATH}/tools \
${D}/${INSTALL_PATH}/${RTE_TARGET} \
${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
+ ${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp \
${D}${includedir} \
${D}${includedir}/arch \
${D}${includedir}/exec-env \
${D}${libdir} \
${D}${MODULE_DIR}
- install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
${D}${MODULE_DIR}/
- install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
${D}${MODULE_DIR}/
+ install -m 0755 ${S}/${RTE_TARGET}/kmod/*.ko${D}${MODULE_DIR}/
install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
- install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
- install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/exec-env/
+ install -m 640 ${S}/${RTE_TARGET}/include/arch/*.h
${D}${includedir}/arch/
+ install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*.h
${D}${includedir}/exec-env/
install -m 0755 ${S}/tools/*.py
${D}/${INSTALL_PATH}/tools/
+ # Install applications
+ install -m 0755 ${S}/${RTE_TARGET}/app/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/app/
+ install -m 0755 ${S}/${RTE_TARGET}/hostapp/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp/
- #Install test applications
- install -m 0755 ${S}/${RTE_TARGET}/app/test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/testpmd
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/dump_cfg
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/cmdline_test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
-
-
- # Install example applications
- # It is expected that user of this include file should define
EXAMPLES_BUILD_DIR
- for app in ${S}/examples/*
+ # Install examples
+ for dirname in ${S}/examples/*
do
- case `basename ${app}` in
- "dpdk_qat" | "vhost" | "vhost_xen" | "Makefile" ) continue
- ;;
- "l2fwd-ivshmem")
- install -
[meta-intel] [fido][PATCH 10/16] meta-isg: dpdk v1.8: introduce target machine selection for DPDK.
DPDK default config set the TARGET machine type to native which is incorrect. The SDK assumes that the DPDK package is built and installed natively. So, to support cross-compilation uses, we add DPDK_TARGET_MACH option here. This variable should be defined at either dpdk bb or bbappend file. Signed-off-by: Ong Boon Leong --- 0-dpdk-defconfig-select-RTE_MACHINE-type.patch | 48 1 file changed, 48 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch new file mode 100644 index 000..979541e --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-defconfig-select-RTE_MACHINE-type.patch @@ -0,0 +1,48 @@ +From 6eaf6b1a61321acb824f9672c12d0e30a2110f52 Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Mon, 16 Mar 2015 11:10:43 +0800 +Subject: [PATCH] DPDK: defconfig: add selectable RTE_MACHINE option + +In order to make sure that DPDK build environment config can handle the +package being built on different build machine for different target machine +which will have different x86 architecture intrinsics than the build machine, +we introduce DPDK_TARGET_MACH to be tunable from dpdk recipe. The machine +type can be under mk/machine folder. + +Upstream-Status: Inappropriate [configuration] + +Signed-off-by: Ong Boon Leong +--- + config/defconfig_i686-native-linuxapp-gcc |2 +- + config/defconfig_x86_64-native-linuxapp-gcc |2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/config/defconfig_i686-native-linuxapp-gcc b/config/defconfig_i686-native-linuxapp-gcc +index a90de9b..c9a74a5 100644 +--- a/config/defconfig_i686-native-linuxapp-gcc b/config/defconfig_i686-native-linuxapp-gcc +@@ -32,7 +32,7 @@ + + #include "common_linuxapp" + +-CONFIG_RTE_MACHINE="native" ++CONFIG_RTE_MACHINE=$(DPDK_TARGET_MACH) + + CONFIG_RTE_ARCH="i686" + CONFIG_RTE_ARCH_I686=y +diff --git a/config/defconfig_x86_64-native-linuxapp-gcc b/config/defconfig_x86_64-native-linuxapp-gcc +index 60baf5b..0e4802d 100644 +--- a/config/defconfig_x86_64-native-linuxapp-gcc b/config/defconfig_x86_64-native-linuxapp-gcc +@@ -32,7 +32,7 @@ + + #include "common_linuxapp" + +-CONFIG_RTE_MACHINE="native" ++CONFIG_RTE_MACHINE=$(DPDK_TARGET_MACH) + + CONFIG_RTE_ARCH="x86_64" + CONFIG_RTE_ARCH_X86_64=y +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 06/16] meta-isg: dpdk v1.8.0: add makefile patches to support split kernel output
Starting form YPv1.8.y onwards, the kernel build output is separately kept under work-shared. Signed-off-by: Ong Boon Leong --- ...-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch | 52 1 file changed, 52 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch new file mode 100644 index 000..bfef221 --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch @@ -0,0 +1,52 @@ +From 69238a0b910bca43ef13154718a7a6c9b0dabe8a Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Thu, 25 Jun 2015 15:39:38 +0800 +Subject: [PATCH] dpdk v1.8.0: add RTE_KERNELDIR_OUT to split kernel build + artifact + +Introduce RTE_KERNELDIR_OUT to be the path to which kernel build +artifacts are located. This is for matching the workflow change +since Yocto Project v1.8 onwards whereby tmp/work-shared contains +separate directories for kernel source and kernel artifacts. + +Upstream-Status: Inappropriate [configuration] + +Signed-off-by: Ong Boon Leong +--- + mk/rte.module.mk |6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/mk/rte.module.mk b/mk/rte.module.mk +index 7bf77c1..d4253a5 100644 +--- a/mk/rte.module.mk b/mk/rte.module.mk +@@ -77,7 +77,7 @@ build: _postbuild + # build module + $(MODULE).ko: $(SRCS_LINKS) + @if [ ! -f $(notdir Makefile) ]; then ln -nfs $(SRCDIR)/Makefile . ; fi +- @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) \ ++ @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) \ + CC=$(KERNELCC) CROSS_COMPILE=$(CROSS) V=$(if $V,1,0) + + # install module in $(RTE_OUTPUT)/kmod +@@ -88,7 +88,7 @@ $(RTE_OUTPUT)/kmod/$(MODULE).ko: $(MODULE).ko + + # install module + modules_install: +- @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) \ ++ @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) \ + modules_install + + .PHONY: clean +@@ -98,7 +98,7 @@ clean: _postclean + .PHONY: doclean + doclean: + @if [ ! -f $(notdir Makefile) ]; then ln -nfs $(SRCDIR)/Makefile . ; fi +- $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR) clean ++ $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) O=$(RTE_KERNELDIR_OUT) clean + @$(foreach FILE,$(SRCS-y) $(SRCS-n) $(SRCS-),\ + if [ -h $(notdir $(FILE)) ]; then rm -f $(notdir $(FILE)) ; fi ;) + @if [ -h $(notdir Makefile) ]; then rm -f $(notdir Makefile) ; fi +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 07/16] meta-isg: dpdk v1.8: add patches for qat, vhost and libvirt PACKAGECONFIG
Introduce two patches to enable DPDK config file to support PACKAGECONFIG options for QAT, vhost and libvirt. Signed-off-by: Ong Boon Leong --- ...ld-config-VHOST-in-common_linuxapp-config.patch | 43 +++ ...d-config-variable-to-enable-disable-dpdk_.patch | 44 2 files changed, 87 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch new file mode 100644 index 000..e8ded8d --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch @@ -0,0 +1,43 @@ +From c1a59d62f2aa7656060d8ebcc8e45e852d931ff1 Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Tue, 17 Feb 2015 00:23:12 +0800 +Subject: [PATCH] dpdk: enable VHOST build config in common_linuxapp config + +Introduce CONFIG_VHOST_ENABLED for package config selection purpose in +building vhost feature. + +Upstream-Status: Inappropriate [configuration] + +Signed-off-by: Ong Boon Leong +--- + config/common_linuxapp |6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/config/common_linuxapp b/config/common_linuxapp +index 2f9643b..67f5edb 100644 +--- a/config/common_linuxapp b/config/common_linuxapp +@@ -361,9 +361,9 @@ CONFIG_RTE_LIBRTE_PIPELINE=y + # + CONFIG_RTE_LIBRTE_KNI=y + CONFIG_RTE_KNI_KO_DEBUG=n +-CONFIG_RTE_KNI_VHOST=n ++CONFIG_RTE_KNI_VHOST=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_KNI_VHOST_MAX_CACHE_SIZE=1024 +-CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=n ++CONFIG_RTE_KNI_VHOST_VNET_HDR_EN=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_KNI_VHOST_DEBUG_RX=n + CONFIG_RTE_KNI_VHOST_DEBUG_TX=n + +@@ -372,7 +372,7 @@ CONFIG_RTE_KNI_VHOST_DEBUG_TX=n + # fuse-devel is needed to run vhost. + # fuse-devel enables user space char driver development + # +-CONFIG_RTE_LIBRTE_VHOST=n ++CONFIG_RTE_LIBRTE_VHOST=$(CONFIG_VHOST_ENABLED) + CONFIG_RTE_LIBRTE_VHOST_DEBUG=n + + # +-- +1.7.9.5 + diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch new file mode 100644 index 000..c86c1a1 --- /dev/null +++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-examples-add-config-variable-to-enable-disable-dpdk_.patch @@ -0,0 +1,44 @@ +From 54c95ca8f76f412c94a9f61e3756420ac554310b Mon Sep 17 00:00:00 2001 +From: Ong Boon Leong +Date: Thu, 12 Feb 2015 16:33:49 +0800 +Subject: [PATCH] examples: add config variable to enable/disable dpdk_qat + +Upstream-Status: Inappropriate [configuration] + +This patch adss following example build configs: + +1) CONFIG_EXAMPLE_DPDK_QAT is used to control dpdk_qat example + by PACKAGECONFIG. + +2) CONFIG_EXAMPLE_VM_POWER_MANAGER is used to control vm_power_manager + example by PACKAGECONFIG. + +Signed-off-by: Ong Boon Leong +--- + examples/Makefile |4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/examples/Makefile b/examples/Makefile +index 81f1d2f..7e9c7bd 100644 +--- a/examples/Makefile b/examples/Makefile +@@ -40,7 +40,7 @@ include $(RTE_SDK)/mk/rte.vars.mk + DIRS-y += cmdline + DIRS-$(CONFIG_RTE_LIBRTE_DISTRIBUTOR) += distributor + ifneq ($(ICP_ROOT),) +-DIRS-y += dpdk_qat ++DIRS-$(CONFIG_EXAMPLE_DPDK_QAT) += dpdk_qat + endif + DIRS-y += exception_path + DIRS-y += helloworld +@@ -68,6 +68,6 @@ DIRS-$(CONFIG_RTE_LIBRTE_VHOST) += vhost + DIRS-$(CONFIG_RTE_LIBRTE_XEN_DOM0) += vhost_xen + DIRS-y += vmdq + DIRS-y += vmdq_dcb +-DIRS-y += vm_power_manager ++DIRS-$(CONFIG_EXAMPLE_VM_POWER_MANAGER) += vm_power_manager + + include $(RTE_SDK)/mk/rte.extsubdir.mk +-- +1.7.9.5 + -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 00/16] DPDK v1.8.0 & v2.0.0 for CID platforms
Dear maintainers, Firstly, the patch add a layer for meta-isg just like dizzy branch. Then, the patchseries add the capabillity of DPDKv1.8.0 and DPDKv2.0.0 on meta-intel fido branch. It reuses DPDK ingredients from dizzy branch as base and further customizes dpdk.inc to handle several build change across DPDK v1.8.0 & v2.0.0. Wu, Chia Chuan has contributed the enhancement for DPDK v2.0.0 and I have checked and signed-off his contributions. I have validated both versions are building fine and the ingredients under packages-split look healthy to my best knowledge. Chia Chuan has helped in testing the ingredients on CID platforms. Although it is a long series, but a lot of the commits are incrementally small for review. Hope that is fine with you. Appreciate your help and effort in reviewing this patchseries. If you find them good, please kindly help to merge them into fido branch. Many thanks, Ong Boon Leong Ong Boon Leong (10): meta-isg: dpdk: improve software installation task meta-isg: dpdk: introduce ARCHDIR variable to dpdk.inc meta-isg: dpdk: add external kernel module build handling for tmp/work-shared meta-isg: dpdk v1.8.0: add makefile patches to support split kernel output meta-isg: dpdk v1.8: add patches for qat, vhost and libvirt PACKAGECONFIG meta-isg: dpdk: fix GCC compiler LDFLAG and CFLAG issue meta-isg: dpdk v1.8: add app makefile patch to enable sysroot setting meta-isg: dpdk v1.8: introduce target machine selection for DPDK. meta-isg: dpdk: intro recipe for DPDK v1.8.0 meta-isg: dpdk: rearrange common meta-data from dpdk_1.8.0.bb into dpdk.inc WU CHIA CHUAN (4): meta-isg: dpdk: move the do_install hostapp directory from dpdk.inc to dpdk_1.8.0.bb meta-isg: dpdk: renaming patches which are common to DPDK v1.8 and DPDK v2.0 meta-isg: dpdk v2.0.0: add patch to handle vhost and ip_fragmentation applications meta-isg: dpdk v2.0.0: initial DPDK v2.0.0 enabling recipe venkatasubramanian pattu (2): meta-isg: Making meta-isg as a layer meta-isg: Add include file for DPDK meta-isg/common/recipes-extended/dpdk/dpdk.inc | 132 ...-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch | 52 0-add-sysroot-option-within-app-makefile.patch | 33 + 0-dpdk-defconfig-select-RTE_MACHINE-type.patch | 48 +++ ...dd-config-variable-to-enable-disable-dpdk.patch | 44 +++ ...ld-config-VHOST-in-common_linuxapp-config.patch | 43 +++ ...T-and-ip_fragmentation-in-common_linuxapp.patch | 50 .../common/recipes-extended/dpdk/dpdk_1.8.0.bb | 35 ++ .../common/recipes-extended/dpdk/dpdk_2.0.0.bb | 29 + meta-isg/conf/layer.conf | 12 ++ 10 files changed, 478 insertions(+) create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk.inc create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-add-RTE_KERNELDIR_OUT-to-split-kernel-bu.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-add-sysroot-option-within-app-makefile.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-dpdk-defconfig-select-RTE_MACHINE-type.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-and-2.0.0-examples-add-config-variable-to-enable-disable-dpdk.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.8.0-dpdk-enable-build-config-VHOST-in-common_linuxapp-config.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-2.0.0-dpdk-enable-VHOST-and-ip_fragmentation-in-common_linuxapp.patch create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_1.8.0.bb create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_2.0.0.bb create mode 100644 meta-isg/conf/layer.conf -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 05/16] meta-isg: dpdk: add external kernel module build handling for tmp/work-shared
DPDK software builds external kernel modules igb_uio.ko, rte_kni.ko & etc that
depend on the availability of kernel source. With splitting of kernel source
and artifacts into separate fodlers under tmp/work-shared, we need to handle
this by introducing do_configure[depends] += "virtual/kernel:do_shared_workdir"
to ensure build dependency is satisfied.
Refer to poky 46cdaf1 kernel: move source and build output to work-shared
This patch also introduces RTE_KERNELDIR_OUT variable to be used to setup
the kernel build artifact path. RTE_KERNELDIR remains as the kernel source path.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc |3 +++
1 file changed, 3 insertions(+)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 1d985ff..61b3259 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -4,6 +4,8 @@ LICENSE = "BSD & LGPLv2 & GPLv2"
LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe"
RDEPENDS_${PN} += "python-subprocess"
+DEPENDS = "virtual/kernel"
+do_configure[depends] += "virtual/kernel:do_shared_workdir"
inherit module
@@ -14,6 +16,7 @@ export RTE_TARGET="${@bb.utils.contains("TUNE_FEATURES",
"corei7", "x86_64-ivshm
export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
+export RTE_KERNELDIR_OUT = "${STAGING_KERNEL_BUILDDIR}"
export INSTALL_PATH = "${prefix}/dpdk"
do_configure () {
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 04/16] meta-isg: dpdk: introduce ARCHDIR variable to dpdk.inc
Starting from DPDK v1.8 onwards, there is name change from
include/arch to include/generic under build directory. So to cater
for such change, we introduce ARCHDIR variable. This variable should
be set under individual version of dpdk recipe.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 910feb4..1d985ff 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -46,7 +46,7 @@ do_install () {
${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp \
${D}${includedir} \
- ${D}${includedir}/arch \
+ ${D}${includedir}/${ARCHDIR} \
${D}${includedir}/exec-env \
${D}${libdir} \
${D}${MODULE_DIR}
@@ -57,7 +57,7 @@ do_install () {
install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
- install -m 640 ${S}/${RTE_TARGET}/include/arch/*.h
${D}${includedir}/arch/
+ install -m 640 ${S}/${RTE_TARGET}/include/${ARCHDIR}/*.h
${D}${includedir}/${ARCHDIR}/
install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*.h
${D}${includedir}/exec-env/
install -m 0755 ${S}/tools/*.py
${D}/${INSTALL_PATH}/tools/
@@ -94,7 +94,7 @@ FILES_${PN}-doc += "\
FILES_${PN}-dev += " \
${INSTALL_PATH}/${RTE_TARGET}/.config \
${includedir} \
- ${includedir}/arch \
+ ${includedir}/${ARCHDIR} \
${includedir}/exec-env \
"
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 01/16] meta-isg: Making meta-isg as a layer
From: venkatasubramanian pattu
This layer provides additional common recipes to be used by all IOTG maintained
platforms.
Signed-off-by: venkatasubramanian pattu
Signed-off-by: Saul Wold
(cherry picked from commit 6a334428e1b92de2b6c322654ae6f64d3ff55ab6)
Signed-off-by: Ong Boon Leong
---
meta-isg/conf/layer.conf | 12
1 file changed, 12 insertions(+)
create mode 100644 meta-isg/conf/layer.conf
diff --git a/meta-isg/conf/layer.conf b/meta-isg/conf/layer.conf
new file mode 100644
index 000..48ad0c3
--- /dev/null
+++ b/meta-isg/conf/layer.conf
@@ -0,0 +1,12 @@
+# We have a conf and classes directory, add to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have recipes-* directories, add to BBFILES
+BBFILES += "${LAYERDIR}/common/recipes-*/*/*.bb \
+${LAYERDIR}/common/recipes-*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "isg"
+BBFILE_PATTERN_isg := "^${LAYERDIR}/common/"
+BBFILE_PRIORITY_isg = "5"
+
+LAYERDEPENDS_isg = "intel"
--
1.7.9.5
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [fido][PATCH 02/16] meta-isg: Add include file for DPDK
From: venkatasubramanian pattu
Added include file dpdk.inc to share common functionality based on
dpdk_1.6.0r2
Added a new variable EXAMPLE_BUILD_DIR. This points to apps build
directory which is different in dpdk v1.6.0r2 and v1.7.0.
Users of dpdk.inc have to define EXAMPLE_BUILD_DIR for the
installation of example apps.
This recipe is cherry-picked from branch dizzy and the commit ID:
1c825a06095178c0c51f28d5867549feac8a47f4:meta-intel/common: Add include file
for DPDK
Signed-off-by: venkatasubramanian pattu
Signed-off-by: Saul Wold
(cherry picked from commit 578494c0c4715bb8d24972fa52850e89c36410a1)
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc | 138
1 file changed, 138 insertions(+)
create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk.inc
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
new file mode 100644
index 000..5e7d52b
--- /dev/null
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -0,0 +1,138 @@
+DESCRIPTION = "Intel(r) Data Plane Development Kit"
+HOMEPAGE = "http://dpdk.org";
+LICENSE = "BSD & LGPLv2 & GPLv2"
+LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe"
+
+RDEPENDS_${PN} += "python-subprocess"
+
+inherit module
+
+export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
+export RTE_SDK = "${S}"
+export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
+export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
+export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
+export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
+export INSTALL_PATH = "${prefix}/dpdk"
+
+
+do_configure () {
+ #
+ ### default value for prefix is "usr", unsetting it, so it
+ ### will not be concatenated in ${RTE_TARGET}/Makefile
+ ### which will cause compilation failure
+ #
+ unset prefix
+
+ make O=$RTE_TARGET T=$RTE_TARGET config
+
+}
+
+
+do_compile () {
+ unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
+
+ cd ${S}/${RTE_TARGET}
+ oe_runmake EXTRA_LDFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
+ EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
+ CROSS="${TARGET_PREFIX}" \
+ prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
+
+}
+
+
+do_install () {
+
+ install -m 0755 -d ${D}/${INSTALL_PATH} \
+ ${D}/${INSTALL_PATH}/doc \
+ ${D}/${INSTALL_PATH}/tools \
+ ${D}/${INSTALL_PATH}/${RTE_TARGET} \
+ ${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
+ ${D}${includedir} \
+ ${D}${includedir}/arch \
+ ${D}${includedir}/exec-env \
+ ${D}${libdir} \
+ ${D}${MODULE_DIR}
+
+ install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
${D}${MODULE_DIR}/
+ install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
${D}${MODULE_DIR}/
+
+ install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
+
+ install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
+ install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
+ install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
+ install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/exec-env/
+ install -m 0755 ${S}/tools/*.py
${D}/${INSTALL_PATH}/tools/
+
+
+ #Install test applications
+ install -m 0755 ${S}/${RTE_TARGET}/app/test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+ install -m 0755 ${S}/${RTE_TARGET}/app/testpmd
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+ install -m 0755 ${S}/${RTE_TARGET}/app/dump_cfg
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+ install -m 0755 ${S}/${RTE_TARGET}/app/cmdline_test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+
+
+ # Install example applications
+ # It is expected that user of this include file should define
EXAMPLES_BUILD_DIR
+ for app in ${S}/examples/*
+ do
+ case `basename ${app}` in
+ "dpdk_qat" | "vhost" | "vhost_xen" | "Makefile" ) continue
+ ;;
+ "l2fwd-ivshmem")
+ install -m 0755 ${app}/guest/${EXAMPLES_BUILD_DIR}/app/guest
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
+
Re: [meta-intel] [fido][PATCH 0/3] QAT recipe for Intel Riverforest
>-Original Message-
>From: Saul Wold [mailto:s...@linux.intel.com]
>Sent: Monday, July 6, 2015 11:38 PM
>To: Mittal, AnujX; meta-intel@yoctoproject.org
>Cc: Ong, Boon Leong
>Subject: Re: [meta-intel] [fido][PATCH 0/3] QAT recipe for Intel Riverforest
>
>On 07/05/2015 10:28 PM, anujx.mit...@intel.com wrote:
>> From: Anuj Mittal
>>
>> Dear Maintainer(s),
>>
>> These patches provide the support for Intel QAT v 2.3.0-34 on
>> RiverForest platforms.
>>
>Is the intent also of this patch set to allow for an upgrade from Dizzy's QAT16
>(2.2.x based) -> this version? Or is there no upgrade path on the device for
>something already installed?
Anuj's focus is on this QAT v2.3.0-34 version for RiverForest platform on fido.
Venkat's work on Crystal Forest and Highland Forest were on dizzy on older QAT
version.
There is no plan for now to upgrade the Highland Forest and Crystal Forest
device support
on Fido due to resource constraints and no strong marketing ask.
Having said above, it is important to have at least matching filename,
structure and reuse
as much as common ingredient to minimize divergence in meta-data which Saul
rightful
pointed that out below.
>
>If it's intended as an upgrade then renaming from qat16 -> qat will allow for
>that
>to happen with out some additional METADATA, such as the PROVIDES_ /
>RPROVIDES_ and RREPLACES_.
>
>
>Are you coordinating with venkatasubramanianx.pa...@intel.com, who is working
>with the Dizzy based patches? It seems that these should be sharing a similar
>base. Maybe work together to review changes the changes.
Yes, common code base is important.
>
>The Dizzy based QAT recipes are using the correct $B and $S correctly, please
>consider looking at that.
>
>I attempted to build your version here and it did not even unpack the
>QAT1.6/QAT1.6.L.2.3.0-34.tar.gz.
>
>The do_install_prepend should not be doing a blind "cp -Pr ${B}/* ${D}".
>
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH v2 0/4 dizzy] meta-crystalforest: Initial Intel QAT-core Implementation
Venkat, Please redo your patch submission. The changelog status is captured as part of the cover-letter not as part of git commit. For the revised patch, it should be v3. As an example, please refer https://lists.yoctoproject.org/pipermail/meta-intel/2015-June/003169.html Saul, Please ignore this version v2 altogether because the patch commit formatting is wrong. BL >-Original Message- >From: Pattu, VenkatasubramanianX >Sent: Wednesday, July 1, 2015 2:59 PM >To: meta-intel@yoctoproject.org >Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX >Subject: [PATCH v2 0/4 dizzy] meta-crystalforest: Initial Intel QAT-core >Implementation > >Intel's QuickAssist Technology is designed to optimize the use and deployment >of >algorithm accelerators in networking and security applications. >As the complexity of networking and security applications continues to grow, >systems need more and more computational resources for workloads, including >cryptography, data compression, and pattern matching. >Intel QuickAssist Technology is designed to optimize the use and deployment of >algorithm accelerators in these kinds of applications. > >Intel QuickAssist Technology employs a hardware-assisted security engine for >implementing major security functions in both wired and wireless applications. >This hardware-assisted security engine works to reserve processor cycles for >application processing, and that in turn not only relieves CPU burden but also >improves overall system performance. > >Intel QuickAssist Technology, made integral to the Intel architecture, aims to >address the demand for hardware appliances with built-in security processing >and >to obviate the need for 3rd party co-processors. > >The Intel QuickAssist Technology software consists of an QAT API that is >implemented by a driver which in turn drives the Intel QuickAssist Accelerator >hardware. >The acceleration driver can run in either kernel space or in user space. >When running in user space, the acceleration driver accesses the hardware >directly from user space. >This Patch enables the QAT core for both Cave Creek and Coleto Creek Platforms. > >The package version of QAT1.5 is 1.7.0-30. Therefore, recipe name is renamed >from qat_1.5.bb into qat15_1.7.0-30.bb. >The package version of QAT1.6 is 2.2.0-30. Therefore, recipe name is renamed >from qat_1.6.bb into qat16_2.2.0-30.bb. > >QAT package is released from 01.org. >https://01.org/packet-processing/intel%C2%AE-quickassist-technology-drivers- >and-patches > >"QAT1.5" for use with Intel Communications Chipset 8900 to >8920(DH89xxCC)Series. >"QAT1.6" for use with Intel Communications Chipset 8925 to >8955(DH895xcc)Series. > >venkatasubramanian pattu (4): > meta-crystalforest: Add include file for QAT > meta-crystalforest: Intel QAT v1.5 recipe under recipes-extended > meta-crystalforest: Alternate cleanfile for QAT v1.6 source repository > meta-crystalforest: Intel QAT v1.6 recipe under recipes-extended > > .../recipes-extended/qat/files/00-qat_qa.rules | 3 + > .../recipes-extended/qat/files/dc_session.h| 277 + > .../qat/files/qat-1.5-enable-dynamic.patch | 35 +++ > .../qat/files/qat-1.6-app-dynamiccompression.patch | 35 +++ > .../qat/files/qat-1.6-app-fix-QA-issue.patch | 33 +++ > meta-crystalforest/recipes-extended/qat/qat.inc| 200 +++ > .../recipes-extended/qat/qat15_1.7.0-30.bb | 16 ++ > .../recipes-extended/qat/qat16_2.2.0-30.bb | 23 ++ > 8 files changed, 622 insertions(+) > create mode 100644 meta-crystalforest/recipes-extended/qat/files/00- >qat_qa.rules > create mode 100755 meta-crystalforest/recipes-extended/qat/files/dc_session.h > create mode 100644 meta-crystalforest/recipes-extended/qat/files/qat-1.5- >enable-dynamic.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/files/qat-1.6-app- >dynamiccompression.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/files/qat-1.6-app- >fix-QA-issue.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/qat.inc > create mode 100644 meta-crystalforest/recipes-extended/qat/qat15_1.7.0-30.bb > create mode 100644 meta-crystalforest/recipes-extended/qat/qat16_2.2.0-30.bb > >-- >1.9.1 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 3/4 dizzy] meta-crystalforest: Removing the hidden windows characters from QAT v1.6 source repository
>-Original Message- >From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- >boun...@yoctoproject.org] On Behalf Of Saul Wold >Sent: Monday, June 22, 2015 11:24 PM >To: Pattu, VenkatasubramanianX; meta-intel@yoctoproject.org >Subject: Re: [meta-intel] [PATCH 3/4 dizzy] meta-crystalforest: Removing the >hidden windows characters from QAT v1.6 source repository > >On 06/19/2015 12:17 AM, venkatasubramanian pattu wrote: >> Note: Since this patch has ASCII characters need to use "git am >> --keep-cr" to apply the patch. >> >Using --keep-cr causes this patch to fail, please verify that >contrib/sgw/dizzy is >correct, I patched it with a simple git am -s. This is really a stain in the software package that should not be there in the 1st place. What is your thought here to provide a cleanly dos2unix formatted file as part of file:// and mv it to replace the stained file before compiling? It is really should have been clean-up at source but this will workaround --keep-cr perhaps? -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 1/4 dizzy] meta-crystalforest: Add include file for QAT
>-Original Message-
>From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
>boun...@yoctoproject.org] On Behalf Of Saul Wold
>Sent: Saturday, June 20, 2015 5:36 AM
>To: Pattu, VenkatasubramanianX; meta-intel@yoctoproject.org
>Subject: Re: [meta-intel] [PATCH 1/4 dizzy] meta-crystalforest: Add include
>file
>for QAT
>
>
>Some minor comments below.
>
>On 06/19/2015 12:13 AM, venkatasubramanian pattu wrote:
>> Added include file qat.inc to share common functionality based on
>> qat_1.5 and qat_1.6.
>>
>> Signed-off-by: venkatasubramanian pattu
>>
>> ---
>> meta-crystalforest/recipes-extended/qat/qat.inc| 201
>+
>> .../recipes-extended/qat/qat/00-qat_qa.rules | 3 +
>> 2 files changed, 204 insertions(+)
>> create mode 100644 meta-crystalforest/recipes-extended/qat/qat.inc
>> create mode 100644
>> meta-crystalforest/recipes-extended/qat/qat/00-qat_qa.rules
>>
>> diff --git a/meta-crystalforest/recipes-extended/qat/qat.inc
>> b/meta-crystalforest/recipes-extended/qat/qat.inc
>> new file mode 100644
>> index 000..e5f802b
>> --- /dev/null
>> +++ b/meta-crystalforest/recipes-extended/qat/qat.inc
>> @@ -0,0 +1,201 @@
>> +SUMMARY = "Intel QuickAssist Technology Driver"
>> +DESCRIPTION = "Intel QuickAssist Technology for packet processing
>> +acceleration for both Intel Coleto Creek & Cave Creek platforms \ Software
>Package. "
>> +
>> +LICENSE = "GPLv2"
>> +LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-
>2.0;md5=801f80980d171dd6425610833a22dbe6"
>> +COMPATIBLE_MACHINE = "crystalforest"
>> +
>> +PR = "r0"
>The PR is really not needed anymore and the default will be r0.
>
>> +KERNEL_VERSION = "${@base_read_file('${STAGING_KERNEL_DIR}/kernel-
>abiversion')}"
>
>There is a better generic "get_kernelversion()" method in linux-yocto-base
>that I
>would suggest using.
>
>> +MODULE_DIR =
>"${D}${base_libdir}/modules/${KERNEL_VERSION}/kernel/drivers"
>> +ICP_TOOLS = "accelcomp"
>> +
>> +S = "${WORKDIR}/${ICP_DRIVER_TYPE}"
>> +B = "${S}/build"
>> +SAMPLE_CODE_DIR =
>"${S}/quickassist/lookaside/access_layer/src/sample_code"
>> +
>> +export KERNEL_SOURCE_ROOT = "${STAGING_KERNEL_DIR}"
>> +export ICP_ROOT = "${S}"
>> +export ICP_BUILD_OUTPUT = "${B}"
>> +export ICP_BUILDSYSTEM_PATH = "${S}/quickassist/build_system"
>> +export ICP_TOOLS_TARGET = "${ICP_TOOLS}"
>> +export ICP_ENV_DIR = "${S}/quickassist/build_system/build_files/env_files"
>> +export FUNC_PATH =
>"${ICP_ROOT}/quickassist/lookaside/access_layer/src/sample_code/functional"
>> +
>> +HOST[unexport] = "1"
>> +HOST[unexport] = "includedir"
>> +
>> +inherit update-rc.d
>> +INITSCRIPT_NAME = "qat_service"
>> +
>> +inherit module
>> +DEPENDS += "openssl"
>> +PARALLEL_MAKE = ""
>> +
>> +# The list of binary built by QAT package.
>> +
>> +LIBS = "\
>> +libadf_proxy.a \
>> +libosal.a \
>> +libicp_qa_al.a \
>> +libicp_qa_al_s.so \
>> +"
>> +
>> +FUNC_KERNEL_OBJ_LIST = "\
>> +algchaining_sample.ko \
>> +ccm_sample.ko \
>> +cipher_sample.ko \
>> +dc_dp_sample.ko \
>> +dc_stateless_multi_op_sample.ko \
>> +dc_stateless_sample.ko \
>> +dh_sample.ko \
>> +drbg_sample.ko \
>> +gcm_sample.ko \
>> +hash_sample.ko \
>> +ipsec_sample.ko \
>> +nrbg_sample.ko \
>> +prime_sample.ko \
>> +ssl_sample.ko \
>> +sym_dp_sample.ko \
>> +"
>> +
>> +FUNC_USER_APP_LIST = "\
>> +dh_sample \
>> +dc_stateful_sample \
>> +dc_dp_sample \
>> +cipher_sample \
>> +sym_dp_sample \
>> +nrbg_sample \
>> +drbg_sample \
>> +dc_stateless_multi_op_sample \
>> +paper4 \
>> +hash_file_sample \
>> +ccm_sample \
>> +ipsec_sample \
>> +algchaining_sample \
>> +ssl_sample \
>> +dc_stateless_sample \
>> +hash_sample \
>> +gcm_sample \
>> +prime_sample \
>> +"
>> +
>> +do_unpack2() {
>> +cd ${WORKDIR}
>> +tar xvf qatmux.l.${PV}.tar_
>> +cd ${S}/
>> +tar xzvf ${ICP_DRIVER_TYPE}.L.${QAT_VERSION}.tar.gz
>> +}
>> +
>> +addtask unpack2 after do_unpack before do_patch
>> +
>> +do_compile() {
>> +export LD="${LD} --hash-style=gnu"
>> +export MACHINE="${TARGET_ARCH}"
>> +cd ${S}/quickassist
>> +oe_runmake EXTRA_OEMAKE="'CFLAGS=${CFLAGS} -fPIC'"
>> +
>> +cd ${SAMPLE_CODE_DIR}
>> +touch ${SAMPLE_CODE_DIR}/performance/compression/calgary
>> +touch ${SAMPLE_CODE_DIR}/performance/compression/canterbury
>> +# build the whole sample code: fips, functional, performance
>> +oe_runmake 'all'
>> +oe_runmake 'fips_user_code'
>> +}
>> +
>> +# Overriding do_install() of yocto module.bbclass so that we #
>> +specially handle the ingredients built by QAT
>
>I know there is not much we can do about this now, but it would be great to
>give
>feedback to the owners of the code to move this install to Makefiles instead of
>here. If the above items are addressed this can go in but please that to the
>QAT
>folks.
The software package was released in the past and we hav
Re: [meta-intel] [PATCH 2/4 dizzy] meta-crystalforest: Intel QAT v1.5 recipe under recipes-extended
>Hi, > >When I build this with dizzy I get a build failure that: > >> | ../../common/cpa_sample_utils.c >> | cpa_dc_stateless_multi_op_checksum_sample.c >> | ../../../performance/qae/linux/user_space/qae_mem_utils.c >> | ../stateless_sample/cpa_dc_sample_user.c >> | /srv/ssd/builds/world/tmp/work/crystalforest-poky-linux/qat/2.2.0-30 >> | -r0/QAT1.5/build/libicp_qa_al_s.so -L/usr/Lib -lpthread -lcrypto -o >> | dc_stateless_multi_op_sample >> | /usr/bin/ld: cannot find -lcrypto >> | collect2: error: ld returned 1 exit status >> | Makefile:111: recipe for target 'default' failed > >This sysroot does contain a /lib/libcrypto.so, and you can see the -L/usr/lib, >but >no -L/lib, Did you do a compile check? Interesting. Perhaps, it is due to sysroot has the libcrypto from earlier build. We did bitbake qat -f -c cleanall before bitbake qat. Will check back again. > > >Also, I am confused with this version-ing of 1.5 and 1.6, but you set PV >in those recipes to 2.2.0-30, which could cause problems with upgrade path. > >Have you tested building qat 1.6 version? I think it will have the same >crypto problem. > >I thing a better thing would be to name them qat15_2.2.0-30 and >qat16_2.2.0-30, that way the package names are distinct. You can still >control which QAT is installed in an image using a virtual/qat set up >similar to the kernel. Well, this is definitely a clean-up needed on QAT source package. The tarball package is as follow qatmux.l.2.2.0-30.tar_.gz which untar into two folders: QAT1.5/QAT1.5.L.1.7.0-30.tar.gz QAT1.6/QAT1.6.L.2.2.0-30.tar.gz I think that to be more specific, we can have the following: qat15_1.7.0-30.bb qat16_2.2.0-30.bb Then as suggested by Saul, use the following PREFERRED_PROVIDER_virtual/qat ?= "qat15" PREFERRED_VERSION_qat15 ?= "1.7.0-%" PREFERRED_PROVIDER_virtual/qat ?= "qat16" PREFERRED_VERSION_qat16 ?= "2.2.0-%" -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 4/4 dizzy] meta-crystalforest: Intel QAT v1.6 recipe under recipes-extended
>-Original Message- >From: Pattu, VenkatasubramanianX >Sent: Friday, June 19, 2015 3:19 PM >To: meta-intel@yoctoproject.org >Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX >Subject: [PATCH 4/4 dizzy] meta-crystalforest: Intel QAT v1.6 recipe under >recipes-extended > >This recipe is targeting on Intel QAT v1.6. > >"QAT1.6" is for use with Intel Communications Chipset 8925 to >8955(DH895xcc)Series. >Therefore, this recipe supports QAT on Coleto Creek platforms. >This recipe is created under meta-intel/meta-crystalforest. > >Signed-off-by: venkatasubramanian pattu > Reviewed-by: Ong Boon Leong >--- > .../qat/qat/qat-1.6-app-dynamiccompression.patch | 35 >++ > .../qat/qat/qat-1.6-app-fix-QA-issue.patch | 33 > meta-crystalforest/recipes-extended/qat/qat_1.6.bb | 18 +++ > 3 files changed, 86 insertions(+) > create mode 100644 meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app- >dynamiccompression.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app- >fix-QA-issue.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/qat_1.6.bb > >diff --git a/meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app- >dynamiccompression.patch b/meta-crystalforest/recipes-extended/qat/qat/qat- >1.6-app-dynamiccompression.patch >new file mode 100644 >index 000..796c861 >--- /dev/null >+++ b/meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app- >dynamiccompression.patch >@@ -0,0 +1,35 @@ >+From 8f042b72e96f306196f92c39caa32d4cfbed3812 Mon Sep 17 00:00:00 >2001 >+From: venkatasubramanian pattu >+Date: Fri, 12 Jun 2015 17:13:21 +0800 >+Subject: [PATCH] app: Enable the Dynamic Compression feature >+ >+This Patch is used to enable the Dynamic Compression feature >+ >+This will fix for qat applications failure. >+ERROR : dcStatelessSample(): cpaDcQueryCapabilities >+dcStatelessSample(): cpaDcGetSessionSize >+[error] dcCheckSessionData() - : Invalid API Param - Invalid huffType value, >+dynamic sessions not supported >+ >+Upstream Status: Inappropriate >+ >+Signed-off-by: venkatasubramanian pattu > >+--- >+ .../lookaside/access_layer/src/common/compression/include/dc_session.h | >2 +- >+ 1 file changed, 1 insertion(+), 1 deletion(-) >+ >+diff --git >a/quickassist/lookaside/access_layer/src/common/compression/include/dc_ses >sion.h >b/quickassist/lookaside/access_layer/src/common/compression/include/dc_se >ssion.h >+index b7dc943..7fda6bb 100755 >+--- >a/quickassist/lookaside/access_layer/src/common/compression/include/dc_ses >sion.h > >b/quickassist/lookaside/access_layer/src/common/compression/include/dc_se >ssion.h >+@@ -80,7 +80,7 @@ >+ #include "sal_qat_cmn_msg.h" >+ >+ /* Defeature Dynamic Compression */ >+-#define ICP_DC_DYN_NOT_SUPPORTED (1) >++/*#define ICP_DC_DYN_NOT_SUPPORTED (1) */ >+ >+ /* Maximum number of intermediate buffers SGLs */ >+ #define DC_MAX_NUM_INTERMEDIATE_BUFFERS (12) >+-- >+1.9.1 >diff --git a/meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app-fix-QA- >issue.patch b/meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app-fix-QA- >issue.patch >new file mode 100644 >index 000..24c2955 >--- /dev/null >+++ b/meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app-fix-QA- >issue.patch >@@ -0,0 +1,33 @@ >+From 9f9529e41adf4aa3607b343da37f8af3f60ec31d Mon Sep 17 00:00:00 >2001 >+From: Sreeju Selvaraj >+Date: Thu, 30 Oct 2014 18:04:36 +0800 >+Subject: [PATCH] app: fix QA issue >+ >+This will fix the qat application build error: >+ERROR: QA Issue: The compile log indicates that host include >+and/or library paths were used >+ >+Upstream Status: Inappropriate >+ >+Signed-off-by: Sreeju Selvaraj >+Signed-off-by: venkatasubramanian pattu > >+--- >+ .../build_system/build_files/env_files/linux_2.6_user_space.mk | 3 >+-- >+ 1 file changed, 1 insertion(+), 2 deletions(-) >+ >+diff --git >a/quickassist/build_system/build_files/env_files/linux_2.6_user_space.mk >b/quickassist/build_system/build_files/env_files/linux_2.6_user_space.mk >+index 2d6e2dc..4c4c1c9 100755 >+--- a/quickassist/build_system/build_files/env_files/linux_2.6_user_space.mk > >b/quickassist/build_system/build_files/env_files/linux_2.6_user_space.mk >+@@ -72,8 +72,7 @@ >+ # >+ #- >+ >+-INCLUDES+=-I/usr/include \ >+- -I$(API_DIR) \ >++INCLUDES+=-I$(API_DIR) \ >+ -I$(OSAL_DIR)/include \ >+ -I$(OSAL_DIR)/src/linux/user_space/include >+ >+-- >+1.9.1 >diff --git a/meta-crystalforest
Re: [meta-intel] [PATCH 3/4 dizzy] meta-crystalforest: Removing the hidden windows characters from QAT v1.6 source repository
This is a DOS formatting patch that is in the released package. Instead of assuming developer build machine is pre-installed with dos2unix step, we proposed that we use a patch to clean-up those trailing line-feed character from DOS. So, please take note that when apply the patch on the git repo, "--keep-cr" is required. >-Original Message- >From: Pattu, VenkatasubramanianX >Sent: Friday, June 19, 2015 3:17 PM >To: meta-intel@yoctoproject.org >Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX >Subject: [PATCH 3/4 dizzy] meta-crystalforest: Removing the hidden windows >characters from QAT v1.6 source repository > >Note: Since this patch has ASCII characters need to use >"git am --keep-cr" to apply the patch. > >Signed-off-by: venkatasubramanian pattu > Reviewed-by: Ong Boon Leong >--- > .../qat/qat/qat-1.6-app-Fix-for-dos2unix.patch | 467 >+ > 1 file changed, 467 insertions(+) > create mode 100644 meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app- >Fix-for-dos2unix.patch > >diff --git a/meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app-Fix-for- >dos2unix.patch b/meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app-Fix- >for-dos2unix.patch >new file mode 100644 >index 000..f1e65f4 >--- /dev/null >+++ b/meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app-Fix-for- >dos2unix.patch >@@ -0,0 +1,467 @@ >+From 8ccae0cd0271ce575451131f5b493cfabd8cd0cb Mon Sep 17 00:00:00 >2001 >+From: venkatasubramanian pattu >+Date: Fri, 12 Jun 2015 17:11:41 +0800 >+Subject: [PATCH] app: Fix for dos2unix >+ >+This patch is used to remove the hidden windows characters from this file >+ >+Upstream Status: Inappropriate >+ >+Signed-off-by: venkatasubramanian pattu > >+--- >+ .../src/common/compression/include/dc_session.h| 438 ++ >--- >+ 1 file changed, 219 insertions(+), 219 deletions(-) >+ >+diff --git >a/quickassist/lookaside/access_layer/src/common/compression/include/dc_ses >sion.h >b/quickassist/lookaside/access_layer/src/common/compression/include/dc_se >ssion.h >+index f4d965f..b7dc943 100755 >+--- >a/quickassist/lookaside/access_layer/src/common/compression/include/dc_ses >sion.h > >b/quickassist/lookaside/access_layer/src/common/compression/include/dc_se >ssion.h >+@@ -1,5 +1,5 @@ >+- >/* >*** >+- * >++/*** >* >++ * >+ * This file is provided under a dual BSD/GPLv2 license. When using or >+ * redistributing this file, you may do so under either license. >+ * >+@@ -58,220 +58,220 @@ >+ * >+ * >+ * version: QAT1.6.L.2.2.0-30 >+- * >+- >** >*/ >+- >+-/** >+- >** >*** >+- * @file dc_session.h >+- * >+- * @ingroup Dc_DataCompression >+- * >+- * @description >+- * Definition of the Data Compression session parameters. >+- * >+- >** >***/ >+-#ifndef DC_SESSION_H >+-#define DC_SESSION_H >+- >+-#include "cpa_dc_dp.h" >+-#include "icp_adf_transport.h" >+-#include "icp_qat_fw_comp.h" >+-#include "sal_qat_cmn_msg.h" >+- >+-/* Defeature Dynamic Compression */ >+-#define ICP_DC_DYN_NOT_SUPPORTED (1) >+- >+-/* Maximum number of intermediate buffers SGLs */ >+-#define DC_MAX_NUM_INTERMEDIATE_BUFFERS (12) >+- >+-/* Maximum size of the state registers 64 bytes */ >+-#define DC_QAT_STATE_REGISTERS_MAX_SIZE (64) >+- >+-/* Size of the history window. >+- * Base 2 logarithm of maximum window size minus 8 */ >+-#define DC_8K_WINDOW_SIZE (5) >+-#define DC_32K_WINDOW_SIZE (7) >+- >+-/* Context size */ >+-#define DC_DEFLATE_MAX_CONTEXT_SIZE (49152) >+-#define DC_DEFLATE_MEDIUM_CONTEXT_SIZE (40960) >+-#define DC_DEFLATE_MIN_CONTEXT_SIZE (32768) >+-#define DC_INFLATE_CONTEXT_SIZE (36864) >+- >+-/* Retrieve the session descriptor pointer from the session context structure >+- * that the user allocates. The pointer to the internally realigned address >+- * is stored at the start of the session context that the user allocates */ >+-#define DC_SESSION_DESC_FROM_CTX_GET(pSession) \ >+-(dc_session_desc_t *) (*(LAC_ARCH_UINT *)pSession) >+- >+-/* Maximum size for the compression part of the content descriptor */ >+-#define DC_QAT_COMP_CONTENT_DESC_SIZE \ >+-sizeof(icp_qat_fw_comp_cd_hdr_t) >+- >+-/* Maximum size for the translator part
Re: [meta-intel] [PATCH 2/4 dizzy] meta-crystalforest: Intel QAT v1.5 recipe under recipes-extended
>-Original Message-
>From: Pattu, VenkatasubramanianX
>Sent: Friday, June 19, 2015 3:15 PM
>To: meta-intel@yoctoproject.org
>Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX
>Subject: [PATCH 2/4 dizzy] meta-crystalforest: Intel QAT v1.5 recipe under
>recipes-extended
>
>This is an Initial version of Intel QuickAssist Technology(QAT)
>recipe support. This recipe is targeting on Intel QAT v1.5.
>
>Intel's QuickAssist Technology is designed to optimize the use
>and deployment of algorithm accelerators in networking and security
>applications.
>
>The package version of QAT1.5 is 1.7.0-30.
>
>"QAT1.5" is for use with Intel Communications Chipset 8900 to
>8920(DH89xxCC)Series.
>Therefore, this recipe supports QAT on Cave Creek platforms.
>This recipe is created under meta-intel/meta-crystalforest.
>
>Signed-off-by: venkatasubramanian pattu
>
Reviewed-by: Ong Boon Leong
>---
> .../qat/qat/qat-1.5-enable-dynamic.patch | 35
>++
> meta-crystalforest/recipes-extended/qat/qat_1.5.bb | 16 ++
> 2 files changed, 51 insertions(+)
> create mode 100644 meta-crystalforest/recipes-extended/qat/qat/qat-1.5-
>enable-dynamic.patch
> create mode 100644 meta-crystalforest/recipes-extended/qat/qat_1.5.bb
>
>diff --git a/meta-crystalforest/recipes-extended/qat/qat/qat-1.5-enable-
>dynamic.patch b/meta-crystalforest/recipes-extended/qat/qat/qat-1.5-enable-
>dynamic.patch
>new file mode 100644
>index 000..6f5eb9f
>--- /dev/null
>+++ b/meta-crystalforest/recipes-extended/qat/qat/qat-1.5-enable-
>dynamic.patch
>@@ -0,0 +1,35 @@
>+From f428c0198d61087ba031985c571574a099096e1c Mon Sep 17 00:00:00
>2001
>+From: venkatasubramanian pattu
>+Date: Wed, 17 Jun 2015 14:34:05 +0800
>+Subject: [PATCH] app: Enable the Dynamic Compression feature
>+
>+This Patch is used to enable the Dynamic Compression feature
>+
>+This will fix for qat applications failure.
>+ERROR : dcStatelessSample(): cpaDcQueryCapabilities
>+dcStatelessSample(): cpaDcGetSessionSize
>+[error] dcCheckSessionData() - : Invalid API Param - Invalid huffType value,
>+dynamic sessions not supported
>+
>+Upstream Status: Inappropriate
>+
>+Signed-off-by: venkatasubramanian pattu
>
>+---
>+ .../lookaside/access_layer/src/common/compression/include/dc_session.h |
>2 +-
>+ 1 file changed, 1 insertion(+), 1 deletion(-)
>+
>+diff --git
>a/quickassist/lookaside/access_layer/src/common/compression/include/dc_ses
>sion.h
>b/quickassist/lookaside/access_layer/src/common/compression/include/dc_se
>ssion.h
>+index da69433..2b755dc 100644
>+---
>a/quickassist/lookaside/access_layer/src/common/compression/include/dc_ses
>sion.h
>
>b/quickassist/lookaside/access_layer/src/common/compression/include/dc_se
>ssion.h
>+@@ -80,7 +80,7 @@
>+ #include "sal_qat_cmn_msg.h"
>+
>+ /* Defeature Dynamic Compression */
>+-#define ICP_DC_DYN_NOT_SUPPORTED (1)
>++/*#define ICP_DC_DYN_NOT_SUPPORTED (1) */
>+
>+ /* Maximum size of the state registers 64 bytes */
>+ #define DC_QAT_STATE_REGISTERS_MAX_SIZE (64)
>+--
>+1.9.1
>diff --git a/meta-crystalforest/recipes-extended/qat/qat_1.5.bb b/meta-
>crystalforest/recipes-extended/qat/qat_1.5.bb
>new file mode 100644
>index 000..8b428d9
>--- /dev/null
>+++ b/meta-crystalforest/recipes-extended/qat/qat_1.5.bb
>@@ -0,0 +1,16 @@
>+include qat.inc
>+
>+PV = "2.2.0-30"
>+
>+export QAT_VERSION = "1.7.0-30"
>+export ICP_DH89XX = "QAT1.5"
>+export ICP_DRIVER_TYPE = "${ICP_DH89XX}"
>+export ICP_FIRMWARE_DIR="firmware"
>+
>+SRC_URI="https://01.org/sites/default/files/page/qatmux.l.${PV}.tar_.gz;name
>=qat \
>+ file://00-qat_qa.rules \
>+ file://qat-1.5-enable-dynamic.patch \
>+ "
>+
>+SRC_URI[qat.md5sum] = "9567adeba4a4af50f4ac3ab70a3091ed"
>+SRC_URI[qat.sha256sum] =
>"00ac245dc6226d6bcba2326d7b6fa045f91a616c67a003f299f404af84d52032"
>--
>1.9.1
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 1/4 dizzy] meta-crystalforest: Add include file for QAT
>-Original Message-
>From: Pattu, VenkatasubramanianX
>Sent: Friday, June 19, 2015 3:14 PM
>To: meta-intel@yoctoproject.org
>Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX
>Subject: [PATCH 1/4 dizzy] meta-crystalforest: Add include file for QAT
>
>Added include file qat.inc to share common functionality based on
>qat_1.5 and qat_1.6.
>
>Signed-off-by: venkatasubramanian pattu
>
Reviewed-by: Ong Boon Leong
>---
> meta-crystalforest/recipes-extended/qat/qat.inc| 201
>+
> .../recipes-extended/qat/qat/00-qat_qa.rules | 3 +
> 2 files changed, 204 insertions(+)
> create mode 100644 meta-crystalforest/recipes-extended/qat/qat.inc
> create mode 100644 meta-crystalforest/recipes-extended/qat/qat/00-
>qat_qa.rules
>
>diff --git a/meta-crystalforest/recipes-extended/qat/qat.inc b/meta-
>crystalforest/recipes-extended/qat/qat.inc
>new file mode 100644
>index 000..e5f802b
>--- /dev/null
>+++ b/meta-crystalforest/recipes-extended/qat/qat.inc
>@@ -0,0 +1,201 @@
>+SUMMARY = "Intel QuickAssist Technology Driver"
>+DESCRIPTION = "Intel QuickAssist Technology for packet processing
>+acceleration for both Intel Coleto Creek & Cave Creek platforms \ Software
>Package. "
>+
>+LICENSE = "GPLv2"
>+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-
>2.0;md5=801f80980d171dd6425610833a22dbe6"
>+COMPATIBLE_MACHINE = "crystalforest"
>+
>+PR = "r0"
>+KERNEL_VERSION = "${@base_read_file('${STAGING_KERNEL_DIR}/kernel-
>abiversion')}"
>+MODULE_DIR =
>"${D}${base_libdir}/modules/${KERNEL_VERSION}/kernel/drivers"
>+ICP_TOOLS = "accelcomp"
>+
>+S = "${WORKDIR}/${ICP_DRIVER_TYPE}"
>+B = "${S}/build"
>+SAMPLE_CODE_DIR =
>"${S}/quickassist/lookaside/access_layer/src/sample_code"
>+
>+export KERNEL_SOURCE_ROOT = "${STAGING_KERNEL_DIR}"
>+export ICP_ROOT = "${S}"
>+export ICP_BUILD_OUTPUT = "${B}"
>+export ICP_BUILDSYSTEM_PATH = "${S}/quickassist/build_system"
>+export ICP_TOOLS_TARGET = "${ICP_TOOLS}"
>+export ICP_ENV_DIR = "${S}/quickassist/build_system/build_files/env_files"
>+export FUNC_PATH =
>"${ICP_ROOT}/quickassist/lookaside/access_layer/src/sample_code/functional"
>+
>+HOST[unexport] = "1"
>+HOST[unexport] = "includedir"
>+
>+inherit update-rc.d
>+INITSCRIPT_NAME = "qat_service"
>+
>+inherit module
>+DEPENDS += "openssl"
>+PARALLEL_MAKE = ""
>+
>+# The list of binary built by QAT package.
>+
>+LIBS = "\
>+ libadf_proxy.a \
>+ libosal.a \
>+ libicp_qa_al.a \
>+ libicp_qa_al_s.so \
>+ "
>+
>+FUNC_KERNEL_OBJ_LIST = "\
>+ algchaining_sample.ko \
>+ ccm_sample.ko \
>+ cipher_sample.ko \
>+ dc_dp_sample.ko \
>+ dc_stateless_multi_op_sample.ko \
>+ dc_stateless_sample.ko \
>+ dh_sample.ko \
>+ drbg_sample.ko \
>+ gcm_sample.ko \
>+ hash_sample.ko \
>+ ipsec_sample.ko \
>+ nrbg_sample.ko \
>+ prime_sample.ko \
>+ ssl_sample.ko \
>+ sym_dp_sample.ko \
>+ "
>+
>+FUNC_USER_APP_LIST = "\
>+ dh_sample \
>+ dc_stateful_sample \
>+ dc_dp_sample \
>+ cipher_sample \
>+ sym_dp_sample \
>+ nrbg_sample \
>+ drbg_sample \
>+ dc_stateless_multi_op_sample \
>+ paper4 \
>+ hash_file_sample \
>+ ccm_sample \
>+ ipsec_sample \
>+ algchaining_sample \
>+ ssl_sample \
>+ dc_stateless_sample \
>+ hash_sample \
>+ gcm_sample \
>+ prime_sample \
>+ "
>+
>+do_unpack2() {
>+ cd ${WORKDIR}
>+ tar xvf qatmux.l.${PV}.tar_
>+ cd ${S}/
>+ tar xzvf ${ICP_DRIVER_TYPE}.L.${QAT_VERSION}.tar.gz
>+}
>+
>+addtask unpack2 after do_unpack before do_patch
>+
>+do_compile() {
>+ export LD="${LD} --hash-style=gnu"
>+ export MACHINE="${TARGET_ARCH}"
>+ cd ${S}/quickassist
>+ oe_runmake EXTRA_OEMAKE="'CFLAGS=${CFLAGS} -fPIC'"
>+
>+ cd ${SAMPLE_CODE_DIR}
>+ touch ${SAMPLE_CODE_DIR}/performance/compression/calgary
>+ touch ${SAMPLE_CODE_DIR}/performance/compression/canterbury
>+ # build the whole sample code: fips, functional, performance
>+ oe_runmake 'all'
>+ oe_runmake 'fips_user_code'
>+}
>+
>+# Overriding do_install() of yocto module.bbclass so that we #
>+specially handle the ingredients built by QAT
>+do
Re: [meta-intel] [PATCH 0/4 dizzy] meta-crystalforest: Initial Intel QAT-core Implementation
Dear maintainers, I have reviewed Venkat's work and patches over couple of revision before this version. This morning, he has shown the QAT test results on Crystal Forest and I have found them to be satisfactory. Please kindly review and if you think that they are acceptable, please help to merge them into meta-intel. Thanks You. Boon Leong >-Original Message- >From: Pattu, VenkatasubramanianX >Sent: Friday, June 19, 2015 3:12 PM >To: meta-intel@yoctoproject.org >Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX >Subject: [PATCH 0/4 dizzy] meta-crystalforest: Initial Intel QAT-core >Implementation > >Intel's QuickAssist Technology is designed to optimize the use and deployment >of algorithm accelerators in networking and security applications. >As the complexity of networking and security applications continues to grow, >systems need more and more computational resources for workloads, including >cryptography, data compression, and pattern matching. >Intel QuickAssist Technology is designed to optimize the use and deployment of >algorithm accelerators in these kinds of applications. > >Intel QuickAssist Technology employs a hardware-assisted security engine for >implementing major security functions in both wired and wireless applications. >This hardware-assisted security engine works to reserve processor cycles for >application processing, and that in turn not only relieves CPU burden but also >improves overall system performance. > >Intel QuickAssist Technology, made integral to the Intel architecture, aims to >address the demand for hardware appliances with built-in security processing >and to obviate the need for 3rd party co-processors. > >The Intel QuickAssist Technology software consists of an QAT API that is >implemented by a driver which in turn drives the Intel QuickAssist Accelerator >hardware. >The acceleration driver can run in either kernel space or in user space. >When running in user space, the acceleration driver accesses the hardware >directly from user space. >This Patch enables the QAT core for both Cave Creek and Coleto Creek Platforms. > >The package version of QAT1.5 is 1.7.0-30. > >The patch (meta-crystalforest: Removing the hidden windows characters from >QAT v1.6 source repository) has ASCII characters need to use "git am --keep-cr" >to apply the patch. > >QAT package is released from 01.org. >https://01.org/packet-processing/intel%C2%AE-quickassist-technology-drivers- >and-patches > >"QAT1.5" for use with Intel Communications Chipset 8900 to >8920(DH89xxCC)Series. >"QAT1.6" for use with Intel Communications Chipset 8925 to >8955(DH895xcc)Series. > >venkatasubramanian pattu (4): > meta-crystalforest: Add include file for QAT > meta-crystalforest: Intel QAT v1.5 recipe under recipes-extended > meta-crystalforest: Removing the hidden windows characters from QAT >v1.6 source repository > meta-crystalforest: Intel QAT v1.6 recipe under recipes-extended > > meta-crystalforest/recipes-extended/qat/qat.inc| 200 + > .../recipes-extended/qat/qat/00-qat_qa.rules | 3 + > .../qat/qat/qat-1.5-enable-dynamic.patch | 35 ++ > .../qat/qat/qat-1.6-app-Fix-for-dos2unix.patch | 467 >+ > .../qat/qat/qat-1.6-app-dynamiccompression.patch | 35 ++ > .../qat/qat/qat-1.6-app-fix-QA-issue.patch | 33 ++ > meta-crystalforest/recipes-extended/qat/qat_1.5.bb | 16 + meta- >crystalforest/recipes-extended/qat/qat_1.6.bb | 18 + > 8 files changed, 807 insertions(+) > create mode 100644 meta-crystalforest/recipes-extended/qat/qat.inc > create mode 100644 meta-crystalforest/recipes-extended/qat/qat/00- >qat_qa.rules > create mode 100644 meta-crystalforest/recipes-extended/qat/qat/qat-1.5- >enable-dynamic.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app- >Fix-for-dos2unix.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app- >dynamiccompression.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/qat/qat-1.6-app- >fix-QA-issue.patch > create mode 100644 meta-crystalforest/recipes-extended/qat/qat_1.5.bb > create mode 100644 meta-crystalforest/recipes-extended/qat/qat_1.6.bb > >-- >1.9.1 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [dizzy][PATCH v2 2/2] meta-isg: dpdk: improve software installation task
do_install() has been non-scalable due to different DPDK SW releases
offer increasingly more examples. So, this patch is intended to make
the do_install() simplified by using regular expression technique to
extract out executables name that are built.
Tested this patch with DPDK v1.6.0r2 and v1.7.0 and the software packages
look intact.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc | 83
1 file changed, 26 insertions(+), 57 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 5e7d52b..910feb4 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -9,13 +9,13 @@ inherit module
export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
export RTE_SDK = "${S}"
-export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
+export RTE_TARGET="${@bb.utils.contains("TUNE_FEATURES", "corei7",
"x86_64-ivshmem-linuxapp-gcc", "i686-native-linuxapp-gcc", d)}"
+
export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
export INSTALL_PATH = "${prefix}/dpdk"
-
do_configure () {
#
### default value for prefix is "usr", unsetting it, so it
@@ -25,10 +25,8 @@ do_configure () {
unset prefix
make O=$RTE_TARGET T=$RTE_TARGET config
-
}
-
do_compile () {
unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
@@ -37,10 +35,8 @@ do_compile () {
EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
CROSS="${TARGET_PREFIX}" \
prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
-
}
-
do_install () {
install -m 0755 -d ${D}/${INSTALL_PATH} \
@@ -48,70 +44,36 @@ do_install () {
${D}/${INSTALL_PATH}/tools \
${D}/${INSTALL_PATH}/${RTE_TARGET} \
${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
+ ${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp \
${D}${includedir} \
${D}${includedir}/arch \
${D}${includedir}/exec-env \
${D}${libdir} \
${D}${MODULE_DIR}
- install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
${D}${MODULE_DIR}/
- install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
${D}${MODULE_DIR}/
+ install -m 0755 ${S}/${RTE_TARGET}/kmod/*.ko${D}${MODULE_DIR}/
install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
- install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
- install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/exec-env/
+ install -m 640 ${S}/${RTE_TARGET}/include/arch/*.h
${D}${includedir}/arch/
+ install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*.h
${D}${includedir}/exec-env/
install -m 0755 ${S}/tools/*.py
${D}/${INSTALL_PATH}/tools/
+ # Install applications
+ install -m 0755 ${S}/${RTE_TARGET}/app/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/app/
+ install -m 0755 ${S}/${RTE_TARGET}/hostapp/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp/
- #Install test applications
- install -m 0755 ${S}/${RTE_TARGET}/app/test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/testpmd
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/dump_cfg
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/cmdline_test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
-
-
- # Install example applications
- # It is expected that user of this include file should define
EXAMPLES_BUILD_DIR
- for app in ${S}/examples/*
+ # Install examples
+ for dirname in ${S}/examples/*
do
- case `basename ${app}` in
- "dpdk_qat" | "vhost" | "vhost_xen" | "Makefile" ) continue
- ;;
- "l2fwd-ivshmem")
- install -m 0755 ${app}/guest/${EXAMPLES_BUILD_DIR}/app/guest
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
-
[meta-intel] [dizzy][PATCH v2 0/2] meta-isg: DPDK recipe clean-up and enhancement
Saul, My bad on the patch format that my vim configuration accidently wipe-out all trailing white-space. This patchseries should apply cleanly ontop of meta-intel dizzy head. This patchset achieves: 1) remove unnecessary dpdk recipes under meta-romley since DPDK recipe is not moved to be under meta-isg/common/recipes-extended 2) enhance the do_install() task that has not been scalable across DPDK release. I have built tested and cross-checked the content under packages-split for both DPDK v1.6.0r2 & DPDK v1.7.0 and find them to be fit. Please review and consider merging them if there is no concern under meta-intel dizzy branch Thank You Ong Boon Leong Intel Corp --- changelog v2 fixed the patch white-trailing issue that causes git am issue. Ong Boon Leong (2): meta-romley: remove dpdk recipe from meta-romley since it is now in meta-isg meta-isg: dpdk: improve software installation task meta-isg/common/recipes-extended/dpdk/dpdk.inc | 83 ++--- meta-romley/recipes-extended/dpdk/dpdk.inc | 140 ...ix-build-switches-to-enable-cmdline-tests.patch | 53 --- ...dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch | 35 -- ...k-1.6.0r2-examples-qos_sched-fix-makefile.patch | 35 -- ...d-config-variables-to-enable-disable-dpdk.patch | 42 --- ...examples-pipeline-build-with-all-examples.patch | 34 -- ...e-extra-devices-creation-with-vdev-option.patch | 44 --- .../dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch | 380 meta-romley/recipes-extended/dpdk/dpdk_1.6.0r2.bb | 45 --- meta-romley/recipes-extended/dpdk/dpdk_1.7.0.bb| 41 --- 11 files changed, 26 insertions(+), 906 deletions(-) delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk.inc delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-app-test-fix-build-switches-to-enable-cmdline-tests.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-examples-qos_sched-fix-makefile.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-Add-config-variables-to-enable-disable-dpdk.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-pipeline-build-with-all-examples.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-remove-extra-devices-creation-with-vdev-option.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk_1.6.0r2.bb delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk_1.7.0.bb -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [dizzy][PATCH v2 1/2] meta-romley: remove dpdk recipe from meta-romley since it is now in meta-isg
dpdk recipe has been moved to meta-isg/common/recipes-extended, so we clean
up this from under meta-romley.
Signed-off-by: Ong Boon Leong
---
meta-romley/recipes-extended/dpdk/dpdk.inc | 140
...ix-build-switches-to-enable-cmdline-tests.patch | 53 ---
...dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch | 35 --
...k-1.6.0r2-examples-qos_sched-fix-makefile.patch | 35 --
...d-config-variables-to-enable-disable-dpdk.patch | 42 ---
...examples-pipeline-build-with-all-examples.patch | 34 --
...e-extra-devices-creation-with-vdev-option.patch | 44 ---
.../dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch | 380
meta-romley/recipes-extended/dpdk/dpdk_1.6.0r2.bb | 45 ---
meta-romley/recipes-extended/dpdk/dpdk_1.7.0.bb| 41 ---
10 files changed, 849 deletions(-)
delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk.inc
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-app-test-fix-build-switches-to-enable-cmdline-tests.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-examples-qos_sched-fix-makefile.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-Add-config-variables-to-enable-disable-dpdk.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-pipeline-build-with-all-examples.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-remove-extra-devices-creation-with-vdev-option.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch
delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk_1.6.0r2.bb
delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk_1.7.0.bb
diff --git a/meta-romley/recipes-extended/dpdk/dpdk.inc
b/meta-romley/recipes-extended/dpdk/dpdk.inc
deleted file mode 100644
index 0547c7e..000
--- a/meta-romley/recipes-extended/dpdk/dpdk.inc
+++ /dev/null
@@ -1,140 +0,0 @@
-DESCRIPTION = "Intel(r) Data Plane Development Kit"
-HOMEPAGE = "http://dpdk.org";
-LICENSE = "BSD & LGPLv2 & GPLv2"
-LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe"
-
-COMPATIBLE_MACHINE = "romley|romley-ivb"
-
-RDEPENDS_${PN} += "python-subprocess"
-
-inherit module
-
-export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
-export RTE_SDK = "${S}"
-export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
-export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
-export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
-export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
-export INSTALL_PATH = "${prefix}/dpdk"
-
-
-do_configure () {
- #
- ### default value for prefix is "usr", unsetting it, so it
- ### will not be concatenated in ${RTE_TARGET}/Makefile
- ### which will cause compilation failure
- #
- unset prefix
-
- make O=$RTE_TARGET T=$RTE_TARGET config
-
-}
-
-
-do_compile () {
- unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
-
- cd ${S}/${RTE_TARGET}
- oe_runmake EXTRA_LDFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
- EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
- CROSS="${TARGET_PREFIX}" \
- prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
-
-}
-
-
-do_install () {
-
- install -m 0755 -d ${D}/${INSTALL_PATH} \
- ${D}/${INSTALL_PATH}/doc \
- ${D}/${INSTALL_PATH}/tools \
- ${D}/${INSTALL_PATH}/${RTE_TARGET} \
- ${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
- ${D}${includedir} \
- ${D}${includedir}/arch \
- ${D}${includedir}/exec-env \
- ${D}${libdir} \
- ${D}${MODULE_DIR}
-
- install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
${D}${MODULE_DIR}/
- install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
${D}${MODULE_DIR}/
-
- install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
-
- install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
- install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
- install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
- install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/ex
[meta-intel] [dizzy][PATCH 2/2] meta-isg: dpdk: improve software installation task
do_install() has been non-scalable due to different DPDK SW releases
offer increasingly more examples. So, this patch is intended to make
the do_install() simplified by using regular expression technique to
extract out executables name that are built.
Tested this patch with DPDK v1.6.0r2 and v1.7.0 and the software packages
look intact.
Signed-off-by: Ong Boon Leong
---
meta-isg/common/recipes-extended/dpdk/dpdk.inc | 83
1 file changed, 26 insertions(+), 57 deletions(-)
diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
index 5e7d52b..910feb4 100644
--- a/meta-isg/common/recipes-extended/dpdk/dpdk.inc
+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
@@ -9,13 +9,13 @@ inherit module
export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
export RTE_SDK = "${S}"
-export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
+export RTE_TARGET="${@bb.utils.contains("TUNE_FEATURES", "corei7",
"x86_64-ivshmem-linuxapp-gcc", "i686-native-linuxapp-gcc", d)}"
+
export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
export INSTALL_PATH = "${prefix}/dpdk"
-
do_configure () {
#
### default value for prefix is "usr", unsetting it, so it
@@ -25,10 +25,8 @@ do_configure () {
unset prefix
make O=$RTE_TARGET T=$RTE_TARGET config
-
}
-
do_compile () {
unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
@@ -37,10 +35,8 @@ do_compile () {
EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
CROSS="${TARGET_PREFIX}" \
prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
-
}
-
do_install () {
install -m 0755 -d ${D}/${INSTALL_PATH} \
@@ -48,70 +44,36 @@ do_install () {
${D}/${INSTALL_PATH}/tools \
${D}/${INSTALL_PATH}/${RTE_TARGET} \
${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
+ ${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp \
${D}${includedir} \
${D}${includedir}/arch \
${D}${includedir}/exec-env \
${D}${libdir} \
${D}${MODULE_DIR}
- install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
${D}${MODULE_DIR}/
- install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
${D}${MODULE_DIR}/
+ install -m 0755 ${S}/${RTE_TARGET}/kmod/*.ko${D}${MODULE_DIR}/
install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
- install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
- install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/exec-env/
+ install -m 640 ${S}/${RTE_TARGET}/include/arch/*.h
${D}${includedir}/arch/
+ install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*.h
${D}${includedir}/exec-env/
install -m 0755 ${S}/tools/*.py
${D}/${INSTALL_PATH}/tools/
+ # Install applications
+ install -m 0755 ${S}/${RTE_TARGET}/app/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/app/
+ install -m 0755 ${S}/${RTE_TARGET}/hostapp/*
${D}/${INSTALL_PATH}/${RTE_TARGET}/hostapp/
- #Install test applications
- install -m 0755 ${S}/${RTE_TARGET}/app/test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/testpmd
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/dump_cfg
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755 ${S}/${RTE_TARGET}/app/cmdline_test
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
-
-
- # Install example applications
- # It is expected that user of this include file should define
EXAMPLES_BUILD_DIR
- for app in ${S}/examples/*
+ # Install examples
+ for dirname in ${S}/examples/*
do
- case `basename ${app}` in
- "dpdk_qat" | "vhost" | "vhost_xen" | "Makefile" ) continue
- ;;
- "l2fwd-ivshmem")
- install -m 0755 ${app}/guest/${EXAMPLES_BUILD_DIR}/app/guest
${D}/${INSTALL_PATH}/${RTE_TARGET}/app
- install -m 0755
[meta-intel] [dizzy][PATCH 0/2] meta-isg: DPDK recipe clean-up and enhancement
Dear maintainter, This patchset achieves: 1) remove unnecessary dpdk recipes under meta-romley since DPDK recipe is not moved to be under meta-isg/common/recipes-extended 2) enhance the do_install() task that has not been scalable across DPDK release. I have built tested and cross-checked the content under packages-split for both DPDK v1.6.0r2 & DPDK v1.7.0 and find them to be fit. Please review and consider merging them if there is no concern under meta-intel dizzy branch Thank You Ong Boon Leong Intel Corp Ong Boon Leong (2): meta-romley: remove dpdk recipe from meta-romley since it is now in meta-isg meta-isg: dpdk: improve software installation task meta-isg/common/recipes-extended/dpdk/dpdk.inc | 83 ++--- meta-romley/recipes-extended/dpdk/dpdk.inc | 140 ...ix-build-switches-to-enable-cmdline-tests.patch | 53 --- ...dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch | 35 -- ...k-1.6.0r2-examples-qos_sched-fix-makefile.patch | 35 -- ...d-config-variables-to-enable-disable-dpdk.patch | 42 --- ...examples-pipeline-build-with-all-examples.patch | 34 -- ...e-extra-devices-creation-with-vdev-option.patch | 44 --- .../dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch | 380 meta-romley/recipes-extended/dpdk/dpdk_1.6.0r2.bb | 45 --- meta-romley/recipes-extended/dpdk/dpdk_1.7.0.bb| 41 --- 11 files changed, 26 insertions(+), 906 deletions(-) delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk.inc delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-app-test-fix-build-switches-to-enable-cmdline-tests.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-examples-qos_sched-fix-makefile.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-Add-config-variables-to-enable-disable-dpdk.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-pipeline-build-with-all-examples.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-remove-extra-devices-creation-with-vdev-option.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk_1.6.0r2.bb delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk_1.7.0.bb -- 1.7.9.5 -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [dizzy][PATCH 1/2] meta-romley: remove dpdk recipe from meta-romley since it is now in meta-isg
dpdk recipe has been moved to meta-isg/common/recipes-extended, so we clean
up this from under meta-romley.
Signed-off-by: Ong Boon Leong
---
meta-romley/recipes-extended/dpdk/dpdk.inc | 140
...ix-build-switches-to-enable-cmdline-tests.patch | 53 ---
...dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch | 35 --
...k-1.6.0r2-examples-qos_sched-fix-makefile.patch | 35 --
...d-config-variables-to-enable-disable-dpdk.patch | 42 ---
...examples-pipeline-build-with-all-examples.patch | 34 --
...e-extra-devices-creation-with-vdev-option.patch | 44 ---
.../dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch | 380
meta-romley/recipes-extended/dpdk/dpdk_1.6.0r2.bb | 45 ---
meta-romley/recipes-extended/dpdk/dpdk_1.7.0.bb| 41 ---
10 files changed, 849 deletions(-)
delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk.inc
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-app-test-fix-build-switches-to-enable-cmdline-tests.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-examples-qos_sched-fix-makefile.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-Add-config-variables-to-enable-disable-dpdk.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-pipeline-build-with-all-examples.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-remove-extra-devices-creation-with-vdev-option.patch
delete mode 100644
meta-romley/recipes-extended/dpdk/dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch
delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk_1.6.0r2.bb
delete mode 100644 meta-romley/recipes-extended/dpdk/dpdk_1.7.0.bb
diff --git a/meta-romley/recipes-extended/dpdk/dpdk.inc
b/meta-romley/recipes-extended/dpdk/dpdk.inc
deleted file mode 100644
index 0547c7e..000
--- a/meta-romley/recipes-extended/dpdk/dpdk.inc
+++ /dev/null
@@ -1,140 +0,0 @@
-DESCRIPTION = "Intel(r) Data Plane Development Kit"
-HOMEPAGE = "http://dpdk.org";
-LICENSE = "BSD & LGPLv2 & GPLv2"
-LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe"
-
-COMPATIBLE_MACHINE = "romley|romley-ivb"
-
-RDEPENDS_${PN} += "python-subprocess"
-
-inherit module
-
-export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
-export RTE_SDK = "${S}"
-export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
-export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
-export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
-export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
-export INSTALL_PATH = "${prefix}/dpdk"
-
-
-do_configure () {
- #
- ### default value for prefix is "usr", unsetting it, so it
- ### will not be concatenated in ${RTE_TARGET}/Makefile
- ### which will cause compilation failure
- #
- unset prefix
-
- make O=$RTE_TARGET T=$RTE_TARGET config
-
-}
-
-
-do_compile () {
- unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
-
- cd ${S}/${RTE_TARGET}
- oe_runmake EXTRA_LDFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
- EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
- CROSS="${TARGET_PREFIX}" \
- prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
-
-}
-
-
-do_install () {
-
- install -m 0755 -d ${D}/${INSTALL_PATH} \
- ${D}/${INSTALL_PATH}/doc \
- ${D}/${INSTALL_PATH}/tools \
- ${D}/${INSTALL_PATH}/${RTE_TARGET} \
- ${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
- ${D}${includedir} \
- ${D}${includedir}/arch \
- ${D}${includedir}/exec-env \
- ${D}${libdir} \
- ${D}${MODULE_DIR}
-
- install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
${D}${MODULE_DIR}/
- install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
${D}${MODULE_DIR}/
-
- install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
-
- install -m 640 ${S}/${RTE_TARGET}/.config
${D}/${INSTALL_PATH}/${RTE_TARGET}/
- install -m 640 ${S}/${RTE_TARGET}/include/*.h
${D}${includedir}/
- install -m 640 ${S}/${RTE_TARGET}/include/arch/*
${D}${includedir}/arch/
- install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
${D}${includedir}/ex
Re: [meta-intel] [PATCH 0/4 dizzy] meta-isg: Intel DPDK Implementation
+>Saul & Darren, >The patch series is a continued work from last what were discussed to bring >dpdk into meta-isg/common so that it can be used for all IOTG supported >platforms >like crystal forest and mohonpeak. > >All of these patches are in the past accepted into meta-isg/common/recipes- >extended Ghee.. I wanted to say meta-romley/recipes-extended above. :) -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 4/4 dizzy] meta-isg: Upgrade DPDK to v1.7.0
>-Original Message- >From: Pattu, VenkatasubramanianX >Sent: Friday, May 8, 2015 12:11 PM >To: meta-intel@yoctoproject.org >Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX >Subject: [PATCH 4/4 dizzy] meta-isg: Upgrade DPDK to v1.7.0 > >Added support for DPDK v1.7.0. > >This recipe is cherry-picked from branch dizzy and the commit ID: >a14718dfaee57827a0666b858cf192dc1cb00db5:meta-intel/common: Upgrade >DPDK to v1.7.0 > >Signed-off-by: venkatasubramanian pattu > Acked-by: Ong Boon Leong >--- > ...d-config-variables-to-enable-disable-dpdk.patch | 41 +++ > ...examples-pipeline-build-with-all-examples.patch | 33 ++ > ...e-extra-devices-creation-with-vdev-option.patch | 43 +++ > .../dpdk/dpdk-1.7.0-ring-simplify-unit-tests.patch | 379 + > .../common/recipes-extended/dpdk/dpdk_1.7.0.bb | 38 +++ > 5 files changed, 534 insertions(+) > create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.7.0- >examples-Add-config-variables-to-enable-disable-dpdk.patch > create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.7.0- >examples-pipeline-build-with-all-examples.patch > create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.7.0- >ring-remove-extra-devices-creation-with-vdev-option.patch > create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.7.0- >ring-simplify-unit-tests.patch > create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_1.7.0.bb > >diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples- >Add-config-variables-to-enable-disable-dpdk.patch b/meta-isg/common/recipes- >extended/dpdk/dpdk/dpdk-1.7.0-examples-Add-config-variables-to-enable-disable- >dpdk.patch >new file mode 100644 >index 000..e17f756 >--- /dev/null >+++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples-Add- >config-variables-to-enable-disable-dpdk.patch >@@ -0,0 +1,41 @@ >+From 63f8ccc5a305b193e219d288ef9e43b9a9fa6aa8 Mon Sep 17 00:00:00 2001 >+From: Sreeju Selvaraj >+Date: Wed, 17 Sep 2014 19:10:01 +0800 >+Subject: [PATCH] examples: Add config variables to enable/disable dpdk_qat and >+ vhost >+ >+Upstream-Status: Inappropriate [configuration] >+ >+This can be used to export CONFIG_EXAMPLE_DPDK_QAT=n if dpdk_qat is not >+in PACKAGECONFIG and also allow to export CONFIG_EXAMPLE_DPDK_VHOST=n >+if vhost is not in PACKAGECONFIG. >+ >+Signed-off-by: Sreeju Selvaraj >+--- >+ examples/Makefile | 4 ++-- >+ 1 file changed, 2 insertions(+), 2 deletions(-) >+ >+diff --git a/examples/Makefile b/examples/Makefile >+index d0624f6..885c938 100644 >+--- a/examples/Makefile > b/examples/Makefile >+@@ -39,7 +39,7 @@ include $(RTE_SDK)/mk/rte.vars.mk >+ >+ DIRS-y += cmdline >+ ifneq ($(ICP_ROOT),) >+-DIRS-y += dpdk_qat >++DIRS-$(CONFIG_EXAMPLE_DPDK_QAT) += dpdk_qat >+ endif >+ DIRS-y += exception_path >+ DIRS-y += helloworld >+@@ -61,7 +61,7 @@ DIRS-$(CONFIG_RTE_LIBRTE_METER) += qos_meter >+ DIRS-$(CONFIG_RTE_LIBRTE_SCHED) += qos_sched >+ DIRS-y += quota_watermark >+ DIRS-y += timer >+-DIRS-y += vhost >++DIRS-$(CONFIG_EXAMPLE_DPDK_VHOST) += vhost >+ DIRS-$(CONFIG_RTE_LIBRTE_XEN_DOM0) += vhost_xen >+ DIRS-y += vmdq >+ DIRS-y += vmdq_dcb >+-- >+1.9.1 >diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples- >pipeline-build-with-all-examples.patch b/meta-isg/common/recipes- >extended/dpdk/dpdk/dpdk-1.7.0-examples-pipeline-build-with-all-examples.patch >new file mode 100644 >index 000..0720af4 >--- /dev/null >+++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.7.0-examples- >pipeline-build-with-all-examples.patch >@@ -0,0 +1,33 @@ >+From 15aef6e666ee2eb0befa153d277d47754f3656e4 Mon Sep 17 00:00:00 2001 >+From: Thomas Monjalon >+Date: Thu, 17 Jul 2014 10:30:52 +0200 >+Subject: [PATCH] examples/pipeline: build with all examples >+ >+Upstream-Status: Backport >+Imported patch from: http://dpdk.org/browse/dpdk/log/ >+ >+When adding this packet framework sample (commit 77a3346), >+it has been forgotten to add it into the global makefile for >+"make examples". >+ >+Signed-off-by: Thomas Monjalon >+(cherry picked from commit a6664a09a7caa5e63f9ae625cf1946b0eef7794e) >+Signed-off-by: Sreeju Selvaraj >+--- >+ examples/Makefile | 1 + >+ 1 file changed, 1 insertion(+) >+ >+diff --git a/examples/Makefile b/examples/Makefile >+index 885c938..1788d6e 100644 >+--- a/examples/Makefile > b/examples/Makefile >+@@ -43,6 +43,7 @@ DIRS-$(CONFIG_EXAMPLE_DPDK_QAT) += dpdk_qat >+ endif >+ DIRS-y += exception_path >+ DIRS-y += helloworld >++DIRS-y += ip_pipeline >+ DIRS-y += ip_reassembly >+ DIRS-$(CONFIG_RTE_MBUF_SCATTER_GATHER) += ip_fr
Re: [meta-intel] [PATCH 2/4 dizzy] meta-isg: Add include file for DPDK
>-Original Message-
>From: Pattu, VenkatasubramanianX
>Sent: Friday, May 8, 2015 12:07 PM
>To: meta-intel@yoctoproject.org
>Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX
>Subject: [PATCH 2/4 dizzy] meta-isg: Add include file for DPDK
>
>Added include file dpdk.inc to share common functionality based on
>dpdk_1.6.0r2
>
>Added a new variable EXAMPLE_BUILD_DIR. This points to apps build
>directory which is different in dpdk v1.6.0r2 and v1.7.0.
>Users of dpdk.inc have to define EXAMPLE_BUILD_DIR for the
>installation of example apps.
>
>This recipe is cherry-picked from branch dizzy and the commit ID:
>1c825a06095178c0c51f28d5867549feac8a47f4:meta-intel/common: Add include
>file for DPDK
>
>Signed-off-by: venkatasubramanian pattu
>
Acked-by: Ong Boon Leong
>---
> meta-isg/common/recipes-extended/dpdk/dpdk.inc | 138
>+
> 1 file changed, 138 insertions(+)
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk.inc
>
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk.inc b/meta-
>isg/common/recipes-extended/dpdk/dpdk.inc
>new file mode 100644
>index 000..5e7d52b
>--- /dev/null
>+++ b/meta-isg/common/recipes-extended/dpdk/dpdk.inc
>@@ -0,0 +1,138 @@
>+DESCRIPTION = "Intel(r) Data Plane Development Kit"
>+HOMEPAGE = "http://dpdk.org";
>+LICENSE = "BSD & LGPLv2 & GPLv2"
>+LIC_FILES_CHKSUM =
>"file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe"
>+
>+RDEPENDS_${PN} += "python-subprocess"
>+
>+inherit module
>+
>+export MODULE_DIR="/lib/modules/${KERNEL_VERSION}/kernel/drivers/net"
>+export RTE_SDK = "${S}"
>+export RTE_TARGET="${TARGET_ARCH}-ivshmem-${TARGET_OS}app-gcc"
>+export ICP_ROOT = "${PKG_CONFIG_SYSROOT_DIR}/usr/include"
>+export ICP_LIB_ROOT= "${PKG_CONFIG_SYSROOT_DIR}/usr/lib"
>+export RTE_KERNELDIR = "${STAGING_KERNEL_DIR}"
>+export INSTALL_PATH = "${prefix}/dpdk"
>+
>+
>+do_configure () {
>+
>
>#
>+ ### default value for prefix is "usr", unsetting it, so it
>+ ### will not be concatenated in ${RTE_TARGET}/Makefile
>+ ### which will cause compilation failure
>+
>
>#
>+ unset prefix
>+
>+ make O=$RTE_TARGET T=$RTE_TARGET config
>+
>+}
>+
>+
>+do_compile () {
>+ unset LDFLAGS TARGET_LDFLAGS BUILD_LDFLAGS
>+
>+ cd ${S}/${RTE_TARGET}
>+ oe_runmake EXTRA_LDFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
>+ EXTRA_CFLAGS=" --sysroot=${STAGING_DIR_HOST}" \
>+ CROSS="${TARGET_PREFIX}" \
>+ prefix="" LDFLAGS="" WERROR_FLAGS="-w" V=1
>+
>+}
>+
>+
>+do_install () {
>+
>+ install -m 0755 -d ${D}/${INSTALL_PATH} \
>+ ${D}/${INSTALL_PATH}/doc \
>+ ${D}/${INSTALL_PATH}/tools \
>+ ${D}/${INSTALL_PATH}/${RTE_TARGET} \
>+ ${D}/${INSTALL_PATH}/${RTE_TARGET}/app \
>+ ${D}${includedir} \
>+ ${D}${includedir}/arch \
>+ ${D}${includedir}/exec-env \
>+ ${D}${libdir} \
>+ ${D}${MODULE_DIR}
>+
>+ install -m 0755 ${S}/${RTE_TARGET}/kmod/igb_uio.ko
> ${D}${MODULE_DIR}/
>+ install -m 0755 ${S}/${RTE_TARGET}/kmod/rte_kni.ko
> ${D}${MODULE_DIR}/
>+
>+ install -m 640 ${S}/${RTE_TARGET}/lib/*.a ${D}${libdir}
>+
>+ install -m 640 ${S}/${RTE_TARGET}/.config
> ${D}/${INSTALL_PATH}/${RTE_TARGET}/
>+ install -m 640 ${S}/${RTE_TARGET}/include/*.h
> ${D}${includedir}/
>+ install -m 640 ${S}/${RTE_TARGET}/include/arch/*
> ${D}${includedir}/arch/
>+ install -m 640 ${S}/${RTE_TARGET}/include/exec-env/*
> ${D}${includedir}/exec-env/
>+ install -m 0755 ${S}/tools/*.py
> ${D}/${INSTALL_PATH}/tools/
>+
>+
>+ #Install test applications
>+ install -m 0755 ${S}/${RTE_TARGET}/app/test
> ${D}/${INSTALL_PATH}/${RTE_TARGET}/app
>+ install -m 0755 ${S}/${RTE_TARGET}/app/testpmd
> ${D}/${INSTALL_PATH}/${RTE_TARGET}/app
>+ install -m 0755 ${S}/${RTE_TARGET}/app/dump_cfg
> ${D}/${INSTALL_PATH}/${RTE_TARGET}/app
>+ install -m 0755 ${S}/${RTE_TARGET}/app/cmdline_test
> ${D}/${INSTALL_PATH}/${RTE_TARGET}/app
>+
>
Re: [meta-intel] [PATCH 3/4 dizzy] meta-isg: Intel DPDK v1.6 recipe under recipes-extended
>-Original Message-
>From: Pattu, VenkatasubramanianX
>Sent: Friday, May 8, 2015 12:09 PM
>To: meta-intel@yoctoproject.org
>Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX
>Subject: [PATCH 3/4 dizzy] meta-isg: Intel DPDK v1.6 recipe under recipes-
>extended
>
>This is an initial version of Intel Data Plane Development Kits
>(DPDK) recipe support. This recipe is targeting on Intel DPDK
>v1.6.0r2.
>
>Intel DPDK is needed for several IoTG maintained BSPs such as Crystal Forest &
>Highland Forest, Mohon Peak.
>Therefore, we place DPDK recipe under meta-isg/common/recipes-extended
>folder.
>
>This recipe is cherry-picked from branch dizzy and the commit ID:
>c249763d3cb92bd06742b7986f08cf844ddb1d51:meta-intel/common: Initial Intel
>DPDK recipe under recipes-extended
>
>This commit is removed in latest dizzy (1.7) due to build failure.
>DPDK v1.7 & v1.6 are validated on Linux kernel v3.10 and not supported on Linux
>kernel v3.17.
>Therefore, this recipe is intended to be supported only on Linux kernel v3.10
>for all
>CID related platforms like Crystal Forest and Highland Forest.
>
>Signed-off-by: venkatasubramanian pattu
>
Acked-by: Ong Boon Leong
>---
> ...ix-build-switches-to-enable-cmdline-tests.patch | 52 ++
> ...dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch | 34 ++
> ...k-1.6.0r2-examples-qos_sched-fix-makefile.patch | 34 ++
> .../common/recipes-extended/dpdk/dpdk_1.6.0r2.bb | 44 ++
> 4 files changed, 164 insertions(+)
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-
>1.6.0r2-app-test-fix-build-switches-to-enable-cmdline-tests.patch
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-
>1.6.0r2-eal-fix-option-base-virtaddr.patch
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-
>1.6.0r2-examples-qos_sched-fix-makefile.patch
> create mode 100644 meta-isg/common/recipes-extended/dpdk/dpdk_1.6.0r2.bb
>
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-app-test-
>fix-build-switches-to-enable-cmdline-tests.patch b/meta-isg/common/recipes-
>extended/dpdk/dpdk/dpdk-1.6.0r2-app-test-fix-build-switches-to-enable-cmdline-
>tests.patch
>new file mode 100644
>index 000..8ca6bfe
>--- /dev/null
>+++ b/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-app-test-fix-
>build-switches-to-enable-cmdline-tests.patch
>@@ -0,0 +1,52 @@
>+From cf953d2bfa7df9aa67459b333db4d4d8a9e72fd6 Mon Sep 17 00:00:00 2001
>+From: Thomas Monjalon
>+Date: Fri, 27 Jun 2014 11:21:11 +0200
>+Subject: [PATCH] app/test: fix build switches to enable cmdline tests
>+
>+Upstream-Status: backport
>+Imported patch from: http://dpdk.org/browse/dpdk/log/
>+
>+There were 2 typos since these commits (in 1.6.0 releases):
>+ 21a7f4e264 fix build without librte_cmdline
>+ cac6d08c8b replace --use-device option by --pci-whitelist and --vdev
>+In makefiles, the build options are prefixed with CONFIG_RTE_
>+but in .c file, it is only RTE_.
>+
>+These typos were disabling cmdline unit tests and test of "--vdev eth_ring"
>option.
>+
>+Signed-off-by: Thomas Monjalon
>+Acked-by: Pablo de Lara
>+Signed-off-by: Chan Wei Sern
>+---
>+ app/test/test_cmdline.c | 2 +-
>+ app/test/test_eal_flags.c | 2 +-
>+ 2 files changed, 2 insertions(+), 2 deletions(-)
>+
>+diff --git a/app/test/test_cmdline.c b/app/test/test_cmdline.c
>+index 77475c4..10a3f77 100644
>+--- a/app/test/test_cmdline.c
> b/app/test/test_cmdline.c
>+@@ -39,7 +39,7 @@
>+ int
>+ test_cmdline(void)
>+ {
>+-#ifdef CONFIG_RTE_LIBRTE_CMDLINE
>++#ifdef RTE_LIBRTE_CMDLINE
>+ printf("Testind parsing ethernet addresses...\n");
>+ if (test_parse_etheraddr_valid() < 0)
>+ return -1;
>+diff --git a/app/test/test_eal_flags.c b/app/test/test_eal_flags.c
>+index a862654..1b80b80 100644
>+--- a/app/test/test_eal_flags.c
> b/app/test/test_eal_flags.c
>+@@ -317,7 +317,7 @@ test_whitelist_flag(void)
>+ const char *wlval3[] = {prgname, prefix, mp_flag, "-n", "1", "-c", "1",
>+ pci_whitelist, "09:0B.3,type=test",
>+ pci_whitelist, "08:00.1,type=normal",
>+-#ifdef CONFIG_RTE_LIBRTE_PMD_RING
>++#ifdef RTE_LIBRTE_PMD_RING
>+ vdev, "eth_ring,arg=test",
>+ #endif
>+ };
>+--
>+1.9.1
>diff --git a/meta-isg/common/recipes-extended/dpdk/dpdk/dpdk-1.6.0r2-eal-fix-
>option-base-virtaddr.patch b/meta-isg/common/recipes-
>extended/dpdk/dpdk/dpdk-1.6.0r2-eal-fix-option-base-virtaddr.patch
>new file mode 100644
>index 000..8204e5a
>-
Re: [meta-intel] [PATCH 1/4 dizzy] meta-isg: Making meta-isg as a layer
>-Original Message-
>From: Pattu, VenkatasubramanianX
>Sent: Friday, May 8, 2015 12:05 PM
>To: meta-intel@yoctoproject.org
>Cc: Ong, Boon Leong; Pattu, VenkatasubramanianX
>Subject: [PATCH 1/4 dizzy] meta-isg: Making meta-isg as a layer
>
>This layer provides additional common recipes to be used by all IOTG maintained
>platforms.
>
>Signed-off-by: venkatasubramanian pattu
>
Acked-by: Ong Boon Leong
>---
> meta-isg/conf/layer.conf | 12
> 1 file changed, 12 insertions(+)
> create mode 100644 meta-isg/conf/layer.conf
>
>diff --git a/meta-isg/conf/layer.conf b/meta-isg/conf/layer.conf
>new file mode 100644
>index 000..48ad0c3
>--- /dev/null
>+++ b/meta-isg/conf/layer.conf
>@@ -0,0 +1,12 @@
>+# We have a conf and classes directory, add to BBPATH
>+BBPATH .= ":${LAYERDIR}"
>+
>+# We have recipes-* directories, add to BBFILES
>+BBFILES += "${LAYERDIR}/common/recipes-*/*/*.bb \
>+${LAYERDIR}/common/recipes-*/*/*.bbappend"
>+
>+BBFILE_COLLECTIONS += "isg"
>+BBFILE_PATTERN_isg := "^${LAYERDIR}/common/"
>+BBFILE_PRIORITY_isg = "5"
>+
>+LAYERDEPENDS_isg = "intel"
>--
>1.9.1
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/4 dizzy] meta-isg: Intel DPDK Implementation
>Subject: [PATCH 0/4 dizzy] meta-isg: Intel DPDK Implementation > >The Data Plane Development Kit (DPDK) is a set of data plane libraries and >network interface controller drivers for fast packet processing. >DPDK provides a programming framework that scales from Intel Atom processors >to Intel Xeon processors and enables faster development of high speed data >packet networking applications. > >With Intel processors, It is possible to transition from using discrete >architectures >per major workload (application, control, packet, and signal processing) to a >single >architecture that consolidates the workloads into a more scalable and >simplified >solution. >As a result, developers may be able to eliminate special-purpose hardware such >as >network processors (NPUs), co-processors, application specific integrated >circuits >(ASICs), and field-programmable gate arrays (FPGAs). > >This recipe is cherry-picked from branch dizzy and the commit ID: >1c825a06095178c0c51f28d5867549feac8a47f4:meta-intel/common: Add include >file for DPDK >c249763d3cb92bd06742b7986f08cf844ddb1d51:meta-intel/common: Initial Intel >DPDK recipe under recipes-extended >a14718dfaee57827a0666b858cf192dc1cb00db5:meta-intel/common: Upgrade >DPDK to v1.7.0. > >These commits are removed in latest dizzy (1.7) due to build failure. >DPDK v1.7 & v1.6 are validated on Linux kernel v3.10 and not supported on Linux >kernel v3.17. >Therefore, this recipe is intended to be supported only on Linux kernel v3.10 >for all >CID related platforms like Crystal Forest and Highland Forest. > Saul & Darren, The patch series is a continued work from last what were discussed to bring dpdk into meta-isg/common so that it can be used for all IOTG supported platforms like crystal forest and mohonpeak. All of these patches are in the past accepted into meta-isg/common/recipes-extended Another patchseries will be sent to remove dpdk from meta-romley/recipes-extended which currently has "COMPATIBLE_MACHINE = "romley|romley-ivb". Venkat has showed that the dpdk recipe build fine and the sanity test on both highland forest & crystal forest platforms are passing fine. So, I recommend that these recipes to be considered for merge into meta-intel dizzy branch as intended above. So, I will give my ack-ed in all of these patch series accordingly. Do tell us if you think there should be revision needed. Many thanks. -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
