These two patches can't be applied to the new version DPDK, so move
them to the version specific bb.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Adjust the LICENSE according to the license files.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Add maintainer info in the README and also drop a stale maintainers.inc
file.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
This has been created as a separate layer for a long time, the
reference of meta-intel in the README seems a bit confusion.
So drop all of them.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Instead of sticking to one specific version on the dependency layers
and having to update it for each release version, just claim that
this layer is compatible with the latest version of the dependency
layers.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Since `9ec5a8a layer.conf: Drop sumo from LAYERSERIES_CORENAMES' and
`9867924 layer.conf: Add thud to LAYERSERIES_CORENAMES' applied in oe-core,
add thud to LAYERSERIES_COMPAT
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
This fixes dpdk build when using an external toolchain by adding
the HOST_CC_ARCH & TOOLCHAIN_OPTIONS to EXTRA_CFLAGS the way
standard Yocto does it to gather all the necessary flags for
compilation.
The TOOLCHAIN_OPTIONS variable also provides the sysroot flag, so
no need to explicitly provide the sysroot.
This commit also fixes the build when using a multilib toolchain
by adding the LDEMULATION flags to the LDFLAGS via TUNE_LDARGS
which are required while linking with a multilib toolchain.
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
Currently the examples&test applications would be installed into
directories like:
/usr/share/examples
/usr/share/test
These directories just seem too general, so change them to:
/usr/share/dpdk/examples
/usr/share/dpdk/test
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
original URI have been deleted(don't know why). Here I just
use yocto source mirror to fix fetch error. But it should be
replace by offcial libibverbs here: "https://github.com/linux-rdma/
rdma-core/tree/master/libibverbs".
Since I don't have condition to test dpdk function, I can only go far
to build success, and seems there is big change between source on
yocto mirror and the offcial libibverbs, so for now, just use the mirror.
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
This patch upgrades DPDK to the latest release of v18.05.
Signed-off-by: Tan, Raymond <raymond.tan@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
The TARGET_ARCH may be different for different x86 machines,
for example i586(qemux86) and i686(genericx86). So choose the "x86"
override to set the correct RTE_TARGET for these machines.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Fix the following parse error when building with unsupported arch, such
as arm:
bb.data_smart.ExpansionError: Failure expanding variable RTE_TARGET, expression was ${RTE_TARGET} which triggered exception Exception: variable RTE_TARGET references itself!
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Otherwise it always return "default" no matter what we set in
"DPDK_TARGET_MACHINE".
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
After changing to the git repo, these checksums become useless.
Just drop them.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
This cleans up the versioned recipes and moves the common
fragments to the include so to make the maintenance easy.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
This is more convenient for development.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Using the following commands to refresh the patches in order to
suppress the fuzz warnings.
devtool modify dpdk
devtool finish --force-patch-refresh dpdk meta-dpdk-dir
No code change.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
The latest Yocto has changed the LAYERSERIES_CORENAMES to "sumo".
So add it to the compatible list.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
This is the latest stable version.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
The license files may be different between different versions. So move
them into the specific bb files.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Otherwise we get this:
| dpdk-18.02/lib/librte_eal/linuxapp/eal/eal_memory.c:27:10: fatal error: numa.h: No such file or directory
| #include <numa.h>
| ^~~~~~~~
| compilation terminated.
Use PACKAGECONFIG to optionally enable the numa option.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
This upgrades the dpdk package to 18.02 which is
the latest release and drops a patch that has
already been merged upstream in this package.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Install and ship test programs into dpdk-test.
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
We have multiple recipes in different layers providing the same libibverbs
library, so we need to use virtual/libibverbs to avoid potential errors.
Make dpdk depend on virtual/libibverbs instead of hardcoding
dpdk-dev-libibverbs.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
dpdk-dev-libibverbs is not the only recipe that provides libibverbs.
In meta-cloud-services, we have a recipe called libibverbs. As both
recipes provide the same library, we need to avoid building both at
the same time at one build.
Use 'virtual/libibverbs' to avoid such problem.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Fix to correctly set SRC_URI and S to avoid do_fetch failure in case of multilib.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
