Enabled wireguard in defconfig. Removed wireguard-modul dependencies for
wireguard-tools since wireguard is already integrated in kernel 5.10.

BCS 746-000655

BCS 746-000629

BCS 746-000629

BCS 746-000629

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/77ada04ca6e1517ef1cca903a804880f5aea8843

Fix the job names for deploy

The variable use in the deploy name was not replaced in the UI. This
hopefully cleansup the UI, and uses the project root variable in the job
only.

BCS 746-000629

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/a51f53d5c7068328b93ad1d66dec44d66f3b9459

CI: Remove 'garz-fricke' references from CI to prepare for group rename

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/a35820b21ba2718e48e56892d87000e4efbd21f0

deploy_gitlab_ci: revert trigger pipeline on integration branch

Explicitly triggering a pipeline in the target repository does not work
easily from this place because we would have to distinguish between the
manifest (which uses branch pipelines) and the sub-projects (which use
merge request pipelines). This separation should not be hard-coded here,
so we move the decision whether or not to run a pipeline to the
.gitlab-ci.yml file of the target. Reverting these two commits:

63279799336fa99bb8bbb908084017173ed44802
    deploy_gitlab_ci: trigger pipeline only if it has not run before

dfc6204abcdfce7f7ee51ee2127500f8aecfaafa
    deploy_gitlab_ci: trigger pipeline on integration branch

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/faf2073101235c05c0bdcb7fd78895a2b86a4eeb

md5: Fixed invalid encoding in open

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/63279799336fa99bb8bbb908084017173ed44802

deploy_gitlab_ci: trigger pipeline only if it has not run before

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/4c6b46212830fe936c684866f096ba63946f95b7

wait_until_merge_status_is_set: always query merge request

The function used to rely on the given merge request object without
checking its current state. If the given object was not in one of the
"unchecked" states, it returned immediately. The state, however, could
have changed between its last query and the call of this function, so
it now checks the state first before deciding anything.

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/dfc6204abcdfce7f7ee51ee2127500f8aecfaafa

deploy_gitlab_ci: trigger pipeline on integration branch

Also did some white space changes like yamlint told me.
The multiproject synthax does not allow variables, so that needs to be
changed immidiatly after the rename.

BCS 746-000629

We disabled SSC for video pll because it leads to problems with the
display signal over mipi and lvds.
This is fixed now in the kernel with
https://gitlab.com/garz-fricke/kernel/linux-imx-kuk/-/commit/897419f00f9913b9fe5d7aec5ac0a1284e7b130a

This patch removes the patch the disabled SSC in u-boot and enables it
again for the VIDEO_PLL1

BCS 746-000626

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/a35820b21ba2718e48e56892d87000e4efbd21f0

deploy_gitlab_ci: revert trigger pipeline on integration branch

Explicitly triggering a pipeline in the target repository does not work
easily from this place because we would have to distinguish between the
manifest (which uses branch pipelines) and the sub-projects (which use
merge request pipelines). This separation should not be hard-coded here,
so we move the decision whether or not to run a pipeline to the
.gitlab-ci.yml file of the target. Reverting these two commits:

63279799336fa99bb8bbb908084017173ed44802
    deploy_gitlab_ci: trigger pipeline only if it has not run before

dfc6204abcdfce7f7ee51ee2127500f8aecfaafa
    deploy_gitlab_ci: trigger pipeline on integration branch

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/faf2073101235c05c0bdcb7fd78895a2b86a4eeb

md5: Fixed invalid encoding in open

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/63279799336fa99bb8bbb908084017173ed44802

deploy_gitlab_ci: trigger pipeline only if it has not run before

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/4c6b46212830fe936c684866f096ba63946f95b7

wait_until_merge_status_is_set: always query merge request

The function used to rely on the given merge request object without
checking its current state. If the given object was not in one of the
"unchecked" states, it returned immediately. The state, however, could
have changed between its last query and the call of this function, so
it now checks the state first before deciding anything.

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/dfc6204abcdfce7f7ee51ee2127500f8aecfaafa

deploy_gitlab_ci: trigger pipeline on integration branch

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/669113ff5a25b7cfae84220d5e3beee1b3bc7fb1

gitlab-ci: upgrade python image to 3.9

Fix pylint errors introduced with new pylint version:
* unspecified-encoding: explicitly set encoding when opening a file
* assigning-non-slot: use "set_reference()" function instead of assigning
  a value to the "reference" attribute
* unused-variable: remove "e" variable on exceptions when not referenced

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/1ef9007ed938d83fd7ed788a7fd7f7d4acd11ec2

accept_merge_request: explicitly remove source branch

A bug in python-gitlab > 2.7.0 [1] brought this up: In the past we
relied on the merge request's setting, whether the source branch should
be deleted or not after a merge. Since we're using the API's merge
function in a fully automated task, however, the branch should always be
deleted. Add the according argument explicitly.

[1]: https://github.com/python-gitlab/python-gitlab/issues/1750

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/79e3437dc264bd60253b2ca26397016df2606756

accept_merge_request: refactoring

* Combine two return statements into one.
* Switch if statement order to remove else branch.

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/a139ffb573adaeb54e3435dc3fd1276789f0a078

