linux/meta-freescale.git/conf/machine, branch rework/remove-mfgtool-specific-recipes

linux--mfgtool, u-boot--mfgtool: Remove specific recipes

2023-04-12T23:09:28+00:00

The use of a specific recipes are not need anymore. For the U-Boot specific case, the UBOOT_CONFIG mechanism allows multiple binaries using different configurations so we can remove this recipes and default to the IMX_DEFAULT_BOOTLOADER as provider. The Linux specific case is completely unnecessary as the USB gadget is supported in all versions we support. 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

imx-base.inc: dynamically choose if boot container should be used

2023-04-12T16:10:00+00:00

The boot container should be used only if we're not using u-boot-imx as IMX_DEFAULT_BOOTLOADER. Signed-off-by: Otavio Salvador

imx-base.inc: fix typo in a comment

2023-04-12T16:10:00+00:00

Signed-off-by: Otavio Salvador

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-base.inc: Fix 8M overrides

2023-04-07T15:39:33+00:00

8MQ video is not working. The problem is traced to a change in `weston.ini`, specifically that the file is now from OE-Core layer instead of meta-freescale. This problem is traced to the move of the `imx-boot-container` override [1], specifically that the override was moved with a trailing `:` that inserts an empty override. ``` MACHINEOVERRIDES="aarch64:armv8a:use-nxp-bsp:imx-generic-bsp:imx-nxp-bsp:imxdrm:imxvpu:imxgpu:imxgpu3d:imxvulkan:mx8-generic-bsp:mx8-nxp-bsp:mx8m-generic-bsp:mx8m-nxp-bsp:mx8mq-generic-bsp:mx8mq-nxp-bsp:imx-boot-container::imx8mq-evk" ``` [1] https://github.com/Freescale/meta-freescale/commit/0ee4cb24eba5171da75ab8eeb72c7eab06083339 Signed-off-by: Tom Hochstein

Move imx-boot-container MACHINEOVERRIDES to extender

2023-03-29T17:05:51+00:00

The imx-boot-container is SoC specific so it should not be set inside the machine but in the BSP basic settings. This commit moves it to the imx-base.inc file as the bootloader recipe can still opt to not inherit the class specifically. Signed-off-by: Otavio Salvador

Remove conditional imx-boot-container MACHINEOVERRIDES

2023-03-29T16:57:49+00:00

The imx-boot-container MACHINEOVERRIDES allows the bootloader recipe to enable the binman support for the SoCs which uses it. The conditional belongs to the bootloader recipe and can be removed from machines. Signed-off-by: Otavio Salvador

gst-devtools: Add recipe for 1.20.3.imx

2023-03-12T01:48:48+00:00

Signed-off-by: Khem Raj

gstreamer1.0-omx: Add 1.20.3.imx recipe