Skip to content
Snippets Groups Projects
Select Git revision
  • integrate/config/troubleshoot-image-diff-report-current/into/kirkstone
  • integrate/config/test-report-image-diff/into/kirkstone
  • integrate/gitlab-ci/CI-report-image-diff/into/kirkstone
  • kirkstone default protected
  • integrate/meta-seconorth-distro/try-integrate-barrier/into/kirkstone
  • dunfell protected
  • test-gitbot-token-build
  • integrate/gitlab-ci/kirkstone-spdx/into/kirkstone
  • yt-277-test-spdx-licenses
  • test-ci-updates-for-release-pipeline
  • integrate/meta-seconorth-distro/fng-system-bmaptools/into/kirkstone
  • integrate/gitlab-ci/test-gitbot-service-account/into/kirkstone
  • integrate/gitlab-ci/test-gitbot-service-account/into/dunfell
  • integrate/gitlab-ci/cleaos-552-build-cleaos-on-hamburgs-ci-servers-test/into/kirkstone
  • integrate/meta-seconorth-machine/kirkstone-u-boot-env-unification/into/kirkstone
  • integrate/meta-seconorth-machine/uuu-install-wic-update/into/kirkstone
  • integrate/meta-seconorth-distro/wic-multiconf-fngs-and-yocto/into/kirkstone
  • integrate/yocto-install/fix-postinstall-for-b-slot-wic/into/kirkstone
  • integrate/meta-seconorth-distro/fngsytem-bmap-tools/into/kirkstone
  • meta-freescale-update
  • test-release-2.0
  • kirkstone/27.0 protected
  • fngsystem/54.0 protected
  • fngsystem/53.0 protected
  • kirkstone/26.0 protected
  • fngsystem/52.0 protected
  • kirkstone/25.0 protected
  • kirkstone/24.1 protected
  • fngsystem/51.1 protected
  • fngsystem/51.0 protected
  • kirkstone/24.0 protected
  • fngsystem/50.0 protected
  • kirkstone/23.0 protected
  • kirkstone/22.1 protected
  • fngsystem/49.0 protected
  • kirkstone/22.0 protected
  • kirkstone/21.1 protected
  • fngsystem/48.0 protected
  • kirkstone/21.0 protected
  • fngsystem/47.0 protected
40 results
Search by author
  • Any Author
  • Alexander Sterger Alexander Sterger alexander.sterger
  • Andrii Sosiuk Andrii Sosiuk andrii.sosiuk
  • **** **** group_556_bot_74cce396359e27efa6278607a72ef350
  • Bernd Mierzowski Bernd Mierzowski bernd.mierzowski
  • Christian Stimming Christian Stimming christian.stimming
  • Christoph Kutzera Christoph Kutzera christoph.kutzera
  • Christos Christos Karampeazis
  • CI Variables Management Service Account CI Variables Management Service Account service_account_ci_vars_management
  • Davide Cardillo Davide Cardillo davide.cardillo
  • Dietmar Muscholik Dietmar Muscholik dietmar.muscholik
  • Dmitry Petrov Dmitry Petrov dmitry.petrov
  • Felix Gerking Felix Gerking felix.gerking
  • GitBot GitBot gitbot
  • Git Bot Service Account Git Bot Service Account service_account_gitbot
  • Hai Nam Tran Hai Nam Tran hai.nam.tran
  • Hilmar Bode Hilmar Bode hilmar.bode
  • Jan-Ove Korneffel Jan-Ove Korneffel jan-ove.korneffel
  • Jonas Höppner Jonas Höppner jonas.hoeppner
  • Lorenzo Pagliai Lorenzo Pagliai lorenzo.pagliai
  • Lukas Rosky Lukas Rosky lukas.rosky
20 authors
  1. Sep 29, 2023
  3. Sep 28, 2023
  5. Sep 25, 2023
  7. Sep 22, 2023
    • Jonas Höppner's avatar
      imx6: Fixed touch performance issues · dec026ea
      Jonas Höppner authored 
      The i2c driver had a performance issue that lead to problems with some
eeti and ilitik touch drivers. This issue was fixed with a kernel
commit.
This updates the related lines in the feature list.

Change-Id: I688be6a7f33251a69782f7bc834f87142c3ef370
      2 tags
      dec026ea
    • GitBot's avatar
      Integrate meta-seconorth-machine/kirkstone-stabilize-ip-for-edgehog · 58aa1cc8
      GitBot authored 
      --

Commit: seco-ne/yocto/layers/meta-seconorth-machine@48a0f29e



systemd-conf:wired.network: do not send DHCP release on service stop

Fix the problem with floating IP addresses after first reboot in Edgehog
image.

Even when a stable MAC is assigned to device via device-tree, an IP address
may change after the first reboot.
This is due to default implementation of built-in DHCP client provided by
systemd-network daemon - DHCP RELEASE packet is sent to the DHCP server
during reboot by this daemon. So, next time a new IP address is allocated
to the same DHCP client (device).

To change this behavior of the DHCP client, a
"KeepConfiguration=dhcp-on-stop" option is enabled in configuration file
for systemd-networkd.

