linux/meta-freescale.git/recipes-graphics/piglit, branch master

piglit: Suppress noncoreoverride on the upstream cl test patches

2026-09-04T12:52:28+00:00

Both patches fix piglit's OpenCL tests generally, not on i.MX: 0001 corrects an install-layout include path in a cl test, 0002 adds the missing CL 2.0 cl_mem_flags mutexes. Neither touches a compile path, so scoping them to imx-generic-bsp would leave the tests broken everywhere else rather than fix a build. Both carry an upstream MR link, so the divergence ends when they merge. Signed-off-by: Luciano Dittgen

oelint: Suppress noncoreoverride findings the scoping fixes made inert

2026-08-07T12:30:02+00:00

Five findings in this rule were genuine before the preceding four commits and are no longer. Suppress them with the same measured rationale used for the rest of the bucket, so they do not sit in the open list implying work that is already done. weston-init's update_file, insert_line_before and insert_line_after are defined unconditionally, but their only caller is do_install:append, which is now scoped to imx-generic-bsp. Off-target they are never invoked and never reach a task script -- measured on qemuarm64, where do_install is byte-identical to the oe-core-only expansion. piglit's PACKAGECONFIG:append and its PACKAGECONFIG_APPEND base default are now the ordinary machine-gated dispatch idiom: the helper defaults to empty and only carries content under imx-generic-bsp, so both are no-ops off-target. Measured on qemuarm64: PACKAGECONFIG, DEPENDS and RDEPENDS unchanged. oelint.vars.noncoreoverride 14 -> 9, layer total 486 -> 482. Suppressions 141 -> 146, audit clean (ineffective 0, no rationale 0). Comment-only; no non-comment line is added or changed. bitbake -p: 1166 recipes, 0 errors. The override/outofcontext churn in the rescan is the known shared-metadata scan non-determinism and nets to zero. The nine findings that remain are deliberately open: two anonymous python blocks the rule cannot suppress, piglit's SRC_URI patches, and six needing either maintainer intent or a layer that is not checked out here. Signed-off-by: Luciano Dittgen

piglit: Scope the gbm and vulkan PACKAGECONFIG default to i.MX

2026-08-07T12:30:00+00:00

PACKAGECONFIG_APPEND carried a non-empty '?=' default of "gbm" plus vulkan-if-enabled, and an unscoped PACKAGECONFIG:append consumed it. Unlike the other helper variables in this layer, whose defaults are empty and therefore inert off-target, this one changed the build of every machine in any build with meta-freescale in BBLAYERS. Give it an empty base default and move the real value to imx-generic-bsp. The existing mx6/mx7 clears still win over that, because their overrides come later in OVERRIDES. Measured with bitbake -e on qemuarm64, meta-freescale in and out of BBLAYERS. Before this commit the layer added, on a machine it does not own: DEPENDS + virtual/libgbm glslang-native vulkan-loader RDEPENDS + glslang EXTRA_OECMAKE -DPIGLIT_USE_GBM=1, and BUILD_VK_TESTS OFF -> ON PACKAGECONFIG + gbm vulkan After it, DEPENDS, RDEPENDS and PACKAGECONFIG match the layer-less expansion. On imx6qdlsabresd every one of those variables is unchanged before vs after this commit. Two differences off-target are deliberately left, and both remain flagged rather than suppressed: * SRC_URI still gains two patches. They fix genuine upstream build errors, so scoping them would make a non-i.MX build that currently succeeds only because meta-freescale is present start failing. The real fix is to send them to openembedded-core and drop them here. * EXTRA_OECMAKE still gains -DPIGLIT_USE_GBM=0, the disabled branch of the PACKAGECONFIG[gbm] knob. A varflag cannot be machine-scoped and defining the knob is standard practice; the flag only states the upstream default explicitly. bitbake -p: 1166 recipes, 0 errors. No build was run, so this is parse/expand-tier evidence only. Signed-off-by: Luciano Dittgen

oelint: Suppress noncoreoverride on the machine-gated bbappend idiom

2026-08-07T12:30:00+00:00

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

piglit: Comment build-fix patches and PACKAGECONFIG dispatch

2026-07-22T14:16:40+00:00

Add short comments explaining the two local SRC_URI patches (the cl-test include-directories fix and the mutually-exclusive CL_MEM memory-flags build error) and noting that the PACKAGECONFIG:append/:remove lines dispatch to the machine-specialized PACKAGECONFIG_APPEND/PACKAGECONFIG_REMOVE helpers defined below. No functional change. Signed-off-by: Luciano Dittgen

global: Use single space around variable assignments

2026-07-12T18:55:50+00:00

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

global: Drop needless whitespace in assignments

2026-07-12T07:54:14+00:00

Remove the stray space between an assignment's opening quote and its line-continuation backslash, and the space before '%' in inline ${@...} expressions. Generated mechanically by oelint-adv's auto-fix for a single rule (oelint.vars.notneededspace), isolated to one commit. The affected values are whitespace-separated lists (leading space is insignificant) and Python format expressions ("%s"% p is equivalent), so there is no functional change; a re-run of oelint-adv reports the rule clean. Signed-off-by: Otavio Salvador

piglit: Limit OpenCL tests to supported i.MX 8 machines

2026-06-24T17:44:30+00:00

Enabling OpenCL globally adds a dependency on virtual/libopencl1 for machines without a provider. Enable it only for i.MX 8 NXP BSP machines using the Vivante GPU stack. Signed-off-by: Luciano Dittgen

piglit: Update bbappend NXP 6.12.20-2.0.0

2025-08-26T15:10:21+00:00

- Add GBM and Vulkan for DRM parts - Remove x11 for 6 and 7 - Add pending patches Signed-off-by: Tom Hochstein

piglit: Restore GL tests

2023-04-03T20:41:46+00:00

The build is working now. Signed-off-by: Tom Hochstein