| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
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>
(cherry picked from commit 7cf349d287a9d6eece4320cf487fc804917c2077)
|
| |
|
|
|
|
|
|
| |
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>
(cherry picked from commit 7db4404952e163fa5ee8c88adc21bff213b04b41)
|
| |
|
|
|
|
|
|
|
|
|
| |
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>
(cherry picked from commit 825d6a47b4fbfdc7afc8eabc13b2c4463e0c4fcc)
|
| |
|
|
|
|
|
|
| |
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>
(cherry picked from commit b650de0478c9a8e6545a23dede75036c29b293d9)
|
|
|
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>
(cherry picked from commit 07931ef7fdf35ca2956481387f8476cd531a9048)
|
