linux/meta-freescale.git/classes, branch backport-scarthgap

EULA: Update to v53

2024-04-01T18:48:10+00:00

This version is used in NXP BSP LF6.6.3-1.0.0. Signed-off-by: Oleksandr Suvorov

uuu_bootloader_tag.bbclass: Use UUU_BOOTLOADER_TAGGED variable

2024-03-09T22:14:32+00:00

Use UUU_BOOTLOADER_TAGGED variable instead of UUU_BOOTLOADER in the stat function to make the code more specific and easy to read. Signed-off-by: Hiago De Franco

uuu_bootloader_tag.bbclass: Add UUU_BOOTLOADER_UNTAGGED

2024-03-08T20:33:21+00:00

Add UUU_BOOTLOADER_UNTAGGED flag to add the possibility to deploy a imx-boot binary without the tagged footer 'UUUBURNXXOEUZX7+A-XY5601QQWWZ%sEN' at the end. The addition of the footer 'UUUBURNXXOEUZX7+A-XY5601QQWWZ%sEN' at the end causes issues when the binary is loaded into RAM memory, this footer may cause issues where the binary size exceeds the typical USB package size used by UUU (1021 bytes). As example, if the footer is split across two distinct USB packages, such as sending 'UUUBURNXXXOE' in the last packet and 'UZX7+A-XY5601QQWWZ%sEND' in the next one, it can lead to UUU halting while waiting for a response in SDPS mode. After sending 'UUUBURNXXXOE', iMX8MP's boot room starts SPL, not waiting for the next packet ('UZX7+A-XY5601QQWWZ%sEND'), leading to UUU breaking. Therefore, deploy both binaries separately (-tagged and -untagged) to allow users to choose the appropriate binary. Signed-off-by: Hiago De Franco

EULA,SCR: Update to v49 for NXP release 6.1.55-2.2.0

2024-01-16T09:34:29+00:00

Signed-off-by: Max Krummenacher

Revert "fsl-dynamic-packagearch: fix MACHINE_SOCARCH definition"

2023-12-31T18:48:02+00:00

This change makes no sense. MACHINE_SOCARCH must include the suffix that makes the value SOC-specific. Otherwise, errors such as this occur: ``` ERROR: imx-dpu-g2d-2.1.12-r0 do_create_spdx_setscene: Recipe imx-dpu-g2d is trying to install files into a shared area when those files already exist. The files and the manifests listing them are: tmp/deploy/spdx/armv8a/packages/libg2d-dev.spdx.json (matched in manifest-armv8a-imx-pxp-g2d.create_spdx) tmp/deploy/spdx/armv8a/packages/libg2d2.spdx.json (matched in manifest-armv8a-imx-pxp-g2d.create_spdx) ``` This reverts commit 6579ce9b77f0036454478b2e07694f7314f97867.

fsl-dynamic-packagearch: fix MACHINE_SOCARCH definition

2023-12-29T13:50:18+00:00

The sstate manifest for populate_sysroot was not being named properly for firmware-sentinel and imx-boot-firmware-files, raising the following error: The sstate manifest for task 'firmware-sentinel:populate_sysroot' (multilib variant '') could not be found. The pkgarchs considered were: microej_imx93, armv7ahf-neon-vfpv4-mx93, armv7ahf-neon-mx93, (and so on...) But none of these manifests exists: ...build/tmp-glibc/sstate-control/manifest-microej_imx93-imx-boot-firmware-files.populate_sysroot ...build/tmp-glibc/sstate-control/manifest-armv7ahf-neon-vfpv4-mx93-imx-boot-firmware-files.populate_sysroot ... and so on. All the other packages were suffixed with TUNE_PKGARCH only, so I couldn't see the reason why only some specific packages from meta-freescale were using that. Remove MACHINE_SOCARCH_SUFFIX so as the sstate manifest is compatible with what's expected in populate_sysroot. Signed-off-by: Joao Marcos Costa

fsl-u-boot-localversion.bbclass: fix SRCREV_machine and AUTOREV use cases

2023-12-05T10:47:35+00:00

Use the same logic as fsl-kernel-localversion.bbclass: commit 16a356ef0d5d62090e84530e125ea6952994aaeb Signed-off-by: Jun Zhu

fsl-kernel-localversion: fix SRCREV_machine and AUTOREV use cases

2023-12-04T14:16:51+00:00

Depending on how one uses the Yocto kernel classes the kernels hash is defined in either "SRCREV_machine" or "SRCREV". If "SRCREV_machine" is in use, "SRCREV" stays at its bitbake default "INVALID". If the "SRCREV_machine" or "SRCREV" is set to "AUTOREV" that value is replaced by "AUTOINC". If using "SRCREV_machine" and/or "AUTOREV" do_kernel_localversion fails | run.do_kernel_localversion:158 exit 128 from 'head=`git --git-dir=.../.git rev-parse --verify --short INVALID 2> /dev/null`' Cope with both use cases. Fixes: 41537394 ("classes: make localversion classes deterministic") Signed-off-by: Max Krummenacher

classes: make localversion classes deterministic

2023-11-28T11:05:41+00:00

The localversion string built into the kernel and u-boot should be deterministic. With OpenEmbedded it is common practice to apply patches to the sources. The commit id of HEAD will differ each time the patching step is rerun. With the previous implementation of the fsl-{kernel,u- boot}-localversion classes this produced non-deterministic commit ids to be used. This is undesireable, because the commit-id read from the version string during runtime is not present in the sources. It also caused problems when building out-of-tree kernel-modules if the kernel itself was taken from sstate cache but the kernel-module needed to be rebuild and retriggered the kernels do_patch task (see #961). Rework to produce a deterministic string that will use the commit id given as SRCREV and count the number of patches applied on top. With e.g. commit id 11aabbcc and 5 patches this will result in a version string +g11aabbcc+p5 Fixes: https://github.com/Freescale/meta-freescale/issues/961 Signed-off-by: Daniel Wagenknecht

image_types_fsl.bbclass: Drop use of IMAGE_NAME_SUFFIX

2023-11-10T03:49:03+00:00

This is no longer required since its already merged into IMAGE_NAME and IMAGE_LINK_NAME via [1] in OE-Core. Infact it causes problems now if we add .rootfs explicitly, this created non-existent filenames and resulting images are wrong. [1] https://git.openembedded.org/openembedded-core/commit/meta/classes-recipe/image-artifact-names.bbclass?id=26d97acc71379ab6702fa54a23b6542a3f51779c Signed-off-by: Khem Raj