- Sep 14, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f8d6de86 Make check error message more verbose -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@21e7edeb Improve ci-test build -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@76bd81d8 Fix check job rules -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a6721243 Move check job to parent pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@593784e1 Refactor check_if_integration_branch_is_up_to_date - Use "source" and "target" terminology in the script, just like in the GitLab CI variables. - Spefify data types for function arguments. - Rename function arguments to better reflect their data types. - Move determination of integration branch into main function, so that the successfull status message can be more verbose. - Remove parent_merge_request feature and checking for gitlab-ci integrations, because the check job does not run on gitlab-ci integration branches at all. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@45b49ee3 Remove build stage on master We don't need to explicitly trigger a build after merging changes in gitlab-ci. A master pipeline on the target projects runs automatically.
-
- Sep 13, 2022
-
-
Felix Gerking authored
The driver is required for usb type c support on the mc3 board. BCS 746-000948
-
Jonas Höppner authored
Adding new variable UBOOT_ADDITIONAL_DTB_NAMES to specify more then one devicetree, use it in the u-boot and the imx-boot recipe to integrate everything into one fit image. imx-boot needs a patch, to use the addional devicetrees in the makefile when writing the fit image.
-
- Sep 09, 2022
-
-
Tobias Kahlki authored
The first device tree in the list is used as default during the installation. If the list is sorted and an overlay is placed as first item, the device is unbootable after the installation.
-
Tobias Kahlki authored
BCS 746-000955 (cherry picked from commit 3e26efcc)
-
- Sep 08, 2022
-
-
Tobias Kahlki authored
BCS 746-000951
-
- Sep 06, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a0f7e84f Rename pipeline stages to reflect YAML filenames
-
- Sep 05, 2022
-
-
Clemens Terasa authored
Add support for the touch-glass-display set SCX1001255GGU06 to TANARO containing an FG1001L0DSSWMG01 panel and an SIS touch. Add the corresponding Device Tree and add the sis-i2c touch driver to the touchdriver packagegroup for all platforms (not only mx6). Additionally sort the variable list.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d25cdebf Really fix potential error message in retrigger job TypeError: 'NoneType' object is not subscriptable Example: https://git.seco.com/seco-ne/yocto/manifest/-/jobs/129201
-
- Sep 02, 2022
-
-
Jonas Höppner authored
Fix imx-boot dtb for tanaro. Set the uart address for imx-atf.
-
Jonas Höppner authored
-
Jonas Höppner authored
Kuk had a version of the bl31.bin add to the mkimage repo, but the yocto way to handle it, is to build it using the imx-atf recipe. Removing this overrides let imx-boot copy the files from the common deploy directory again.
-
Jonas Höppner authored
We used firmware files checked in into the mkimage repo by kuk, but the intended way is to use them from the firmware-imx-8m recipe. Setting this variable provides them for imx-boot.
-
- Aug 31, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3eef782e deploy_gitlab_ci: integrate only correct projects into the manifest Previously we integrated all projects into the manifest, even those that belonged to a different manifest branch. That led to all manifests having the same project revisions, even if they should be different due to different intgrated project branches. Save a list of integration sources for each manifest branch separately now, so that we can check which project belongs to which manifest branch later. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2b851ac6 Fix potential error message in retrigger job TypeError: 'NoneType' object is not subscriptable Example: https://git.seco.com/seco-ne/yocto/infrastructure/ci-test/minimal-manifest/-/jobs/127610 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c3fd0ecc Check if variable is defined before checking it value -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1be0f4b Fix jinja2 "or" operator -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8da534ec Run integration pipeline for target branch only When we're integrating a single branch into a single manifest branch, there is no need to run the intgeration pipeline for all configured integrations, but only for those that match the target branch of the current merge request. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8c94b725 ci-test: add job to check for correct foo branch This should catch an error where during a gitlab-ci merge process the wrong foo branch is integrated into the manifest, which happened in Yocto. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@163c7e1e Add yml extension to jinja2 templates -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@59523aa0 check job: disable verbose output -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@28bf0065 retrigger: add job states to log message
-
- Aug 30, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@fd742017 deploy_gitlab_ci: fix target branch in integration merge request We need to pass the correct target branch to the merge request creation instead of using the project's default branch. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@38379173 Run yamllint job on gitlab-ci integrations Otherwise no pipeline is created at all in these merge requests, which prevents the MR from being merged. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dce4f8a3 changelog_generator: Fix machine project ID We have deleted the original project due to git corruption. Replace with the new project's ID. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a7aa7c26 deploy_gitlab_ci: fix project argument passing -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8a38f194 Put all manifest intgeration jobs into a single stage -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a09564c1 deploy_gitlab_ci: explicitly pass gitlab-ci project and branch -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@172e7625 Improve error messages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f0f5a370 Improve naming of functions and variables -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c8b484ca Retrigger MRs from all integrating projects Instead of getting the projects from the manifest file, search them via their INTEGRATION variable. Improve log messages on this occasion: print URL instead of just IDs. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e75bfc1 Deploy gitlab-ci to multiple branches Add different integration jobs for different manifest branches. The merge stage only has one job for each manifest, though, because otherwise we cannot guarantee a consistent state for all branches. Extend the deploy script for this purpose, so that it can deploy to multiple manifest branches at once. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@771dcff1 Fix temporary dir path We were passing the complete TemporaryDirectory object to the repo clone function instead of just the path string, resulting in the repo being cloned into a local dir "<TemporaryDirectory '/tmp/tmphwakypf8'>". Fix this to actually use the generated temp dir. This change makes it necessary to keep the TemporaryDirectory object reference until we don't need the directory anymore, otherwise it will be removed immediately. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dce219c8 Print less important output in grey color -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e36261d deploy_gitlab_ci: remove hard-coded integration targets Get targets dynamically using the INTEGRATION variable instead. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@94cd6781 Recurse to child pipelines on retrigger This makes it possible to retrigger jobs that are not part of the given pipeline but in any nested child pipeline of it. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@fb1219a7 Ignore __pycache__ in scripts directory -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0c29c995 Refactoring: rename arguments for consistency -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d461090b Remove hard coded project and branch variables MANIFEST_PROJECT, MASTER_BRANCH_MANIFEST, MASTER_BRANCH_PROJECT -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a4aae414 Add rules for integration pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bfa38b24 Improve log messages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1c9670d9 commit_and_push: do not pass branch Branch can be implicitly determined via the repo.
-
- Aug 29, 2022
-
-
Tobias Kahlki authored
The MC3 board requires a custom devicetree. The devicetree was added to the current 5.15.32 kernel.
-
- Aug 26, 2022
-
-
Jonas Höppner authored
meta-frescale now uses a newer version of u-boot. We keep the old recipe here until we also updated u-boot for our devices.
-
- Aug 19, 2022
-
-
Tobias Kahlki authored
The post-install for fngsystem is running in a temp directory. This directory was missing the new artifacts (devicetree and overlays) to properly run. Further, the combine step of kernel + devicetree was failing for fngsystem, because the fngsystem partition is too small (at least for i.MX8 devices). To work around this, the post-install scripts checks for a "combine_kernel" file in the boot partition and only combines the kernel and the devicetree if the file is present. Cherry-pick from 4c3847e5
-
Tobias Kahlki authored
We still have some issues with the allocation of continous memory for the VPU support. Enabled some additional drivers/frameworks in the kernel to perform further tests.
-
- Aug 18, 2022
-
-
Tobias Kahlki authored
The 5.15.32 kernel is the first official kernel from NXP for Kirkstone. Forked the kernel from NXP and applied our changes on top of it.
-
- Aug 17, 2022
-
-
Tobias Kahlki authored
The logo selection is based on disabling the fngsystem or seco logo in the defconfig. Fixed the defconfig to re-enable the selection mechanism.
-
- Aug 16, 2022
-
-
Tobias Kahlki authored
-
Tobias Kahlki authored
The names of the fngsystem and guf (now seco) logo have changed.
-
Tobias Kahlki authored
We don't use the audit messages and they spam the log constantly. Disabled them in the defconfig.
-
- Aug 15, 2022
-
-
Felix Gerking authored
BCS 746-000835
-
- Aug 10, 2022
-
-
Tobias Kahlki authored
-
- Aug 08, 2022
-
-
Felix Gerking authored
Since we may need a different driver for touch tuning purposes, it is advantageous to integrate the driver as a module. BCS 746-000889 (cherry picked from commit f88db235)
-
- Aug 05, 2022
-
-
Jonas Höppner authored
-
Jonas Höppner authored
-
Jonas Höppner authored
-
Jonas Höppner authored
-
- Aug 04, 2022
-
-
Tobias Kahlki authored
We don't want to use the machine overrides from the meta-freescale layer. Therefore, we disabled the filter mechanism and re-added the old SoC names. To reflect this change, the files have been moved to the correct folders.
-
- Aug 03, 2022
-
-
Jonas Höppner authored
The overlays should be at the end, and the normal devicetrees from the second on should be sorted alphabetically, but the first entry should be kept as default used during installation when no dtb is given as parameter.
-
Jonas Höppner authored
The freescale layer would require this change, but we don't use the freescale layer together with the imx6 machines.
-
- Aug 02, 2022
-
-
Tobias Kahlki authored
NXP removed the old MACHINEOVERRIDES (mx6, mx8m, ...) and filters them out during the Yocto build. We rely on them quite often in our recipes and therefore disabled the filter for now.
-
Tobias Kahlki authored
NXP suggests using the dma-heap allocator instead of the ION memory manager from kernel 5.15.5 onwards.
-
- Jul 30, 2022
-
-
Tobias Kahlki authored
Activated/Enabled modules/drivers that might be related to the Hantro VPU and DRM.
-
Tobias Kahlki authored
Set the preferred gstreamer version for the i.MX8M devices to 1.18.5.
-
Tobias Kahlki authored
The mx8mm had a duplicate definition of the preferred kernel provider and version. Also the preferred version in the include for the i.MX8 devices has been changed to the correct name (linux-imx).
-
Tobias Kahlki authored
The defconfig for the 5.15.5 kernel is used by the mx8mm and mx8mp. The location "imx8mguf" is only accessible by the mx8mm. To make the config available to the mx8mp, the config folder was renamed. Note: imx8mguf is the machine name of the mx8mm. This is a known bug and will be fixed in the future.
-