From: Chunrong Guo <chunrong.guo@...> Signed-off-by: Chunrong Guo <chunrong.guo@...> --- conf/machine/ls1046ardb.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git

From: Chunrong Guo <chunrong.guo@...> Signed-off-by: Chunrong Guo <chunrong.guo@...> --- conf/machine/ls1043ardb.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

From: Chunrong Guo <chunrong.guo@...> Signed-off-by: Chunrong Guo <chunrong.guo@...> --- conf/machine/ls1028ardb.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

From: Chunrong Guo <chunrong.guo@...> Signed-off-by: Chunrong Guo <chunrong.guo@...> --- conf/machine/ls1012ardb.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

I wrote... OK, so I now have mesa building without any issues. It now stops in the do_configure phase of chromium-ozone-wayland with the following output: | Command: python

Andrey wrote... I am building from master and that pull request appears to be included but it looks to be specific for the i.MX8 whereas we are building for the i.MX6. I’ll try hacking the recipe

This was the issue #115 (https://github.com/Freescale/meta-freescale/issues/115), which has been resolved by PR #151 (https://github.com/Freescale/meta-freescale/pull/151) for master branch. Are

I wrote... I am trying to get run some comparative tests by building the chromium-ozone-wayland recipe from meta-browser but the build is failing with the following error: meson.build:427:4: ERROR:

Otavio wrote... I have been looking at the contents of your meta-browser layer and also searching around on the internet and have found a number of references to Ozone and DRM/GBM but haven’t been

Hi, I'm currently trying to build gstreamer1.0 with Yocto Thud. My host machine is a Debian 9 (stretch) Linux. It always succeeded with previous version of Yocto rocko and sumo. But there

Otavio wrote... So, switching from the built-in kernel driver for the GPU to the external one hasn’t done anything to improve the frame rate. Not that I really expected it to do so. My guess at

Otavio wrote.. Cog (v0.4.0) and WPE WebKit (v2.26.1) from meta-webkit. It is building with the following defined: PREFERRED_PROVIDER_virtual/wpebackend =

Good. Using what? WPE, Chromium, WebEngine? -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854

Otavio wrote… OK, so I think I will disable the built in version and use the external kernel module. I am building for a Boundary Devices Nitrogen 6 Lite board (i.MX6 Solo) using Yocto and the

Hello Andy, We use the kernel module as a way to easy the upgrade of GPU driver releases. If using the built-in the Linux kernel version needs to match the GPU driver release while if using the

Hello, What is the difference between the “Vivante GCCore” driver (CONFIG_DRM_VIVANTE) available in the 4.14.x kernel and the galcore.ko file that is being built and to the kernel modules

Carlos wrote... It is the same. I have been testing with http://fabricjs.com//animation and https://themaninblue.com/experiment/AnimationBenchmark/canvas/ and in all circumstances I see 10-12fps. The

How the performance compares if you disable accelerated-2d-canvas? It gets worse or its the same? Usually on the web application side there are different things that can be optimized to make it

Hello, Broadening this out to the Freescale and Yocto mailing lists to see if any one has any answers… We are using Cog and WPE Webkit on an i.MX6 Solo based board with a user interface that is