linux/meta-freescale.git/recipes-bsp/formfactor, branch master

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

Generalize overrides subsystem for NXP and Mainline support

2022-02-21T23:06:28+00:00

Essentially, we extend the overrides to a generic-bsp, nxp-bsp, and mainline-bsp. So, for example, the mx8mq override is split into: - imx-generic-bsp: compatible with every i.MX SoC and both BSP variants - imx-nxp-bsp: compatible with every i.MX SoC but specific to NXP BSP - imx-mainline-bsp: compatible with every i.MX SoC but specific to Mainline BSP - mx8-generic-bsp: compatible with every i.MX8 SoC and both BSP variants - mx8-nxp-bsp: compatible with every i.MX8 SoC but specific to NXP BSP - mx8-mainline-bsp: compatible with every i.MX8 SoC but specific to Mainline BSP - mx8m-generic-bsp: compatible with every i.MX8M SoC and both BSP variants - mx8m-nxp-bsp: compatible with every i.MX8M SoC but specific to NXP BSP - mx8m-mainline-bsp: compatible with every i.MX8M SoC but specific to Mainline BSP - mx8mq-generic-bsp: compatible with every i.MX8MQ SoC and both BSP variants - mx8mq-nxp-bsp: compatible with every i.MX8MQ SoC8 but specific to NXP BSP - mx8mq-mainline-bsp: compatible with every i.MX8MQ SoC but specific to Mainline BSP The extender mechanism is responsible for extending the override list to include the generic overrides. We can then use the three different variants to handle the metadata correctly. Generically speaking, the conversion mainly was automated (with a lot of back and forth until getting it right). To convert an existing layer, the following script can be used: ```sh git ls-files classes recipes-* \ | xargs sed -i \ -e 's,:$mx[6-8]\w*$,:\1-nxp-bsp,g' \ -e 's,($mx[6-8]\w*$),(\1-nxp-bsp),g' \ -e 's,$mx[6-8]\w*$|,\1-nxp-bsp|,g' \ -e 's,|$mx[6-8]\w*$),|\1-nxp-bsp),g' \ \ -e 's,:$mx[5s]\w*$,:\1-generic-bsp,g' \ -e 's,($mx[5s]\w*$),(\1-generic-bsp),g' \ -e 's,$mx[5s]\w*$|,\1-generic-bsp|,g' \ -e 's,|$mx[5s]\w*$),|\1-generic-bsp),g' \ \ -e 's,:$vf\w*$,:\1-generic-bsp,g' \ -e 's,:$vf[56]0\w*$,:\1-generic-bsp,g' \ -e 's,$vf\w*$|,\1-generic-bsp|,g' \ -e 's,|$vf\w*$),|\1-generic-bsp),g' \ -e 's,$vf[56]0\w*$|,\1-generic-bsp|,g' \ -e 's,|$vf[56]0\w*$),|\1-generic-bsp),g' \ \ -e 's,:$imx$ ,:\1-nxp-bsp ,g' \ -e 's,($imx$),(\1-nxp-bsp),g' \ -e 's,$imx$|,\1-nxp-bsp|,g' \ -e 's,|$imx$),|\1-nxp-bsp),g' for d in $(find -type d | egrep '/mx[6-8]w*'); do git mv $d $d-nxp-bsp done for d in $(find -type d | egrep '/imx$'); do git mv $d $d-nxp-bsp done for d in $(find -type d | egrep '/mx[5s]w*'); do git mv $d $d-generic-bsp done ``` Fixes: #791. Signed-off-by: Otavio Salvador

layer: Convert to new override syntax

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

Signed-off-by: Khem Raj

formfactor: Fix typo in comment

2018-12-13T16:01:31+00:00

Signed-off-by: Tom Hochstein

formfactor: Add machconfig for 6SLL and 7ULP

2018-08-31T00:57:09+00:00

Signed-off-by: Tom Hochstein Signed-off-by: Otavio Salvador

formfactor: Add machconfig for i.MX6 Q/QP/DL/Solo/SL/SX

2016-10-18T18:26:15+00:00

in poky, the formfactor/config set HAVE_KEYBOARD=1, as it assumes a key is connected as default. This causes the disable of the software keyboard launch in matchbox. Set HAVE_KEYBOARD=0 for i.MX6 Q/QP/DL/Solo/SL/SX. Signed-off-by: Lauren Post Signed-off-by: Jun Zhu Signed-off-by: Otavio Salvador

formfacor: Add generic machconfig formfactors for i.MX 6UltraLite and 7Dual

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

Signed-off-by: Lauren Post Signed-off-by: Otavio Salvador

Move meta-fsl-arm content to layer root

2015-07-16T18:01:29+00:00

The meta-fsl-arm is going to be used as the base for this layer. It contains a clean history and allowing a more granullar set of changes. This commit is just a rename of all contents of meta-fsl-arm subdirectory to this layer's root, subsequent changes are based on top of that. Signed-off-by: Otavio Salvador