Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
0 authors
  1. Jul 20, 2022
    • GitBot's avatar
      Integrate linux-guf/NALLINO_add_keypad_gpios · 88179d68
      GitBot authored 
      --

Commit: seco-ne/kernel/linux-guf@30adc80b

arm: dts: Add muxing for ecSPI on NALLINO

Prepare the use of the SPI interface on the keypad. Add the pin muxing
and the ecspi node, however leave the status "disabled".
The default mode for the corresponding keypad pins is GPIO.

BCS 746-000993

--

Commit: seco-ne/kernel/linux-guf@f7a96c37

arm: dts: Nallino: Add keypad GPIO names

Add the names for the keypad GPIOs. By default thse should be muxed as
GPIO (inputs). By using the gpiod tooling it should be possible to make
use of them.

BCS 746-000993
      88179d68
  3. Jul 15, 2022
  5. Jul 13, 2022
    • GitBot's avatar
      Integrate gitlab-ci/add-test-reporting-to-test-jobs · e57f3fce
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@52bae4a1

Lava Testreporting: Add script to generate markdown report for given jobids

Adds scripts for mark down generation.
Adds scripts for lava test result queries.
Adds script to generate a mark down report from this data
Call script from submit_test to generate a report directly
after the testrun.
      e57f3fce
    • GitBot's avatar
      Integrate gitlab-ci/run-test-from-gitlab-directly · 83d6e0db
      GitBot authored 
      --

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

CI: Lava Test: Allow to install test image directly from gitlab

The images from the build job can be directly installed from gitlab.
To achive this some changes in the complete pipeline have been needed.

1. The variables used in the build job, like CI_PARAM_IMAGE, ... and
   related variables like BUILDPATH are only valid in the build job now.
2. The build job writes every variable needed in a follow up job into
   build.env. This also includes the url to the fng-install.sh of the
   final image.
3. The build.env file is used as dotenv artifact, as well as normal
   file artifact.
   The dotenv make the written variables automatically available in
   follow up jobs, that are using the aritfacts, like the deploy job.
   The normal file artifact is available via artifact download.
   (I did't found a way to download the dotenv file instead)
4. Some scripts have been added:
   - Find a job inside the pipeline by name, as the id is not known in
     advance.
   - Download all artifacts or one file of the artifacts from a given
     job
   - Download one file of the latest job by name
5. The scripts are used to download the build.env into the test job
   (where not artifacts are needed anymore)
6. The script is sourced and all variables are available inside the
   script.

Additionally this adds a fake build job to the ci-test pipeline, that
copies an image from srv73 and stores it as artifact in a way that a
test-job can run on it, like in the normal yocto pipeline.
      83d6e0db
  7. Jul 12, 2022
    • GitBot's avatar
      Integrate gitlab-ci/share-build-and-test-job-basics · b7c8ae9f
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@075aeccb

Refactoring: share build and test job basics for ci-test and Yocto

This shares YAML code for the following procedures:
- Build environment
- Source code checkout via repo
- SSH key and known hosts setup
- LAVA test submission
- Docker check if build folder is empty
      b7c8ae9f
    • GitBot's avatar
      Integrate linux-imx-kuk/rtc_overlays · 24345722
      GitBot authored 
      --

Commit: seco-ne/kernel/linux-imx-kuk@11963a85

tanaro:rtcs: Fix to RTC overlay mechanism

The first approach of selecting a RTC didn't work as expected.
The active RTC must reside on the rtc0 alias because otherwise
the hwclock utilities can't access the RTC.
For this to work, we now have a placeholder in the main device tree
that is filled with the actual values in one of the two overlays.
This breaks with the naming conventions for I2C bus devices, but
right now, we don't have a better solution.

BCS 746-000877
      24345722
  9. Jul 08, 2022
  11. Jul 07, 2022
  13. Jul 06, 2022
    • GitBot's avatar
      Integrate gf-emc-test-suite/rs485echo_fix_transmission_behavior · 56adf752
      GitBot authored 
      --

Commit: seco-ne/tools/gf-emc-test-suite@113135af

rs485echo: Fix RS485 transmission delays

Before, the delay_rts_before_send delay_rts_after_send fields were not
explicitly initialized. This led to a erroneous transmission behaviour.
Now the RS485 port settings are read before the half duplex
configuration is done. This ensures that the delays are set to 0 or to
a predefined value (device tree).

BCS 746-000908
      56adf752
    • GitBot's avatar
      Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more · eba8f16e
      GitBot authored 
      --

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

CI: pipeline yocto: Change scope of CI_PARAM_IMAGE, ... to fix fngsystem build

The variables CI_PARAM_IMAGE, CI_PARAM_DISTRO, CI_MACHINE have been
defined outside the job in the '.gitlab-ci.yml' file. This has a lower
precedence then variables defined inside the job, but it seems that
these variables are used in the scope of 'Trigger variables' when
available in the trigger job. These override the value set in the
template. As main results this made FNGSystem jobs build the normal
yocto.
      eba8f16e
    • GitBot's avatar
      Integrate gitlab-ci/CI-readd-allow-failure-true · 7580fc24
      GitBot authored 
      --

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

CI: Readd allow_failure:true to fix not finished pipelines

According to the docs a manual job always has allow_failure set to
true, but we see a lot of jobs staying in an unfinished state since
the removal of the allow_failure: true keyword for the sdk and test
jobs. This should fix the broken behaviour.
      7580fc24
    • GitBot's avatar
      Integrate gitlab-ci/test-artifact-upload · f93cbd00
      GitBot authored 
      --

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

CI: Hardcode the artifacts path in the generated job description

Some gitlab update(?) seem to have changed the behaviour in
variable passing. In the scripts the variables are available
but in the artifacts path does not resolve them any more.
May be it has something to do with the introduction of the
trigger:forward keyword.
      f93cbd00
  15. Jun 28, 2022
  17. Jun 21, 2022
  19. Jun 20, 2022
  21. Jun 13, 2022
  23. Jun 01, 2022
  25. May 31, 2022
  27. May 30, 2022
  29. May 24, 2022
  31. May 20, 2022
  33. May 13, 2022