Move build instruction into the manifest.
Add license information to the REAMDE.md.

BCS 746-000657
BCS 746-000659
BCS 746-000780

The patch code was integrated into u-boot, so the patches didn't
applied anymore.

* Name kernel recipe linux-imx
  Don't use linux-imx-kuk to allow two different entries in the
  SRCREV.conf to specify the SRCREV independently for the 5.10 and
  the 5.15 version. As the 'kuk' part is not in this branch it also
  makes sense to remove the appendix.
* defconfig from 5.10.9 after 'savedefconfig' use with 5.15 and
  savedefconfig from 5.15 kernel again
* Recipe pointing to new kernel branch
* Change the naming of the installed devicetrees with 5.15 kernel
  The subfolder and prefix is now seconorth instead of keithkoep and guf.

BCS 746-000672

We disable the creation of symlinks for the kernel.
Because of our FAT boot partition, the symlinks lead to errors
during the installation process.
Disabling the link creation fixes the installation, but leads to
another error during the pack operation of Flash-N-Go-System.
This new issue needs to be fixed separately.

The machine include was moved to seconorth but not updated
in the machines themself.

The includes have been altered and renamed to reflect the name change
to seconorth.

The kernel modules have been updated to reflect the name change to
seconorth.

The kernel includes and recipes have been renamed to seconorth.
Also the defconfigs have been moved to fitting folders.

Also updated the URLs in the recipes.

The rotation is specific for the DualEspresso and was moved to the
appropriate layer.

The Yocto build is broken because of the missing links for the Kernel.
Since removing the links from the deploy doesn't fix our issue with
the boot filesystem we reenable them.

In Yocto Kirkstone, a new way to create kernel symlinks was added.
Since we use a FAT partition for the Kernel, symlinks are not supported.
Disable the creation of symlinks.

The WIC image isn't working at the moment.
Since we don't use it anyways, we disable the creation for now.

The MACHINE_OVERRIDES for the mx8 devices have changed.
Because of the change, the search for the mx8 specific
bootscripts and configuration failed.
Renamed the folders to the correct names.

(cherry picked from commit 2a8b2f2c)

- Updated old infos
- Renamed G&F to SECO North
- Updated URLs
- Fixed some spelling errors


(cherry picked from commit 1ab3758a)

Added missing variable to machine config.
Fixed wrong override and small clean-ups in u-boot-imx.

The URL for the imx-mkimage was outdated.
Updated the config to our new Git server (git.seco.com).

- Removed old copy of the i.MX8MM config
- Clean-up of the configs and include
- Rewritten some comments to clarify old statements/questions

The imx-gpu-viv module was added to the dynamic layer to backport gpu
support to dunfell.
The backport isn't needed anymore and was removed.

Fix the indentation of the ilitek driver. It creates a warning leading
to an error and prevents the driver from being built.

The recipes in the dynamic layer haven't been updated by the conversion
script.

Bitbake throws a warning when no branch is defined for an git
repository. Added the default branch to the SRC_URI.
Also updated to the correct GPLv2 license file.

The license file for GPLv2 was renamed to GPL-2.0-only.
Changed to the new file and new hash.

* Conversion of the OVERRIDE syntax
* New folder names for NXP specific folders

For NXP changes see the new MACHINE_OVERRIDES mechanism

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6c3a8ff7

CI:package_release: Remove "GUF-" prefix from gitlab artifacts dir

BCS 746-000637

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@d809d630

manifest-CI: Refactor manifest pipeline files

* Split up build and package steps in separate files
* Add additional comments
* Add log output

BCS 746-000637

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@c917791b

Fix remote name on retrigger stage

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1ba52853

Move repositories to git.seco.com

Rename variable JENKINSGUF_SSH_PRIVATE_KEY / SSH_PRIVATE_KEY to
GITLAB_PRIVATE_KEY on this occasion, because it contains a private key
that was generated exclusively for this use case. The according public
key has been added as a deploy key in GitLab to all repositories that
this repository needs access to.

Add more detailed documentation concerning this configurationdirectly in
the gitlab-ci files.