freescale / meta-freescale Goto Github PK
View Code? Open in Web Editor NEWLayer containing NXP hardware support metadata
License: Other
meta-freescale's People
Contributors
Stargazers
Watchers
Forkers
luozhenhua vankoven zongchunyu schnitzeltony redbrain17 vctlabs accordionman drewmoseley johncheng110 digicouk qiupq dl9pf cierebaj eiger824 adowdy wrjiafang danrinkes fedenunez sanjeevs1 gpenghe oknow23 boundarydevices thochstein psivasubramanian yoedistro dkhughes kejingjing justgaoyuan petegriffin mentorembedded asmaaswt andrey-konovalov sbourdelin ptsneves agners angolini ac-frg mariangeo fbertux daiyinger matlanq alexgg initerworker vdehors maxkrummenacher texierp jorisoffouga joshuawatt carolzhuyuqing power535 kynetics pheel79 tstockk ukaiser dv1 bmghirbi hmsfeng albanbedel yohaglooko wukh0312 zandrey jasonhuang-msi cpboyd amotus toolmmy panfir mike-scott zeragmbh liuming50 mhaseeb31 johareh zpfvo sigma-random ricardosalveti rehsack dkomljenovic2502 makohoek andred mbessler nicephil shlokk96 twoerner fschrempf guochunrong willee2015 septum-sacrament-consult-wow roumy mattmart3 schiffermtq zeeblex kergoth leimaohui junzhuimx kevswims tibalt agre hexagon-geo-surv steelpalm selesnie renn22meta-freescale's Issues
gstreamer-plugins-good_1.14.imx compilation error
gstreamer-plugins-good v4l2 plugin compilation error for iMX6ULL:
| ../../../git/sys/v4l2/gstv4l2videodec.c: In function 'gst_v4l2_video_dec_loop':
| ../../../git/sys/v4l2/gstv4l2videodec.c:645:30: error: 'DRM_FORMAT_MOD_AMPHION_TILED' undeclared (first use in this function); did you mean 'DRM_FORMAT_MOD_VIVANTE_TILED'?
| guint64 drm_modifier = DRM_FORMAT_MOD_AMPHION_TILED;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
| DRM_FORMAT_MOD_VIVANTE_TILED
| Makefile:928: recipe for target 'libgstvideo4linux2_la-gstv4l2videodec.lo' failed
| make[3]: *** [libgstvideo4linux2_la-gstv4l2videodec.lo] Error 1
| Makefile:898: recipe for target 'v4l2' failed
| make[2]: *** [v4l2] Error 2
Integrate i.MX release L5.4.3-1.0.0
kernel-module-imx-gpu-viv module warning
I got warnings when set two variable keys under branch master and rocko:
MACHINE_HAS_VIVANTE_KERNEL_DRIVER_SUPPORT = "1"
MACHINE_USES_VIVANTE_KERNEL_DRIVER_MODULE = "0"
I found the question of this and maybe resolved it:
--- a/classes/fsl-vivante-kernel-driver-handler.bbclass
+++ b/classes/fsl-vivante-kernel-driver-handler.bbclass
@@ -41,9 +41,9 @@ python fsl_vivante_kernel_driver_handler () {
return
if use_vivante_kernel_driver_module != "1":
- e.data.appendVar('RPROVIDES_kernel-base', ' kernel-module-imx-gpu-viv')
- e.data.appendVar('RREPLACES_kernel-base', ' kernel-module-imx-gpu-viv')
- e.data.appendVar('RCONFLICTS_kernel-base', ' kernel-module-imx-gpu-viv')
+ e.data.appendVar('RDEPENDS_${KERNEL_PACKAGE_NAME}-base', ' kernel-module-imx-gpu-viv')
+ e.data.appendVar('RDEPENDS_${KERNEL_PACKAGE_NAME}-base', ' kernel-module-imx-gpu-viv')
+ e.data.appendVar('RCONFLICTS_${KERNEL_PACKAGE_NAME}-base', ' kernel-module-imx-gpu-viv')
}
Am I right?
Applying Qt Patch error
ISSUES
NOTE: Applying patch '0015-Add-eglfs-to-IMX-GPU.patch' (../sources/meta-freescale/dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase/0015-Add-eglfs-to-IMX-GPU.patch)
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0015-Add-eglfs-to-IMX-GPU.patch
patching file mkspecs/linux-oe-g++/qmake.conf
Hunk #1 succeeded at 34 with fuzz 1 (offset -3 lines).
Now at patch 0015-Add-eglfs-to-IMX-GPU.patch
NOTE: Applying patch '0016-Configure-eglfs-with-egl-pkg-config.patch' (../sources/meta-freescale/dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase/0016-Configure-eglfs-with-egl-pkg-config.patch)
WARNING:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0016-Configure-eglfs-with-egl-pkg-config.patch
patching file src/plugins/platforms/eglfs/eglfs-plugin.pro
Hunk #1 succeeded at 7 with fuzz 2 (offset 5 lines).
Now at patch 0016-Configure-eglfs-with-egl-pkg-config.patch
DEBUG: Python function patch_do_patch finished
DEBUG: Python function do_patch finished
ENVIRONMENT
- Ubuntu 18.04
- meta-freescale (thud)
- meta-freescale-distro (thud)
- meta-qt5 (thud)
- poky (thud)
- meta-openembedded (thud)
STEPS TO REPRODUCE
DISTRO : fslc-wayland
MACHINE: imx8mqevk
bitbake qtbase
u-boot-fslc fails for imx5 machines
building on master:
Build Configuration:
BB_VERSION = "1.44.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "opensuseleap-15.1"
TARGET_SYS = "arm-oe-linux-gnueabi"
MACHINE = "imx53qsb"
DISTRO = "nodistro"
DISTRO_VERSION = "nodistro.0"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta-freescale = "master:9227f4c9e6d77d3fa15f67d178ba9da02c5550fe"
meta = "master:44a4ac2294da0f53cbbfabc7ece836fe97f4d3f7"
I get:
| make[1]: *** No rule to make target '/z/build-master/meta-freescale/build/tmp-glibc/work/imx53qsb-oe-linux-gnueabi/u-boot-fslc/v2019.07+gitAUTOINC+ca0ab15271-r0/git/arch//cpu/u-boot.lds', needed by 'u-boot.lds'. Stop.
and also:
| echo >&2 " /z/build-master/meta-freescale/build/tmp-glibc/work/imx53qsb-oe-linux-gnueabi/u-boot-fslc/v2019.07+gitAUTOINC+ca0ab15271-r0/git is not clean, please run 'make mrproper'"; \
$ bitbake virtual/bootloader -e | grep "^B="
B="/z/build-master/meta-freescale/build/tmp-glibc/work/imx53qsb-oe-linux-gnueabi/u-boot-fslc/v2019.07+gitAUTOINC+ca0ab15271-r0/git"
$ bitbake virtual/bootloader -e | grep "^S="
S="/z/build-master/meta-freescale/build/tmp-glibc/work/imx53qsb-oe-linux-gnueabi/u-boot-fslc/v2019.07+gitAUTOINC+ca0ab15271-r0/git"
cairo doesn't compile
cairo doesn't compile on "master". The do_compile task gives an error:
| arm-poky-linux-gnueabi-libtool: link: arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot -D_REENTRANT -I/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/include/pixman-1 -I/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/include/freetype2 -I/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/include/freetype2 -DLINUX -I/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/include/libdrm -I/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/include/libdrm -I/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/include/libpng16 -Wall -Wextra -Wmissing-declarations -Werror-implicit-function-declaration -Wpointer-arith -Wwrite-strings -Wsign-compare -Wpacked -Wswitch-enum -Wmissing-format-attribute -Wvolatile-register-var -Wstrict-aliasing=2 -Winit-self -Wunsafe-loop-optimizations -Wno-missing-field-initializers -Wno-unused-parameter -Wno-attributes -Wno-long-long -Winline -fno-strict-aliasing -fno-common -Wp,-D_FORTIFY_SOURCE=2 -Wno-unused-but-set-variable -D_REENTRANT -I/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/include/glib-2.0 -I/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/lib/glib-2.0/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0=/usr/src/debug/cairo/1.14.12-r0 -fdebug-prefix-map=/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot= -fdebug-prefix-map=/poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot-native= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/cairo-sphinx cairo_sphinx-sphinx.o ../../util/cairo-script/.libs/libcairo-script-interpreter.so ../../boilerplate/.libs/libcairoboilerplate.a /poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/build/src/.libs/libcairo.so ../../src/.libs/libcairo.so -lpthread -lpixman-1 -lfontconfig -lfreetype -lGLESv2 -lEGL -ldl -lpng16 -lxcb-shm -lxcb -lxcb-render -lXrender -lX11 -lXext -lz -lglib-2.0 -lrt -lm
| /poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/8.2.0/ld: /poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/lib/libGAL.so: undefined reference to `log@GLIBC_2.29'
| /poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/8.2.0/ld: /poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/lib/libGAL.so: undefined reference to `pow@GLIBC_2.29'
| /poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/8.2.0/ld: /poky/build-neo-thud/tmp/work/cortexa9t2hf-neon-mx6sx-poky-linux-gnueabi/cairo/1.14.12-r0/recipe-sysroot/usr/lib/libGAL.so: undefined reference to `exp@GLIBC_2.29'
| collect2: error: ld returned 1 exit status
Wrong when populate SDK
I want to setup a standalone compiling environment from yocto project, but meet with the following wrong:
$ DISTRO=fsl-imx-wayland MACHINE=imx8mqevk bitbake core-image-base –c populate_sdk Loading cache: 100% |############################################| Time: 0:00:00
Loaded 3299 entries from dependency cache.
Parsing recipes: 100% |##########################################| Time: 0:00:02
Parsing of 2450 .bb files complete (2448 cached, 2 parsed). 3301 targets, 439 skipped, 9 masked, 0 errors.
ERROR: Nothing PROVIDES '–c'
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Can anyone help me for that?
Thanks in advance.
ddr-phy recipe builds native fiptool during build process
The ddr-phy recipe builds fiptool during its do_install(), and it uses the host's toolchain (not even Yocto's native toolchain). This causes unexpected host dependencies (e.g. fiptool requires openssl but this may not be installed on the host).
bug(dunfell): MACHINEOVERRIDES change breaks qtbase (and probably more)
I think this might be related to 341ba18
Basically, I've noticed that in my configuration, it adds -opengl desktop rather than -opengl egl which throws a configuration error.
[to be closed] Bad performances of QWebEngine
Hi,
I compile QWebEngine with meta-qt5 sumo on top of meta-freescale for the UDOO Neo (CPU i.MX6 SoloX, Vivante GPU) with the Linux kernel 4.1.
The performances are really bad when I display 2 inline SVG. The CPU reaches the maximum temperature and QWebEngine crashes randomly. The CPU usage displayed with top is over 60%.
[16063.864286] System is too hot. GPU3D will work at 16/64 clock.
Here is the code I try to run:
<!DOCTYPE html>
<html>
<head>
<title>Machines</title>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" type="text/css">
<link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Open+Sans+Condensed:300" rel="stylesheet">
<style>
svg.machine {
height: 300px;
max-width: 100%;
shape-rendering: geometricPrecision;
text-rendering: geometricPrecision;
image-rendering: optimizeQuality;
fill-rule: evenodd;
clip-rule: evenodd; }
svg.machine .machine {
display: block; }
svg.machine .machine .label {
fill: #727272;
font-family: 'Open Sans Condensed', sans-serif;
font-weight: 300;
font-size: 75000px;
text-align: center;
text-anchor: middle;
letter-spacing: -1px; }
svg.machine .machine .mask {
fill: white; }
svg.machine .machine .draw {
fill: #727272; }
svg.machine .number polygon {
fill: #00a627;
stroke: #fff;
stroke-width: 4000;
stroke-linejoin: round; }
svg.machine .number text {
fill: white;
font-weight: bold;
font-weight: 700;
font-size: 110000px;
font-family: 'Open Sans', sans-serif;
text-align: center;
text-anchor: start; }
svg.machine.taken > .machine > .draw, svg.machine.taken > .machine > .label, svg.machine.taken > .number polygon {
fill: #CD2628; }
svg.machine.taken > .machine > .mask {
fill: #FAE9E9; }
</style>
</head>
<body>
<div class="row">
<div class="col-sm-6 text-center">
<svg class="machine" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 500000 800000">
<defs><linearGradient id="shadowgrad" x1="0" y1="0" x2="0" y2="1"><stop offset="0" style="stop-opacity:0; stop-color:black"/><stop offset="1" style="stop-opacity:0.35; stop-color:black"/></linearGradient></defs>
<g class="machine">
<text class="label" x="250000" y="780000">Washing machine</text>
<polygon class="shadow" fill="url(#shadowgrad)" points="381195,596338 500001,596338 447930,686527 381095,686794"/>
<polygon class="mask" points="444699,190671 444699,679480 435706,688473 65209,688473 55713,678978 55713,190671 106773,157128 393640,157128"/>
<polygon class="mask" points="444699,190671 444699,679480 435706,688473 65209,688473 55713,678978 55713,190671 106773,157128 393640,157128"/>
<path class="draw" d="M396677 397755c7052,1566 12381,7889 12381,15409l0 92369c0,7511 -5325,13845 -12381,15412 -24072,57251 -80678,97460 -146676,97460 -87839,0 -159055,-71216 -159055,-159055 0,-87839 71216,-159055 159055,-159055 65998,0 122603,40208 146676,97460zm-146676 -59167c44008,0 82515,23546 103622,58723l33090 0c-7247,-15981 -17433,-30956 -30575,-44098 -58617,-58617 -153657,-58617 -212273,0 -58617,58617 -58617,153656 0,212273 58616,58618 153656,58618 212273,0 13142,-13142 23331,-28116 30577,-44099l-33091 0c-21107,35177 -59614,58725 -103623,58725 -66693,0 -120762,-54069 -120762,-120762 0,-66694 54069,-120762 120762,-120762zm90193 178578c-3278,-3008 -5132,-7123 -5132,-11633l0 -29264c-9208,-6274 -15254,-16842 -15254,-28823 0,19249 -15605,34854 -34856,34854 -19253,0 -34858,-15605 -34858,-34854 0,19249 -15603,34854 -34856,34854 -19251,0 -34856,-15605 -34856,-34854 0,19802 -16430,35561 -36197,34826 11988,47327 54860,82346 105911,82346 37398,0 70404,-18795 90098,-47452zm53082 -110823l-42361 0c-3756,0 -6821,3065 -6821,6821l0 92369c0,3753 3066,6823 6821,6823l42361 0c3755,0 6821,-3070 6821,-6823l0 -92369c0,-3756 -3063,-6821 -6821,-6821zm-323031 -219067l359560 0 -37918 -22749 -283725 0 -37917 22749zm228015 28999l79315 0c2935,0 5336,2401 5336,5337l0 15254c0,2936 -2401,5339 -5336,5339l-79315 0 0 -25930zm-88591 0l80713 0 0 25930 -80713 0 0 -25930zm-87191 0l79313 0 0 25930 -79313 0c-2937,0 -5338,-2403 -5338,-5339l0 -15254c0,-2936 2401,-5337 5338,-5337zm313869 50997l-372644 0 0 412986 372644 0 0 -412986zm-372644 -3942l372644 0 0 -68204 -372644 0 0 68204zm388346 416928c2,8666 -7034,15703 -15702,15703l-372644 0c-8669,0 -15703,-7031 -15703,-15703l0 -489057c0,-6175 3565,-11516 8749,-14081l43378 -26026c2522,-1508 5296,-2225 8035,-2221l283725 -49c3407,0 6561,1086 9134,2929l43361 26015c4897,2929 7614,8113 7619,13433l48 489057z"/>
</g><!--/.machine -->
<g class="number">
<polygon points="105670,539360 146770,563080 187850,586810 187850,634250 187850,681700 146770,705420 105670,729140 64590,705420 23500,681700 23500,634250 23500,586810 64590,563080"/>
<g transform="matrix(1.01342,0,0,1,-94145.3,258734)">
<text x="164000" y="415990">1</text>
</g>
</g><!--/.number -->
</svg>
</div>
<div class="col-sm-6 text-center">
<svg class="machine" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 500000 800000">
<defs><linearGradient id="shadowgrad" x1="0" y1="0" x2="0" y2="1"><stop offset="0" style="stop-opacity:0; stop-color:black"/><stop offset="1" style="stop-opacity:0.35; stop-color:black"/></linearGradient></defs>
<g class="machine">
<text class="label" x="250000" y="780000">Dryer</text>
<polygon class="shadow" fill="url(#shadowgrad)" points="381195,596338 500001,596338 447930,686527 381095,686794"/>
<polygon class="mask" points="444699,190671 444699,679480 435706,688473 65209,688473 55713,678978 55713,190671 106773,157128 393640,157128"/>
<polygon class="mask" points="444699,190671 444699,679480 435706,688473 65209,688473 55713,678978 55713,190671 106773,157128 393640,157128"/>
<path class="draw" d="M452049 680258c2,8666 -7034,15703 -15702,15703l-372644 0c-8669,0 -15703,-7031 -15703,-15703l0 -489057c0,-6175 3565,-11516 8749,-14081l43378 -26026c2522,-1508 5296,-2225 8035,-2221l283725 -49c3407,0 6561,1086 9134,2929l43361 26015c4897,2929 7614,8113 7619,13433l48 489057zm-356623 -418726l307356 0c5022,0 9183,4054 9183,9035l0 115489 2261 0c5038,0 9182,4126 9182,9143l0 90262c0,5012 -4143,9143 -9182,9143l-2261 0 0 115490c0,4981 -4162,9035 -9183,9035l-307356 0c-5018,0 -9182,-4051 -9182,-9035l0 -339527c0,-4983 4163,-9035 9182,-9035zm308687 124524l0 -116986 -310017 0 0 342521 310017 0 0 -116987 -18676 0c-5031,0 -9181,-4100 -9181,-9143l0 -90262c0,-5018 4143,-9143 9181,-9143l18676 0zm11263 8079l-31075 0 0 92309 31075 0 0 -92309zm-292898 -177860l79313 0 0 25930 -79313 0c-2937,0 -5338,-2403 -5338,-5339l0 -15254c0,-2936 2401,-5337 5338,-5337zm87191 0l80713 0 0 25930 -80713 0 0 -25930zm88591 0l79315 0c2935,0 5336,2401 5336,5337l0 15254c0,2936 -2401,5339 -5336,5339l-79315 0 0 -25930zm-228015 -28999l359560 0 -37918 -22749 -283725 0 -37917 22749zm366102 7850l-372644 0 0 485132 372644 0 0 -485132z"/>
</g><!--/.machine -->
<g class="number">
<polygon points="105670,539360 146770,563080 187850,586810 187850,634250 187850,681700 146770,705420 105670,729140 64590,705420 23500,681700 23500,634250 23500,586810 64590,563080"/>
<g transform="matrix(1.01342,0,0,1,-94145.3,258734)">
<text x="164000" y="415990">2</text>
</g>
</g><!--/.number -->
</svg>
</div>
</div>
</body>
</html>
I've compared the performances with Chromium Browser on the official UDOObuntu distro. They're OK on it so this is not related to the hardware.
I've done several tests with the imx-gpu-testapps from the meta-freescale-distro layer. They are very demanding for the GPU but the CPU usage is OK.
I've noticed that the galcore module (Vivante driver) uses 4% of the CPU when running the test apps (it's displayed in bold) but uses 0% with QWebEngine. On UDOObuntu, the Vivante driver (CONFIG_MXC_GPU=y) is built in the kernel (v3.14).
The chrome://gpu page shows:
I'm not able to compile Qt5 for UDOObuntu so far.
Any idea how to make it work?
Edit
I found that the @-webkit-keyframes CSS property applied on the SVG was responsible of the issue.
qtbase: update patches
Originally filed as #42, which was closed without comment.
0016-Configure-eglfs-with-egl-pkg-config.patch hasn't been needed since Qt v5.9:
qt/qtbase@e9a7739
In Yocto Warrior and Zeus, this causes a fuzz warning:
WARNING: qtbase-5.13.0+gitAUTOINC+fc9ae22c88-r0 do_patch: Fuzz detected:
Applying patch 0016-Configure-eglfs-with-egl-pkg-config.patch
patching file src/plugins/platforms/eglfs/eglfs-plugin.pro
Hunk #1 succeeded at 7 with fuzz 2 (offset 5 lines).
The context lines in the patches can be updated with devtool:
devtool modify qtbase
devtool finish --force-patch-refresh qtbase <layer_path>
Don't forget to review changes done by devtool!
WARNING: qtbase-5.13.0+gitAUTOINC+fc9ae22c88-r0 do_patch: QA Issue: Patch log indicates that patches do not apply cleanly. [patch-fuzz]
build fails on master after commit split out u-boot tools
imx-boot_0.2.bb do_compile Failure
ISSUE
| NOTE: Copy ddr_firmware: lpddr4_pmu_train_2d_dmem.bin from /home/user1/DATA2/SeiWhale/Yocto/build-seiwhale/tmp/deploy/images/imx8mqevk -> /home/user1/DATA2/SeiWhale/Yocto/build-seiwhale/tmp/work/imx8mqevk-fsl-linux/imx-boot/0.2-r0/git/iMX8M
| cp: cannot stat '/home/user1/DATA2/SeiWhale/Yocto/build-seiwhale/tmp/deploy/images/imx8mqevk/imx-boot-tools/u-boot-nodtb.bin': No such file or directory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/user1/DATA2/SeiWhale/Yocto/build-seiwhale/tmp/work/imx8mqevk-fsl-linux/imx-boot/0.2-r0/temp/log.do_compile.4266)
ERROR: Task (/home/user1/DATA2/SeiWhale/Yocto/sources/meta-freescale/recipes-bsp/imx-mkimage/imx-boot_0.2.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3585 tasks of which 1417 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
=> recipes imx-boot_0.2.bb failed at do_compile because cannot find the file u-boot-nodtb.bin
My Environment
- Ubuntu 18.04
- meta-freescale Branch Thud
- Meta-freescale-distro
- some metadata need for my distro.
Steps to reproduce:
- Select distro fslc-wayland (contains in meta-freescale-distro)
- Select machine imx8mqevk
- bitbake core-image-weston
Got an error “Checking for program pkg-config : not found” during execution “bitbake image_name”
I built the image with gstreamer-imx plugin and bitbake asked me for imx-codec. I found it in meta-freescale layer and added it into my image.
Now my local.conf has the next additional lines:
IMAGE_INSTALL_append = " gstreamer1.0-plugins-imx imx-codec"
ACCEPT_FSL_EULA = "1"
And bblayers.conf:
BBLAYERS = "
${OEROOT}/../meta-gstreamer1.0
${OEROOT}/../meta-nodejs
${OEROOT}/../meta-phytec
${OEROOT}/../meta-qt5
${OEROOT}/../meta-rauc
${OEROOT}/../meta-yogurt
${OEROOT}/../meta-freescale
"
And during the build I have got the next issue (on screenshots)
https://i.imgur.com/2aEUJKq.png
https://i.imgur.com/VQOqOhJ.png
I have checked the version of installed pkg-config and it's env variable:
echo $PKG_CONFIG_PATH
/usr/local/lib/x86_64-linux-gnu/pkgconfig
pkg-config --version
0.29.1
Does anyone know how to avoid this trouble?
I am working with phyboard-nunki (IMX6)
Revert "linux-qoriq recipes: reorder merge_delta_config task"
6e0b6f unfortunately causes a blank build for e.g. ls2088ardb fail as that:
ERROR: linux-qoriq-4.19-r0 do_preconfigure: Execution of '/build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/run.do_preconfigure.13614' failed with exit code 2:
/build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/run.do_preconfigure.13614: 119: /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/run.do_preconfigure.13614: cannot open /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/defconfig: No such file
WARNING: exit code 2 from a shell command.
ERROR: Logfile of failure stored in: /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/log.do_preconfigure.13614
Log data follows:
| DEBUG: Executing shell function do_preconfigure
| /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/run.do_preconfigure.13614: 119: /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/run.do_preconfigure.13614: cannot open /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/defconfig: No such file
| WARNING: exit code 2 from a shell command.
| ERROR: Execution of '/build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/run.do_preconfigure.13614' failed with exit code 2:
| /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/run.do_preconfigure.13614: 119: /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/temp/run.do_preconfigure.13614: cannot open /build/sno/mdr-gt-build/tmp/work/ls2088ardb-poky-linux/linux-qoriq/4.19-r0/defconfig: No such file
| WARNING: exit code 2 from a shell command.
|
ERROR: Task (/build/sno/sources/meta-freescale/recipes-kernel/linux/linux-qoriq_4.19.bb:do_preconfigure) failed with exit code '1'
This is caused by do_preconfigure() from classes/fsl-kernel-localversion.bbclass expects a ${WORKDIR}/defconfig which was earlier created by merge_delta_config.
I have no idea what linux-variscite is which @zpfvo has problems with, but I think we should find a better solution.
It seems, that preconfigure has to be run after merge_delta_config and we should figure out why this linux-variscite fails.
kernel-module-imx-gpu-viv compile error with Yocto Zeus
The same problem from #136 also appears when trying to build kernel-module-imx-gpu-viv Yocto Zeus:
| In file included from poky/build/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/kernel-module-imx-gpu-viv/6.2.4.p4.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_linux.h:61,
| from poky/build/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/kernel-module-imx-gpu-viv/6.2.4.p4.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:61:
| poky/build/tmp/work-shared/imx6qdlsabresd/kernel-source/include/linux/module.h:132:6: error: 'init_module' specifies less restrictive attribute than its target 'gpu_init': 'cold' [-Werror=missing-attributes]
| 132 | int init_module(void) __attribute__((alias(#initfn)));
| | ^~~~~~~~~~~
| poky/build/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/kernel-module-imx-gpu-viv/6.2.4.p4.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:1330:1: note: in expansion of macro 'module_init'
| 1330 | module_init(gpu_init);
| | ^~~~~~~~~~~
| poky/build/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/kernel-module-imx-gpu-viv/6.2.4.p4.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:1287:19: note: 'init_module' target declared here
| 1287 | static int __init gpu_init(void)
| | ^~~~~~~~
| In file included from poky/build/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/kernel-module-imx-gpu-viv/6.2.4.p4.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_linux.h:61,
| from poky/build/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/kernel-module-imx-gpu-viv/6.2.4.p4.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:61:
| poky/build/tmp/work-shared/imx6qdlsabresd/kernel-source/include/linux/module.h:138:7: error: 'cleanup_module' specifies less restrictive attribute than its target 'gpu_exit': 'cold' [-Werror=missing-attributes]
| 138 | void cleanup_module(void) __attribute__((alias(#exitfn)));
| | ^~~~~~~~~~~~~~
| poky/build/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/kernel-module-imx-gpu-viv/6.2.4.p4.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:1331:1: note: in expansion of macro 'module_exit'
| 1331 | module_exit(gpu_exit);
| | ^~~~~~~~~~~
| poky/build/tmp/work/imx6qdlsabresd-poky-linux-gnueabi/kernel-module-imx-gpu-viv/6.2.4.p4.0-r0/git/src/hal/os/linux/kernel/gc_hal_kernel_driver.c:1318:20: note: 'cleanup_module' target declared here
| 1318 | static void __exit gpu_exit(void)
| | ^~~~~~~~
| cc1: all warnings being treated as errors
I used this workaround:
diff --git a/hal/os/linux/kernel/gc_hal_kernel_driver.c b/hal/os/linux/kernel/gc_hal_kernel_driver.c
index 87f26e721773..52f829bc477e 100644
--- a/hal/os/linux/kernel/gc_hal_kernel_driver.c
+++ b/hal/os/linux/kernel/gc_hal_kernel_driver.c
@@ -1284,7 +1284,7 @@ static struct platform_driver gpu_driver = {
};
#endif /* USE_LINUX_PCIE */
-static int __init gpu_init(void)
+static int gpu_init(void)
{
int ret = 0;
@@ -1315,7 +1315,7 @@ static int __init gpu_init(void)
return 0;
}
-static void __exit gpu_exit(void)
+static void gpu_exit(void)
{
#if USE_LINUX_PCIE
pci_unregister_driver(&gpu_driver);
Machine is imx6qdlsabresd.
Gtk+3 got error with xwayland distro
I use fsl-xwayland distro here. I bitbake core-image-sato but I got error while building matchbox-panel
configure: WARNING: using cross tools not prefixed with host triplet
checking pkg-config is at least version 0.9.0... yes
checking for MATCHBOX_PANEL... no
configure: error: Package requirements (glib-2.0
gmodule-export-2.0
x11
gdk-x11-3.0
gtk+-3.0) were not met:
No package 'gdk-x11-3.0' found
I found that there is PACKAGECONFIG_remove in file meta-freescale/recipes-graphics/gtk+/gtk+3_%.bbappend
DEPENDS_append_imxgpu2d = " virtual/egl"
PACKAGECONFIG_remove_imxgpu2d = "
${@bb.utils.contains("DISTRO_FEATURES", "wayland", "x11", "", d)}
"
So We can use wayland only or x11 only and we can't use xwayland distro, correct me is i am wrong.
Symbolic links override between general purpose and mfgtool
Actual Behavior
When I have run the mfgtool image, the symbolic links of u-boot mfgtool and the kernel mfgtool replaced the current reference of my mainline image.
Possible Answer
- Create specific links to the last build files mfgtool (u-boot, dtb, kernel).
- Rewrite symbolic links output (u-boot, kernel).
Specifications
- Version: Sumo
ds2781_battery driver probe error
Enabled w1-gpio driver for 1-wire devices, also enabled w1_ds2781 ds2781_battery drivers. Master finds ds2781 chip, but ds2781-battery driver returns -22(EINVAL)
[ 849.897604] w1_master_driver w1_bus_master1: Attaching one wire slave 3d.000000a87881 crc 17
[ 849.971330] ds2781-battery ds2781-battery.0.auto: failed to register battery
[ 849.978650] ds2781-battery: probe of ds2781-battery.0.auto failed with error -22
tested on linux-fslc/4.20+gitAUTOINC+bf414f71d7-r0
mesa 19.1.0 doesn't build
Hi @thochstein!
Mesa 19.1.0 doesn't compile without adding use-mainline-bsp override, it fails with error:
Host machine cpu family: arm
Host machine cpu: arm
Target machine cpu family: arm
Target machine cpu: arm
Build machine cpu family: x86_64
Build machine cpu: x86_64
meson.build:422:4: ERROR: Problem encountered: building dri drivers require at least one windowing system or classic osmesaWhen using use-mainline-bsp build works fine.
Thanks!
iMX8MQ based board stopped booting the Linux kernel on zeus
I noticed that my iMX8MQ based board stopped booting the Linux kernel on zeus branch after #326 was merged.
The error I see during boot is the following:
[ 4.469525] i.mx8-hdp 32c00000.hdmi: 0,ff,ff,ff,ff,ff,ff,0
[ 26.045415] INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 26.056537] 2-...: (2 GPs behind) idle=cfc/0/0 softirq=515/515 fqs=0
[ 26.068567] 3-...: (0 ticks this GP) idle=610/0/0 softirq=481/481 fqs=0
[ 26.080898] (detected by 1, t=5422 jiffies, g=-160, c=-161, q=71)
[ 26.092642] Task dump for CPU 2:
[ 26.101373] swapper/2 R running task 0 0 1 0x00000002
[ 26.114005] Call trace:
[ 26.121953] [<ffff000008085b54>] __switch_to+0x94/0xd8
[ 26.132648] [<ffff000008094fe0>] arm_cpuidle_suspend+0x30/0x38
[ 26.144061] [<ffff0000089f59b0>] arm_enter_idle_state+0x38/0x68
[ 26.155539] [<ffff0000089f3a38>] cpuidle_enter_state+0x1c8/0x228
[ 26.167090] [<ffff0000089f3ad0>] cpuidle_enter+0x18/0x20
[ 26.177864] [<ffff000008108ea8>] call_cpuidle+0x18/0x30
[ 26.188486] [<ffff0000081090e0>] do_idle+0x1a0/0x1d8
[ 26.198805] [<ffff0000081092c4>] cpu_startup_entry+0x24/0x28
[ 26.209856] [<ffff00000808f098>] secondary_start_kernel+0x110/0x120
[ 26.221516] Task dump for CPU 3:
[ 26.230093] swapper/3 R running task 0 0 1 0x00000002
[ 26.242574] Call trace:
[ 26.250329] [<ffff000008085b54>] __switch_to+0x94/0xd8
[ 26.260880] [<ffff000008094fe0>] arm_cpuidle_suspend+0x30/0x38
[ 26.272115] [<ffff0000089f59b0>] arm_enter_idle_state+0x38/0x68
[ 26.283477] [<ffff0000089f3a38>] cpuidle_enter_state+0x1c8/0x228
[ 26.294966] [<ffff0000089f3ad0>] cpuidle_enter+0x18/0x20
[ 26.305703] [<ffff000008108ea8>] call_cpuidle+0x18/0x30
[ 26.316314] [<ffff0000081090e0>] do_idle+0x1a0/0x1d8
[ 26.326519] [<ffff0000081092c4>] cpu_startup_entry+0x24/0x28
[ 26.337308] [<ffff00000808f098>] secondary_start_kernel+0x110/0x120
[ 26.348638] rcu_preempt kthread starved for 5422 jiffies! g18446744073709551456 c1844674407
3709551455 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=3
[ 26.367215] rcu_preempt I 0 8 2 0x00000000
[ 26.378046] Call trace:
[ 26.385763] [<ffff000008085b54>] __switch_to+0x94/0xd8
[ 26.396294] [<ffff000008d46620>] __schedule+0x1a8/0x590
[ 26.406893] [<ffff000008d46a40>] schedule+0x38/0xa0
[ 26.417126] [<ffff000008d49d10>] schedule_timeout+0x178/0x318
[ 26.428277] [<ffff000008127c58>] rcu_gp_kthread+0x3f8/0x7b0
[ 26.439234] [<ffff0000080e9c10>] kthread+0x100/0x130
[ 26.449545] [<ffff000008084df0>] ret_from_fork+0x10/0x18
kernel-module-imx-gpu-viv compile error with gcc 9 and imx-kernel 4.14.98
I encountered a compile error while building kernel-module-imx-gpu-viv with kernel 4.14.98 and gcc 9. Poky, meta-freescale, meta-freescape-3rdparty, meta-openembedded are all set to the master branch.
The issue is related to stricter checks in GCC 9 for attributes. These cause compiler errors.
I managed to fix this by applying two backported patches on the imx-kernel 4.14.98. The problem is that I cannot remember where I got these two backports from anymore.
I am writing this so this issue is documented, and attaching the patches so you have something to work with.
X11: Segmentation fault at address 0x4
I still experiment #93 on thud with x11-base IMAGE_FEATURE on a UDOO Neo iMX6 at startup.
I plan to run the Electron framework on the official st1232 7'' touchscreen kit for UDOO Neo.
/etc/X11/xorg.conf:
Section "Device"
Identifier "i.MX Accelerated Framebuffer Device"
Driver "vivante"
Option "fbdev" "/dev/fb0"
Option "vivante_fbdev" "/dev/fb0"
Option "HWcursor" "false"
Option "DisplayEngine" "pxp"
EndSection
Section "ServerFlags"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection
Section "InputClass"
Identifier "Touchscreen"
MatchProduct "st1232-touchscreen"
Driver "evdev"
Option "Calibration" "3 794 476 0"
EndSection
/var/log/Xorg.0.log:
X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
[ 63.243] Build Operating System: Linux 4.15.0-72-generic x86_64
[ 63.244] Current Operating System: Linux 4.1.15+2.0.x-udoo+g34f88fa2766c #1 SMP PREEMPT Mon Jan 6 14:51:20 UTC 2020 armv7l
[ 63.244] Kernel command line: console=ttymxc0,115200,115200 root=/dev/mmcblk0p1 rootwait rw rootfstype=ext4 uart_from_osc clk_ignore_unused cpuidle.off=1 consoleblank=0
[ 63.257] Build Date: 07 January 2020 10:34:32AM
[ 63.257]
[ 63.258] Current version of pixman: 0.34.0
[ 63.258] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 63.258] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 63.260] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 7 11:51:16 2020
[ 63.288] (==) Using config file: "/etc/X11/xorg.conf"
[ 63.288] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 63.297] (==) No Layout section. Using the first Screen section.
[ 63.297] (==) No screen section available. Using defaults.
[ 63.297] (**) |-->Screen "Default Screen Section" (0)
[ 63.297] (**) | |-->Monitor "<default monitor>"
[ 63.298] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 63.298] (**) | |-->Device "i.MX Accelerated Framebuffer Device"
[ 63.298] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 63.298] (**) Option "BlankTime" "0"
[ 63.298] (**) Option "StandbyTime" "0"
[ 63.298] (**) Option "SuspendTime" "0"
[ 63.298] (**) Option "OffTime" "0"
[ 63.298] (==) Automatically adding devices
[ 63.298] (==) Automatically enabling devices
[ 63.298] (==) Automatically adding GPU devices
[ 63.298] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 63.299] (WW) The directory "/usr/share/fonts/X11/misc/" does not exist.
[ 63.299] Entry deleted from font path.
[ 63.299] (WW) The directory "/usr/share/fonts/X11/TTF/" does not exist.
[ 63.299] Entry deleted from font path.
[ 63.299] (WW) The directory "/usr/share/fonts/X11/OTF/" does not exist.
[ 63.299] Entry deleted from font path.
[ 63.299] (WW) The directory "/usr/share/fonts/X11/Type1/" does not exist.
[ 63.299] Entry deleted from font path.
[ 63.299] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 63.299] Entry deleted from font path.
[ 63.299] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 63.299] Entry deleted from font path.
[ 63.299] (==) FontPath set to:
[ 63.299] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 63.299] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 63.299] (II) Loader magic: 0x54cd6d78
[ 63.300] (II) Module ABI versions:
[ 63.300] X.Org ANSI C Emulation: 0.4
[ 63.300] X.Org Video Driver: 24.0
[ 63.300] X.Org XInput driver : 24.1
[ 63.300] X.Org Server Extension : 10.0
[ 63.301] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 63.301] (II) no primary bus or device found
[ 63.301] falling back to /sys/devices/platform/Vivante GCCore/drm/card0
[ 63.301] (II) LoadModule: "glx"
[ 63.326] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 63.463] (II) Module glx: vendor="X.Org Foundation"
[ 63.463] compiled for 1.20.1, module version = 1.0.0
[ 63.463] ABI class: X.Org Server Extension, version 10.0
[ 63.463] (II) LoadModule: "vivante"
[ 63.467] (II) Loading /usr/lib/xorg/modules/drivers/vivante_drv.so
[ 63.478] (II) Module vivante: vendor="X.Org Foundation"
[ 63.478] compiled for 1.20.1, module version = 1.0.0
[ 63.478] ABI class: X.Org Video Driver, version 24.0
[ 63.478] (II) VIVANTE: fb driver for vivante: VivanteGC500, VivanteGC2100,
VivanteGCCORE
[ 63.479] (--) using VT number 1
[ 63.482] (WW) Falling back to old probe method for vivante
[ 63.482] (II) Loading sub module "fbdevhw"
[ 63.482] (II) LoadModule: "fbdevhw"
[ 63.482] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 63.484] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 63.484] compiled for 1.20.1, module version = 0.0.2
[ 63.484] ABI class: X.Org Video Driver, version 24.0
[ 63.484] (II) VIVANTE(0): using default device
[ 63.484] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 63.485] (WW) VIVANTE(0): Cannot get device preferred mode '/sys/class/graphics/fb0/mode (Not a directory)'
[ 63.485] (II) VIVANTE(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 16/16
[ 63.485] (==) VIVANTE(0): Depth 16, (==) framebuffer bpp 16
[ 63.485] (==) VIVANTE(0): RGB weight 565
[ 63.485] (==) VIVANTE(0): Default visual is TrueColor
[ 63.485] (==) VIVANTE(0): Using gamma correction (1.0, 1.0, 1.0)
[ 63.485] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 63.485] (**) VIVANTE(0): mExaHwType:1
[ 63.485] (II) VIVANTE(0): checking modes against framebuffer device...
[ 63.485] (II) VIVANTE(0): checking modes against monitor...
[ 63.485] (II) VIVANTE(0): Virtual size is 0x0 (pitch 0)
[ 63.485] (==) VIVANTE(0): DPI set to (96, 96)
[ 63.485] (II) Loading sub module "fb"
[ 63.485] (II) LoadModule: "fb"
[ 63.485] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 63.493] (II) Module fb: vendor="X.Org Foundation"
[ 63.493] compiled for 1.20.1, module version = 1.0.0
[ 63.493] ABI class: X.Org ANSI C Emulation, version 0.4
[ 63.493] (II) Loading sub module "exa"
[ 63.493] (II) LoadModule: "exa"
[ 63.495] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 63.499] (II) Module exa: vendor="X.Org Foundation"
[ 63.499] compiled for 1.20.1, module version = 2.6.0
[ 63.499] ABI class: X.Org Video Driver, version 24.0
[ 63.500] (II) VIVANTE(0): printing discovered frame buffer 'fb0' supported modes:
[ 63.501] (II) VIVANTE(0): Modeline "U:800x480p-60"x0.0 33.66 800 850 1000 1056 480 500 502 525 -hsync -vsync -csync (31.9 kHz e)
[ 63.501] (II) VIVANTE(0): Output mxs-lcdif1 has no monitor section
[ 63.501] (II) VIVANTE(0): Printing probed modes for output mxs-lcdif1
[ 63.501] (II) VIVANTE(0): Modeline "U:800x480p-60"x60.7 33.66 800 850 1000 1056 480 500 502 525 -hsync -vsync -csync (31.9 kHz e)
[ 63.501] (II) VIVANTE(0): Output mxs-lcdif1 connected
[ 63.502] (II) VIVANTE(0): Using sloppy heuristic for initial modes
[ 63.502] (II) VIVANTE(0): Output mxs-lcdif1 using initial mode U:800x480p-60 +0+0
[ 63.502] (II) VIVANTE(0): imxDisplayPreInit: virtual set 800 x 480, display width 0
[ 63.502] (II) VIVANTE(0): VivPreInit: adjust display width 800
[ 63.502] (II) VIVANTE(0): reserve 4177920 bytes for on screen frame buffer; total fb memory size 33554432 bytes; offset of shadow buffer 4177920
[ 63.504] (II) VIVANTE(0): hardware: mxs-lcdif1 (video memory: 32768kB)
[ 63.512] (II) VIVANTE(0): FB Start = 0x7458d000 FB Base = 0x7458d000 FB Offset = (nil)
[ 63.513] (II) VIVANTE(0): test Initializing EXA
[ 63.817] (II) EXA(0): Driver allocated offscreen pixmaps
[ 63.817] (II) EXA(0): Driver registered support for the following operations:
[ 63.817] (II) Solid
[ 63.817] (II) Copy
[ 63.817] (II) Composite (RENDER acceleration)
[ 63.817] (II) UploadToScreen
[ 63.817] (==) VIVANTE(0): Backing store enabled
[ 63.818] (==) VIVANTE(0): DPMS enabled
[ 63.820] drmOpenDevice: node name is /dev/dri/card0
[ 63.821] drmOpenDevice: open result is 11, (OK)
[ 63.821] drmOpenDevice: node name is /dev/dri/card0
[ 63.821] drmOpenDevice: open result is 11, (OK)
[ 63.821] drmOpenByBusid: Searching for BusID platform:Vivante GCCore:00
[ 63.821] drmOpenDevice: node name is /dev/dri/card0
[ 63.821] drmOpenDevice: open result is 11, (OK)
[ 63.821] drmOpenByBusid: drmOpenMinor returns 11
[ 63.821] drmOpenByBusid: drmGetBusid reports platform:Vivante GCCore:00
[ 63.821] (II) [drm] DRM interface version 1.4
[ 63.821] (II) [drm] DRM open master succeeded.
[ 63.821] (II) VIVANTE(0): [drm] Using the DRM lock SAREA also for drawables.
[ 63.821] (II) VIVANTE(0): [drm] framebuffer handle = 0xac100000
[ 63.821] (II) VIVANTE(0): [drm] added 1 reserved context for kernel
[ 63.821] (II) VIVANTE(0): X context handle = 0x1
[ 63.821] (EE) VIVANTE(0): [drm] failed to setup DRM signal handler
[ 63.821] (EE) VIVANTE(0): [dri] DRIScreenInit failed. Disabling DRI.
[ 63.822] (II) Initializing extension Generic Event Extension
[ 63.822] (II) Initializing extension SHAPE
[ 63.822] (II) Initializing extension MIT-SHM
[ 63.822] (II) Initializing extension XInputExtension
[ 63.825] (II) Initializing extension XTEST
[ 63.825] (II) Initializing extension BIG-REQUESTS
[ 63.825] (II) Initializing extension SYNC
[ 63.825] (II) Initializing extension XKEYBOARD
[ 63.825] (II) Initializing extension XC-MISC
[ 63.825] (II) Initializing extension XFIXES
[ 63.825] (II) Initializing extension RENDER
[ 63.825] (II) Initializing extension RANDR
[ 63.825] (II) Initializing extension COMPOSITE
[ 63.825] (II) Initializing extension DAMAGE
[ 63.825] (II) Initializing extension MIT-SCREEN-SAVER
[ 63.825] (II) Initializing extension DOUBLE-BUFFER
[ 63.825] (II) Initializing extension DPMS
[ 63.825] (II) Initializing extension Present
[ 63.825] (II) Initializing extension DRI3
[ 63.825] (II) Initializing extension X-Resource
[ 63.826] (II) Initializing extension XVideo
[ 63.826] (II) Initializing extension XVideo-MotionCompensation
[ 63.826] (II) Initializing extension GLX
[ 63.826] (II) AIGLX: Screen 0 is not DRI2 capable
[ 63.974] (II) IGLX: Loaded and initialized swrast
[ 63.974] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 63.974] (II) Initializing extension XFree86-VidModeExtension
[ 63.974] (II) Initializing extension XFree86-DGA
[ 63.974] (II) Initializing extension XFree86-DRI
[ 63.974] (II) Initializing extension DRI2
[ 63.974] (II) Initializing extension vivext
[ 63.974] (II) VIVANTE(0): Setting screen physical size to 211 x 127
[ 64.295] (II) config/udev: Adding input device 20cc000.snvs:snvs-powerkey (/dev/input/event0)
[ 64.295] (**) 20cc000.snvs:snvs-powerkey: Applying InputClass "evdev keyboard catchall"
[ 64.296] (**) 20cc000.snvs:snvs-powerkey: Applying InputClass "libinput keyboard catchall"
[ 64.296] (II) LoadModule: "libinput"
[ 64.297] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 64.323] (II) Module libinput: vendor="X.Org Foundation"
[ 64.323] compiled for 1.20.1, module version = 0.28.0
[ 64.323] Module class: X.Org XInput Driver
[ 64.323] ABI class: X.Org XInput driver, version 24.1
[ 64.323] (II) Using input driver 'libinput' for '20cc000.snvs:snvs-powerkey'
[ 64.323] (**) 20cc000.snvs:snvs-powerkey: always reports core events
[ 64.323] (**) Option "Device" "/dev/input/event0"
[ 64.323] (**) Option "_source" "server/udev"
[ 64.324] (II) event0 - 20cc000.snvs:snvs-powerkey: is tagged by udev as: Keyboard
[ 64.324] (II) event0 - 20cc000.snvs:snvs-powerkey: device is a keyboard
[ 64.325] (II) event0 - 20cc000.snvs:snvs-powerkey: device removed
[ 64.360] (**) Option "config_info" "udev:/sys/devices/soc0/soc/2000000.aips-bus/20cc000.snvs/20cc000.snvs:snvs-powerkey/input/input0/event0"
[ 64.360] (II) XINPUT: Adding extended input device "20cc000.snvs:snvs-powerkey" (type: KEYBOARD, id 6)
[ 64.362] (II) event0 - 20cc000.snvs:snvs-powerkey: is tagged by udev as: Keyboard
[ 64.362] (II) event0 - 20cc000.snvs:snvs-powerkey: device is a keyboard
[ 64.365] (II) config/udev: Adding input device st1232-touchscreen (/dev/input/event1)
[ 64.365] (**) st1232-touchscreen: Applying InputClass "Touchscreen"
[ 64.365] (II) LoadModule: "evdev"
[ 64.366] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 64.372] (II) Module evdev: vendor="X.Org Foundation"
[ 64.372] compiled for 1.20.1, module version = 2.10.6
[ 64.372] Module class: X.Org XInput Driver
[ 64.372] ABI class: X.Org XInput driver, version 24.1
[ 64.372] (II) Using input driver 'evdev' for 'st1232-touchscreen'
[ 64.372] (**) st1232-touchscreen: always reports core events
[ 64.372] (**) evdev: st1232-touchscreen: Device: "/dev/input/event1"
[ 64.373] (II) evdev: st1232-touchscreen: Using mtdev for this device
[ 64.373] (--) evdev: st1232-touchscreen: Vendor 0 Product 0
[ 64.378] (--) evdev: st1232-touchscreen: Found absolute axes
[ 64.378] (--) evdev: st1232-touchscreen: Found absolute multitouch axes
[ 64.378] (II) evdev: st1232-touchscreen: No buttons found, faking one.
[ 64.378] (II) evdev: st1232-touchscreen: Forcing relative x/y axes to exist.
[ 64.379] (II) evdev: st1232-touchscreen: Configuring as mouse
[ 64.379] (**) evdev: st1232-touchscreen: YAxisMapping: buttons 4 and 5
[ 64.379] (**) evdev: st1232-touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 64.379] (**) Option "config_info" "udev:/sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0055/input/input1/event1"
[ 64.379] (II) XINPUT: Adding extended input device "st1232-touchscreen" (type: MOUSE, id 7)
[ 64.379] (II) evdev: st1232-touchscreen: initialized for relative axes.
[ 64.379] (WW) evdev: st1232-touchscreen: ignoring absolute axes.
[ 64.381] (**) st1232-touchscreen: (accel) keeping acceleration scheme 1
[ 64.381] (**) st1232-touchscreen: (accel) acceleration profile 0
[ 64.381] (**) st1232-touchscreen: (accel) acceleration factor: 2.000
[ 64.381] (**) st1232-touchscreen: (accel) acceleration threshold: 4
[ 64.384] (II) config/udev: Adding input device FreescaleGyroscope (/dev/input/event2)
[ 64.384] (II) No input driver specified, ignoring this device.
[ 64.384] (II) This device may have been added with another device file.
[ 64.385] (II) config/udev: Adding input device FreescaleAccelerometer (/dev/input/event3)
[ 64.385] (II) No input driver specified, ignoring this device.
[ 64.385] (II) This device may have been added with another device file.
[ 64.386] (II) config/udev: Adding input device FreescaleMagnetometer (/dev/input/event4)
[ 64.386] (II) No input driver specified, ignoring this device.
[ 64.386] (II) This device may have been added with another device file.
[ 64.431] (EE)
[ 64.432] (EE) Backtrace:
[ 64.432] (EE)
[ 64.433] (EE) Segmentation fault at address 0x4
[ 64.434] (EE)
Fatal server error:
[ 64.440] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 64.440] (EE)
[ 64.441] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 64.442] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 64.442] (EE)
[ 64.447] (EE) Server terminated with error (1). Closing log file.
Output of Valgrind:
# valgrind -v xinit
==935== Memcheck, a memory error detector
==935== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==935== Using Valgrind-3.14.0-353a3587bb-20181007X and LibVEX; rerun with -h for copyright info
==935== Command: xinit
==935==
--935-- Valgrind options:
--935-- -v
--935-- Contents of /proc/version:
--935-- Linux version 4.1.15+2.0.x-udoo+g34f88fa2766c (oe-user@oe-host) (gcc version 8.2.0 (GCC) ) #1 SMP PREEMPT Mon Jan 6 14:51:20 UTC 2020
--935--
--935-- Arch and hwcaps: ARM, LittleEndian, ARMv7-neon-vfp
--935-- Page sizes: currently 4096, max supported 4096
--935-- Valgrind library directory: /usr/lib/valgrind
--935-- Reading syms from /usr/bin/xinit
--935-- Considering /usr/bin/xinit ..
--935-- .. CRC mismatch (computed 0427098f wanted 2dad0690)
--935-- object doesn't have a symbol table
--935-- Reading EXIDX entries: 1 available
--935-- Reading EXIDX entries: 0 attempted, 0 successful
--935-- Reading syms from /lib/ld-2.28.so
--935-- Considering /lib/ld-2.28.so ..
--935-- .. CRC mismatch (computed 8c9ee842 wanted d6e37b5f)
--935-- Considering /lib/.debug/ld-2.28.so ..
--935-- .. CRC is valid
--935-- Reading syms from /usr/lib/valgrind/memcheck-arm-linux
--935-- Considering /usr/lib/valgrind/memcheck-arm-linux ..
--935-- .. CRC mismatch (computed aa520794 wanted ca933b97)
--935-- object doesn't have a symbol table
--935-- object doesn't have a dynamic symbol table
--935-- Reading EXIDX entries: 1 available
--935-- Reading EXIDX entries: 0 attempted, 0 successful
--935-- Scheduler: using generic scheduler lock implementation.
--935-- Reading suppressions file: /usr/lib/valgrind/default.supp
==935== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-935-by-root-on-???
==935== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-935-by-root-on-???
==935== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-935-by-root-on-???
==935==
==935== TO CONTROL THIS PROCESS USING vgdb (which you probably
==935== don't want to do, unless you know exactly what you're doing,
==935== or are doing some strange experiment):
==935== /usr/lib/valgrind/../../bin/vgdb --pid=935 ...command...
==935==
==935== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==935== /path/to/gdb xinit
==935== and then give GDB the following command
==935== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=935
==935== --pid is optional if only one valgrind process is running
==935==
--935-- REDIR: 0x40123c1 (ld-linux-armhf.so.3:strlen) redirected to 0x580c8414 (???)
--935-- REDIR: 0x4012dc0 (ld-linux-armhf.so.3:memcpy) redirected to 0x580c8478 (???)
--935-- REDIR: 0x4011dd1 (ld-linux-armhf.so.3:strcmp) redirected to 0x580c8584 (???)
--935-- REDIR: 0x4011d11 (ld-linux-armhf.so.3:index) redirected to 0x580c8440 (???)
--935-- Reading syms from /usr/lib/valgrind/vgpreload_core-arm-linux.so
--935-- Considering /usr/lib/valgrind/vgpreload_core-arm-linux.so ..
--935-- .. CRC mismatch (computed 1bdfe5d9 wanted 13795a94)
--935-- object doesn't have a symbol table
--935-- Reading syms from /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so
--935-- Reading syms from /usr/lib/libX11.so.6.3.0
--935-- Considering /usr/lib/libX11.so.6.3.0 ..
--935-- .. CRC mismatch (computed 9da8f404 wanted cee17203)
--935-- object doesn't have a symbol table
--935-- Reading syms from /lib/libc-2.28.so
--935-- Considering /lib/libc-2.28.so ..
--935-- .. CRC mismatch (computed 3c087447 wanted a5f92159)
--935-- Considering /lib/.debug/libc-2.28.so ..
--935-- .. CRC is valid
--935-- Reading syms from /usr/lib/libxcb.so.1.1.0
--935-- Considering /usr/lib/libxcb.so.1.1.0 ..
--935-- .. CRC mismatch (computed a166091f wanted 3ab80123)
--935-- object doesn't have a symbol table
--935-- Reading syms from /lib/libdl-2.28.so
--935-- Considering /lib/libdl-2.28.so ..
--935-- .. CRC mismatch (computed dbb67142 wanted 6dbe92f4)
--935-- Considering /lib/.debug/libdl-2.28.so ..
--935-- .. CRC is valid
--935-- Reading syms from /usr/lib/libXau.so.6.0.0
--935-- Considering /usr/lib/libXau.so.6.0.0 ..
--935-- .. CRC mismatch (computed 5cb6a58a wanted b746f6ea)
--935-- object doesn't have a symbol table
--935-- Reading syms from /usr/lib/libXdmcp.so.6.0.0
--935-- Considering /usr/lib/libXdmcp.so.6.0.0 ..
--935-- .. CRC mismatch (computed 9118bea0 wanted ab0e43f4)
--935-- object doesn't have a symbol table
--935-- REDIR: 0x49a49b1 (libc.so.6:rindex) redirected to 0x48422f8 (rindex)
--935-- REDIR: 0x49a4701 (libc.so.6:strlen) redirected to 0x4842b08 (strlen)
--935-- REDIR: 0x49a48a9 (libc.so.6:strncmp) redirected to 0x48434b8 (strncmp)
--935-- REDIR: 0x49a6c29 (libc.so.6:strchrnul) redirected to 0x48477e4 (strchrnul)
--935-- REDIR: 0x49a9e40 (libc.so.6:memcpy) redirected to 0x4844840 (memcpy)
--935-- REDIR: 0x49a59c0 (libc.so.6:memset) redirected to 0x4846c34 (memset)
--936-- REDIR: 0x49a3de1 (libc.so.6:index) redirected to 0x4842548 (index)
--936-- REDIR: 0x49a47dd (libc.so.6:strnlen) redirected to 0x4842a40 (strnlen)
--936-- REDIR: 0x49a5a3d (libc.so.6:mempcpy) redirected to 0x4847910 (mempcpy)
X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.15.0-72-generic x86_64
Current Operating System: Linux vesta 4.1.15+2.0.x-udoo+g34f88fa2766c #1 SMP PREEMPT Mon Jan 6 14:51:20 UTC 2020 armv7l
Kernel command line: console=ttymxc0,115200,115200 root=/dev/mmcblk0p1 rootwait rw rootfstype=ext4 uart_from_osc clk_ignore_unused cpuidle.off=1 consoleblank=0
Build Date: 07 January 2020 10:34:32AM
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 7 17:51:11 2020
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> ignored
> X11 cannot support keycodes above 255.
> This warning only shows for the first high keycode.
Errors from xkbcomp are not fatal to the X server
(EE)
(EE) Backtrace:
(EE)
(EE) Segmentation fault at address 0x4
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
--935-- REDIR: 0x49a2079 (libc.so.6:calloc) redirected to 0x48414f0 (calloc)
--935-- REDIR: 0x49a1649 (libc.so.6:malloc) redirected to 0x483e8e4 (malloc)
--935-- REDIR: 0x49a1b05 (libc.so.6:free) redirected to 0x483ff24 (free)
--935-- REDIR: 0x49eccc9 (libc.so.6:__strcpy_chk) redirected to 0x484787c (__strcpy_chk)
--935-- REDIR: 0x49a3de1 (libc.so.6:index) redirected to 0x4842548 (index)
--935-- REDIR: 0x49a5089 (libc.so.6:strstr) redirected to 0x4847f9c (strstr)
--935-- REDIR: 0x49aa321 (libc.so.6:memchr) redirected to 0x4843fd4 (memchr)
--935-- REDIR: 0x49a5a3d (libc.so.6:mempcpy) redirected to 0x4847910 (mempcpy)
--935-- REDIR: 0x49a5afd (libc.so.6:strncasecmp) redirected to 0x4843838 (strncasecmp)
--935-- REDIR: 0x49a3eb1 (libc.so.6:strcmp) redirected to 0x4843d4c (strcmp)
--935-- REDIR: 0x49a4a55 (libc.so.6:strpbrk) redirected to 0x484817c (strpbrk)
--935-- REDIR: 0x49a41b1 (libc.so.6:stpcpy) redirected to 0x4846448 (stpcpy)
--935-- Reading syms from /lib/libnss_files-2.28.so
--935-- Considering /lib/libnss_files-2.28.so ..
--935-- .. CRC mismatch (computed 087c3558 wanted aa0a3f4c)
--935-- Considering /lib/.debug/libnss_files-2.28.so ..
--935-- .. CRC is valid
--935-- REDIR: 0x49a41c1 (libc.so.6:strcpy) redirected to 0x4842d00 (strcpy)
--935-- REDIR: 0x49a5ac1 (libc.so.6:strcasecmp) redirected to 0x4843788 (strcasecmp)
--935-- REDIR: 0x49a5680 (libc.so.6:memmove) redirected to 0x4846d14 (memmove)
--935-- REDIR: 0x49a1ccd (libc.so.6:realloc) redirected to 0x4841758 (realloc)
--935-- REDIR: 0x49a53cd (libc.so.6:bcmp) redirected to 0x48462d8 (bcmp)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
--935-- Discarding syms at 0x4ea5a90-0x4ea9bf0 in /lib/libnss_files-2.28.so (have_dinfo 1)
==935==
==935== HEAP SUMMARY:
==935== in use at exit: 0 bytes in 0 blocks
==935== total heap usage: 63 allocs, 63 frees, 24,436 bytes allocated
==935==
==935== All heap blocks were freed -- no leaks are possible
==935==
==935== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==935== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
IMAGE_BOOT_FILES broken after recent kernel-devicetree.bbclass changes
Description
The recent openembedded-core commit 1860d9d3c62e2e94cd68a809385873ffd8270b6d changed the names of DTB files in the deploy directory, but meta-freescale's IMAGE_BOOT_FILES content hasn't been updated to reflect this.
The DTB related contents of IMAGE_BOOT_FILES is generated using the make_dtb_boot_files function in conf/machine/include/utilities.inc which expects the file names of the DTBs in the deploy directory to be prefixed with ${KERNEL_IMAGETYPE}, but they no longer are.
Steps to reproduce the issue:
- Build an image with MACHINE=imx7s-warp and "wic.gz" in IMAGE_FSTYPES.
Describe the results you received:
ERROR: my-image-1.0-r0 do_image_wic: Function failed: do_image_wic (log file is located at /data/w7/build/tmp/work/imx7s_warp-oe-linux-gnueabi/my-image/1.0-r0/temp/log.do_image_wic.5799)
ERROR: Logfile of failure stored in: /data/w7/build/tmp/work/imx7s_warp-oe-linux-gnueabi/my-image/1.0-r0/temp/log.do_image_wic.5799
Log data follows:
...
| DEBUG: Executing shell function do_image_wic
| INFO: Creating image(s)...
|
| ERROR: _exec_cmd: install -m 0644 -D /data/w7/build/tmp/deploy/images/imx7s-warp/zImage-imx7s-warp.dtb /data/w7/build/tmp/work/imx7s_warp-oe-linux-gnueabi/my-image/1.0-r0/deploy-my-image-image-complete/my-image-imx7s-warp-20180711143641/tmp.wic.sqhyghzx/boot.2/imx7s-warp.dtb returned '1' instead of 0
| output: install: cannot stat '/data/w7/build/tmp/deploy/images/imx7s-warp/zImage-imx7s-warp.dtb': No such file or directory
|
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_wic (log file is located at /data/w7/build/tmp/work/imx7s_warp-oe-linux-gnueabi/my-image/1.0-r0/temp/log.do_image_wic.5799)
Describe the results you expected:
No build errors.
Additional details (revisions used, host distro, etc.):
meta-freescale version: ce51c26
oe-core version: f9324af88a99eca28b160fa31aa4516fd397e44b
dp-firmware-cadence: fetch fails after #293
dp-firmware-cadence inherits fsl-eula-unpack, but LICENSE is set to "NXP-Binary-EULA", not "Proprietary", triggering the check introduced by #293.
This affects at least master and zeus.
libimxdmabuffer build error
I appended libimxdmabuffer in yocto image.
The following error occurred :
ERROR: libimxdmabuffer-1.0.0+gitAUTOINC+db17cb57d1-r0 do_install_ptest_base: Function failed: do_install_ptest_base (log file is located at /data/imx-yocto-bsp/build-xwayland/tmp/work/aarch64-mx8mm-poky-linux/libimxdmabuffer/1.0.0+gitAUTOINC+db17cb57d1-r0/temp/log.do_install_ptest_base.13630)
ERROR: Logfile of failure stored in: /data/imx-yocto-bsp/build-xwayland/tmp/work/aarch64-mx8mm-poky-linux/libimxdmabuffer/1.0.0+gitAUTOINC+db17cb57d1-r0/temp/log.do_install_ptest_base.13630
Log data follows:
| DEBUG: Executing shell function do_install_ptest_base
| grep: Makefile: No such file or directory
| install: cannot stat '/data/imx-yocto-bsp/build-xwayland/tmp/work/aarch64-mx8mm-poky-linux/libimxdmabuffer/1.0.0+gitAUTOINC+db17cb57d1-r0/git/test-alloc': No such file or directory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_install_ptest_base (log file is located at /data/imx-yocto-bsp/build-xwayland/tmp/work/aarch64-mx8mm-poky-linux/libimxdmabuffer/1.0.0+gitAUTOINC+db17cb57d1-r0/temp/log.do_install_ptest_base.13630)
ERROR: Task (/data/imx-yocto-bsp/sources/meta-freescale/recipes-bsp/libimxdmabuffer/libimxdmabuffer_1.0.0.bb:do_install_ptest_base) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4332 tasks of which 4331 didn't need to be rerun and 1 failed.
When I checked the work folder, it seemed that the path was specified incorrectly.
libimxdmabuffer_1.0.0.bb
install -m 0755 ${B}/test-alloc ${D}${PTEST_PATH}/test
I changed the above line to:
install -m 0755 ${B}/test/test-alloc.c ${D}${PTEST_PATH}/test
libimxdmabuffer build success.
I would like to hear if this change is okay.
git.arm.linux.org.uk down
Hi,
currently git.arm.linux.org.uk is not reachable. Therefore at least xf86-video-armada and libdrm-armada are not fetchable.
As a workaround for me I've created a mirror of them (from my download cache) here at github:
https://www.github.com/g0hl1n/xf86-video-armada
https://www.github.com/g0hl1n/libdrm-armada
Unfortunately I've got an old revision of xf86-video-armada which fails to build because of compiler warnings.
Does anybody know why the site is offline?
Or know a (official) mirror?
Or has an up-to-date clone of the repos?#
Thanks & regards;Richard.L
gstreamer1.0-plugins-imx fails to build on latest master.
Hi
gstreamer1.0-plugins-imx is built with waf which requires a native python2 binary.
openembedded core recently dropped python2 as part of the host-tools which are available by default and thus gstreamer1.0-plugins-imx and friends fails to configure.
I sent merge requests to the relevant projects Freescale/gstreamer-imx, Freescale/libimxvpuapi, Freescale/libimxdmabuffer and I intend to bump the recipes here if those should get accepted.
Max
build(core-image-sato): conflict with remove_imxgpu2d and matchbox
I ran into an issue on the rocko release and noticed this thread for morty:
https://lists.yoctoproject.org/pipermail/poky/2017-June/011007.html
Simply commenting out these lines from recipes-graphics/gtk+/gtk+3_%.bbappend allowed the build to continue:
# PACKAGECONFIG_remove_imxgpu2d = " \
# ${@bb.utils.contains("DISTRO_FEATURES", "wayland", "x11", "", d)} \
# "That is still present in the current master & sumo branches, so presumably the build issue is still present in the pending sumo release.
u-boot-imx-mfgtool compiled with error
My environment
meta-freescale: thud
meta-openembedded: thud
poky: thud
Ubuntu 18.04
ISSUE:
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| install: cannot create regular file '/home/thinhnguyen/DATA2/imx8mqevk/Yocto/build-imx8mqevk/tmp/work/imx8mqevk-imx8mqevk-linux/u-boot-imx-mfgtool/2017.03-r0/image/boot/spl/u-boot-spl.bin-imx8mqevk-mfgtool-2017.03-r0-mfgtool-2017.03-r0': No such file or directory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_install (log file is located at /home/thinhnguyen/DATA2/imx8mqevk/Yocto/build-imx8mqevk/tmp/work/imx8mqevk-imx8mqevk-linux/u-boot-imx-mfgtool/2017.03-r0/temp/log.do_install.12427)
ERROR: Task (/home/thinhnguyen/DATA2/imx8mqevk/Yocto/sources/meta-freescale/recipes-bsp/u-boot/u-boot-imx-mfgtool_2017.03.bb:do_install) failed with exit code '1'
Reproduce Steps:
- Select Machine: imx8mqevk
- Set UBOOT_CONFIG = "mfgtool"
- bitbake u-boot-imx-mfgtool
do_populate_sdk: No manifest generated from: lib32-alsa-lib
Hi,
I am trying to build an SDK I suspect the same error would pop up when building an image. The problem that I am facing is that I need to include lib32-alsa-lib to my SDK but I am getting the following error
ERROR: strix-sdk-1.0-r0 do_populate_sdk: No manifest generated from: lib32-alsa-lib in virtual:multilib:lib32:/home/builder/workdir/layers/poky/meta/recipes-multimedia/alsa/alsa-lib_1.1.5.bb
ERROR: strix-sdk-1.0-r0 do_populate_sdk: Function failed: do_populate_sdk
ERROR: Logfile of failure stored in: /home/builder/workdir/builds/imx8mm/tmp/work/imx8mm-strix-linux/strix-sdk/1.0-r0/temp/log.do_populate_sdk.138
ERROR: Task (/home/builder/workdir/layers/meta-strix/meta-strix-common/recipes-core/images/strix-sdk.bb:do_populate_sdk) failed with exit code '1'
The reason for this is that that PACKAGE_ARCH is overwritten at
and that the find_sstate_manifest function in poky
will not look for the manifest named armv7ahf-neon-mx8mm set by
Do you have any idea how I can solve this based on the code in
It should be possible to add armv7ahf-neon-mx8mm to PACKAGE_EXTRA_ARCHS but I cannot find how I should do that.
BR
Måns Zigher
gstreamer1.0-plugins-base 1.14.imx undefined reference to `pow@GLIBC_2.29'
Branch: THUD
OS: Ubuntu 18.04
Machine: iMX8mq-evk
ERROR:
| /home/thinhnguyen/DATA2/EVK/Yocto/build-EVK/tmp/work/aarch64-mx8m-evk-linux/gstreamer1.0-plugins-base/1.14.imx-r0/recipe-sysroot-native/usr/bin/aarch64-evk-linux/../../libexec/aarch64-evk-linux/gcc/aarch64-evk-linux/8.2.0**/ld:** /home/thinhnguyen/DATA2/EVK/Yocto/build-evk/tmp/work/aarch64-mx8m-evk-linux/gstreamer1.0-plugins-base/1.14.imx-r0/recipe-sysroot/usr/lib/libgstreamer-1.0.so: undefined reference to `pow@GLIBC_2.29'
| collect2: error: ld returned 1 exit status
| Makefile:717: recipe for target 'gst-discoverer-1.0' failed
| make[2]: *** [gst-discoverer-1.0] Error 1
| make[2]: Leaving directory '/home/thinhnguyen/DATA2/EVK/Yocto/build-evk/tmp/work/aarch64-mx8m-evk-linux/gstreamer1.0-plugins-base/1.14.imx-r0/build/tools'
| Makefile:718: recipe for target 'all-recursive' failed
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory '/home/thinhnguyen/DATA2/EVK/Yocto/build-evk/tmp/work/aarch64-mx8m-evk-linux/gstreamer1.0-plugins-base/1.14.imx-r0/build'
| Makefile:649: recipe for target 'all' failed
| make: *** [all] Error 2
| ERROR: oe_runmake failed
Receipes that depend on libusb are broken
They should depend on "libusb1"
linux-imx-headers header files do not get added to Yocto SDKs
I tried this with current master:
MACHINE=imx8mmevk bitbake -c populate_sdk core-image-weston
The produced SDK did not contain the headers from linux-imx-headers, even though it is listed in the RDEPENDS list. I even tried to explicitely append linux-imx-headers to TOOLCHAIN_TARGET_TASK, and still, nothing.
Problem with MACHINEOVERRIDES_EXTENDER_FILTER_OUT
Hi @otavio ,
It seems we have a problem with the MACHINEOVERRIDES_EXTENDER_FILTER_OUT variable.
Actually, I had a doubt about the following output:
BB_VERSION = "1.42.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "imx7s-warp"
DISTRO = "poky"
DISTRO_VERSION = "2.7"
TUNE_FEATURES = "arm armv7ve vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
More precisely with the variable TUNE_FEATURES.
Example :
$: bitbake -e core-image-base | grep '^TUNE_FEATURES'
TUNE_FEATURES="arm arm armv7ve vfp thumb neon callconvention-hard"
...
armv7ve seems incorrect for the mx7 family according to the imx-base file.
And now, if I comment on the variable 'MACHINEOVERRIDES_EXTENDER_FILTER_OUT_use-mainline-bsp' :
$: bitbake -e core-image-base | grep '^TUNE_FEATURES'
TUNE_FEATURES="arm vfp cortexa7 neon thumb callconvention-hard"
...
I have the right definition corresponding to the definition in the imx-base file.
The behaviour is the same for all variables.
Another example :
Without MACHINEOVERRIDES_EXTENDER_FILTER_OUT_use-mainline-bsp:
$: bitbake -e core-image-base | grep '^UBOOT_ENTRYPOINT'
UBOOT_ENTRYPOINT="0x80008000"
UBOOT_ENTRYPOINT_mx51="0x90008000"
UBOOT_ENTRYPOINT_mx53="0x70008000"
UBOOT_ENTRYPOINT_mx6="0x10008000"
UBOOT_ENTRYPOINT_mx6sl="0x80008000"
UBOOT_ENTRYPOINT_mx6sll="0x80008000"
UBOOT_ENTRYPOINT_mx6sx="0x80008000"
UBOOT_ENTRYPOINT_mx6ul="0x10008000"
UBOOT_ENTRYPOINT_mx6ull="0x10008000"
UBOOT_ENTRYPOINT_mx7="0x80008000"
UBOOT_ENTRYPOINT_mx8mq="0x4048000000"
UBOOT_ENTRYPOINT_mxs="0x40008000"
UBOOT_ENTRYPOINT_vf="0x80008000"
with MACHINEOVERRIDES_EXTENDER_FILTER_OUT_use-mainline-bsp :
$: bitbake -e core-image-base | grep '^UBOOT_ENTRYPOINT'
UBOOT_ENTRYPOINT_mx51="0x90008000"
UBOOT_ENTRYPOINT_mx53="0x70008000"
UBOOT_ENTRYPOINT_mx6="0x10008000"
UBOOT_ENTRYPOINT_mx6sl="0x80008000"
UBOOT_ENTRYPOINT_mx6sll="0x80008000"
UBOOT_ENTRYPOINT_mx6sx="0x80008000"
UBOOT_ENTRYPOINT_mx6ul="0x10008000"
UBOOT_ENTRYPOINT_mx6ull="0x10008000"
UBOOT_ENTRYPOINT_mx7="0x80008000"
UBOOT_ENTRYPOINT_mx8mq="0x40480000"
UBOOT_ENTRYPOINT_mxs="0x40008000"
UBOOT_ENTRYPOINT_vf="0x80008000"
So no UBOOT_ENTRYPOINT defined in fact.
Any idea ?
Thanks
/Pierre-Jean
gstreamer build failures with upstream (meson migration)
Latest gstreamer in oe-core has switched from autotools to meson build, therefore Freescale fork is not compatible anymore and build fails.
I've entered this issue here just for tracking, I'm currently updating gstreamer in my fork to work with meson. So far, I was able to update -base with -good and -bad on the way.
If anyone else is working on this - please log the state here, we might then try to sync forks.
-- andrey
optee-os do_package failure
Hi,
I'm getting an error when building optee-os-3.2.0.imx-r0 on zeus with the imx8mqevk:
ERROR: optee-os-3.2.0.imx-r0 do_package: QA Issue: optee-os: Files/directories were installed but not shipped in any package:
/lib
/lib/firmware
/lib/firmware/tee-header_v2.bin
/lib/firmware/tee-pageable_v2.bin
/lib/firmware/tee-pageable.bin
/lib/firmware/tee-pager_v2.bin
/lib/firmware/tee.bin
/lib/firmware/tee-pager.bin
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
optee-os: 8 installed and not shipped files. [installed-vs-shipped]
ERROR: optee-os-3.2.0.imx-r0 do_package: Fatal QA errors found, failing task.
I managed to fix the issue by replacing these two lines :
install -d ${D}/lib/firmware/
install -m 644 ${B}/core/*.bin ${D}/lib/firmware/
by
install -d ${D}/usr/lib/firmware/
install -m 644 ${B}/core/*.bin ${D}/usr/lib/firmware/
Please feel free to correct me or to ask for any additional information regarding the issue.
imx-gpu-viv issue with xserver-xorg
Is there a reason imx-gpu-viv hasn't been updated to version 6.2.4.p4.0 as on https://source.codeaurora.org/external/imx/meta-fsl-bsp-release/tree/imx/meta-bsp/recipes-graphics/imx-gpu-viv?h=sumo-4.14.98-2.0.0_ga ?
I still get a vague seg fault if unless I rollback xserver-xorg to 1.19.6 like in Variscite's BSP: varigit/meta-variscite-fslc@5e18d51
(EE)
(EE) Backtrace:
(EE)
(EE) Segmentation fault at address 0x4
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
Weston does not start after upgrade (imx8mmevk machine with 4.19.y kernel)
Duplicating the original thread from meta-freescale yocto mailing list:
After the recent upgrade of Weston (commit: a4fdb40) I started to receive the error from G2D on i.MX8M Mini at the start with following output:
Date: 2019-12-18 UTC
[16:51:24.982] weston 6.0.1
https://wayland.freedesktop.org
Bug reports to:
https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 6.0.1-36-g4ee0a1da-dirty g2d-renderer: refine
enable overlay view feature (2019-10-17 12:57:52 +0800)
[16:51:24.982] Command line: /usr/bin/weston
[16:51:24.982] OS: Linux, 4.19.35-1.1.0+g0f9917c56d59, #1 SMP PREEMPT
Wed Oct 30 11:02:38 UTC 2019, aarch64
[16:51:24.982] Using config file '/etc/xdg/weston/weston.ini'
[16:51:24.982] Output repaint window is 16 ms maximum.
[16:51:24.982] Loading module '/usr/lib/libweston-6/drm-backend.so'
[16:51:24.986] initializing drm backend
[16:51:24.991] logind: session control granted
[16:51:24.994] using /dev/dri/card0
[16:51:24.994] DRM: supports universal planes
[16:51:24.994] DRM: supports atomic modesetting
[16:51:24.994] DRM: supports picture aspect ratio
[16:51:24.994] Loading module '/usr/lib/libweston-6/g2d-renderer.so'
[16:51:24.995] g2d_open fail.
[16:51:24.995] g2d_renderer_create faile.
[16:51:24.995] failed to initialize g2d render
If the G2D support is disabled in the /etc/xdg/weston/weston.ini by commenting the line:
#use-g2d=1
then Weston falls back to use the GL backend, which also fails with the following output:
Date: 2019-12-18 UTC
[16:56:14.652] weston 6.0.1
https://wayland.freedesktop.org
Bug reports to:
https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 6.0.1-36-g4ee0a1da-dirty g2d-renderer: refine
enable overlay view feature (2019-10-17 12:57:52 +0800)
[16:56:14.653] Command line: /usr/bin/weston
[16:56:14.653] OS: Linux, 4.19.35-1.1.0+g0f9917c56d59, #1 SMP PREEMPT
Wed Oct 30 11:02:38 UTC 2019, aarch64
[16:56:14.653] Using config file '/etc/xdg/weston/weston.ini'
[16:56:14.653] Output repaint window is 16 ms maximum.
[16:56:14.653] Loading module '/usr/lib/libweston-6/drm-backend.so'
[16:56:14.657] initializing drm backend
[16:56:14.663] logind: session control granted
[16:56:14.667] using /dev/dri/card0
[16:56:14.667] DRM: supports universal planes
[16:56:14.667] DRM: supports atomic modesetting
[16:56:14.667] DRM: supports picture aspect ratio
[16:56:14.672] Loading module '/usr/lib/libweston-6/gl-renderer.so'
[16:56:14.704] EGL client extensions: EGL_EXT_client_extensions
EGL_EXT_platform_base EGL_KHR_platform_wayland
EGL_EXT_platform_wayland EGL_KHR_platform_gbm
[16:56:14.712] EGL version: 1.5
[16:56:14.712] EGL vendor: Vivante Corporation
[16:56:14.712] EGL client APIs: OpenGL_ES OpenVG
[16:56:14.712] EGL extensions: EGL_KHR_fence_sync EGL_KHR_reusable_sync
EGL_KHR_wait_sync EGL_KHR_image EGL_KHR_image_base
EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image
EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image
EGL_EXT_image_dma_buf_import
EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_lock_surface
EGL_KHR_create_context EGL_KHR_surfaceless_context
EGL_EXT_create_context_robustness EGL_EXT_buffer_age
EGL_ANDROID_native_fence_sync EGL_WL_bind_wayland_display
EGL_WL_create_wayland_buffer_from_image EGL_KHR_partial_update
[16:56:14.712] EGL_KHR_surfaceless_context available
[16:56:14.725] failed to create context
[16:56:14.725] EGL error state: EGL_BAD_ALLOC (0x3003)
[16:56:14.725] EGL error state: EGL_SUCCESS (0x3000)
[16:56:14.725] failed to initialize egl
zeus branch is not affected by this issue, there the Weston is operable.
Following are SRCREVs of components in question that could've potentially impact the Weston.
From master branch build (which is failing):
# imx8mmevk-fslc-linux
SRCREV_pn-optee-os = "6a52487eb0ff664e4ebbd48497f0d3322844d51d"
SRCREV_pn-kernel-module-qca6174 = "2f4ae376ce3db65c3270a4bf7e804f3e86052c8c"
SRCREV_pn-imx-boot = "dd0234001713623c79be92b60fa88bc07b07f24f"
SRCREV_pn-linux-imx = "0f9917c56d5995e1dc3bde5658e2d7bc865464de"
SRCREV_pn-u-boot-imx = "4d377539a1190e838eae5d8b8a794dde0696d572"
SRCREV_pn-kernel-module-qca9377 = "2f4ae376ce3db65c3270a4bf7e804f3e86052c8c"
SRCREV_pn-kernel-module-imx-gpu-viv = "0f9917c56d5995e1dc3bde5658e2d7bc865464de"
SRCREV_pn-cryptodev-module = "fd8b15ef1c8398a69a37932ee48c74ab40329a29"
# aarch64-mx8mm-fslc-linux
SRCREV_pn-gstreamer1.0-plugins-good = "a31aabb7581d3f491cd31889d44479bb0f34990b"
SRCREV_pn-imx-gpu-apitrace = "09579e67262af9c993dd082055a924c2c61cf34d"
SRCREV_pn-imx-gst1.0-plugin = "0c5f48b3aee473d8c8f3e853eb2078f054caa4d2"
SRCREV_pn-gstreamer1.0-plugins-bad = "0191521ba226904e4b2f84c38e5f6ae75169a18a"
SRCREV_pn-imx-alsa-plugins = "cde60d68ab2acee913dbfacb8aabb53d87dd3e38"
SRCREV_boostdesc_pn-opencv = "34e4206aef44d50e6bbcd0ab06354b52e7466d26"
SRCREV_contrib_pn-opencv = "2c32791a9c500343568a21ea34bf2daeac2adae7"
SRCREV_ipp_pn-opencv = "32e315a5b106a7b89dbed51c28f8120a48b368b4"
SRCREV_opencv_pn-opencv = "371bba8f54560b374fbcd47e7e02f015ac4969ad"
SRCREV_vgg_pn-opencv = "fccf7cd6a4b12079f73bbfb21745f9babcd4eb1d"
SRCREV_pn-gstreamer1.0 = "d42548da09724ad8cc1aa4f1944607920be2f4c0"
SRCREV_pn-linux-imx-headers = "a51dda8feec03e8c675230786d64ee050944dbfd"
SRCREV_pn-imx-gpu-sdk = "d35bac9419895ea516c25e2f36a6084729d9e6ce"
SRCREV_pn-imx-atf = "70fa7bcc1a2035ab8402550911b3ae29eff55371"
SRCREV_pn-weston = "4ee0a1da010053b35495e82ad30aa5a8b1c34e6c"
SRCREV_pn-libdrm = "5748c8ff40f1ae87487c01e580f145a43542cbda"
SRCREV_pn-gstreamer1.0-plugins-base = "f62f8ab685e549eefaecdb1e700239a5a408fcad"
SRCREV_pn-imx-test = "709d14b037e7a45af018875c4a880f8f9c198288"
From zeus branch build (which is operable):
# imx8mmevk-fslc-linux
SRCREV_pn-optee-os = "6a52487eb0ff664e4ebbd48497f0d3322844d51d"
SRCREV_pn-kernel-module-qca6174 = "e008d2578b09f1f593f65ede48529a52312e3957"
SRCREV_pn-imx-boot = "dd0234001713623c79be92b60fa88bc07b07f24f"
SRCREV_pn-linux-imx = "1175b59611537b0b451e0d1071b1666873a8ec32"
SRCREV_pn-u-boot-imx = "0d6d8807793e74402e23772062469aeb4808dd48"
SRCREV_pn-kernel-module-qca9377 = "e008d2578b09f1f593f65ede48529a52312e3957"
SRCREV_pn-kernel-module-imx-gpu-viv = "f54dc1486d13d44766cdb6551d094313f077b535"
SRCREV_pn-cryptodev-module = "fd8b15ef1c8398a69a37932ee48c74ab40329a29"
# aarch64-mx8mm-fslc-linux
SRCREV_pn-gstreamer1.0-plugins-good = "a31aabb7581d3f491cd31889d44479bb0f34990b"
SRCREV_pn-imx-gpu-apitrace = "013499c63d9eddd8c792bd8b136991caa3b8a100"
SRCREV_pn-imx-gst1.0-plugin = "0c5f48b3aee473d8c8f3e853eb2078f054caa4d2"
SRCREV_pn-gstreamer1.0-plugins-bad = "0191521ba226904e4b2f84c38e5f6ae75169a18a"
SRCREV_pn-imx-alsa-plugins = "9a63071e7734bd164017f3761b8d1944c017611f"
SRCREV_boostdesc_pn-opencv = "34e4206aef44d50e6bbcd0ab06354b52e7466d26"
SRCREV_contrib_pn-opencv = "2c32791a9c500343568a21ea34bf2daeac2adae7"
SRCREV_ipp_pn-opencv = "32e315a5b106a7b89dbed51c28f8120a48b368b4"
SRCREV_opencv_pn-opencv = "371bba8f54560b374fbcd47e7e02f015ac4969ad"
SRCREV_vgg_pn-opencv = "fccf7cd6a4b12079f73bbfb21745f9babcd4eb1d"
SRCREV_pn-gstreamer1.0 = "d42548da09724ad8cc1aa4f1944607920be2f4c0"
SRCREV_pn-linux-imx-headers = "dfc78102d29f81d9316b281a3b8af3dff95174c8"
SRCREV_pn-imx-gpu-sdk = "d35bac9419895ea516c25e2f36a6084729d9e6ce"
SRCREV_pn-imx-atf = "1cb68fa0a0dd8bc00b9871b51d4c4e1d0a827b2d"
SRCREV_pn-weston = "fb563901657b296c7c7c86d26602a622429e334f"
SRCREV_pn-libdrm = "95645843f59495387a072d48374718f22e69d7a4"
SRCREV_pn-gstreamer1.0-plugins-base = "f62f8ab685e549eefaecdb1e700239a5a408fcad"
To me it looks like graphics drivers are broken in the 4.19.y version (which were also recently upgraded to match kernel major/minor).
Looks like we're hitting a regression in Weston with all recent upgrades from NXP of all components (Kernel, drivers, Weston, ...).
@otavio @thochstein @Mihaix: can you please have a look at this?
I believe a lot of people would be affected by this once Yocto 3.1 would roll-out and everyone would
start to upgrade.
Thanks a lot!
-- andrey
gtk+3_%.bbappend causes build failure
The bbappend for gtk+3 is causing chromium-x11 to fail. It relies on the gtk x11 headers to be present, but this removes x11 from the distro features, and causes the headers to not be generated. Commenting out the bbappend contents allows the build to succeed.
weston_4.0.0.imx and libdrm_2.4.84.imx used for mx7d
Is there any advantage for mx7d to use special version of weston/drm? Shouldn't this only be changed for mx7ulp?
Error: OpenCl support on imx8mq processor with vivante GPU
Hello, we are currently working on a project that requires GPU parallel processing on an imx8mq processor with a vivante GPU. We have tried building for the imx8 evaluation kit as well as for our own carrier board and were unable to successfully get OpenCl to populate onto the build. We were able to get OpenCv however when attempting to detect OpenCl it was not on the image. We also compiled the SDK for this particular build which contained the needed OpenCl libraries for our architecture though when attempting to run any OpenCL program after transferring them to our image they were not able to execute. We are wondering if there is a way to get OpenCl working using just the meta-freescale layer. Thank you in advance for any assistance you can offer!
Machine: imx8mq
Branch: zeus
imx8m Nano: missing machine description
Hello all,
I've started to work on the build for i.MX8M Nano CPU and found out that actually the master branch has a machine definition missing.
There are binaries available from NXP website, which could be obtained under the Linux Binary Demo Files - i.MX 8M Nano EVK and it looks like the image is based on the sumo branch. I've checked this repo, but unfortunately was not able to find any reference to the imx8mnevk machine.
Does this machine description exists somewhere and can someone from NXP contribute it here?
I've created a draft machine description for my testing purposes but faced an issue with the U-Boot not starting: SPL uses the ROMAPI to boot the image, but loading from SD interface fails. I was actually hoping that if the machine description would be contributed - I could sort out the issue with U-Boot I'm currently having.
Thanks a lot!
-- andrey
openssl-qoriq shared library packaging problems
Hi,
The openssl-qoriq recipe puts libcrypto.so.1.1/libssl.so.1.1 into both libcrypto/libssl packages and into the openssl-qoriq-ptest package. This is a problem because Yocto detects multiple shlib providers for libcrypto.so.1.1 and libssl.so.1.1 and can end up using the wrong one as dependency for other packages using these shared libraries.
If openssl-qoriq-ptest is used as the dependency for everything, then libcrypto/libssl are not even included in the rootfs image, so no programs using openssl will work because libcrypto.so.1.1/libssl.so.1.1 exist only in /usr/lib/openssl-qoriq/ptest/ instead of /lib or /usr/lib.
This issue is made worse due to a bug in package.bbclass which has indeterministic behaviour in case of multiple shlib providers, see this upstream fix:
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=41a5dbd16b0c9f5f97e7a160830cf7ca5de52ec6
Looking at openssl-qoriq_1.1.0g.bb, do_install_ptest() already contains some code which possibly was intended to prevent this issue (by renaming the *.so symlinks), but looks like it's incomplete (not handling the real *.so.* files).
Our work-around for now is to disable ptest completely (remove it from DISTRO_FEATURES) so openssl-qoriq-ptest doesn't get built at all.
ERROR: ParseError at meta-freescale/recipes-graphics/imx-gpu-viv/imx-gpu-viv-6.inc:32: unparsed line: '"'
OpenGL ES 2.x support in gstreamer1.0-plugins-base bbappend broken
The gstreamer1.0-plugins-base bbappend enables the gles2 packageconfig for imxgpu3d, but not the egl one. However, on the imx6 and imx8, both are needed for proper OpenGL ES 2.x support.
Here is the patch: https://gist.github.com/dv1/8475271a79f1dfd932132ae9251366dc
Adding a white-space into each (append) variable
Summary
Many append variables in meta-freescale haven't a white a the string start. According to the official documentation, all append variable require a white-space to prevent the #57 problem.
Official Documentation
3.1.8. Appending and Prepending (Overrid#e Style Syntax)
B_append = " additional data"
Question
Do you want a pull request on sumo branch with all replaced appended variables?
DP/eDP port support on imx8mq
I saw that the current kernel revision for imx8mq seems to have support for DP in imx-hdp driver. There is also a dp/edp device tree. Have you guys ever tested anything in that regard? I was looking for a board with DP but couldn't find any.
Weird behavior using menuconfig with configuration fragments
I am trying to use the new support for configuration fragments that was introduced in #386. I am following the instructions from the kernel-dev manual here: https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#creating-config-fragments to create configuration fragments. I have run the kernel_configme step, run the menuconfig step and then generated a fragment using diffconfig.
After adding that fragment to my BSP I wanted to make additional changes so I reran the kernel_configme step and checked that the .config file generated contained the correct changes from my first fragment and it did. However, when I go ahead and run the menuconfig step all those changes go away and are not present in the .config anymore or in the menuconfig gui. If I load the previous .config into menuconfig then I can see all the old changes I am expecting but then running diffconfig creates a fragment with all the new and old changes which is not what I want since I am trying to keep the fragments separate.
Am I missing a step here or is there a bug in the menuconfig step that is causing it to not pull the fragments into the config before it runs the tool?
Overall these kernel improvements are a big improvement though!
Thanks!
libdrm is broken
The codeaurora.org git appears to no longer be available resulting in building libdrm to fail
ERROR: libdrm-2.4.91.imx-r0 do_fetch: Fetcher failure for URL: 'git://source.codeaurora.org/external/imx/libdrm-imx.git;protocol=https;branch=libdrm-imx-2.4.91'. Unable to fetch URL from any source.
ERROR: libdrm-2.4.91.imx-r0 do_fetch: Function failed: base_do_fetch
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.