Hi all,
I am trying to use mender on an i.MX8M system-on-module to handle over-the-air
updates. I ran into issues with the meta-fsl-bsp-release which uses the
imx-uboot that is too old.
Is there work being done on upstreaming the i.MX8M bsp from
meta-fsl-bsp-release into the meta-freescale l
Hello,
What is the significance of the vendor being set to fslc in the
toolchain? Is it simply a label, or does it have some compatibility
differences (compared with -unknown-).
The reason I ask is because I was wondering if there would be any issues
using off the shelf Rust or Go compilers and s
* See discussion at [1]
* Tested for linux-fslc
[1]
http://lists.openembedded.org/pipermail/openembedded-core/2018-April/149912.html
Signed-off-by: Andreas Müller
---
...check-lxdiaglog.sh-Allow-specification-of.patch | 63 ++
recipes-kernel/linux/linux-imx.inc
fixes
| ERROR: Feature 'xcomposite-glx' was enabled, but the pre-condition
'features.wayland-client && features.opengl && !features.opengles2 &&
features.xlib && libs.xcomposite && libs.glx' failed.
|
| ERROR: Feature 'xcomposite-glx' was enabled, but the pre-condition
'features.wayland-server &
* they were not updated for long time
* they mach neither name nor version of the recipes in meta-browser
* they cause parse-errors
Signed-off-by: Andreas Müller
---
.../chromium/chromium-wayland_48.0.2548.0.bbappend | 29 --
.../chromium/chromium_52.0.2743.76.bbappend
* it does not apply with meta-qt5 master
* it changes (breaks currently) qtwebkit for all boards when adding
meta-freescale to layers
Signed-off-by: Andreas Müller
---
...h-the-uniform-precision-qualifiers-in-ver.patch | 42 --
.../qt5-layer/recipes-qt/qt5/qtwebkit_%.bbappe
