linux/meta-freescale.git/recipes-core, branch master

imx-base: Move the i.MX SDK host tools to TOOLCHAIN_HOST_TASK

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

A bbappend to nativesdk-packagegroup-sdk-host added nativesdk-imx-usb-loader, nativesdk-mxsldr, nativesdk-u-boot-mkimage and nativesdk-wayland to RDEPENDS unconditionally, so an SDK built for any machine in a build with meta-freescale in BBLAYERS picked up i.MX flashing tools. Measured on qemuarm64 with bitbake -e: RDEPENDS gained exactly those four. The obvious fix -- scoping that RDEPENDS to a machine override -- would be worse than the leak. That packagegroup has a fixed PACKAGE_ARCH of ${SDK_ARCH}-nativesdk, so making its contents depend on MACHINE would emit different package content under one package architecture, and two SDKs built from the same TMPDIR would overwrite each other in the feed. oe-core's own recipe is careful here: it varies only by SDK_ARCH and DISTRO_FEATURES, never by MACHINE. Drop the bbappend and add the tools to TOOLCHAIN_HOST_TASK in imx-base.inc instead. populate_sdk_base consumes that variable in the SDK recipe, which is already machine-specific, so there is no package-architecture hazard. imx-base.inc is required only by i.MX machine configurations -- 27 of them, no QorIQ -- and the append is additionally scoped to imx-generic-bsp to match the IMAGE_CLASSES line above it. Measured with bitbake -e, before vs after: qemuarm64 TOOLCHAIN_HOST_TASK gains none of the four tools imx6qdlsabresd TOOLCHAIN_HOST_TASK gains exactly the four tools; nothing else in the expansion moves Note for QorIQ: those machines previously received these tools through the unconditional bbappend and no longer do. Three of the four are i.MX-specific, so this is intended, but it is a behaviour change for machines this layer does own. bitbake -p: 1166 recipes, 0 errors. No SDK was built, so the effect on a populated SDK is inferred from TOOLCHAIN_HOST_TASK, not measured. 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

nativesdk-packagegroup-sdk-host: Order RDEPENDS alphabetically

2026-07-27T17:34:05+00:00

oelint.vars.dependsordered flags the three nativesdk-* entries as out of alphabetical order. Sort them (imx-usb-loader, mxsldr, u-boot-mkimage); the conditional wayland entry stays last. RDEPENDS is a set, so this is build-neutral. Signed-off-by: Luciano Dittgen

udev-rules-qoriq: Add version to filename per oelint

2026-07-22T12:20:39+00:00

Rename udev-rules-qoriq.bb to udev-rules-qoriq_1.0.bb so the recipe filename carries an explicit version (file.underscores). PV was already the default "1.0", so this is no functional change. Signed-off-by: Luciano Dittgen

udev-rules-imx: Add version to filename per oelint

2026-07-22T12:20:39+00:00

Rename udev-rules-imx.bb to udev-rules-imx_1.0.bb so the recipe filename carries an explicit version (file.underscores). PV was already the default "1.0", so this is no functional change. Signed-off-by: Luciano Dittgen

udev-rules-qoriq: Set SUMMARY, HOMEPAGE and SECTION per oelint

2026-07-13T11:40:17+00:00

Add the missing mandatory SUMMARY and HOMEPAGE and set SECTION. Signed-off-by: Otavio Salvador

udev-rules-imx: Set SUMMARY and SECTION per oelint

2026-07-13T11:40:17+00:00

Add the missing mandatory SUMMARY and set SECTION. Signed-off-by: Otavio Salvador

global: Indent multi-line variable continuations

2026-07-12T08:14:32+00:00

Align the continuation lines of multi-line variable assignments, as suggested by oelint-adv's auto-fix for a single rule (oelint.vars.multilineident), isolated to one commit. The auto-fix strips the leading space from a value's first line, which for a ':append' is a required separator; those five recipes had their leading space restored by hand, so ':append'/':prepend' concatenation is unchanged. A few multi-line values (e.g. DESCRIPTION) gain internal whitespace, which is cosmetic and collapses on display. Build-tested: parsing all 2948 recipes for an i.MX machine reports 0 errors. A residual set (the restored ':append' recipes, whose separator space oelint cannot reconcile with its indent preference, plus opencv/dpdk where oelint's own fix does not satisfy its checker) is left for per-recipe handling. 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

global: Clean up BitBake list spacing

2026-07-07T17:40:00+00:00

Normalize list continuations, append spacing, quote style, and simple flag values so the metadata follows oelint BitBake syntax expectations. Tested with: git diff --check. Signed-off-by: Luciano Dittgen