This patch series aims to add SoC identification/SYSC/RST support for RZ/G2[ME] SoCs. This patch series is based on linux-4.19.y-cip and all the patches in this series are cherry-picked from linux rc

I think so, yes. It currently only works for mainline and stable branches. I have an open issue to add support for CIP branches. That would be fine with me. So long as I'm working for CIP,

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

Hi Ben, during the past face to face TSC meeting that took place in Nürnberg, there were two questions about the CVE tracker you have done that would need some more details from you that what I

Hello maintainers, all, As discussed previously we need to decide what Kernel configs to use/support for the arm64 architecture. Arm64 only has one supported config upstream –

Hello Daniel,

Yes, you can set that as well (IMAGE_TYPE = "targz-img"). We are using it for building containers. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded

[..] Jan: is it possible to add tar.gz to IMAGE_TYPE in ISAR? that's an easy format for LAVA to deploy to nfs/nbd. Patryk: from the documentation it seems that nbdroot supports the raw image format.

Isar-cip-core generally has to goal to generate fully bootable images ("turn-key" solution). That means an SD card or eMMC or raw flash image that contains all necessary artifacts at the right

Hello Jan,

Hello Daniel, Thank you for your feedback.

About which boards are we talking? How does the boot process and imaging look like for them? That will help assessing the effort (which can vary a lot, specifically with modern, complex

I don't disagree. I have no idea how much effort that would mean. Maybe it's worth asking around on LKML for suggestions. In any case, it will take 2 year - at least - to have that available in all

Am Mon, 18 Mar 2019 11:18:54 +0100 schrieb "[ext] Jan Kiszka" <jan.kiszka@...>: We really need a kernel patch for a binfmt cgroup/namespace. Henning

Checked, this seems to work (lesson learned: never create a test entry in binfmt_misc with magic:mask of 0:0). Will write a kas patch. Jan -- Siemens AG, Corporate Technology, CT RDA IOT

Well dpkg-reconfigure would be a bit nicer... Claudius -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell,

Ugly... And that call will actually be nop due to how the script works (if it works at all). It seems this binfmt installation never worked for the isar-kas container: builder@384a365634ab:~$ ls

Well you could just call '/var/lib/dpkg/info/qemu-user-static.postinst' from the docker entry point :)

...which is good to know. Maybe it gets tricked by something being enabled already. But I thought I tested this. Anyway, I guess we need to study that script /wrt how to achieve some reliable