linux/meta-freescale.git/dynamic-layers/multimedia-layer, branch g2d-rename

wireplumber: Drop the redundant FILES entry for the config directory

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

The oe-core default FILES:${PN} already carries ${datadir}/${BPN}, which packages /usr/share/wireplumber and everything under it, so appending the conf.d path added nothing -- and it did so unconditionally, on machines this layer does not own. Built wireplumber on imx8mm-lpddr4-evk with do_package forced: FILELIST, PKGSIZE and RDEPENDS are unchanged; only FILES loses the entry. Signed-off-by: Luciano Dittgen

bluealsa: Scope the disabled autostart to i.MX machines

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

Upstream leaves bluealsa.service enabled and disables only the -aplay one, so this bbappend overrode core behaviour on every machine, which fails yocto-check-layer. The reason it exists -- pipewire owns Bluetooth audio -- holds only on our i.MX BSP, so imx-generic-bsp is the right scope; elsewhere the upstream default applies again. Built bluealsa on imx8mm-lpddr4-evk with do_package forced; buildhistory is identical. Signed-off-by: Luciano Dittgen

wireplumber: Reformat SRC_URI:append per review

2026-08-24T18:03:25+00:00

Per review, put an empty opening quote and move every URI onto a new continuation line. The space after the opening quote stays, so BitBake still separates the appended URIs from the base SRC_URI when it joins the :append with no separator. This satisfies oelint.vars.multilineident without a nooelint directive. SRC_URI is whitespace-split, so the fetched sources are unchanged. Comment-and-whitespace change 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

pipewire: Order DEPENDS, fix override syntax and patch metadata per oelint

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

Move the DEPENDS:append above SRC_URI (oelint.var.order.DEPENDS) and rewrite the conditional bluez-lc3 line as PACKAGECONFIG:append:class-target:imx-nxp-bsp so :append leads the override list (oelint.vars.overrideappend). Add an explanatory comment on the PACKAGECONFIG:remove dispatch line noting it consumes the machine-specialized PACKAGECONFIG_REMOVE helper defined just below it. Correct the 0001 patch Upstream-Status reason from the non-standard '[i.MX specific]' to '[embedded specific]', and restore the missing Signed-off-by on the 0003 patch from its declared author. No functional change to the build; override-order and DEPENDS position are applied at finalization regardless of textual placement. 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: 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

bluealsa: move bbappend to dynamic-layers to avoid parsing errors

2026-03-26T08:47:25+00:00

The bluealsa recipe already exists in the meta-multimedia layer from the meta-openembedded repository. When meta-multimedia is not included in the configuration, the bbappend file triggers a parsing error: ERROR: No recipes in default available for: meta-freescale/recipes-multimedia/bluealsa/bluealsa_%.bbappend To prevent this issue and ensure the bbappend is applied only when the appropriate layer is present, the file has been moved to dynamic-layers. Signed-off-by: Benjamin Missey

wireplumber_%.bbappend: Add nxp config

2026-03-23T02:46:20+00:00

Signed-off-by: Zelan Zou

pipewire: Refresh patch

2026-03-23T02:46:20+00:00

Signed-off-by: Zelan Zou