linux/meta-freescale.git/classes, branch topic/add-initial-uuu-scripts

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

2023-04-01T20:37:43+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-01T20:37:43+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

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

imx-boot-container: add copy of soc-specific firmware

2022-11-26T17:45:34+00:00

- Currently only the DDR firmware files are copied - i.MX 8MQ SoC also requires either HDMI or DP firmware - Refactor the copy from deploydir to the U-Boot build folder to be generic to all firmware files Signed-off-by: Gary Bisson

bb.data.update_data is deprecated

2022-11-14T23:27:09+00:00

EULA,SCR: Update for NXP release 5.15.52-2.1.0

2022-10-23T15:43:18+00:00

Signed-off-by: Tom Hochstein

classes/fsl-dynamic-packagearch: Add multilib support

2022-09-16T19:50:13+00:00

Currently, the class doesn't support multilib image/SDK generation for packages built for MACHINE_SOCARCH with MULTILIB support and this commit fixes this. To reproduce the error, add to local.conf: require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE:virtclass-multilib-lib32 = "armv7athf-neon-vfpv4" IMAGE_INSTALL_append = "lib32-libusb1" Build image with: 'bitbake core-image-minimal' The build will fail during do_rootfs/do_populate_sdk on lib32-wayland-protocols package.

fsl-eula-unpack.bbclass: Expose a function for reuse

2022-08-10T15:59:34+00:00

Expose find_nxp_eula_licenses for others to use. Signed-off-by: Tom Hochstein