| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The series [1] changed the way sources are fetched/unpacked and
S needs to follow that. Additionally for git repos it moved away from
having 'git/' as the checkout directory.
This has been partly tested by building weston based image for
imx6/imx6ull/imx7/imx8/imx8mm/imx8mp/imx95 based images.
E.g. none of the recipes specific for qoriq is built time tested.
As walnascar is no longer compatible with master/whinlatter drop
it from LAYERSERIES_COMPAT.
[1] https://lore.kernel.org/openembedded-core/20250616095000.2918921-1-alex.kanavin@gmail.com/
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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 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>
|
|
|
|
|
|
|
| |
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>
|
|
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>
|