Merge in ICO/coreos from master to kirkstone-next
* commit 'dd11a6ccbc1f4d6a7549b9e3807847c860c3cb0c':
chore: update all external meta-layers
feat(cn913x): cleanup: remove wifi related things
fix(bblayers.conf.sample): fix metalayer name for meta-lts-kernel-mixin
feat(eagle40-03): switch to kernel v6.6 for eagle-40-03
feat(meta-lts-mixins): add meta-lts-mixins layer
fix(openembedded-core): update to latest version
fix(netmodule-hw34): fix consoles definitions
When introducing CN913x devices by using the meta-belden-marvell-bsp layer
trusted-firmwarre-a recipe was copied from meta-arm and modified. Now the
original recipe is used from meta-arm and the changes were put into a
bbappend.
Also trusted-firmware-a version changed from 2.3 to 2.6.
The meta-belden-coreos-layer will contain changes that are specfic to a release
version. In this case kirkstone. It holds adjustments and/or fixes that will
not go into upstream.
This commit contains a bugfix for libnl.
BREAKING CHANGE: bblayers.conf / bblayers.conf.sample of project
using CoreOS should be adapted to use external-layers instead
of layers for each moved layers
The layer.conf of meta-belden-coreos now depends on:
- meta-virtualization (needed for podman)
- meta-webserver (needed for cockpit)
The bblayers.conf.sample file now enable theses two layers and theirs dependancies