| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
Move the recipe into meta-freescale as part of consolidating all
recipe content into a single layer. meta-freescale-distro is becoming a
thin backward-compatibility layer that only keeps the distro definitions
for the wrynose LTS lifetime and is no longer used for recipe development.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
| |
i.MX 8MQ, 8MM: Bump 25.09.00 -> 26.03.00
i.MX 8MP , 8MNULite, 8MN: Bump 25.09.00 -> 26.03.00
i.MX95: Bump 25.12.00 -> 26.03.00
i.MX952: 25.12.00
i.MX 8ULP, 93: Bump 25.12.00 -> 26.03.00
Signed-off-by: Zelan Zou <zelan.zou@nxp.com>
|
| |\
| |
| | |
Upstream packages base on lf 6.12.49 2.2.0
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
i.MX 8MQ,8MM,8MP,8MNULite,8MN: 25.03.00 -> 25.09.00
i.MX95,93: 25.06.00 -> 25.12.00
i.MX8ULP:25.03.00 -> 25.12.00
New added: i.MX943: 25.12.00
Signed-off-by: Zelan Zou <zelan.zou@nxp.com>
|
| | |
| |
| |
| |
| |
| |
| | |
Add support for mx943-nxp-bsp for imx-mcore-demos
Based on 6.12.49-2.2.0 NXP BSP release
Signed-off-by: Benjamin Missey <benjamin.missey@non.se.com>
|
| |/
|
|
|
|
|
| |
Import imx-mcore-demos version 25.12.00 from meta-imx.
Based on 6.12.49-2.2.0 NXP BSP release
Signed-off-by: Benjamin Missey <benjamin.missey@non.se.com>
|
| |
|
|
| |
Signed-off-by: Zelan Zou <zelan.zou@nxp.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
| |
For 7D there are no .elf files and there is a build break:
```
| install: cannot stat '.../imx7d-sabresd-m4-freertos-1.0.1/*.elf': No such file or directory
```
Fixes #2056.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
|
|
|
| |
The demo extension is overridable so the new install behavior needs to
use the variable.
Fixes #2056.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
|
|
| |
imx95: 2.16.001 -> 24.12.00
Signed-off-by: Zelan Zou <zelan.zou@nxp.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This pulls in all other dev packages. It looks like the unversioned
shared object is not (no longer?) needed, i.e. the driver points to
the versioned object.
| readelf --dynamic opt/imx8-isp/bin/daA3840_30mc.drv
| ...
| 0x000000000000000e (SONAME) Library soname: [libdaA3840_30mc.so.1]
(/usr/lib/libdaA3840_30mc.so is the only file in the -dev package.)
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Drop md5sum check as no longer mandated in Yocto Project.
SRC_URI[md5sum] used to also be commonly used, but it is deprecated and
should be replaced by SRC_URI[sha256sum] when updating existing recipes. See:
- https://docs.yoctoproject.org/dev/singleindex.html#fetching-code
- https://docs.yoctoproject.org/dev/singleindex.html#src-uri-checksum-behaviour
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
| |
Add new recipe for imx-m7-demos and update README.
Signed-off-by: Hiago De Franco <hiago.franco@toradex.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Update to the new NXP BSP 6.6.23-2.0.0.
- Replace m33 demos 2.14.1 and 2.15.000 with 2.16.000 version.
- Replace m4 demos 2.14.0 and 2.14.1 with 2.16.000 version, and fix
2.9.0 license checksum.
- Replace m7 demos 2.14.0, 2.14.1 and 2.15.000 with 2.16.000 version.
- Fix SRC_URI from imx-mcore-demos wich was causing the link to have an
extra '/', making the download fail.
Signed-off-by: Hiago De Franco <hiago.franco@toradex.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Update M-core demos to be aligned to the NXP BSP LF6.6.3-1.0.0
release.
Changes:
- i.MX95: add (m7 2.15.000)
- i.MX93: update (m33 2.14.2 -> 2.15.000
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
|
| |
|
|
|
|
|
|
| |
There is a newer version of m4 demos 2.14.1 for imx8mm.
Remove supporting imx8mm from m4 2.14.0.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
|
| |
|
|
|
|
|
|
|
| |
The README file shows the mcore-demos version for each supported SoC.
This patch updates the version, basically it includes 6.1.55-2.2.0, but
also fix some other versions.
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| |
|
|
|
|
| |
Add a new version: 2.14.2.
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Update versions of M7 demos to be aligned with NXP BSP LF6.1.36-2.1.0.
For imx8mn:
- 2.13.0 -> 2.13.1
For imx8mp:
- 2.13.1 -> 2.14.1
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
|
| |
|
|
|
|
|
|
|
| |
Update versions of M4 demos to be aligned with NXP BSP LF6.1.36-2.1.0.
- remove obsolete 2.13.0
- add 2.14.1
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
|
| |
|
|
|
|
| |
Update the version to be aligned with NXP BSP LF6.1.36-2.1.0.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@foundries.io>
|
| |
|
|
|
|
| |
Replace `base_libdir` with `nonarch_base_libdir`
Signed-off-by: Valentin Jec <valentin.jec@nxp.com>
|
| |
|
|
| |
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| |
|
|
| |
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| |
|
|
| |
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This rework the recipes making use of new imx-generic-bsp override; it
has been applied to:
- alsa-state
- firmware-imx
- imx-kobs
- imx-test
- imx-uuc
- linux-fslc
- linux-fslc-lts
- packagegroup-fsl-mfgtool
- u-boot-fslc
- uuu
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Essentially, we extend the overrides to a generic-bsp, nxp-bsp, and
mainline-bsp.
So, for example, the mx8mq override is split into:
- imx-generic-bsp: compatible with every i.MX SoC and both BSP variants
- imx-nxp-bsp: compatible with every i.MX SoC but specific to NXP BSP
- imx-mainline-bsp: compatible with every i.MX SoC but specific to Mainline BSP
- mx8-generic-bsp: compatible with every i.MX8 SoC and both BSP variants
- mx8-nxp-bsp: compatible with every i.MX8 SoC but specific to NXP BSP
- mx8-mainline-bsp: compatible with every i.MX8 SoC but specific to Mainline BSP
- mx8m-generic-bsp: compatible with every i.MX8M SoC and both BSP variants
- mx8m-nxp-bsp: compatible with every i.MX8M SoC but specific to NXP BSP
- mx8m-mainline-bsp: compatible with every i.MX8M SoC but specific to Mainline BSP
- mx8mq-generic-bsp: compatible with every i.MX8MQ SoC and both BSP variants
- mx8mq-nxp-bsp: compatible with every i.MX8MQ SoC8 but specific to NXP BSP
- mx8mq-mainline-bsp: compatible with every i.MX8MQ SoC but specific to Mainline BSP
The extender mechanism is responsible for extending the override list to
include the generic overrides. We can then use the three different
variants to handle the metadata correctly.
Generically speaking, the conversion mainly was automated (with a lot of
back and forth until getting it right).
To convert an existing layer, the following script can be used:
```sh
git ls-files classes recipes-* \
| xargs sed -i \
-e 's,:\(mx[6-8]\w*\),:\1-nxp-bsp,g' \
-e 's,(\(mx[6-8]\w*\)),(\1-nxp-bsp),g' \
-e 's,\(mx[6-8]\w*\)|,\1-nxp-bsp|,g' \
-e 's,|\(mx[6-8]\w*\)),|\1-nxp-bsp),g' \
\
-e 's,:\(mx[5s]\w*\),:\1-generic-bsp,g' \
-e 's,(\(mx[5s]\w*\)),(\1-generic-bsp),g' \
-e 's,\(mx[5s]\w*\)|,\1-generic-bsp|,g' \
-e 's,|\(mx[5s]\w*\)),|\1-generic-bsp),g' \
\
-e 's,:\(vf\w*\),:\1-generic-bsp,g' \
-e 's,:\(vf[56]0\w*\),:\1-generic-bsp,g' \
-e 's,\(vf\w*\)|,\1-generic-bsp|,g' \
-e 's,|\(vf\w*\)),|\1-generic-bsp),g' \
-e 's,\(vf[56]0\w*\)|,\1-generic-bsp|,g' \
-e 's,|\(vf[56]0\w*\)),|\1-generic-bsp),g' \
\
-e 's,:\(imx\) ,:\1-nxp-bsp ,g' \
-e 's,(\(imx\)),(\1-nxp-bsp),g' \
-e 's,\(imx\)|,\1-nxp-bsp|,g' \
-e 's,|\(imx\)),|\1-nxp-bsp),g'
for d in $(find -type d | egrep '/mx[6-8]w*'); do
git mv $d $d-nxp-bsp
done
for d in $(find -type d | egrep '/imx$'); do
git mv $d $d-nxp-bsp
done
for d in $(find -type d | egrep '/mx[5s]w*'); do
git mv $d $d-generic-bsp
done
```
Fixes: #791.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
MACHINE_SOCARCH is not universally defined and results in errors on
non-fsl machines.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
openembedded-core, commit 5bf3e447d2 ("package: Add sanity check for
allarch packagegroups") added a check which now emits an error.
Fix that.
| ERROR: packagegroup-fsl-isp-1.0-r0 do_package_write_ipk: An allarch packagegroup shouldn't depend on packages which are dynamically renamed (basler-camera to libdaa3840-30mc1)
| ERROR: packagegroup-fsl-isp-1.0-r0 do_package_write_ipk: An allarch packagegroup shouldn't depend on packages which are dynamically renamed (basler-camera-dev to libdaa3840-30mc-dev)
| ERROR: packagegroup-fsl-isp-1.0-r0 do_package_write_ipk: An allarch packagegroup shouldn't depend on packages which are dynamically renamed (basler-camera-dbg to libdaa3840-30mc-dbg)
| ERROR: packagegroup-fsl-isp-1.0-r0 do_package_write_ipk: An allarch packagegroup shouldn't depend on packages which are dynamically renamed (basler-camera-dev to libdaa3840-30mc-dev)
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
| |
|
|
|
|
|
| |
NXP has dropped support for qcacld, plus the code is not compatible
with 5.10, so drop BSP support.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
| |
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
Add a packagegroup to support opencv i.MX packages.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
|
| |
|
|
|
|
| |
Add a packagegroup to support ISP and Basler Camera.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
|
| |
|
|
| |
Signed-off-by: Simone Agresta <simone.agresta@bticino.it>
|
| |
|
|
|
|
|
|
| |
These modules rdepends on qca-tools which is currently arm/aarch64 and
glibc specific, therefore mark the recipes depending on qca-tools so as
well.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
| |
The prebuilt tools are for glibc based targets
no point in building for musl
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|