linux/meta-freescale.git/classes, branch topic/secure-boot-rework

imx-base.inc: avoid explicit imx-boot dependency

2022-07-29T16:20:52+00:00

We shouldn't force `imx-boot` dependency for i.MX8 SoCs as many can use U-Boot mainline and those use `imx-boot-container` to generate the binary blob. We moved the backward-compatibility note, about 'imx-boot' to the 'imx-boot-container' class. Signed-off-by: Otavio Salvador

EULA,SCR: Update for NXP release 5.15.32-2.0.0

2022-07-28T18:49:29+00:00

Signed-off-by: Tom Hochstein

mfgtool-initramfs-image: Fix override of IMAGE_FSTYPES

2022-06-15T17:38:04+00:00

The fix to allow the user to override the IMAGE_FSTYPES setting for mfgtool-initramfs-image [1] does break the default behavior by turning the setting into a no-op: ``` # $IMAGE_FSTYPES [6 operations] # set? /.../sources/meta-freescale/conf/machine/include/imx-base.inc:463 # "${SOC_DEFAULT_IMAGE_FSTYPES}" # set /.../sources/poky/meta/conf/documentation.conf:214 # [doc] "Formats of root filesystem images that you want to have created." # set? /.../sources/poky/meta/conf/bitbake.conf:832 # "tar.gz" # set? /.../sources/meta-freescale/classes/mfgtool-initramfs-image.bbclass:16 # "cpio.zst.u-boot" # override[mxs-generic-bsp]:set? /.../sources/meta-freescale/classes/mfgtool-initramfs-image.bbclass:17 # "cpio.gz.u-boot" # pre-expansion value: # "${SOC_DEFAULT_IMAGE_FSTYPES}" IMAGE_FSTYPES="wic.bmap wic.gz" ``` The layer uses an extra variable SOC_DEFAULT_IMAGE_FSTYPES to override IMAGE_FSTYPES [2], so use it here. [1] 0a29050 classes: IMAGE_FSTYPES as weak variable in mfgtool-initramfs-image [2] 541b8b8 imx-base.inc: Move IMAGE_FSTYPES override to a SoC variable Signed-off-by: Tom Hochstein

recipes-bsp: drop custom deploy location for TF-A binary

2022-06-14T18:55:57+00:00

Upstream TF-A and downstream TF-A fork uses different deployment locations for results binaries, which leads to failures during image build when switching between upstream and downstream versions. Drop the custom TF-A deployment location, which is only specific to NXP downstream deployment, allowing the TF-A binaries from upstream and downstream to be picked up from the same location, namely - image deployment folder. Signed-off-by: Andrey Zhizhikin

layer-wide: define configurable default TF-A provider

2022-06-14T18:51:40+00:00

TF-A package can have several providers: upstream TF-A implementation, or NXP downstream fork. Functionality to switch this provider, and to select which package shall be included into the target image is missing in the layer however, defaulting the usage of the layer to NXP downstream fork only. Introduce the Default TF-A Provider define, make it overridable, and default it to NXP downstream fork. This allows user to re-define the package name later shall they choose to integrate upstream TF-A package instead. Current upstream TF-A version (v2.7) does not support HAB feature of i.MX8M family, see [1]. If the upstream TF-A version is chosen, then HAB will not be available for all SoCs that are opting-in. This is indicated in the comment where default TF-A provider variable is set. This might change with future TF-A release, so later it can be revised and statement in include file can be potentially removed. Signed-off-by: Andrey Zhizhikin Link: [1]: https://lists.trustedfirmware.org/archives/list/tf-a@lists.trustedfirmware.org/message/5UYYI4CNLQ5OWWHU466JBK6I5QIQ2VRS/

Merge pull request #1104 from dimonoff/master

2022-06-13T22:26:50+00:00

classes: mfgtool-initramfs-image use weak variable for IMAGE_FSTYPES

classes: IMAGE_FSTYPES as weak variable in mfgtool-initramfs-image

2022-06-10T01:42:37+00:00

With `IMAGE_FSTYPES` weak variable, we are able to use `cpio.gz` and generate fsl-image-mfgtool-initramfs as KERNEL_IMAGETYPES = "fitImage". This weak variable allows use to choose a suitable values for IMAGE_FSTYPES. (see from poky: image_types.bbclass)

kernel-itbimage: delete this bbclass

2022-06-09T10:08:58+00:00

It is no longer used. Signed-off-by: Thomas Perrot

EULA,SCR: Update for NXP release 5.15.5-1.0.0

2022-05-10T15:19:44+00:00

Signed-off-by: Tom Hochstein

imx-boot-container: resurrect imx-boot symlink

2022-04-26T10:08:59+00:00

Having a symlink named 'imx-boot' allows to have the consumers of the boot container, e.g. wic to be oblivious on who created the bootcontainer. Signed-off-by: Max Krummenacher