At the moment we don't want to upgrade to the 2021.10 version from
the OpenST Linux Kirkstone release. Therefore let's add a copy
of the legacy recipe from Dunfell for now.

At the moment we don't want to upgrade to the 2.6 version from
the OpenST Linux Kirkstone release. Therefore let's add a recipe
for the legacy version from Dunfell for now.

Add another reference to the path in Kirkstone so we can be compatible
with both, old and new releases.

Use the new SPDX names as done in later Yocto releases like Kirkstone.
A separate patch applied for Dunfell that backports the new license
names makes sure that we stay compatible with both releases.

Use the new SPDX names as done in later Yocto releases like Kirkstone.
A separate patch applied for Dunfell that backports the new license
names makes sure that we stay compatible with both releases.

We override the default value of UBOOT_ENTRYPOINT set in meta-freescale
to get rid of the alignment kernel boot warning. For this to work in both,
Dunfell and Kirkstone, we need to apply some fixes.

This adds the necessary changes fpr compatibility with the v2.6-based
TF-A code from meta-freescale's imx-atf.

At the same time we add a compat bbappend for dunfell to stay with
the previously used TF-A version.

* Remove deprecated patches
* Use default branch and ref from base repo
* Specify UART for i.MX8MM SoM in machine config
* Specify ATF_PLATFORM for i.MX8MM SoM in machine config

Copied from the imx8mm-evk configuration in meta-freescale.

Weaken the include for the path in Dunfell releases and add another
reference to the path in Kirkstone so we can be compatible with both
releases.

In commit

ce868964 ("meta-ktn-imx: u-boot-ktn-common.inc: Remove unneeded do_compile() override")

we removed the do_compile() override, but this is still needed, at
least in Dunfell. Revert this.

This is useful for backwards compatibility with older releases such as
Dunfell which might need additional changes/backports.

Use the new SPDX names as done in later Yocto releases like Kirkstone.
A separate patch applied for Dunfell that backports the new license
names makes sure that we stay compatible with both releases.

These changes are already available in later releases like Kirkstone.
Let's apply this onyl for Dunfell.

In the past we copied content from poky.conf into our own distro
config. This bears the problem of redundant configuration. Let's
include poky.conf and only overwrite values where needed.

If we need a custom distro config based on ktn.conf (for customer
projects, etc.) we should create a copy of ktn.conf in the custom
layer and change the content as needed.

This also makes use of the BASE_SERIES variable passed via
local.conf to determine for which Yocto series/release we are
building.

Kas doesn't support referencing env variables as we assumed it would.
Rewrite the config to take account of this.

Add abstraction for Yocto base series/release in KAS config and CI

See merge request sw/ked/meta-kontron!3

Use job matrix and YOCTO_SERIES env variable for build jobs.

In order to support multiple Yocto releases and switch between them,
use an env variable YOCTO_SERIES to set the default refspec. This
value is also passed to Bitbake in the BASE_SERIES variable.

With this we can create series conf files like dunfell.yml to select
a certain Yocto base release/series.

Layer cleanup and fixes to prepare for Kirkstone compatibility

See merge request sw/ked/meta-kontron!2

This fixes the following type of warning:

    [...] += is not a recommended operator combination, please replace it

This also fixes the warning about the deprecated git protocol
for GitHub.

This fixes the following type of warning:

    [...] += is not a recommended operator combination, please replace it

This fixes the following type of warning:

    [...] += is not a recommended operator combination, please replace it