linux/meta-freescale.git/recipes-graphics/mesa, branch wrynose

mesa-etnaviv-env: Checksum the license header in the shipped script

2026-09-03T20:01:11+00:00

SRC_URI ships only a conf file and a shell script from this layer, with no license header to checksum, so the recipe checksummed oe-core's generic MIT text, which never changes and so verified nothing. Declare MIT with an SPDX identifier in both shipped files and checksum the line in the one do_install actually ships under use-mainline-bsp+sysvinit. Validated on MACHINE=imx8mp-ddr4-evk with IMX_DEFAULT_BSP forced to mainline, the only override that installs mesa-etnaviv.sh. Intended output change: the shipped script grows by the SPDX line, so PKGSIZE goes 63 -> 94. FILELIST is unchanged. Signed-off-by: Luciano Dittgen (cherry picked from commit 246b05bb0fd097c9077eac6ed05f7842dfe996a4)

oelint: Suppress noncoreoverride on the machine-gated bbappend idiom

2026-08-09T00:38:12+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 (cherry picked from commit f22a7b5863e81b58c21ee5c9f535074ea4d09497)

mesa-etnaviv-env: Order variables per oelint

2026-07-23T14:43:24+00:00

Place S before PACKAGE_ARCH into canonical order, clearing oelint's order.S. Signed-off-by: Luciano Dittgen (cherry picked from commit c2e89a54ff15b1a0a4f6541e4a39a053f48366a8)

mesa-demos: Document noncoreoverride construct per oelint

2026-07-22T14:34:43+00:00

Add an explanatory comment on the PACKAGECONFIG:remove dispatch line, documenting that it consumes machine-specialized helper vars which default to "" and are overridden per i.MX GPU variant (imxgpu/imxgpu2d/ imxgpu3d). This is a deliberate, unconditional oelint.vars.noncoreoverride construct. No functional change. Signed-off-by: Luciano Dittgen (cherry picked from commit e59601aaa37a80b94c2706952009f484b3c4e9df)

mesa-etnaviv-env: Set DESCRIPTION, SECTION and order per oelint

2026-07-14T12:54:27+00:00

Add the missing mandatory DESCRIPTION, set SECTION, and move SRC_URI ahead of PACKAGE_ARCH. Signed-off-by: Otavio Salvador (cherry picked from commit 66b22e7da4cb9dd308d928a255aba3c8422cb72e)

global: Use single space around variable assignments

2026-07-13T20:13:21+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 (cherry picked from commit 2d0bdc93bd8eb274c24d127405e54cecd0a744b6)

global: Drop needless whitespace in assignments

2026-07-13T18:55:06+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 (cherry picked from commit 96b4f44279d022af8930f01d4a09c12df0be07e4)

mesa: Drop un-used NXP BSP overrides

2026-03-10T22:10:28+00:00

The imx-gpu-viv recipe was once reliant on mesa, but today there appears to be no such dependency, so drop the overrides. Signed-off-by: Tom Hochstein

mesa-etnaviv-env: Add HOMEPAGE variable

2026-01-23T07:31:49+00:00

Add HOMEPAGE variable to mesa-etnaviv-env recipe. Signed-off-by: Weisser, Pascal

mesa: Drop patches as no longer needed

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

The issues addressed by the patches are fixed in the current version. Signed-off-by: Tom Hochstein