linux/meta-freescale.git/classes/qoriq_build_64bit_kernel.bbclass, branch g2d-rename

Merge pull request #2679 from lucianogdittgen/oelint-task-noanonpython

2026-09-10T18:06:52+00:00

Remove or document the layer's anonymous python functions

qoriq_build_64bit_kernel: Document the multilib promotion block

2026-09-10T17:12:25+00:00

The block conditionally replaces KERNEL_CC, KERNEL_LD and KERNEL_AR. A declarative form would have to state what those keep when the flag is unset, which means restating the kernel.bbclass defaults inside this class. DEPENDS is also read before the task graph exists, so a task cannot carry any of this. Signed-off-by: Luciano Dittgen

qoriq_build_64bit_kernel: Append the multiarch distro feature

2026-09-10T15:42:31+00:00

Appending to REQUIRED_DISTRO_FEATURES:e6500 builds that scope up from empty, so on an e6500 machine it replaces REQUIRED_DISTRO_FEATURES rather than extending it. Nothing else sets it today, so the value is unchanged; :append keeps it that way if a consumer ever does. Tested on t2080rdb: bitbake -e still reports " multiarch" and linux-qoriq's buildhistory records no changes. Signed-off-by: Luciano Dittgen

qoriq_build_64bit_kernel: Suppress noncoreoverride on the anonymous python

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

The class is gated by BUILD_64BIT_KERNEL, a variable any machine may set, not by a machine override, so it cannot carry one; e6500.inc is the only in-tree setter. Rewriting the block as :e6500 assignments would narrow that contract and needs an e6500 multilib kernel build to validate, which this tree cannot produce. The directive trades the warning for a false oelint.file.inlinesuppress_na info: oelint misses the blockoffset hit. 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

qoriq_build_64bit_kernel: Scope arch QA override

2026-06-30T19:39:56+00:00

Only remove the arch QA check when BUILD_64BIT_KERNEL promotes the QorIQ kernel build to the 64-bit toolchain. This keeps the override tied to the configuration that needs it and handles an empty ERROR_QA value safely. Tested as part of the series with bitbake -p and yocto-check-layer. Signed-off-by: Luciano Dittgen

layer: Convert to new override syntax

2021-08-12T17:08:24+00:00

Signed-off-by: Khem Raj

recipes: Use features_check instead of distro_features_check

2019-11-23T15:17:02+00:00

distro_features_check is now deprecated Signed-off-by: Khem Raj

remove True option to getVar calls

2019-01-17T14:29:17+00:00

getVar() has been defaulting to expanding by default for a long time (2016), thus remove the True option from getVar() calls with a regex search and replace. Search & replace made using the following command: sed -e 's|$d\.getVar \?$( \?$[^,()]*$, \?True)|\1(\2)|g' \ -i $(git grep -E 'getVar ?$ ?([^,()]*), ?True$' \ | cut -d':' -f1 \ | sort -u) Signed-off-by: André Draszik

classes/u-boot: Update getVar syntax

2016-04-19T18:03:26+00:00

This runs: sed -e 's:$\.getVar([^,()]*$):\1, False):g' -i `grep -ril getVar *` on the layer to update the getVar usages without an expand parameter, This ensures the layer continues to work with bitbake master. There is no functionality change although some of these sites may benefit from expand=True. Signed-off-by: Richard Purdie Signed-off-by: Zhenhua Luo Signed-off-by: Otavio Salvador