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

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)

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: Strip trailing whitespace

2026-07-13T18:55:06+00:00

Remove trailing whitespace across the layer's recipes. Generated mechanically by oelint-adv's auto-fix for a single rule (oelint.spaces.lineend), isolated to one commit so the mechanical change is easy to review and revert. Pure whitespace removal with no semantic effect; a re-run of oelint-adv reports the rule clean. No build change expected. Signed-off-by: Otavio Salvador (cherry picked from commit 1161bee242e93dd083efdd5f32d16efa67e9946e)

xserver-xorg: remove glamor pixmap patch

2025-12-19T11:31:13+00:00

Already implemented in xserver-xorg Signed-off-by: QingLee95

xserver-xorg: Refresh the patch to match 21.1.9 version

2023-12-29T23:16:16+00:00

Signed-off-by: Khem Raj

xserver-xorg: Replace glamor inverse color patch

2023-08-01T18:37:49+00:00

Replace glamor patch for Ubuntu inverse color issue. Signed-off-by: Tom Hochstein Signed-off-by: Otavio Salvador

recipes: Add missing patch tag Upstream-Status

2023-06-22T01:33:11+00:00

Signed-off-by: Khem Raj

xserver-xorg: fix patch fuzz

2023-05-18T16:05:20+00:00

Reformat the patch so that the do_patch step stops complaining about patch fuzz. Signed-off-by: Dan McGregor

xserver-xorg: Drop patches which are no more applicable

2022-09-14T02:40:30+00:00

Some of these patches are already upstream [1] Others are moved to xwayland Glamor patches were backports no longer needed [1] https://gitlab.freedesktop.org/xorg/xserver/-/commit/cc05c01925755310f027c61daa29648a10155f96 Signed-off-by: Khem Raj

xserver-xorg: Drop Remove-check-for-useSIGIO-option.patch

2022-09-14T00:58:10+00:00

This patch is already upstreamed [1] [1] https://gitlab.freedesktop.org/xorg/xserver/-/commit/36e353bcf428c4e6a31292ffa749ea6395cba4a3 Signed-off-by: Khem Raj