| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| | |
imx-boot-container: don't overwrite ATF_MACHINE_NAME
|
| |/
|
|
|
|
|
| |
If ATF_MACHINE_NAME is set in local.conf this assignment overwrites the
preset. Use a default assignment instead
Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
|
| |\
| |
| | |
wayland-protocols: Refresh alpha-compositing and hdr10 patches
|
| |/
|
|
|
|
|
|
|
| |
After upgrading to wayland-protocols 1.48, refresh
0001-unstable-Add-alpha-compositing-protocol.patch and
0002-unstable-Add-hdr10-metadata-protocol.patch so they apply cleanly
after the meson.build protocol list schema changed.
Signed-off-by: Franz Schnyder <franz.schnyder@toradex.com>
|
| | |
|
| |\
| |
| | |
Consolidate recipe content from meta-freescale-distro
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |\
| |
| | |
backport: Modernise the backport workflow
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The workflow used the deprecated zeebe-io/backport-action@v0.0.4 and
relied on the default GITHUB_TOKEN, which is read-only by default, so it
could not actually create the backport branches and pull requests.
Switch to the maintained korthout/backport-action@v4, grant the
required contents and pull-requests write permissions, and bump
actions/checkout to v4. Trigger on both 'closed' and 'labeled' so a
'backport <branch>' label backports automatically on merge whether it
was added before or after merging, with no manual /backport comment.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |\ \
| |/
|/| |
[RFC] Distro to fragments
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
distro/fsl and distro/fslc were referenced as one-of options but never
existed as real fragments; they were a leftover from an older format
where the distro variable drove a bitbake-setup template name.
Replace them with the built-in distro/ fragment prefix (distro/poky and
distro/nodistro), which maps directly to the DISTRO variable via the
OE_FRAGMENTS_BUILTIN mechanism. No fragment files are needed; the
built-in handler sets DISTRO = <value> from the fragment name.
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replace the old display-backend-only and distro-bundled preset
configurations with ones that explicitly select a BSP fragment
alongside the display backend:
- fslc-framebuffer: bsp/fslc + framebuffer
- nxp-framebuffer: eula/accept-fsl-eula + bsp/nxp + framebuffer
- fslc-eula-framebuffer: eula/accept-fsl-eula + bsp/fslc + framebuffer
The phantom fsl preset (no fragments) and the broken accept-fsl-eula
preset (wrong fragment path freescale-layer/accept-fsl-eula) are
removed. The old fsl-{wayland,xwayland,framebuffer} and standalone
{wayland,xwayland,framebuffer} presets are removed; they did not
express a BSP choice and are superseded by the new presets.
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
BSP selection (linux-fslc vs linux-imx, u-boot-fslc vs u-boot-imx)
previously required a separate DISTRO from meta-freescale-distro.
These fragments let users express the same choice with DISTRO = "poky"
without depending on a dedicated distro layer.
The fslc fragment covers the mainline-tracking BSP (linux-fslc,
u-boot-fslc). The nxp fragment covers the NXP downstream BSP
(linux-imx, u-boot-imx) and carries the provider preferences and
GStreamer version pins previously found in fsl-base.inc.
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
fslc-x11 was the only display backend distro with no fragment
equivalent; users migrating from meta-freescale-distro had no
way to replicate its DISTRO_FEATURES adjustments with the new
fragment-based workflow.
Signed-off-by: Daiane Angolini <daiane.angolini@foundries.io>
|
| |\ \
| | |
| | | |
imx-mkimage: imx-boot: Specify build dependencies in DEPENDS
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Dependencies listed via do_compile[depends] are invisible to the SBOM script
from OpenEmbedded.
List the build-time dependencies for imx-boot in the DEPENDS variable instead,
while preserving the required task order, allowing these components to be
automatically included in the imx-boot SBOM.
Signed-off-by: Leonardo Costa <leonardo.costa@toradex.com>
|
| |\ \
| | |
| | | |
vulkan-wsi-layer: Fix build issue with GCC 16
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'__STDC_VERSION__' is predefined by the compiler in C++ mode. Redefining
it triggers '-Wbuiltin-macro-redefined', which with '-Werror' fails the
build with GCC 16.
error: '__STDC_VERSION__' defined [-Werror]
As suggested in the Vulkan WSI Layer issue tracker, add a C++ guard
before the __STDC_VERSION__ define.
Signed-off-by: Franz Schnyder <franz.schnyder@toradex.com>
|
| |\| |
| |/
|/| |
imx-atf: Fix build failure with GCC 16.1.0
|
| |/
|
|
|
|
|
|
|
|
| |
The scmi_imx9 source declares a tmp pointer that is never read.
The newer GCC version 16.1.0 treats the unused pointer as
-Wunused-but-set-variable. With -Werror, this breaks the build.
Add a patch to remove the unused tmp pointer.
Signed-off-by: Franz Schnyder <franz.schnyder@toradex.com>
|
| |\
| |
| | |
wayland-protocols: fix non target builds
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was found that at least in some configurations a nativesdk
(and likely a native) build failed as the wayland-protocols
artefacts weren't found.
Don't apply the patches or change the PACKAGE_ARCH if not building
for target.
See also meta-freescale issue #2525.
Fixes: 48dfc5f5f33c ("wayland-protocols: use upstream repo with NXP downstream patches")
Signed-off-by: Max Krummenacher <max.oss.09@gmail.com>
|
| |\
| |
| | |
kernel-module-nxp-wlan: fix device wakeup capability of mwifiex driver
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The device is always advertised as being wakeup capable, even if no
interrupt line has been allocated for it.
Add a patch to Initialize the device only as wakeup capable if an
interrupt has been registered.
Signed-off-by: Franz Schnyder <franz.schnyder@toradex.com>
|
| |\ \
| | |
| | | |
Ethos-U update and compile fix
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Markus Niebel <Markus.Niebel@ew.tq-group.com>
|