- Jul 20, 2022
-
-
GitBot authored
-- Commit: seco-ne/kernel/linux-guf@5d2e0fb4 arm: dts: NALLINO: Adjust drive strengths As requested by the EE department adjust the drive strengths for LCD, SD1 and Backlight PWM. BCS 746-000990
-
GitBot authored
-- Commit: seco-ne/kernel/linux-guf@aac44baf arm: dts: NALLINO: Activate SSC and assign PLL2_PFD1 as LCDIF clock parent In order to jitter the Display the LCDIF clock need to be derived from the PLL2 which supports Spread Spectrum clocking. With this and the OS and RAM validation tests Spread Spectrum can be generally used. Thus enable it by default. BCS 746-000990
-
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
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@cd3c70f1 qtbase: Add gif To add qgif to the Qt environment add the gif PACKAGECONFIG.
-
- Jul 19, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@f88db235 maxtouch:imx6: Integrate touch driver as module Since we may need a different driver for touch tuning purposes, it is advantageous to integrate the driver as a module. BCS 746-000889
-
- Jul 18, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@5f3c2a2a image-nogplv3 classes: Remove the explicit PACKAGE_EXCLUDE The explicit PACKAGE_EXCLUDE should not be necessary and prohibited by using INCOMPATIBLE_LICENSE. Further if a compatible package is available (i.e. for meta-gplv2) PACKAGE_EXCLUDE would prevent it from being included in an image. -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@25358873 layer.conf: Make dependencies more explicit Add meta-gplv2 and SECO Northern Europe's guf-distro as layer dependency. -- Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@ce565b80 distro: Add guf-wayland-no-gplv3.conf Previously it was found under meta-seconorth-distro however better fints in this layer.
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@340c26c7 distro: Remove guf-wayland-no-gplv3 The distro is meant as basis for an image containing no GPLv3 code. However we refactored parts into a separate layer. Remove the distro config guf-wayland-no-gplv3 and add it to the special no-gplv3 layer.
-
Clemens Terasa authored
Add the meta-gplv2 layer to the manifest and download it by default. Without the addition to the bblayers.conf it will not be used. Change-Id: I65fec794edf0f8aeb3e2cea172a9b1eaf0421f61
-
- Jul 15, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@ad7371e0 linux: defconfig: imx6ull: Add GPIO and PWM beeper as module Add support for GPIO and PWM beepers. This enables the on-board beeper on the SECO Northern Europe NALLLINO platform. BCS 746-000992
-
GitBot authored
-- Commit: seco-ne/kernel/linux-guf@0c1c9ad5 arm: dts: Add NALLINO PWM beeper Add the support for the PWM5 and the connected on-board beeper to the SECO Northern Europe NALLINO platform. BCS 746-000992
-
GitBot authored
-- Commit: seco-ne/tools/gf-emc-test-suite@8e0e4e6c bball_qml: Pass arguments to internal qmlscene To use the bball_qml sample with a different Qt platform (i.e. linuxfb) we need to pass the @-platform@ parameter. However, this was not possible with the current bball_qml shell script. Add pass the script arguments to qmlscene as well. BCS 746-000991
-
- Jul 14, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@55a34692 maxTouch:udev: Add udev rule to skip maxTouch fwr loading fallback The current version of the atmel_mxt_ts driver tries to load a controller configuration on each driver probe. However, if no config is provided or can't be provided because the driver is built-in, the driver probing process is delayed by 60 seconds because of a sysfs firmware load fallback. Added a udev rule that automatically cancels the sysfs firmware fallback. BCS 746-000892 -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@82cbcf67 imx6:mxt-touch: Add kernel support for atmel mxt touch BCS 746-000886
-
- Jul 13, 2022
-
-
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.
-
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
-
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.
-
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.
-
- Jul 12, 2022
-
-
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
-
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
-
- Jul 11, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@883e6834 fngsystem: Added lsb-release to fngsystem The lsb-release command can be used to query detailed information regarding the Yocto image/build (from the userspace). -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@f584eef6 packagegroup: Added lsb-release to guf-small The lsb-release command is used by Lava to query system information.
-
- Jul 08, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-machine@df176aae machine:tanaro: Added RTC overlays In the future, the TANARO will be produced with two possible RTC variants. Both variants are present in the main devicetree but are disabled by default. During the installation, one of the RTCs will be activated via one of the two devicetree overlays. BCS 746-000877 -- Commit: seco-ne/yocto/layers/meta-seconorth-machine@49cec441 machine: Clean-up of i.MX8MM machine Also small changes to the Kernel include file.
-
GitBot authored
-- Commit: seco-ne/kernel/linux-imx-kuk@9b1710b2 tanaro:rtcs: Added overlays for the TANARO RTCs The TANARO will be produced with one of two RTC variants. One of them will be activated during the installation by applying one of the overlays. BCS 746-000877
-
Jonas Höppner authored
BCS 746-000917 Change-Id: Ie2cc0b608c1823ce34b65308ceedfa2885f2674b
-
- Jul 07, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@38c8f73c FNGSystem: Install kernel-modules to fix missing sound support We did remove the kernel modules for FNGSystem to reduce the image size. Compared to FNGSystem 27 the kernelmodules are adding about 2 MB, which seems to be OK for me.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800 CI: Add hardcoded artifact's path generation also for fng system
-
GitBot authored
-- Commit: seco-ne/tools/gf-productiontests@5d76a070 Print test result to console when the test is done
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@f9407345 shared-conf: Allow on/off for bool values not only true/false -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@920b5c91 fnginstall-postinstallation: Fix boot partition detection for fngsystem The scripts failed if run in an installed fngsystem. This is needed in FT2, when new xml files are installed after the FNGSystem installation.
-
- Jul 06, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@b3c8ca1b alsa:imx6: Switch to sgtl5000 as default audio card Replaced absolute card number by the ID of the sgtl5000 audio card. Added additional alsa configuration files for imx6ull as it does not have the sgtl5000 codec. BCS 746-000548
-
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
-
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.
-
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.
-
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.
-
- Jun 28, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f39e65ab Manifest: really include yamllint in the full pipeline Previous commit did not have the effect due to wrong extend order.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0dd147c8 SDK: Remove package step from build sdk, add sdk to artifacts, create deploy_sdk -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ecab2962 Manifest: include yamllint in full pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a4071423 Manifest pipeline: run full build pipeline when triggered via web UI -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8862b213 Manifest refactoring: move job rules into classes This way they can be reused instead of redefining them in each job. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d604b330 Fix wrong remote name in ci-test pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e810c2ac Fix wrong manifest project ID for ci-test pipeline
-
- Jun 27, 2022
-
-
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
-
- Jun 22, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@325cd3c2 multiscreen-compositor: Adapt receipe to adapted naming, add message client
-
- Jun 21, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@9b8cf51c Share manifest pipeline for ci-test and yocto Combine all common yaml parts in manifest-pipeline.yml and add manifest-pipeline-yocto.yml and manifest-pipeline-ci-test.yml containing the different variable assignments for each environment. This change implicitly introduces parent-child build job generation in the ci-test pipeline, like it is done in the yocto pipeline already. The ci-test build jobs have been moved to build-jobs-ci-test.jinja2 accordingly. Furthermore rename GITLAB_CI_CURRENT_REV to GITLAB_CI_REVISION and remove the run conditions from all generated build jobs, since these are already present in the upstream trigger job. The repos including these files have to be updated with the new file and variable names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1b939fe Use CI variables in build template directly The job generation script implicitly passes the OS environment to the template, so that the template has access to all GitLab CI variables. Hence there is no need to explicitly pass any of them as command line arguments. This change makes the "generate-build-jobs" job more generic, so that it can be shared with the ci-test pipeline in the future. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@775c09c1 Add gitlab_backup script to download all project exports of a gitlab group
-
GitBot authored
-- Commit: seco-ne/tools/qt-multi-screen-compositor@bb90d170 Cleanup: Add common header for client and server, remove unused code -- Commit: seco-ne/tools/qt-multi-screen-compositor@9c3b785e Config: Move the read rotation function inside the config class -- Commit: seco-ne/tools/qt-multi-screen-compositor@3bc95fd9 Add compositor-message tool, massiv renaming and cleanup -- Commit: seco-ne/tools/qt-multi-screen-compositor@00617781 Add server class, implement command decoding Add hide and show window MoveWindowToScreen
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@98409477 multiscreen-compositor: Adapt receipe to adapted naming, add message client
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@7f68f307 Yocto manifest build: re-enable build:merge_request job This job was accidentally disabled in 2e6c1b4, because it was included in the generated child pipeline. This pipeline is not created on the master, though, so the condition for the job was never met. Move the job to the parent pipeline again, so that it gets executed on the master like before. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@970c7fd7 Re-add yamllint stage to ci test manifest pipeline Was accidentally removed in previous commit.
-
GitBot authored
-- Commit: seco-ne/yocto/layers/meta-seconorth-distro@c0871d1e fng-install: Fix --partition-scheme change in FNGSystem install script When switching from scheme 1 to 2, there was a bug leading to an unformated partition. Additionally I removed the partition message for FT2. This is only used during the yocto installation and was in the wrong position anyway. -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@a4ecd599 fng-install: Move the partition-scheme parameter to the fngsystem install script The implmentation was not really working when used in a yocto installation, as it would have needed a relocation of FNGSystem. Now the explicit change of the partition scheme is only be possible together with the installation of FNGSystem. -- Commit: seco-ne/yocto/layers/meta-seconorth-distro@e811145d fng-install: Fix installation issue when used with fresh FNGSystem 15.1 When FNGSystem 15.1 was just installed and only one partition was setup on the device the installation failed. This is fixed here. Also: in A-B installation mode is the used target (A or B) reported after the installation.
-