Users are required to prepare a local git repository, by default "../kernel", however there is no check at the moment. Alternatively, we could also create a repository for them (mkdir ../kernel; git i

Currently the user is required to create its own remotes by hand. This should not be necessary, because the information is already collected in conf/remotes.yml. For that reason, if we detect that any

Otherwise, the script will not find all the expected tags and fail with a message like: fatal: ambiguous argument 'v5.1..torvalds/master': unknown revision or path not in the working tree Signed-off-b

This is probably a copy&paste mistake that had no effect because the contents of _get_configured_remotes and _get_configured_branches is the same. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@tos

The Readme indicated some remote names (torvalds, stable) but not all of them. Ask the user to check conf/remotes.yml instead. I also added information on how to override or extend the configuration f

Hello Ben, I am trying to write a Quickstart about "cip-kernel-sec" for the CIP wiki (see initial draft attached). The Readme file mentions that you need two remote branches (torvalds and stable) defi

OK, I added that and sent the patch to the list. I have also sent you a merge request on gitlab with the 3 patches. Thanks, Daniel

A similar bmap patch has been sent to ISAR upstream, but while it gets accepted and until we update the ISAR version, we can use this backport. Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshib

Thanks Michael, It seems that worked out! https://gitlab.com/cip-project/cip-core/deby/-/jobs/229463821 Best regards, Daniel

Hi Michael, [snip] I tried but I got this weird behavior: https://gitlab.com/cip-project/cip-core/deby/-/jobs/228110647 $ export USER_ID=30000 $ /bin/bash /kas/docker-entrypoint $ whoami root $ cat /e

Continuing with this conversation on the public list, it seems that the job on gitlab-cloud-ci failed: https://gitlab.com/cip-project/cip-core/deby/-/jobs/226291592 --- Error summary --- ERROR: OE-cor

ext4load seems to be available on the u-boot command line. After loading boot.scr, don't we need the "source" command to work? "source" does not seem to be configured in the pre-installed u-boot. Also

This patch adds support for the iwg20m board to isar-cip-core. - Kernel version notes This board is only supported by the 4.4 kernel. For that reason, the preferred version is set to 4.4 and the user

Hi Jan, Here is the patch again with kernel set to 4.4 by default [next] iwg20m: add support for this board Thanks, Daniel P.S.: sorry for not using some prefix the last time.

Hello Michael, I have added an initial, very simple, gitlab-ci yaml script for building CIP tiny profile (Deby for BBB). https://gitlab.com/cip-project/cip-core/deby/blob/master/.gitlab-ci.yml I have

Sorry, i forgot to fill the subject line for the --compose option.

This patch adds support for the iwg20m board to isar-cip-core. - Kernel version notes This board is only supported by the 4.4 kernel. The document doc/README_iwg20m.md already explains that. - U-boot

Hi Jan, This patch adds support for the iwg20m board on ISAR CIP Core. [PATCH] iwg20m: add support for this board For now, it uses the u-boot shipped with the board. We could improve that in the futur

Hi Jan, I was surprised to see so many u-boot debian packages: https://packages.debian.org/search?keywords=u-boot For now, please let me go the legacy way (ask users to 'setenv' things). Do you have a