ae49a255fa
Do not evaluate TRUSTFENCE_SIGN_MODE on conditions where the sign mode is not relevant: 1) U-Boot binary file should be signed directly after building it when simple U-Boot images are used, but it should not be signed when imx-boot bundled images are used. For those, the signing process is performed later over the whole imx-boot bundled binary file on a different recipe. We use BOOTLOADER_IMAGE_RECIPE variable to evaluate this distinction. BOOTLOADER_IMAGE_RECIPE is set to "u-boot" by default and is set to "imx-boot" on ccimx8x and ccimx8mn machine configuration files. 2) For signing imx-boot images we should treat differently those images that include the RAM configuration in their name and those that don't, as we do for the rest of the tasks in the same recipe. We can ignore the sign mode method in this case. https://jira.digi.com/browse/DEL-7023 Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com> |
||
|---|---|---|
| .. | ||
| alsa-state | ||
| digi-sc-firmware | ||
| firmware-atheros | ||
| firmware-imx | ||
| firmware-qualcomm | ||
| formfactor | ||
| imx-atf | ||
| imx-mkimage | ||
| imx-seco | ||
| imx-vpu | ||
| trustfence-cst | ||
| u-boot | ||
| usbutils | ||