Signed-off-by: default avatarMikhail Vanyulin <mikhail.vanyulin@rtsoft.de>
      58aa1cc8
  9. Sep 21, 2023
  11. Sep 20, 2023
  13. Sep 19, 2023
  15. Sep 18, 2023
    • GitBot's avatar
      Integrate uboot-imx-kuk/mx6-enable-fastboot · 893ae50e
      GitBot authored 
      --

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@0ca48bfa

seco-mx6: enable fastboot

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@abf30977

seco-mx6: update config via savedefconfig
      893ae50e
    • GitBot's avatar
      Integrate linux-imx-kuk/i2c_imx_isr_read_fsl · 0d2d5788
      GitBot authored 
      --

Commit: seco-ne/kernel/linux-imx-kuk@a6646c02

arm:dts:imx6qdl-san: Enable i2c msg read within ISR for bus 3

Some connected touches lead to a large traffic on the bus.
If this traffic is handled too slowly, some ugly effects show up,
such as input delays or a high CPU load due to the touch driver.
Set the enable-isr-read flag to speed up the message read process.

Cherry-picked from 52d249fcd8ff14c01bce0b4049613b11c779426e
https://git.seco.com/seco-ne/kernel/linux-guf

BCS 746-001477 746-001000

--

Commit: seco-ne/kernel/linux-imx-kuk@8ab02e4d

drivers:i2c-imx: Add option for i2c read processing within ISR

By default the read msg process is handled by the follwing queue
mechanism:
1. Client driver read request
2. The i2c driver triggers a read and waits for a byte to be ready to read
3. ISR sends a wake_up call to the queue when the byte is ready to read
5. The i2c driver becomes scheduled again and reads the byte
6. The i2c driver waits for the next byte and so on

For some reason, it often takes a long time to reschedule the i2c
driver after the ISR reports ready status. This causes problems with
i2c devices that cause a lot of bus traffic, such as touch devices.
To resolve this, the devicetree flag "enable-i2c-isr" enables the
following read routine:
1. Client driver read request
2. The i2c driver triggers a read and waits for the ISR
3. The ISR reads the bytes itself and wakes up the queue when
   all bytes are processed

This way the wake_up calls are reduced by the number of bytes in a message
and processing becomes much faster. However the ISR does more, but adding
something that controls the scheduling of the i2c driver also seems to be
very complicated.

Cherry-picked from 850be496c49aeca59bf9caa295a939d39fb4dbec
https://git.seco.com/seco-ne/kernel/linux-guf

BCS 746-001477 746-001000
      0d2d5788
    • GitBot's avatar
      Integrate linux-guf/i2c_imx_isr_read · 7c4c771f
      GitBot authored 
      --

Commit: seco-ne/kernel/linux-guf@1ec2a30d

arm:dts:imx6qdl-san: Enable i2c msg read within ISR for bus 3

Some connected touches lead to a large traffic on the bus.
If this traffic is handled too slowly, some ugly effects show up,
such as input delays or a high CPU load due to the touch driver.
Set the enable-isr-read flag to speed up the message read process.

BCS 746-001477 746-001000

--

Commit: seco-ne/kernel/linux-guf@8037dbaa

drivers:i2c-imx: Add option for i2c read processing within ISR

By default the read msg process is handled by the follwing queue
mechanism:
1. Client driver read request
2. The i2c driver triggers a read and waits for a byte to be ready to read
3. ISR sends a wake_up call to the queue when the byte is ready to read
5. The i2c driver becomes scheduled again and reads the byte
6. The i2c driver waits for the next byte and so on

For some reason, it often takes a long time to reschedule the i2c
driver after the ISR reports ready status. This causes problems with
i2c devices that cause a lot of bus traffic, such as touch devices.
To resolve this, the devicetree flag "enable-i2c-isr" enables the
following read routine:
1. Client driver read request
2. The i2c driver triggers a read and waits for the ISR
3. The ISR reads the bytes itself and wakes up the queue when
   all bytes are processed

This way the wake_up calls are reduced by the number of bytes in a message
and processing becomes much faster. However the ISR does more, but adding
something that controls the scheduling of the i2c driver also seems to be
very complicated.

BCS 746-001477 746-001000
      7c4c771f
    • GitBot's avatar
      Integrate gitlab-ci/hide-stages-if-variables-not-set and 4 more · dfde16e9
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@64dc51d3

Use regex operator to check for multiple variables

The "&&" operator does not work as expected when checking if multiple
variables are set.

See for reference:
https://gitlab.com/gitlab-org/gitlab/-/issues/321371

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@89fbce24

Hide Confluence stage if confluence variables not set

--

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

Hide deploy stage if DEPLOY_RELEASE_TARGET not set

--

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

Hide FTP stage if DEPLOY_FTP_TARGET not set

This makes the variable HIDE_FTP_UPLOAD_STAGE obsolete, because we can
hide the FTP stage now by setting DEPLOY_FTP_TARGET to an empty string.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@409c4f27

