Linux API continuity
Reuse POSIX threads, timers, sockets, epoll and common user-space applications.
LINRT REAL-TIME LINUX DISTRIBUTION
LinRT Oxygen
Linux-native deterministic performance with PREEMPT_RT
Choose Oxygen when standard Linux APIs, a rich embedded ecosystem and maintainability matter as much as bounded response times. It keeps the application model familiar while reducing kernel scheduling latency.
TECHNOLOGY PROFILE
KERNELPREEMPT_RT
MODELSingle Linux kernel
APIsPOSIX / Linux APIs
DRIVERSLinux driver model
Best starting point for Linux-native industrial products with measured real-time requirements.
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?
Real-time without abandoning the Linux programming model.
Choose Oxygen when standard Linux APIs, a rich embedded ecosystem and maintainability matter as much as bounded response times. It keeps the application model familiar while reducing kernel scheduling latency.
Broad ecosystem
A natural fit for Qt / Wayland, industrial connectivity and mainstream driver integration where qualified.
Simpler operations
Unified Linux scheduling, tooling, debugging and vulnerability management workflows.
Flexible tuning
CPU isolation, scheduler priorities, IRQ affinities and memory locking to fit measured loads.
02 / How the architecture works
Linux-native deterministic performance with PREEMPT_RT
Oxygen uses a PREEMPT_RT-enabled Linux kernel. Critical threads use real-time scheduling policies while Linux provides the services, drivers and user-space interfaces. The complete system remains in-band: competing kernel activity, hardware interrupts and application design still influence worst-case latency.
Engineering trade-off: Oxygen does not guarantee hard deadlines simply because PREEMPT_RT is enabled. Determinism must be demonstrated by end-to-end timing tests.
03 / Engineering considerations
Typical applications & What must be validated
Typical applications
- Industrial HMI with bounded control loops
- Connected gateways, protocol conversion and device management
- Edge systems combining real-time workloads with Qt or multimedia
- New applications built on standard Linux / POSIX APIs
Latency engineering checklist
- Define the actual deadline, jitter budget and worst-case-load profile.
- Prioritize SCHED_FIFO / SCHED_RR threads carefully; avoid starvation.
- Audit IRQ threading, DMA paths, drivers, clocks and memory allocation.
- Use cyclictest / rtla and application-specific end-to-end measurements.
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 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 — 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.
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
Oxygen
PREEMPT_RTThreaded 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 →Cobalt
Xenomai 3 · Cobalt / RTDMA separate high-priority real-time execution stage with mature Xenomai APIs, RTDM drivers and optional compatibility skins for selected legacy applications.
Explore the distribution →Tungsten
Xenomai 4 · EVL / libevlDovetail 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.
Technical references
Technical baseline and upstream documentation used for this presentation. Product scope and availability must be confirmed with LinRT.