On 2018年10月16日 22:25, Anuj Mittal wrote:
Can this be done in your local configuration? I don't think it's
appropriate to say this unless we know it really works.
OK
//Hongxu
Thanks,
Anuj
On 10/14/18 11:32 PM, Hongxu Jia wrote:
It probably wouldn't even work since default value is core2duo
for qemu in tune-core2.inc which doesn't support SSE 4.2 (which is a
requirement for dpdk).
So use native value for qemux86-64 and qemux86 although these two
arches does not support SSE 4.2, but it still makes sense to do the
build testing on Yocto supported machine.
Signed-off-by: Hongxu Jia <hongxu....@windriver.com>
---
recipes-extended/dpdk/dpdk.inc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
index 194986b..5251adc 100644
--- a/recipes-extended/dpdk/dpdk.inc
+++ b/recipes-extended/dpdk/dpdk.inc
@@ -15,6 +15,8 @@ SRC_URI = "git://dpdk.org/dpdk${STABLE};branch=${BRANCH} \
COMPATIBLE_MACHINE = "null"
COMPATIBLE_HOST_libc-musl_class-target = "null"
COMPATIBLE_HOST_linux-gnux32 = "null"
+COMPATIBLE_MACHINE_qemux86-64 = "qemux86-64"
+COMPATIBLE_MACHINE_qemux86 = "qemux86"
# dpdk example apps dpdk_qat and vhost have dependancy on fuse and qat.
# fuse is in meta-filesystems and qat is not yet upstreamed.
@@ -64,6 +66,9 @@ DPDK_RTE_TARGET_x86 = "i686-native-linuxapp-gcc"
DPDK_RTE_TARGET_aarch64 = "arm64-${DPDK_TARGET_MACH}-linuxapp-gcc"
export RTE_TARGET = "${DPDK_RTE_TARGET}"
+DPDK_TARGET_MACHINE_qemux86 = "native"
+DPDK_TARGET_MACHINE_qemux86-64 = "native"
+
# The list of intel Comms platforms and their target machine
# process mapping. The supported target machine is listed under
# dpdk/mk/machine
--
_______________________________________________
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
