summaryrefslogtreecommitdiffstats
path: root/dynamic-layers/arm-toolchain
Commit message (Collapse)AuthorAgeFilesLines
* imx-oei: provide virtual/imx-oeiHiago De Franco2025-03-241-0/+2
| | | | | | | | | | | Some hardware vendors provide a customized Optional Executable Image (OEI) with changes specific to their boards (e.g. Toradex SMARC i.MX95). Add a virtual provider to avoid conflicts between the OEI recipes from other layers. This follows the pattern used for the related imx-system-manager. Signed-off-by: Hiago De Franco <hiago.franco@toradex.com>
* imx-system-manager: use `MACHINE_ARCH` as `PACKAGE_ARCH`Alexander Stein2024-10-231-0/+2
| | | | | | | The recipe build changes depending on the `SYSTEM_MANAGER_CONFIG` value, which is machine-specific. Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
* imx-system-manager: import recipe from meta-imxMax Krummenacher2024-10-222-0/+65
| | | | | | | | | | imx-system-manager at 6.6.36-2.1.0 NXP BSP release. This provides among others the DDR configuration which may require machine dependent configurations. Thus additionally add a virtual provider. Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
* imx-oei: use `MACHINE_ARCH` as `PACKAGE_ARCH`Alexander Stein2024-09-131-0/+2
| | | | | | | The recipe build changes depending on the `OEI_BOARD` value, which is machine-specific. Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
* imx-oei: move to dynamic-layers and add arm-toolchainHiago De Franco2024-09-081-0/+57
The recipe depends on meta-arm-toolchain, therefore it should be on dynamic-layers/arm-toolchain folder. Create it and make the necessary changes for conf/layer.conf. Fixes: 61beaf5861f2 ("recipes-bsp: introduce imx-oei recipe") Signed-off-by: Hiago De Franco <hiago.franco@toradex.com>