linux/meta-freescale.git/classes/use-imx-security-controller-firmware.bbclass, branch master

use-imx-security-controller-firmware: Make PACKAGE_ARCH a weak default

2026-08-18T20:26:36+00:00

The class set PACKAGE_ARCH with a hard "=". imx-boot inherits the class and then sets its own PACKAGE_ARCH = "${MACHINE_ARCH}", while imx-seco and firmware-ele-imx inherit the class and rely on "${MACHINE_SOCARCH}". Use "?=" so the class provides a default that inheriting recipes can override, matching use-imx-headers.bbclass. This is value-preserving: bitbake.conf defines PACKAGE_ARCH with the weaker "??=", so "?=" here still yields "${MACHINE_SOCARCH}" for the non-overriding inheritors, while imx-boot's later "=" after the inherit still wins. Validated with a real build in a resolved environment for one of the non-overriding inheritors (MACHINE=imx93-11x11-lpddr4x-evk, target firmware-ele-imx): PACKAGE_ARCH resolves to "cortexa55-mx93" (= MACHINE_SOCARCH) both before and after, and comparing buildhistory across the parent and this commit shows the only delta is metadata-revs, with no change to the generated package. Behaviour-preserving. Signed-off-by: Luciano Dittgen

use-imx-security-controller-firmware: Document anonymous python per oelint

2026-07-17T12:18:19+00:00

Suppress task.noanonpython on the anonymous python guard: SoCs that require a SECO firmware must fail parsing early (SkipRecipe) when SECO_FIRMWARE_NAME is undefined, which needs anonymous python. bbclass.underscores on the class filename is handled by the layer-wide suppression. No functional change. 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

use-imx-security-controller-firmware: Add i.MX 91 configuration

2025-01-29T07:27:34+00:00

Add the SECO FW file name for i.MX 91. It is based on imx-6.6.52_2.2.0 NXP BSP release. Signed-off-by: Alexander Stein

use-imx-security-controller-firmware: Add i.MX 95 configuration

2024-10-21T22:13:56+00:00

Add the SECO FW file name for i.MX 95. Signed-off-by: Max Krummenacher

imx-base.inc: Implement generic SOC revision design

2023-08-21T18:48:06+00:00

Rework imx-boot and use-imx-security-controller-firmware.bbclass with a generic SOC revision design implemented in imx-base.inc. This does replace the machine feature design using `soc-rev*`, but maintains backwards compatibility by incorporating that design into the default settings. Signed-off-by: Tom Hochstein

imx: fw: allow to build for mainline bsp too

2023-04-10T09:22:46+00:00

SECO/SC FW/HDMI FW and friends should not be restricted to imx-nxp-bsp. If one wants to build machines for a mainline kernel / user space these would be required to build the boot container too. Signed-off-by: Max Krummenacher

use-imx-security-controller-firmware.bbclass: SECO_FIRMWARE_NAME as weak variable

2023-03-22T03:50:52+00:00

With `SECO_FIRMWARE_NAME` weak variable, user can update with new name when new version is released. Signed-off-by: Jun Zhu

use-imx-security-controller-firmware: Add i.MX 93 configuration

2023-02-14T13:59:01+00:00

It add SECO_FIRMWARE_NAME for mx93-nxp-bsp. It is based on 5.15.71_2.2.0 NXP BSP release. Signed-off-by: Daiane Angolini

use-imx-security-controller-firmware: Configure for imx8ulp

2023-02-07T11:16:40+00:00

Add SECO_FIRMWARE_NAME for i.MX 8ULP. Signed-off-by: Daiane Angolini