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

- Added new recipe for 5.10.9 kernel
- Updated preferred kernel version to 5.10.9

BCS 746-000535

Added missing backslash in code sample

BCS 746-000459

--

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

submit_test.py: Add option to submit tests for all devices of a type

Uses submit_all instead of submit.
Some code cleanup also.

--

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

submit_tests.py: Add python script to submit tests to lava and wait for results

The testsuite is generated per platform and submited to the lava server.
The resulting jobs are monitored and the results are downloaded in the
results/ subfolder.

--

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

package_release.py: Add option to specify to output folders

The paths have been hardcoded inside the script before. To
allow reuse in different situations, the hardcoded paths are removed
and options are added instead.

Clemens Terasa authored 3 years ago and Jonas Höppner committed 3 years ago

Update to the latest Ubuntu version.
Also try to write Yocto with capital letters.

Reformat some parts for line wrapping and add very basic i.MX6
installation hints.

--

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

CI: Adapt package_release to also deploy artifacts locally

To upload the sdk the local deployment on build host is needed as it is
too big for the uploads.

Move copy functionality to extra function. It also generates md5sum.txt
from the source file's md5sums.
Copy locally (host system) and as gitlab artifact.

Add option to copy doc files ( all .md in given folder).

BCS 746-000262

Add the kernel-module-imx6-spreadspectrum that adds the spread spectrum
feature to reduce EMI.

The dynamic user interface is the /proc/mx6_spreadspectrum but the
normal interface is the device tree interface.

For more details on the module use the source (Luke).

BCS 746-000453

Update to use the recent proc_ops.
Fix possible buffer overflow: The bounds were checked by the complaining
compiler, so I do not deserve credit.

Harmonize the recipes and Makefiles for imx6-spreadspectrum and
rtc-pcf8563-guf.

The imx6-spreadspectrum is still not installed by default for imx6(ull)
devices.

BCS 746-000453

Adds the G&F iMX6 spread spectrum module.
Pulled version c8281e68 from the G&F
rocko port.

Does not build yet due to kernel 4.1 to 5.10 incompatibilities.

BCS 746-000453

Upgrade the Linux kernel for the i.MX6 devices (SAN* platforms) and
iMX6ULL (NALLINO) from v5.10.32 to v5.10.57.

BCS 746-000445

SANTINO-LT is the first G&F iMX6 platform that uses a different UART
debug port, UART5 instead of UART2. It is not possible to use both port
settings together with early printk. Even though this is unfortunate,
we do not need the early printk feature enabled in production so diable
it here.

CONFIG_VT_HW_CONSOLE_BINDING and CONFIG_LEDS_TRIGGERS are still due to
default dependencies.

BCS 746-000428

Add SANTINO-LT support by adding the device tree blobs to the
deployment.

BCS 746-000428

Because the other SN65DSI83/84 drivers did not fit our needs we decided
to try the latest mainline addition.
See https://patchwork.kernel.org/project/dri-devel/patch/20210608094046.22516-1-marex@denx.de/

The driver uses the same device tree compatible description as the
non-mainline TI SN65DSI84 driver so disable this one for now.

Add the panel-lvds driver as well to support generic LVDS panels.

BCS 746-000279

There is a hook for fngsystem to enable it for the fng system build
but it needs the disable entry to work correctly.

The output used '' but we want to see the loaded variables so
"" is needed.

Each bootscript receipe provides the scriptname.
The distro will pull the correct script later.

For tanaro a bootscript for u-boot is needed.
Use install scripts also for tanaro.

BCS 746-000378

Because we store some boot information (bootselect) data in the PCF8563
we need to modify the driver in a way that it does not reset the RTC
registers. However, we do not want to push this into the kernel so we
decided to create an out-of-tree fork.

Then, however, both drivers the in-kernel and out-of-tree driver
conflicting each other, and thus build the former as module and do not
load it by default.

BCS 746-000337

BCS 746-000399

BCS 746-000399

Remove WIC from image types to build
Remove spreadspectrum from fngsystem image, as it pulls python in.

BCS 746-000410

Its wired in yocto network does only work with the fix, in fngsystem
it does not.

One logo, centered, white background, no rotation.
Rotation may be set in a postinstall step later.

