The value(--disable-static) of EXTRA_OECONF set by poky is not supported by openssl-qoriq-1.0.1i. remove it to fix the following build error: | Usage: Configure [no-<cipher> ...] [enable-<cipher> ...]

Hi Nora, The PCA9672 is a GPIO expander chip via I2C bus, and no any relative with P2041 GPIO IP block. P2041 dts file has included the GPIO node in both upstream kernel and SDK2.0 which will be relea

Hi Hongxu, The e500v2 targets don't support usdpaa. Can you submit a patch to add COMPATIBLE_MACHINE to limit the supported machines. Best Regards, Zhenhua

https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/tree/arch/powerpc/boot/dts/fsl/p2041si-post.dtsi#n395 Best Regards, Zhenhua

I just got the comments from SDK developer, there is no such node in upstream, he thinks it should be a I2C node, not a GPIO node. Sorry for the confusion. Best Regards, Zhenhua

Hi Bob, Please see my inline comments. Best Regards, Zhenhua

Bob, The fixes in meta-fsl-ppc will be ported to meta-freescale, 4 patches ported from meta-fsl-ppc were submitted for meta-freescale layer. http://patchwork.openembedded.org/project/meta-freescale/li

Hi Hongxu,

After investigation, this is an issue in oe-core. The reason is that the generated qemu binary name of ppc64 targets is qemu-ppc instead of qemu-ppc64, the gobject-introspection uses qemu-ppc64, so th

The following binaries are generated by qemu-native, qemu-ppc64 is not there, but qemu-ppc64 is used by g-ir-scanner-qemuwrapper script of gobject-introspection. tmp/sysroots/x86_64-linux/usr/bin/qemu

The meta-freescale is a layer instead of a repo project, you can use meta-freescale layer or SDK ISOs(http://www.nxp.com/products/software-and-tools/run-time-software/linux-sdk/linux-sdk-for-qoriq-pro

Hello Koveshnikov, I didn't understand what's the problem of usdpaa-apps clean, the usdpaa-apps supports "make ARCH=xxx clean", the clean step will be skipped if CLEANBROKEN is set to "1". Best Regard

The python-pygobject-3.18.2 depends on gobject-introspection which uses qemu-ppc64 native utility, currently qemu-native doesn't support qemu-ppc64, so use python-pygobject-2.28.3 for ppc64e5500 and p

The python-pygobject-3.18.2 depends on gobject-introspection which uses qemu-ppc64 native utility, currently qemu-native doesn't support qemu-ppc64, so use python-pygobject-2.28.3 for ppc64e5500 and p

Please ignore this patch.

Signed-off-by: Zhenhua Luo <zhenhua.luo@...> --- README | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README b/README index 33d4c08..23eebb1 100644 --- a/README +++ b/README @@ -10,6 +1

Signed-off-by: Zhenhua Luo <zhenhua.luo@...> --- README | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/README b/README index 10158ef..8b43567 100644 --- a/README +

There is no appropriate fix for oe-core now, the image build of ppc64 target is blocked by the issue, so adding the information in README to provide a workaround. Best Regards, Zhenhua

Hello all, The following update is merged in krogoth branch of meta-fsl-ppc, thanks. commit ec1f751131454a9279792cf9a0279f1f40055a2b Author: Zhenhua Luo <zhenhua.luo@...> Date: Fri Apr 15 19:10:11

Hello all, The following update is merged in master branch of meta-fsl-ppc, thanks. commit ec1f751131454a9279792cf9a0279f1f40055a2b Author: Zhenhua Luo <zhenhua.luo@...> Date: Fri Apr 15 19:10:11