LinRTBY DIGITAL DATA SOFTWARE

LINRT REAL-TIME LINUX DISTRIBUTION

LinRT Tungsten

Modern dual-kernel performance with Xenomai 4 / EVL
Choose Tungsten for new, highly timing-sensitive designs that benefit from a compact and scalable real-time core running alongside general-purpose Linux. The EVL execution model is built around the Dovetail interface.

Xenomai 4 / EVLDovetaillibevlOut-of-band execution
TECHNOLOGY PROFILE
KERNELXenomai 4 / EVL
MODELDual kernel + Dovetail
APIslibevl application APIs
DRIVERSEVL-aware OOB I/O
Preferred evaluation path for new, dedicated out-of-band real-time applications.
LinRT 5.3Q4 2026 · CRA Ready planned
LinRT 6.x LTSQ1 2027 · i.MX95 planned
NXP i.MXi.MX6 · 8MP · 91/93 · 95
SecurityCRA evidence approach

01 / Why choose this approach?

Keep hard time-critical work separate from general-purpose Linux.

Choose Tungsten for new, highly timing-sensitive designs that benefit from a compact and scalable real-time core running alongside general-purpose Linux. The EVL execution model is built around the Dovetail interface.

01 / ENGINEERING BENEFIT

Compact RT core

EVL focuses on essential scheduling and synchronization primitives for dedicated real-time workloads.

02 / ENGINEERING BENEFIT

Scalable model

SMP-oriented out-of-band execution and clear boundaries between critical and non-critical activities.

03 / ENGINEERING BENEFIT

Modern API

libevl provides file-descriptor-oriented primitives for real-time tasks and device interaction.

04 / ENGINEERING BENEFIT

Forward-looking kernel work

The upstream EVL/Dovetail project tracks modern Linux lines including a 6.18-based LTS branch.

02 / How the architecture works

Modern dual-kernel performance with Xenomai 4 / EVL

Tungsten layers the EVL core on a Dovetail-enabled Linux kernel. Critical threads, synchronization and suitable device paths execute out-of-band via EVL. Linux continues to host administration, user interfaces, storage, and non-critical services. libevl is a distinct ABI and not a transparent replacement for Xenomai 3.

Reference execution model. Board-level integration and exact APIs require qualification.
Reference execution model. Board-level integration and exact APIs require qualification.
Engineering trade-off: EVL is not source- or binary-compatible with Xenomai 3 by default. Platform, driver and application porting must be scoped and tested.

03 / Engineering considerations

Typical applications & What must be validated

Typical applications

  • New high-frequency industrial control loops
  • Low-jitter data acquisition with qualified device paths
  • Mixed-criticality applications with strong functional separation
  • Embedded platforms migrating toward modern Xenomai 4 / EVL

EVL engineering checklist

  • Select a maintained EVL/Dovetail kernel branch qualified for the SoM.
  • Use libevl APIs in the time-critical path; manage in-band transitions.
  • Validate interrupt pipeline, clocks, SMP behavior and real-time I/O.
  • Measure deadline misses and maximum latency under representative Linux stress.

04 / BSP portfolio & SoM targets

LinRT 5.3 in Q4 2026 · LinRT 6.x LTS in Q1 2027

Q4 2026 PLANNED / NOT YET RELEASED

LinRT 5.3 — CRA Ready

LinRT 5.3 is planned for Q4 2026 as the CRA-Ready evolution of the LinRT 5.x LTS family, on Yocto 5.0 Scarthgap LTS. BSP security controls and traceable validation evidence are the delivery goals; the separate customer CRA Certification Kit is planned for early 2027 alongside LinRT 6.x LTS.

Q1 2027 PLANNED / NOT YET RELEASED

LinRT 6.x LTS — NXP i.MX95

LinRT 6.x LTS is planned for Q1 2027, targeting Yocto 6.0 Wrynose LTS, Linux 6.18 LTS and Qt 6.12 LTS. NXP i.MX95 SoM support is announced as part of this generation, subject to configuration-specific qualification.

LinRT product roadmap — all diagram labels are in English
LinRT product roadmap — all diagram labels are in English
LinRT 5.x LTS

LinRT 5.x LTS — Scarthgap LTS baseline

LinRT 5.x LTS uses Yocto Project 5.0 “Scarthgap” LTS, with Linux 6.6 / 6.12 LTS variants according to target and distribution. LinRT 5.3 (product version, not Yocto 5.3) is planned for Q4 2026 as CRA Ready.

LinRT 6.x LTS · roadmap

LinRT 6.x LTS — Q1 2027 roadmap

LinRT 6.x LTS is planned for Q1 2027, targeting Yocto Project 6.0 “Wrynose” LTS, Linux 6.18 LTS and Qt 6.12 LTS. Support for NXP i.MX95 is planned with this release, subject to qualification for each BSP variant.

Reference and target hardware families. Final support must be confirmed per distribution, SoM vendor, board design and kernel branch.

05 / CRA readiness

Security evidence as part of BSP engineering

The proposed LinRT CRA-Ready BSP and CRA Certification Kit aim to make product-level cybersecurity assessment more repeatable, with evidence tied to a defined software image and hardware configuration.

Reference evidence workflow (English labels); not a substitute for a product conformity assessment.
Reference evidence workflow (English labels); not a substitute for a product conformity assessment.
CRA CERTIFICATION KIT · EARLY 2027

CRA Certification Kit — planned with LinRT 6.x LTS

Planned for early 2027 alongside the initial LinRT 6.x LTS release, the CRA Certification Kit is designed to help manufacturers turn BSP-level cybersecurity controls into traceable evidence for their own product conformity assessments.

SBOM & vulnerability tracking

Software Bill of Materials, CVE/VEX workflows and component traceability for a defined BSP build.

Security verification

Reusable hardening checks, boot and update assessments, and repeatable validation procedures.

Documented evidence

Requirements-to-tests mapping, result templates and evidence package structures for customer integration.

The Kit supports a product-specific Cyber Resilience Act conformity process; it is not a CRA certificate and does not replace the manufacturer’s risk assessment or legal responsibilities.

CRA Ready describes a compliance-support engineering objective; it is not a CE certificate or a guarantee that any finished product complies with the CRA. Qualification and features depend on SoM, kernel and board configuration.

06 / Explore another edition

Explore each distribution

Single-kernel, Linux-native real time

Oxygen

PREEMPT_RT

Threaded interrupt handling, preemptible kernel paths and standard POSIX / Linux APIs. The simplest route when latency targets can be met within the Linux ecosystem.

Explore the distribution →
Dual-kernel, RTDM and legacy RTOS APIs

Cobalt

Xenomai 3 · Cobalt / RTDM

A separate high-priority real-time execution stage with mature Xenomai APIs, RTDM drivers and optional compatibility skins for selected legacy applications.

Explore the distribution →
Dual-kernel, modern compact real-time core

Tungsten

Xenomai 4 · EVL / libevl

Dovetail connects Linux and the EVL core; libevl exposes dedicated real-time services to C/C++ applications requiring predictable out-of-band execution.

Explore the distribution →

Build a qualified real-time Linux platform

Discuss SoM support, system integration, real-time driver architecture and the scope of the LinRT CRA-Ready roadmap.

Discuss your embedded project →

Technical references

Technical baseline and upstream documentation used for this presentation. Product scope and availability must be confirmed with LinRT.