BCS 746-000275

The regulator was left on in error case, but devm/regulator core
complained about it.

removes esp.:
 * lock debugging and debugging sysmbols for variables, etc.
 * support for i.MX3x, i.MX5x, i.MX6 non-ULL SoCs, i.MX8x
 * support for IPUv1, IPUv3, VPUs, GPUs
 * support for DVB and IR remote control modules

reduces (compressed) kernel size from almost 10 MB to just
under 6 MB. (uncompressed kernel is still almost twice as big as the
Rocko 4.9.88 kernel for 6ULL, though)

BCS 746-000388

--

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

list_commits: use "--" as separator

Unfortunately, GitLab still interpreted three of the four dashes as
start and end of YAML syntax, so we go back to two dashes.

--

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

list_commits: use "----" as separator

The former "---" was still rendered as YAML syntax by GitLab in some
cases.

--

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

create_merge_request: optimize description

Restore the "---" separator which was removed in a previous commit. The
description simply must not start with this separator. If we include it
only in between the blocks, all instances are rendered as a horizontal
line, which makes the MR description more readable. Include a helper
function for this purpose, which extracts the message body from a commit
message.

--

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

deploy_gitlab_ci: show instructions if merge fails

--

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

update_submodule: fix accidental multi-commits

If integration branch already existed and had to be replaced, the new
commit was accidentally pushed on top of the already existing commit
instead of replacing it. Fixed this by checking out the master branch
again before creating the commit.

--

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

list_commits: replace "---" with "--"

GitLab renders "---" as a horizontal line or as a frame. We do not want
this, so replace it with "--".

--

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

create_merge_request: use commit message as description

--

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

check_pipeline_status: reduce flush sleep again

Sometimes the job log of canceled jobs still is truncated, even with the
larger sleep. Thus we can reduce it again. Usually the job log is
complete after a retry.

--

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

check_pipeline_status: increase flush sleep

--

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

check_pipeline_status: add ability to cancel job

If an upstream pipeline has been canceled, this is reflected in the job
result now.

--

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

deploy stage: simplify yaml syntax

--

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

deploy_gitlab_ci: automatically rebase if merge fails

--

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

Fix pipeline execution on master

--

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

Add deploy stage

The jobs in the deploy stage have to be triggered manually in GitLab.
There is one deploy job for each project which uses the gitlab-ci
scripts as a submodule, so that the deployment can be performed step by
step.

If executed within MR context, an integration MR is created and left
open. The user can extend this integration MR, e.g. if CI scripts have
been renamed, changed command line arguments or other changes requiring
updates of the correspronding .gitlab-ci.yml file. Subsequent runs of
this job will re-create the integration branch, so manual changes are
lost in this case.

If executed on the master branch (i.e. after the source MR has been
merged), the job does exactly the same, plus the integration MR will be
automatically merged. If this fails, the job will fail as well.

--

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

merge_into_manifest: add wait loop until MR has been updated

We still had cases where a merge request was rebased multiple times after an
initial (actually required) rebase:

https://gitlab.com/garz-fricke/yocto/infrastructure/ci-test/minimal-bar/-/jobs/1345964713

I assume that GitLab simply does not update the MR that fast and so we attempt
to do a rebase, while the MR still reports it is merge-ready.

Adding a wait loop now where the MR's sha is compared to the one of the new
commit in order to make sure that the MR has been updated before we attempt
another rebase.

--

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

accept_merge_request: add additional error handling

We had one case where the merge() function returned successfully, but the MR
was not merged (needed a rebase actually):

https://gitlab.com/garz-fricke/yocto/infrastructure/ci-test/minimal-bar/-/jobs/1345574290

This seems to be a known issue:

https://gitlab.com/gitlab-org/gitlab-foss/-/issues/59577
https://gitlab.com/gitlab-org/release-tools/-/issues/277#note_154733089

It seems like in these rare cases, the error is reflected in the merge_error
field. Add evaluation of this to the error handling.

--

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

retrigger_mr_pipeline_job: prevent rare exception where MR has no pipeline

There are rare cases where a merge request does not have a pipeline, even
though this might only occur under testing circumstances, e.g.:

https://gitlab.com/garz-fricke/yocto/infrastructure/ci-test/minimal-foo/-/merge_requests/58