gitlab-ci: update bool values to YAML 1.2 spec

The outdated YAML 1.1 specification allowed values like 'yes' or 'no'
for boolean fields [1]. The newer spec 1.2 allows only 'true' and
'false' [2], so we update them to be conform with it.

[1]: https://yaml.org/type/bool.html
[2]: https://yaml.org/spec/1.2.2/#10212-boolean

There is a new repo containing the sources for this touch driver.
This change now pulls everything from there.

BCS 746-000628

The change is already merged in u-boot v2020.04

BCS 746-000495

Disabled SSC for video pll because it leads to problems when converting
lcdif to mipi signals on imx8mp. An alternative SSC method will be required
in the future.

BCS 746-000495

Tobias Kahlki authored 3 years ago and Jonas Höppner committed 3 years ago

The service for loading the sdma firmware was replaced by a udev rule.

BCS 746-000514
BCS 746-000503

Adapt defconfig: Select the correct bootlogo and enable bootlogo rotation

Set the rotation hardcoded ( for now) for mx8mplus.

Instead of defining a custom job which mirrors the build result from the
manifest, use the GitLab multi-project feature to trigger a downstream
job in the manifest.

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/cb831c1a4f1d590a66ed9033f72a24bb8ac8d661

check_pipeline_status: add parameter for ref

Remove the trigger source parameter again because it did not serve the
use case. Add ref parameter instead.

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/c16ae4ea464e3af84baaaea65c406cba55643b4d

check_pipeline_status: add parameter for trigger source

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/d321e1f616f8672340e86486a79b66f3769febec

Add an addtional flag to enable AlphaPlan FWR generation

BCS DevOps-000023 DevOps-000024

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/9befb0ed5635a3fa43a1deebcde6f4ee34c9184e

Run pylint in the yocto build image also, to check if all py deps are installed

* Enabled mainline driver for SN65DSI84 bridge

BCS 746-000506 746-E00063

KERNEL_DEVICETREE contains a list of devicetrees. Now the first of those
is used as default devicetree for the boot script instead of a hardcoded
one.

Add machine conf.
Adapt u-boot branch for new machine.
Adapt imxmkimage branch for new machine.
Adapt kernel receipe.

* Fixes sporadic freezes during the boot process on trizepsmini pconxs v3
* New guf branch: guf_imx_v2019.04_5.4.3_2021-11-29
* Rebased on 70d18dcbd4771e2eb325ce9b7cfb742e72877acd (kuk_imx_v2019.04_5.4.3_2.0.0)

BCS 746-000604

Felix Gerking authored 3 years ago and Jonas Höppner committed 3 years ago

The FPGA is configured differently in this device tree than in the
atm0700 so that the display colors are displayed correctly.

BCS 746-000539

We had separate lists, but all files in KERNEL_DEVICETREE are
IMAGE_BOOT_FILES. So this can be replaced by an expression.

GitBot authored 3 years ago and Tobias Kahlki committed 3 years ago

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/d8ea12260f556396326fe340e269d7813010a184

Add alphaplan FWR generator

alphaplan_fwr.py: Creates alphaplan software packages for the build
release artifacts. According to the release, all relevant artifacts are
collected in a list structure and the corresponding aphaplan
information are added for each artifact (attributes, md5sum, path, etc.).
The list is attached to major software package structure. This structure
is written in a json file for documentation. Afterwards the structure is
send to an AlphaPlan webservice that creates the FWR articles.
alphaplan_keys.py: Generates a dictionary which contains all AlphaPlan
specific information for the artifacts. Flag classes are used to define
unique keys for the dictionary accesses.

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/19c3e164e97614c2672d3121a315b7db577a290d

submit_test.py: Add option to specify branch of the test repository

Previously the default branch was allways used to generate the tests
from, now it is possible to specify the branch as cmdline option.
Additionally, the revision of the test repository is added to the
call of the test generator, so the tests run at a fix rev.

BCS 746-000547

--

Commit: https://gitlab.com/garz-fricke/yocto/infrastructure/gitlab-ci/-/commit/c07bfd8e93f7c7d5fd97c18ecf0da91c480308db

package_release: Store some variables as env file for usage in later jobs

Add the in-kernel driver for the AD7879 resistive touch driver connected
via I2C. The AD7879 will replace the previous STMPE controller due to
EOL of the STPME.

BCS 746-000567

Enable adaptivity as a driver feature for the rtl8723ds Wifi driver used
for the module of TANARO.

Adaptivity is required by the European regulations.

BCS 746-000602

The kuk kernel already contains a useful devicetree file. Added this
to the yocto build.

BCS 746-000539

The proposal branch for the TANARO 5.10 kernel was
moved to an active release branch.

BCS 746-000535

BCS 746-000535

The reset driver is used by the PCIEe driver.

BCS 746-000535

BCS 746-000535

- Removed generic backlight driver due to incompatibility

BCS 746-000535

The current driver in meta-freescale doesn't compile with the 5.10.9 kernel.

BCS 746-000535

The licence hash betwenn kernel version 5.4.24 and 5.10.9 has changed.

BCS 746-000535