| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
oelint.vars.noncoreoverride flags every statement in a bbappend that
carries no MACHINE or DISTRO override suffix, because an unconditional
override of core behaviour fails yocto-check-layer. The check is purely
syntactic: it cannot see that a statement's effective value is already
machine-gated, which is exactly how most of this layer is written.
DRM-REMOVE = "" <- flagged
DRM-REMOVE:imxgpu:mx6-nxp-bsp = "drm-gl drm-gles2"
PACKAGECONFIG:remove = "${DRM-REMOVE}" <- flagged
Neither line can be scoped. A fallback default cannot carry an override
for the machines it is the fallback for, and the dispatch line that
consumes it is a no-op wherever the helper expands empty. Scoping them
anyway would damage correct metadata: weston-init reads HAS_G2D as "elif
${HAS_G2D};" in shell, where an empty value is a syntax error.
Suppress the 58 sites proven inert, each with its own rationale. The
proof is a bitbake -e comparison on MACHINE=qemuarm64 -- a machine this
layer does not own -- with meta-freescale in and out of BBLAYERS. At
every suppressed site SRC_URI, DEPENDS, PACKAGECONFIG, OPENGL_PKGCONFIGS
and REQUIRED_DISTRO_FEATURES are unchanged; eight recipes show no
effective difference at all. The helper variables are defined in the
datastore but every consumer is override-scoped. For the 18
FILESEXTRAPATHS sites there is a stronger result: FILESPATH and
FILESEXTRAPATHS are both in BB_BASEHASH_IGNORE_VARS, so they cannot
reach a task signature.
Two anonymous python blocks are deliberately left unsuppressed and
explained in place instead. For those, oelint anchors the finding to the
line before the block, so a directive placed above only moves the anchor
onto itself: the finding survives and inlinesuppress_na is reported for
the directive. oelint.task.noanonpython anchors the same block to the
'python' line and suppresses correctly, so the two rules disagree about
where the construct starts. Upstream oelint bug candidate.
The rule count goes 76 -> 18 and the layer total 548 -> 491. The 16
findings that remain are not noise: they are measured, genuine
unconditional changes to machines this layer does not own, and are left
open for separate fixes.
This change is comment-only; no non-comment line is added or modified.
Validated with bitbake -p (1166 recipes, 0 errors) and an authoritative
driver rescan showing zero introduced findings in any of the 24 edited
files. The residual override/outofcontext churn in the rescan is the
known shared-metadata scan non-determinism and nets to zero.
Signed-off-by: Luciano Dittgen <luciano.dittgen@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
meta-freescale used columnar alignment (multiple spaces padding the
variable name out to a common column) for tables of assignments such as
the fsl-eula-unpack MD5 sums and PACKAGECONFIG[...] entries. The Yocto
Recipe Style Guide and oelint-adv (oelint.vars.spacesassignment) call for
a single space around the assignment operator.
Collapse the padding to a single space on every flagged assignment. The
change is purely whitespace around the operator: variable names, operators
and values (including whitespace inside quoted values) are untouched, as
confirmed by an empty 'git diff -w'.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
| |
Since i.MX 8, DRM is supported by default by the i.MX GPU. Simplify the
DRM config logic by reversing the default, making it clear that it is
i.MX 6 and 7 that do not support DRM.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
| |
Add the relevant configuration for an i.MX 95 SoC.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
| |
|
|
|
|
| |
Fix dynamic layer overrides missed by the script.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
imx-gpu-viv_6.4.0.p1.0-aarch32 does not provide virtual/libgbm and thus
a build with drm* in PACKAGECONFIG does fail.
Thus remove drm* from PACKAGECONFIG for those machines.
| ERROR: Nothing PROVIDES 'virtual/libgbm' (but .../glmark2_git.bb DEPENDS on or otherwise requires it)
| gpulib PROVIDES virtual/libgbm but was skipped: incompatible with machine
fixes: 7801868f glmark2: Remove bbappend
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
| |
|
|
|
|
|
|
|
|
| |
The default PACKAGECONFIG for glmark2 builds just fine on imxgpu3d and
imxgpu2d platforms, and doing so enables support for the drm based
tests.
Tested on imx8mq and imx8qm
Signed-off-by: Joshua Watt <Joshua.Watt@garmin.com>
|
| |
|
|
|
|
|
|
|
| |
The recipe has been reworked to use the 'imxgpu2d' and 'imxgpu3d'
feature overrides, while on that, the '_remove' operator usage has
been removed as it is impossible to override using a bbappend file.
Change-Id: I89d4a4d461b182ad3d7ca8ed8ebbfe2183caf467
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
| |
If DISTRO_FEATURES contains x11 and wayland, configure the package
for a Wayland backend.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
| |
6SoloLite
The i.MX 6SoloLite has no 3D support, so don't build glmark2 with OpenGL
ES 2.0 support.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
The PACKAGECONFIG is now overriden, so we avoid getting broken in case
changes on meta-oe are commited.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
The linking against GL is failing so we need to remove this support as
an intermediate solution.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
| |
This handles the PACKAGECONFIG setting depending on the
DISTRO_FEATURES avaiability (X11 or Wayland). It adds GL and GLES2
support for the available flavours.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
|
The external layer's specific changes are now in the 'dynamic-layers'
subdirectory. This approach ease the identification of layer specific
recipes and extensions as all those are more visible isolated of the
main layer components.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|