BSP Tracker / BSP Status / Renesas
Renesas upstreams aggressively and its BSP is CIP-based — mainline plus a small delta on a super-long-term-support kernel. GPU and camera are upstream; the H.264 codec is not. The real reason to stay on the vendor tree is the ten-year maintained kernel, which mainline does not give you.
Can you ship mainline instead, and what exactly do you lose if you do?
Mainline, with named losses
| Block | IP | Upstream | Detail |
|---|---|---|---|
| GPU | Mali-G31 (Bifrost) | upstream | renesas,r9a07g044-mali; panfrost. |
| VPU | H.264 codec unit | unverified | No upstream driver or binding found; it ships in the Verified Linux Package. |
| NPU | none (DRP-AI is on RZ/V2L) | n/a | |
| ISP | CRU + MIPI CSI-2 | upstream | renesas,rzg2l-cru; drivers/media/platform/renesas. |
Repository. https://github.com/renesas-rz/rz_linux-cip
Newest branch that actually exists. rz-6.12-cip14, tracking Linux 6.12. Last commit 2026-05-25.
Cadence. Built on CIP SLTS kernels — the point of which is a maintained kernel for a decade, which mainline does not offer. Branches: 5.10-cip54, 6.1-cip43, 6.12-cip14, each with a PREEMPT_RT variant.
Committed until 2038. The product page carries a Product Longevity Program badge for 2038. The wording is intent rather than guarantee: Renesas 'strives to maintain supply' for the duration of programme participation.
Layer. meta-renesas. No branch for the current Yocto LTS.
No wrynose branch. Worse, much of the shipped Verified Linux Package tooling still sits on dunfell branches — Yocto 3.1. If your build policy requires the current LTS, RZ/G2L has no layer branch for it.
Evaluate on. RZ/G2L Evaluation Board Kit (SMARC), MYIR MYD-YG2LX
Production modules.
The best boring-industrial profile here: a real 2038 longevity badge, a CIP super-long-term kernel, upstream-first, three independent SoM sources. Its weakness is Yocto and the closed video codec.
Renesas RZ/G2L (R9A07G044): upstream fixes stop December 2028. That leaves 29 months. After that date the kernel this BSP is based on receives no further security fixes from upstream, and maintaining it becomes your team’s responsibility.
There are three options:
All three are engineering work, and all three are work we do: reading vendor kernel trees, checking what mainline actually supports, and moving products from one to the other. This page is built from the same work.
An email when a kernel series reaches end of life, a board row changes, or a layer picks up a release branch. Nothing else.
RSS