Do not run CI test sub-pipeline on master
      dfde16e9
  17. Sep 15, 2023
  19. Sep 14, 2023
  21. Sep 13, 2023
  23. Sep 12, 2023
    • GitBot's avatar
      Integrate linux-imx-kuk/fix_wm9705_dig2 · 1ee67229
      GitBot authored 
      --

Commit: seco-ne/kernel/linux-imx-kuk@b5006e3e

driver:wm9705: Check and re-set dig2 config register

Due to an unknown reason, the dig2 config register resets randomly. This
disables the generation of pen-down interrupts. Without the interrupt, doesn't
sample further touches.
As a first workaround, we check the dig2 config register before exiting the
sample function and re-set the config value, if it was reset.

BCS 746-001452
BCS 746-001447
      1ee67229
    • GitBot's avatar
      Integrate yocto-install/fngsystem-add-rootfs-postinstall · f0e6d58e
      GitBot authored 
      --

Commit: seco-ne/tools/yocto-install@6c54f459



fngsystem: add script to run postinstallation on installed yocto

This is a fix for issue with ID 746-001246: "FNG-System: Add way to manually
update the configuration"

To solve the problem (to be able to update the settings in Yoto after xconfig
import), we added a fngsystem-rootfs-postinstall.sh script to the FNG System.
It is a simplified version of the existing fng-install.sh script and right now
it supports only an "--AB-target" argument from the original script.

This script can be run like this:
yocto-postinstallation.sh

Note: due to lack of iMX8 boards for which AB partition layout may be used,
this functionality in the script has not been tested yet (but already exists).

Signed-off-by: default avatarMikhail Vanyulin <mikhail.vanyulin@rtsoft.de>
      f0e6d58e
  25. Sep 11, 2023
  27. Sep 08, 2023
    • GitBot's avatar
      Integrate gitlab-ci/remove-release-name-from-deploy-target and 10 more · bc1b37bd
      GitBot authored 
      --

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

Refactoring: remove RELEASE_NAME from deploy targets

Append it to the configured target at the deploy class level instead.
This removes the need for eval'ing the variables before usage.
RELEASE_NAME can be used directly at the class level because it is known
from build-version.env.

This makes the deploy behavior identical to the Azure stage.

--

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

Remove top-level "release" folder from package

--

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

Define MACHINE variable on job level

Instead of passing MACHINE from stage to stage or loading it from
testdata.json, use the original value from the Jinja2 loop and set it
directly for each job where it is used.

--

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

Introduce separate variables to set RELEASE_NAME and RELEASE_VERSION

The expressions to calculate RELEASE_NAME and RELEASE_VERSION cannot be
stored within these variables themseselves. If set on the trigger level,
they would override the calculated values in build-version.env then,
as trigger variables always have the highest precedence.

Use separate variables RELEASE_VERSION_EXPRESSION and
RELEASE_NAME_EXPRESSION to define how RELEASE_VERSION and RELEASE_NAME
are calculated instead.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@372d192b

Use RELEASE_VERSION and RELEASE_NAME from build-version job

Instead of passing these variables from stage to stage or regenerating
their values in later stages, use the ones set in the build-version job
at all places.

--

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

Remove RELEASE_SUFFIX variable

The RELEASE_NAME variable can be set directly now, so there's no need to
have a dedicated RELEASE_SUFFIX anymore. A previous configuration like

  RELEASE_SUFFIX: "-custom"

can now be achieved using:

  RELEASE_NAME: "Yocto-${RELEASE_VERSION}-custom"

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@922f49f8

Add yocto version job

This adds a machine-independent job "build-version" which populates the
RELEASE_VERSION and RELEASE_NAME variables, so that following jobs can
use these without depending on the various build jobs.
The variables can be set from the trigger job in a project's
`.gitlab-ci.yml` file. They are eval'ed before saving them to
version.env, so we can use deferred variable expansion or even command
execution to construct their values. This mechanism is already used for
the Flash-N-Go System variables.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@073ae81e

LAVA: rename MACHINE to LAVA_MACHINE

Rename variable in order to avoid confusion with the original MACHINE
variable used everywhere else. Also rename the local Jinja2 variable to
include an underscore to make naming consistent.

--

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

Clean build.env before writing

This had been accidentally removed in
5e36715ef6cf98df4c1b98fedddc0c3c50ed4040.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1860ca8e

Remove LOG_PREFIX variable

This was used in times when the same code was executed from different
places. We don't do that anymore, so the variable is obsolete.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3d2dbe4d

Documentation: update job generation chapter
      bc1b37bd
  29. Sep 06, 2023
  31. Sep 05, 2023
    • GitBot's avatar
      Integrate config/fix_fngsystem_nogplv3 · 2471d784
      GitBot authored 
      --

Commit: config@edf6b42d

config:setup: Add check to fngsystem NoGPLv3 feature

Some custom projects already include the NoGPLv3 or GPLv2 layer. If these
layers are already present, the Bitbake parsing fails. As a precaution,
check if the layers are already present and only add them if not.
      2471d784
  33. Sep 04, 2023
  35. Sep 01, 2023
  37. Aug 31, 2023