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

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

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

This series aims to add basic SoC support for r8a7743/r8a7745. All the patches in this series are cherry-picked from the upstream kernel. This series has been tested against linux-cip tag

Err, right, that's what I meant. Yes, I'm sure. I've just written the doc for a product SDK, and that uses no further settings as well,

We should probably suggest to call "USER_ID=$(id -u) docker run ..." - it there a way to achieve this in an easier way? Still learning all this docker stuff. Hmm, they should, I'm using them for

Hi Jan,

Looks good. You should just set version to 0.10 and use yesterday's release. You can pull the corresponding docker image from https://hub.docker.com/r/kasproject/, and there should be a pip package as

Hi all, # Chris, I wanted to discuss about the U-Boot policy last night during the online meeting but somehow I missed the URL change. We have had some discussions about U-boot for a while but I

Hi Jan,

Hello Agustin, As long as the binaries don't include Renesas' proprietary libraries for graphics or multimedia [1] we are happy for CIP to distribute them as per option 1) above. For the Kernel,

Hello Yoshi-san, Agreed. We intend to follow the proper process when backporting to the actual CIP Kernel. The repository above is just a quick release to allow users to get the iWave RZ/G1M board

I agree with you. But I have a consideration for current status for renesas-cip repository. I think the current repository is under development. It looks Renesas's upstreaming effort for CIP. We can

Hi Chris and all, I had looked the repository and have a suggestion. When you backport patches from upstream, could you add the following line in commit message? (cherry picked from commit

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

Robert Marshall <robert.marshall@...> writes: A further update on progress on this issue: We've configured the Windows 10 virtual machine with ser2net (running on the vm and enabling

Nice work! Maybe I find the time to model a binary Debian variant as well, using Isar [1] - ideally prior to DebConf. Btw, instead of having yet another setup.sh, you may want to have a look at kas

Hello Agustin, Let me check internally as to what we can provide. Kind regards, Chris

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