The retrigger_mr_pipeline_job script throws an exception in these cases:

https://gitlab.com/garz-fricke/yocto/infrastructure/ci-test/minimal-manifest/-/jobs/1345385316

Fix this by checking for existing pipeline before querying it.

--

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

merge_into_manifest: add merge_status check before merge attempt

We had some cases where the merge job added rebases of a commit where rebasing
was not necessary at all, e.g.:
https://gitlab.com/garz-fricke/yocto/layers/meta-guf-machine/-/jobs/1270293595

This is obviously a known issue in GitLab concerning the HTTP return value of
the merge endpoint:
https://gitlab.com/gitlab-org/gitlab/-/issues/196962

Suggested workaround is to manually check merge_status and wait until it is
ready before attempting to merge the MR.

--

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

Add diagram detailing the CI pipeline flow

* Add a draw.io diagram that illustrates the flow of the CI pipelines
across the manifest and layer repos
* Add a png export of the diagram

--

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

Add diagram detailing the CI pipeline flow

* Add a draw.io diagram that illustrates the flow of the CI pipelines
across the manifest and layer repos

Somehow the relocation is done with before switching on the caches
which is very slow when the load address is too close to the final
kernel location.

So ganz 100% verstanden hab ich den Code in „boot/compressed/head.S“ zwar nicht, aber es sieht so aus, als erwartet der Code am Anfang des phys. RAMs Platz, um eine MMU-Tabelle anlegen zu können (16KB) – die ist notwendig um MMU und Caches einschalten zu können – und überprüft dabei, in welchem Adressbereich der Code selbst gerade läuft.
·         Kommt er zu dem Schluss, dass da genug Platz ist,
o   schaltet er zuerst MMU und Caches ein,
o   verschiebt sich selbst, den komprimierten Kernel und den DTB mit allerlei Pointer-Anpassungen irgendwohin, wo er beim Auspacken nicht überschrieben werden kann
o   und erledigt dann das Entpacken.
·         Sind zwischen phys. Start des RAMs und laufendem Code weniger als 16KB + eine kleine Reserve von 1 MB (für schlechte Zeiten oder so…) Platz
o   Verschiebt sich der Code selbst, den komprimierten Kernel und den DTB mit allerlei Pointer-Anpassungen zuerst irgendwohin, wo er beim Auspacken nicht überschrieben werden kann
o   Startet sich selbst dann neu
o   Schaltet dann erst MMU und Caches ein
o   Und erledigt dann das Entpacken

Sprich: wird der gepackte Kernel irgendwo in die ersten gut 1MB des phys. RAM-Bereichs geladen und von da gestartet, läuft die ganze Relokation mit ausgeschalteten Caches, was auf dem 6ULL offenbar so langsam ist, dass es nur noch tröpfelt…
(Da der 6ULL nur ein 16-Bit RAM Interface hat und mit abgeschalteter MMU keinerlei Caching, Buffering o.ä. stattfindet, müssten schon nur für einen einzigen 32-Bit RAM-Zugriff zwei vollständige DDR3-Lese-Bursts ausgelöst werden, die jeweils 8x16-Bit liefern (DDR3 RAM macht immer 8-fach Burst), wovon aber jeweils nur die ersten 16 Bit tatsächlich verwendet werden. Da kann man die Daten wohl genauso gut auch per Rauchzeichen übertragen…)

BCS 746-000387

The gitpkgv.bbclass states:
```
gitpkgv.bbclass assumes the git repository has been cloned, and
contains SRCREV. So ${GITPKGV} and ${GITPKGVTAG} should never be
used in PV, only in PKGV.  It can handle SRCREV = ${AUTOREV}, as
well as SRCREV = "<some fixed git hash>".
```
Change the version variables from PV to PKGV.

Add the Quectel EC20 Modem, the ath9k, and teh ath3k drivers.

BCS 746-000340
BCS 746-000341
BCS 746-000342

Add the imx6dl SANTOKA support simply by adding the corresponding device
tree files to the image.

BCS 746-000372

Add the USB3503 HSIC USB-hub driver. This should  enable the internal
USB port for SANTARO and SANTOKA. At least it works for SANTOKA.

BCS 746-000359