Applied this one - the rest was already in next. Thanks, Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux

From: Quirin Gylstorff <quirin.gylstorff@...> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> --- kas-cip.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

From: Quirin Gylstorff <quirin.gylstorff@...> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> --- ....135-cip31-rt13.bb => linux-cip-rt_4.19.160-cip39-rt17.bb} | 4 ++--

From: Quirin Gylstorff <quirin.gylstorff@...> If cross compiling should be used the configuration path for pkgconfig needs to be adapted for the target architecture. Add pkg-config as build

From: Quirin Gylstorff <quirin.gylstorff@...> libubootenv provides hardware independent access to u-boot environments. This change conflicts with u-boot tools < 10.2019. Signed-off-by:

From: Quirin Gylstorff <quirin.gylstorff@...> - Update Kernel releases - Update ISAR to current HEAD of next - fix swupdate cross-compile - use libubootenv for swupdate & u-boot this works

Hi Pavel,

Hi, Pavel-san, Thanks for your offer. Yes, please do so! Best regards, -- M. Kudo

Hi! I believe the next step with 5.10.y is to create linux-5.10.y-cip branch at kernel.org. I'd propose to start with whatever is newest stable at the moment, so probably 5.10.8 or 5.10.9. Is it okay

Hello, This is where the issue is. The new filename is using a '.' instead of a '-'. i.e. - linux-cip-rt_4.4.244.cip51-rt32.bb + linux-cip-rt_4.4.244-cip51-rt32.bb Kind regards, Chris

Something is still broken, see https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/970301333 and https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/970301342. Pulling this patch

Thanks, applied. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux

Not necessarily. A downstream user could still include or bbappend cip-core-image while overwriting the password variable. Fine with me - except that the patch does two things in one: move

From: Quirin Gylstorff <quirin.gylstorff@...> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> --- kas-cip.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

From: Quirin Gylstorff <quirin.gylstorff@...> libubootenv provides hardware independent access to u-boot environments. This change conflicts with u-boot tools < 10.2019. Signed-off-by:

From: Quirin Gylstorff <quirin.gylstorff@...> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> --- ....135-cip31-rt13.bb => linux-cip-rt_4.19.160-cip39-rt17.bb} | 4 ++--

From: Quirin Gylstorff <quirin.gylstorff@...> - Update Kernel releases - Update ISAR to current HEAD of next - fix swupdate cross-compile - use libubootenv for swupdate & u-boot this works

From: Quirin Gylstorff <quirin.gylstorff@...> If cross compiling should be used the configuration path for pkgconfig needs to be adapted for the target architecture. Add pkg-config as build

Isar supports libubootenv since e77d030ed0ac5b122aa7b798131062946cb36699 cip-core since 683866e2b0c5113b849ef82cf206b3bb5c6e3e30 Quirin

Yes, since one next e77d030ed0ac5b122aa7b798131062946cb36699. Quirin