Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
0 authors
  1. Jul 27, 2023
    • GitBot's avatar
      Integrate gitlab-ci/separate-images-in-multiple-pipelines and 1 more · 06ac1a04
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@9406ad75

Yocto build: separate images in multiple pipelines

Instead of building the Yocto image, the Yocto SDK and the FNGSystem
image in one single pipeline, separate them into three independent
pipelines that are triggered in parallel.

This makes the concept more modular: we have a single general pipeline
now which is configurable from outside via variables. Hence we can have
a custom number of pipelines along with custom build targets in each
project without having to make code changes in the gitlab-ci project.

The default Yocto manifest pipeline configures three build pipelines:

- yocto-build-jobs
- sdk-build-jobs
- fngsystem-build-jobs

In a project including the Yocto manifest pipeline, we can disable
certain build pipelines using job rules, e.g. disabling the SDK build:

sdk-build-jobs:
  rules:
    - when: never

Furthermore we can add more pipelines by simply adding jobs extending
the '.build-jobs' class in the project's .gitlab-ci.yml:

yocto-custom-build-jobs:
  extends:
    - .build-jobs
  variables:
    BITBAKE_TASK: build
    CI_PARAM_IMAGE: custom-image
    CI_PARAM_DISTRO: custom-distro
    PACKAGE_TYPE: image

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@447804d2

.gitlab-ci: increase analyze timeout
      06ac1a04
  3. Jul 25, 2023
    • GitBot's avatar
      Integrate gitlab-ci/unify-image-and-sdk-package-jobs and 3 more · 44f528d4
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@5762a54c

Yocto build: unify image and SDK package jobs

Image and SDK package jobs call the same package script just with
different arguments. Instead of having two job classes `package_release`
and `package_sdk` for these two tasks, merge them into the base class
`package` and make the differences configurable via a variable
`PACKAGE_TYPE`.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@8e72eac2

Yocto build: add variable for manual builds

Instead of hard-coding the rules for manual builds in each actual job,
conditionally add this to the `buildbase` class and add a variable
`MANUAL_BUILD` to the according jobs.

--

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

Yocto build: unify image and SDK build jobs

Image and SDK builds share a lot of similar code. Instead of having two
job classes `build_yocto_image` and `build_yocto_sdk` for these two
tasks, merge them into the base class `build_yocto` and make the
differences configurable via a variable.

The `dump_install_command` part of the script, which was not executed
for SDK builds, is always present now, but it's only executed if the
`INSTALLSCRIPT` variable is set, which is not the case for SDK builds.

The `collect_srcrevs` part of the script is executed in all cases. It
was not part of the SDK build before, but it's not less relevant there.

--

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

Yocto build: make main artifacts path configurable

Instead of specifying all possible artifacts paths and abusing the fact
that GitLab ignores non-existing paths during artifact upload, implement
a cleaner solution with a configurable path.
      44f528d4
  5. Jul 24, 2023
  7. Jul 19, 2023
  9. Jul 18, 2023
  11. Jul 17, 2023
  13. Jul 05, 2023
    • Marc-Oliver Westerburg's avatar
      MC3 UCB1400 touch: fix touch pressure for Weston · 9ec0c273
      Marc-Oliver Westerburg authored 
      The UCB1400 touch driver claimed to report Min/Max pressure coordinates of 0, which caused Weston to refuse to use the touch:

Jul 05 11:49:10 GFMM00000000 weston[1189]: [11:49:10.521] event1  - UCB1400 touchscreen interface: is tagged by udev as: Touchscreen
Jul 05 11:49:10 GFMM00000000 weston[1189]: [11:49:10.522] event1  - UCB1400 touchscreen interface: kernel bug: device has min == max on ABS_PRESSURE
Jul 05 11:49:10 GFMM00000000 weston[1189]: [11:49:10.522] event1  - UCB1400 touchscreen interface: was rejected
Jul 05 11:49:10 GFMM00000000 weston[1189]: [11:49:10.522] event1  - not using input device '/dev/input/event1'

This patch fixes this issue. Now the driver correctly claims to report pressure values in the range 0..MAX_ADC_VALUE
      9ec0c273
  15. Jun 23, 2023
    • Marc-Oliver Westerburg's avatar
      MC3 UCB1400: modify code/filter to reduce jitter · 88c0a123
      Marc-Oliver Westerburg authored 
      On MC3 with UCB1400 resisitive touch we see huge amounts of noise on the
analogue touch-signals - esp. when evaluating sampling x-coordinates -
due to crosstalk from the display signals running over the same cable.
This causes lots of jitter in the touch-coordinates reported, esp. for a
brief moment after each touch-down.

This patch modified the code to discard the first few samples after each
touch-down, ignore (and immediately retry) samples, when too much noise
is recognized, and tweak the filters to reduce the jitter.

BCS: 746-001399
      88c0a123
  17. Jun 16, 2023
  19. Jun 12, 2023
  21. Jun 08, 2023