linux/meta-freescale.git/classes, branch rework-kernel-recipes

classes/image_populate_mfgtool: fix basehash value change

2023-04-14T19:10:42+00:00

Signed-off-by: Otavio Salvador

classes/image_populate_mfgtool: avoid error copying duplicated files

2023-04-13T19:50:02+00:00

Eventually, multiple `uuu` script may install same binaries. We need to ensure we install them once, otherwise it'll fail as it might try to override a existing binary. This commit ensure all dependencies and binaries are mentioned once, removing duplication. Fixes: ae7af6f8 ("classes/image_populate_mfgtool: init") Signed-off-by: Otavio Salvador

classes/mfgtool-initramfs-image: remove u-boot-mfgtool dependency

2023-04-12T20:12:18+00:00

The initramfs image doesn't use the U-Boot binaries so there is no reason for a dependency on it. Signed-off-by: Otavio Salvador

classes/image_populate_mfgtool: init

2023-04-12T20:12:18+00:00

The class provides the infrastructure for MFGTOOL generation and is tied to images. To generate the bundle, the task populate_mfgtool must be called. For example: ,----[ Running populate_mfgtool for core-image-minimal image ] | $: bitbake core-image-minimal -c populate_mfgtool `---- The class behavior is controlled through the MFGTOOLCONFIG (analogous to PACKAGECONFIG) variable. The MFGTOOLCONFIG variable itself specifies a space-separated list of the script to enable. Following the script, you can determine the behavior of each script by providing up to two order-dependent arguments, which are separated by commas. You can omit any argument you like but must retain the separating commas. The order is important and specifies the following: 1. Extra dependencies that should be added to the do_populate_mfgtool task, if the script is enabled. 2. Extra binaries that should be added to the bundle, if the script is enabled. For example: ,----[ Defining foo.uuu.in and bar.uuu script ] | MFGTOOLCONFIG = "foo.uuu.in bar.uuu" | MFGTOOLCONFIG[foo.uuu.in] = "dep-foo1:do_deploy dep-foo2:do_deploy,file-foo1" | MFGTOOLCONFIG[bar.uuu] = "dep-bar1:do_deploy,file-bar1 file-bar2" `---- The dep-foo1:do_deploy, dep-foo2:do_deploy, and dep-bar1:do_deploy are added to do_populate_mfgtool dependencies. In addition, file-foo1, file-bar1, and file-bar2 are copied to the bundle, only if the script is enabled. During the mfgtool bundle generation, the uuu.in files are processed and some variables replaced. The variables are: - MACHINE - UBOOT_BINARY - SPL_BINARY - IMAGE_BASENAME Signed-off-by: Otavio Salvador

Merge pull request #1488 from MaxKrummenacher/master-imx-boot

2023-04-10T10:54:11+00:00

imx-boot-container: drop from machine overrides

2023-04-10T09:40:55+00:00

Moving the override from the .conf files to the common imx-base.inc and setting the use of imx-boot-container unconditionally on the used SoC makes the use of an extra override obsolete. Simply set UBOOT_PROVIDES_BOOT_CONTAINER depending on the used SoC is enough. Both the U-Boot recipe and the class implementing the logic don't need the override but only look at the variable. This also simplifies overriding the value set in imx-base.inc in an individual .conf should that be needed. Signed-off-by: Max Krummenacher

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

fsl-eula-unpack.bbclass: Update EULA for NXP release 6.1.1-1.0.0

2023-04-09T14:45:38+00:00

EULA is V42 now. Signed-off-by: Jun Zhu

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