The 0.9.1 release box of B@D has been successfully imported into Windows 10 and both a QEMU and BBB health check have been run on that virtual machine. This setup also works when provisioning a box

Actually, there's something not quite right here. With just CONFIG_ARCH_R8A7743 and CONFIG_ARCH_R8A7745 enabled (but no other R-Car platforms) I get: arch/arm/mach-shmobile/built-in.o: In function

These all look good to me, so I've applied these to the linux-4.4.y-cip branch. Are you going to add more driver support (e.g. ravb, xhci-rcar) and device tree sources? Ben. -- Ben

No, also that works: It won't leave the proxy settings behind in the image, but it allows to build it behind a proxy. We don't want to generate "proxified" images that will then only work in a very

Hi Jan,

Hello Daniel, Sorry we missed you! Thank you for resuming the conversation. Chris: Agreed. Chris: Ideally yes, but currently I don't think all of the reference boards are in mainline u-boot, and

From: Sergei Shtylyov <sergei.shtylyov@...> Add minimal support for the RZ/G1E (R8A7745) SoC. Signed-off-by: Sergei Shtylyov <sergei.shtylyov@...> Reviewed-by: Geert

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:

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

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