Hello Hayashi-san, This is an option. I guess I've spent too long in the oe world without apt. A key dependency here though is to make sure that the boards have a direct connection to the internet. Ok

Hello Punit, Please do ?? True. Good point, agreed. This is something we do indeed need to do. Thanks, Chris

Hello Daniel, Not a bad idea. I'll give it a go. Do you have an 'RT' config fragment you can share? I guess it depends on what approach the Kernel maintainers would rather take. Maintainers: Do we wan

Hello, Okay. I'm thinking that we aren't going to be able to escape having a separate 'testing' version of CIP-Core, based on ISAR on the assumption that it has more supported packages then Deby. Or n

Hello Pavel, Hayashi-san, Jan, Daniel, Addressing this email to all of you as both RT and CIP Core are involved. I started to look into RT testing in more detail today. I've created an RT configuratio

Hello Quirin, Thank you for sharing this. Once you're happy with it, please sent a merge request to linux-cip-ci and I'll help review it in detail. I've added you as a developer to the project, so you

Sounds like a plan. I'll add it to my backlog, unless anyone else is keen. Kind regards, Chris

Happy new year to you all! Just a quick update to go through the latest status and some recent changes to the CIP testing for the Linux Kernel. # LAVA Labs We currently have two LAVA labs, lab-cip-ren

Hello Hayashi-san, I've submitted a MR that fixes this issue: https://gitlab.com/cip-project/cip-core/deby/merge_requests/3 Note that there is still a build failure as it seems that one of the package

Hello, It doesn't look like there are any recent changes in the .gitlab-ci.yml file. However the GitLab runner we use was upgraded to a newer version since your last build. @Adler, Michael, @Gylstorff

For those interested in such things, please see: https://gitlab.com/gitlab-org/gitlab/issues/43710 Kind regards, Chris

Hi Pavel, I've force-pushed the linux-4.4.y-cip branch to match upstream, which should hopefully solve this issue going forward. Kind regards, Chris

Hello Pavel, This error happens now and then. It's caused by GitLab taking too long to fetch the CI configs from a separate GitLab repo. Usually trying again a few minutes later works. I've started th

Hello all, Just a heads up that the Mentor LAVA lab will be offline for most of Saturday due to some electrical maintenance in the building where it is hosted. This will affect the Altera-Terasic-Deo-

Hello Smita, all, I've submitted a pull request[0] that sets CONFIG_IGB to 'y' in siemens_ipc227e_defconfig. The reason behind this is so that the Kernel will boot/mount the RFS when using a bzImage i

Hello Greg, [...] The two dtbs that fail to build are fixed by reverting by the patches below: ea03518a3123 ("arm64: dts: allwinner: a64: enable sound on Pinebook") d0a925e2060d ("arm64: dts: qcom: sd

I've only just started building with this config in our CI setup, but building the dtbs locally with v4.19.88 didn't produce these results for me (and building locally with v4.19.89-rc1 does result in

Hello, 7150 arch/arm64/boot/dts/arm/juno.dtb: Warning (graph_port): /etf@20010000/ports/port@1: graph node unit address error, expected "0" 7151 arch/arm64/boot/dts/arm/juno.dtb: Warning (graph_port):

Latest 4.19 now building, but I'm seeing a number of warnings and errors when trying to build the arm64 defconfig dtbs. https://gitlab.com/cip-playground/linux-stable-rc-ci/-/jobs/374092442 arm/juno.d

Thanks Greg, building okay for me now. Regards, Chris