Hello Kazu-san, Thank you for confirming. Below is the merge request for the same. https://gitlab.com/zuka0828/isar-cip-core/-/merge_requests/1 Thanks Venkata.

Hello Venkata, Thank you for checking the result. I confirmed that this variable should not be overwritten in the image recipe. Could you send MR including this update to

Thank you for your comments, Punit. I'll reply to your queries, see the followings. We considered and decided to adopt only sudo binary. As the result, sudo source code includes both sudo and

Hello Kazu-san, I observed 'init' system is not included in the image when append operator is not used and so booting the image is not successful. Here is the output of `bitbake -e

# Add cip-dev@... to CC Hi Pavel, Thanks for your comment.

Hello Venkata, Thank you for the information. Regarding the usage of `IMAGE_PREINSTALL`, I'm not sure if we always need `+` in the image recipe. Example:

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. *Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting

Hi Jan and All, Both de0-nano and IPC227E targets are up and running. I have monitored for test jobs on it and those completed successfully. Thank You!! Regards, Bikram

Hi Jan and All,, We are working on it. Looks like we have a slow network in last few days in our lab that results in rootfs download timeout failure. Time being we need to increase the current

Bikram, could someone on your side check the board status in the Mentor lab? Thanks! I'm not happy about the parsability of those LAVA logs either, but I have no idea if/how that can be improved

Hi, As mentioned earlier, I had some questions / queries regarding the requirements for the proposed packages. Sending them here for discussion. Kento Yoshida <kento.yoshida.wz@...>

Hi! Yes... I don't need that target, but I need de0-nano... and it did not work last time I checked. On a related note... it would be good to somehow show difference between "kernel test failure"

Hi All, Is kselftest maintained in the cip-kernel tree? I do see some branch[1] maintained by Nobuhiro-san for kselftest, but it's out of 5.6 linux tree. The reason being to gather collective

Hi Kazu-san and Dinesh, I have created the image with all proposed security packages included. applied the below change, and booted the image in QEMU correctly. ----------------- diff --git

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. *Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting

Hi, Pavel-san, Thanks for your updates. If you cannot make it, see you next week on the IRC. Best regards, -- M. Kudo

Hi! I'm not sure if I'll be able to make it on IRC this Thursday. Work done this week: reviews on 4.19.107 and 4.19.108. Attempt to create new 4.19-rt release, but it has failures

The logs read like the targets are not (always) coming up, e.g. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/457824214#L377 Jan -- Siemens AG, Corporate Technology, CT RDA IOT

Hi! And something went seriously wrong after these tests. I submitted same tree twice, and got different results. First this -- de0-nano

Hi! I managed to narrow the bad commit to the -rt tree, between: OK 122904930 pick 69aa73357e6a rcu: Don't allow to change rcu_normal_after_boot on RT pick 849ef8789077 pci/switchtec: fix