Skip to content
Snippets Groups Projects
  1. Jul 20, 2022
  2. Jul 19, 2022
  3. Jul 18, 2022
  4. Jul 15, 2022
  5. Jul 14, 2022
  6. Jul 13, 2022
    • GitBot's avatar
      Integrate meta-seconorth-machine/rtc_overlays · fc7e26e5
      GitBot authored
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-machine@283c6dfb
      
      bootscript:dt: Added devicetree description file for i.MX8
      
      Added an description file with the default devicetree for i.MX8
      devices.
      The file is parsed/used by the post-install scripts to generate
      the boot configuration.
      
      BCS 746-000877
      
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-machine@ba9e87ec
      
      bootscripts: Clean-up and reformat
      
      Changed the copyright and URL in the bootscript recipes.
      Also did a clean-up/reformat of the recipes.
      fc7e26e5
    • GitBot's avatar
      Integrate meta-seconorth-distro/rtc_overlay_rebase · ae138446
      GitBot authored
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-distro@2cc3f539
      
      fng-install:prepare-dt: Replaced loop with find
      
      Fixes SC2044
      
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-distro@c14d978b
      
      fng-install:post-install: Added comments to scripts
      
      Extended the documentation and comments in the post-install scripts.
      
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-distro@32b8f0c2
      
      fng-install:rtc: Added RTC detection for the TANARO
      
      The TANARO will be produced with one of two RTC variants.
      We detect the RTC by querying the first register during the
      post-install and activate one of two devicetree overlays.
      
      BCS 746-000877
      
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-distro@3a397d44
      
      fng-install:prepare-kernel: Removed i.MX8 specific script
      
      The i.MX8 used a custom post-install script for the prepare-kernel
      step. Since the default script has been adopted for the i.MX8, the
      custom script is removed.
      
      BCS 746-000877
      
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-distro@3edf9fc8
      
      fng-install:prepare-image: Added new scripts and clean-up
      
      The new scripts (prepare-overlays and prepare-xml2dto) for the
      post-install steps have beend added.
      Also wrong indentations have been replaced and the lists have been
      sorted.
      
      BCS 746-000414
      BCS 746-000877
      
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-distro@40d7ba85
      
      fng-install:prepare-kernel: Added i.MX8 support
      
      The default prepare-kernel script didn't support the i.MX8.
      Tweaked the script, to support the custom requirements of the i.MX8.
      The i.MX6 specific parts for the generation of the overlays (from the
      shared XML) and the gf_platform detection has been moved to new scripts.
      
      BCS 746-000877
      
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-distro@5f97c8e6
      
      post-install: Rework and fix of overlay handling
      
      Overlays that have been installed by Yocto are now moved
      into /boot/overlays. This is due to the inability of Yocto
      to easily handle devicetree overlays during the build.
      
      Overlays that are provided via the parameters of fng-install
      (--DTBO) are also placed inside /boot/overlays. Additionally,
      they are appended to the overlays variable inside the
      overlays.txt file.
      The overlays.txt file is parsed during the prepare-kernel
      post-install step. The loaded overlays are then applied to
      the default devicetree.
      
      BCS 746-000414
      BCS 746-000877
      ae138446
    • 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
  8. Jul 11, 2022
  9. Jul 08, 2022
  10. Jul 07, 2022
  11. Jul 06, 2022
  12. Jun 28, 2022
  13. Jun 27, 2022
    • GitBot's avatar
      Integrate meta-seconorth-machine/fix_sis_touch-release_events · db25ebfb
      GitBot authored
      --
      
      Commit: seco-ne/yocto/layers/meta-seconorth-machine@0326de4b
      
      SIS: Fix touch-up issue
      
      Sometimes we get no touchup signal in Qt.
      This was seen with the QML drag-and-drop example.
      
      Looking at the output of evtest of the sis input device, you see
      different behavior for a working and a missing touch-up.
      
      Failed:
      <pre>
      ...
      Event: time 1587646331.383580, type 3 (EV_ABS), code 0 (ABS_X), value 2365
      Event: time 1587646331.383580, type 3 (EV_ABS), code 1 (ABS_Y), value 2894
      Event: time 1587646331.383580, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2365
      Event: time 1587646331.383580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2894
      Event: time 1587646331.383580, -------------- SYN_REPORT ------------
      Event: time 1587646331.402073, type 3 (EV_ABS), code 0 (ABS_X), value 2367
      Event: time 1587646331.402073, type 3 (EV_ABS), code 1 (ABS_Y), value 2887
      Event: time 1587646331.402073, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0
      Event: time 1587646331.402073, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 0
      Event: time 1587646331.402073, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2367
      Event: time 1587646331.402073, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2887
      Event: time 1587646331.402073, -------------- SYN_REPORT ------------
      </pre>
      
      Good
      <pre>
      Event: time 1587646407.907930, -------------- SYN_REPORT ------------
      Event: time 1587646407.922769, type 3 (EV_ABS), code 0 (ABS_X), value 790
      Event: time 1587646407.922769, type 3 (EV_ABS), code 1 (ABS_Y), value 1747
      Event: time 1587646407.922769, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 790
      Event: time 1587646407.922769, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 1747
      Event: time 1587646407.922769, -------------- SYN_REPORT ------------
      Event: time 1587646407.945577, type 3 (EV_ABS), code 0 (ABS_X), value 840
      Event: time 1587646407.945577, type 3 (EV_ABS), code 1 (ABS_Y), value 1918
      Event: time 1587646407.945577, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 840
      Event: time 1587646407.945577, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 1918
      Event: time 1587646407.945577, -------------- SYN_REPORT ------------
      Event: time 1587646407.968810, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0
      Event: time 1587646407.968810, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 0
      Event: time 1587646407.968810, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
      Event: time 1587646407.968810, -------------- SYN_REPORT ------------
      </pre>
      
      It seems that the @ABS_MT_TRACKING_ID value -1@ is missing somehow.
      
      This might be the case when the driver sends a valid coodinate but also
      states that the pressure is 0.
      
      Fix this by sending a touch-up (all ABS_PRESSUE, ABS_MT_PRESSURE, and
      ABS_BUTTON 0 and ABS_MT_TRACKING_ID -1) when pressure is 0.
      
      BCS 746-000871
      db25ebfb
  14. Jun 22, 2022
  15. Jun 21, 2022
Loading