Hello Ben, I hope the move went okay. I plan to start backporting some patches to the CIP Kernel soon, to begin adding support for the Renesas CIP reference platform. I’ve had a look at [1] and have a

Dear CIP friends, I should have sent this report last week but I was travelling. For those of you who are not following our work closely at gitlab.com here is a summary of the main work that Don, Robe

Hello Ben, Do you have a plan for when future releases of the CIP Kernel will be made? It would be good to have a fixed release cadence or roadmap, so people using the Kernel can plan their activities

Hi, as a results of the work we have done to take control over building the CIP kernel and initramfs, we have introduced in our critical content path a fourth wiki page[1], so now we have five.[2] Thi

I've released Linux version 4.4.75-cip6. This adds the fixes from stable versions 4.4.70-4.4.75 inclusive, plus two regression fixes that were missing from the 4.4 stable branch. I reviewed those fixe

Dear CIP friends, please check below. This is a use case we will meet in a few weeks/months. It is important to see others walking the same route. -------- Forwarded Message -------- Subject: [Lava-us

Hi, one of the tasks that the CIP testing team has been performing since before the B@D release is a daily LAVA health check using the CIP kernel and BBB[2]. What is a health check? According to LAVA

Hi, please see below an example of a report sent to the kernel-build-reports@... of the latest LTS kernel version. As you know, kernelci is mainly targeting kernel developers, not kernel maintainers.

Hi, three new repositories has been created: * https://gitlab.com/cip-project/cip-testing/imported-kernel-tests For those third party tests we will use to test the CIP kernel * https://gitlab.com/cip-

There is a known issue with b@d when running a lava QEMU health check from behind a web proxy. When attempting to retrieve the kernel, it produces the error Invalid job data: ["HTTPSConnectionPool(hos

Dear CIP friends, as you know, B@D was released right before OSSJ started. I would like to thank the LF and the CIP board for doing the extra effort to go through the license clearance/approval proces

The B@D development team has been investigating if there are any issues with the use of the B@D VM on Windows. The ticket https://gitlab.com/cip-project/cip-testing/testing/issues/106 is being used to

Hi, Kernel maintenance 1. We have a new CIP kernel v4.4.75cip6 As anecdote, the kernel includes two patches that fix two regressions introduced by LTS patches. These fixes will be part of the next LTS

Dear CIP friends, I’d like to announce the availability of a development repo [1] based on the CIP Kernel for the iWave RZ/G1M Qseven Development Platform [2]. The main aim of this repository is to al

Hi Chris, one of the things we need to figure out is how we will distribute the kernel including the support for the Renesas board at CIP. We have three options to provide the kernel with the board su

From: Sergei Shtylyov <sergei.shtylyov@...> Add support for the first two members of the Renesas RZ/G family, RZ/G1M/E (also known as R8A7743/5). The Ether core is the same as in the R-Car gen2 SoCs,

From: Sergei Shtylyov <sergei.shtylyov@...> Renesas RZ/G SoC have the R-Car gen2 compatible IRQC interrupt controllers. Document RZ/G1[ME] (also known as R8A774[35]) SoC bindings. Signed-off-by: Serge

From: Sergei Shtylyov <sergei.shtylyov@...> Renesas RZ/G SoC also have the SCIF, SCIFA, SCIFB, and HSCIF ports and they seem compatible with the R-Car gen2 SoC in this respect... Document RZ/G1[ME] (a

From: Sergei Shtylyov <sergei.shtylyov@...> Add minimal support for the RZ/G1M (R8A7743) SoC. Based on the original (and large) patch by Dmitry Shifrin <dmitry.shifrin@...>. Signed-off-by: Sergei Shty

From: Laurent Pinchart <laurent.pinchart+renesas@...> The four SoCs use identical machine operations, consolidate them into two machine definitions in a single file. Signed-off-by: Laurent Pinchart <l