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

It seems to mess with the out-of-tree SIS vendor driver. Thus get rid of
the in-kernel driver for now from the linux defconfig and use the
sis-i2c vendor driver instead.

The touchgpio driver uses a problematic function
gpio_sysfs_set_active_low that changed the semantics in Linux v4.2´.

It uses the gpiolib framework now based on the gpiod framework.
The simple solution is to disable the only user of the export
functionality in the SIS driver.

As we use u-boot from the freescale layer for imx8 and u-boot from
meta-guf-machine in imx6ull there was some mixup with the include files.

Do not rely on patches that have been available in poky to reduce the
dependency between the layers.

lzop was missing during kernel image build.

BCS 746-000293

The SMDMA needs a firmware blob. It could be added to the Linux kernel,
however it is easier to add the SDMA support as module.

Use the ```make savedefconfig``` to generate a minimal and portable
defconfig.

Add the i.MX6 Dual/Quad Plus variant of the G&F SANTOKA device tree to
the image. With this it can be installed and it boots up. There seems to
be an issue with OpenGL or Qt applications on my 900-3577R device, but
the framebuffer seems to be OK.

With the recent adaption it is possible to build the iMX6 based G&F
platforms with the latest LTS kernel version 5.10.32.

Thus change the preferred Linux kernel version to 5.10.32. Use a weak
assignment to be able to override this in the local.conf.

BCS 746-000295

Add the linux-guf-5.10 recipe and copy the files form 5.4.

Do not use the
use-pkg-config-native-to-find-host-lcrypto-in-sysroot.patch because it
does not apply right now.

Also assign PREFERRED_VERSION of the linux-guf recipe weakly to be able
to overwrite this in the local.conf

Only tested with imx6guf.

BCS 746-000295

Due to changes in the procfs exports in Kernel version 5.6, the change
of touch drivers are necessary.

Mainly because of the change
https://lore.kernel.org/netdev/20191225172546.GB13378@avx2/ that changed
the proc_create file operations  from sruct file_operations to proc_ops.

The ilitek driver needed adjustments because of the transition from time
to ktime.

BCS 746-000295

Add the TANARO device tree with the QP-070WSVGAMMLI1S
glass-touch-display-set also to the boot partition.

The ilitek driver could not be built out-of-tree because of legacy
functions that are not exported anymore in later kernels
(vfs_{read,write}).

Rewrite the driver to use the newer kernel_{read,write} functions.

Also reduce the stack size of the ilitek_sensortest_write function to
fit the defaule CONFIG_FRAME_WARN size being used for our 32bit
systems.

BCS 746-000307

Port the driver from the SAN platforms from the G&F rocko port.

BCS 746-000307

Add the TANARO device tree with the QP-070WSVGAMMLI1S
glass-touch-display-set.

bitbake complains about the trailing slash:
Recipe auo-pixcir sets B variable with trailing slash
Removed in in the include file.

During upgrade I noticed, that we introduced a depency between the layer
version using include file from one layer in our layer.
This patch copies the current version into this layer so the old version
of u-boot should also build if the u-boot version in poky does change.

BCS 746-000293

The links in the boot partition do not work on the used fat partitions.
With tar of the dunfell fngsystem this is an error, which stops the
installation and the links have never bee installed anyway.

BCS 746-000274

Remove the systemd service that set the spread spectrum settings for the
VideoPLL1 during startup from the linux userland as this was unreliable.
The settings will be applied in u-boot already.

The spreadspectrum python script is still installed and can be used to
verify the settings, as well as modifying them in a debug environment.

BCS 746-000332

Norman Stetter authored 4 years ago and Jonas Höppner committed 4 years ago

* Add bootscript for alternative boot mode (FNG System)
* Cleanup recipe file from unneeded deploy and release tasks that are no
longer needed
* Exchange the loadaddress for the cpio based on ram start of the machine.

BCS 746-000268

The script calculates register settings for the SSC in the VIDEO PLL
from modulation frequency and modulation range and writes it to the
register using devmem2.

BCS 746-000297

The unset field generated a -- in the filenames, which is not
that nice.

The devicetree have bee moved to a garz-fricke subfolder. This
patch adapts the machine config file accordingly.

Getty was started on ttymxc1 though we changed default serial port to
ttymxc0 in the devicetree earlier.

BCS 746-000172

Cleanup include files as the conf/guf-recipe file is going to be
removed.

BCS 746-000245

This gitpkgv class creates a sortable version string from the git revisions,
by counting the revisions similar to git describe. So the next commit to the
package will not generate this warning again.

BCS 746-000245

The ilitek driver uses device tree properties pre-fixed with "ilitek".
Although this is a good way to distinguish mainline/standard kernel and
vendor specific properties this is in our case not useful.

We already introduces the non-prefixed version with the same information
mainly to use the Garz & Fricke specific touchgpio API.

Thus simply re-use the non-prefixed properties to reduce information
duplication in the device tree.

This also reduces the complexity in the Garz & Fricke overlay mechanism
using gfxml2dto.

When imx-sdma is built into the kernel the rootf, where the sdma
firmware binary is located is not ready when the driver tries to load
the firmware. This can be avoided by building the imx-sdma driver as a
module, so it gets loaded after the rootfs is ready

BCS 746-000154