Standard Linux Boot vs. GraphLab Boot
Recorded comparison of the same hardware running an unmodified embedded Linux system and the same system with GraphLab Boot enabled.
Watch high-resolution version on YouTube.
Designed for production systems
Deterministic early UX
First pixel is rendered by the real-time core, giving the system deterministic display behavior from power-on.
Flicker-free boot bridging
Continuous display output from power-on through Linux startup with a seamless DRM handover.
Minimal integration surface
Integrates into standard boot flows using a small SPL hook, device tree additions, and a Linux DRM handover driver.
How it works
Real-time graphics stack
The real-time core runs a lightweight graphics pipeline and becomes the display authority at power-on.
Linux boots in parallel
Linux initializes normally on the application cores while the display remains continuously driven by the real-time core.
Seamless handover
A DRM handover transfers display ownership to Linux without re-initializing the panel - no mode reset, no blanking.
The real-time core owns the display from power-on while Linux boots on the application cores.
Validated on real production hardware
GraphLab Boot is designed for heterogeneous SoCs that combine real-time cores and application cores, enabling early display ownership and deterministic handover to Linux graphics.
Currently validated hardware
NXP i.MX8M Plus
Vendor-independent architecture designed for heterogeneous SoCs with real-time and application cores.
Software Ecosystem
GraphLab Boot integrates with standard embedded Linux graphics stacks using a controlled DRM display handover.
Validated platforms
Minimal Yocto Project build (Scarthgap)
Torizon OS on Toradex Verdin iMX8M Plus
Integration verified on both a minimal Yocto Scarthgap system and a full Torizon OS distribution.
Architecture compatible
Android systems using the Linux DRM graphics architecture.
The display handover architecture is compatible with Android-based systems using the standard Linux DRM graphics pipeline.
Where GraphLab Boot fits best
Industrial HMI
No black screen. Predictable startup behavior.
Automotive & Mobility
Flicker-free startup sequence; deterministic early UX behavior.
Medical & Regulated
Traceable boot stages; controlled display behavior.
Silicon / SoM Partners
Leverages heterogeneous cores; showcases platform capability without OS disruption.
Get started
See GraphLab Boot on real hardware and request an evaluation kit.
For more technical information, visit the GraphLab Developer Docs.
To try the demo, first create your GraphLab Portal workspace. The technical docs and onboarding steps are available in the portal.
Share your project details and our sales team will contact you with commercial and rollout information.
Evaluation hardware
Order the official Toradex evaluation hardware directly from Toradex.
Common questions
Does GraphLab Boot replace our bootloader?
No. GraphLab Boot does not replace your bootloader. It integrates into the standard boot flow and runs on the system's real-time core, while your existing bootloader and Linux system start normally on the application cores. The display remains stable until Linux takes ownership through a seamless DRM handover.
How does the flicker-free handover actually work?
GraphLab Boot runs a lightweight graphics pipeline called GraphLabCore on the system’s real-time core. GraphLabCore renders the first pixel during early boot and maintains continuous display output while Linux initializes. Linux then takes ownership of the display through a dedicated DRM handover, avoiding display re-initialization, mode resets, or black frames.
Is the boot process traceable or auditable?
Yes. GraphLab Boot provides a controlled and deterministic early display stage. Boot stages can be logged and analyzed, which can be valuable for regulated industries and systems that require traceable startup behavior.
Does this interfere with secure boot or the chain of trust?
No. GraphLab Boot is designed to integrate with secure boot flows. The real-time core firmware can run as signed code, and control is then handed to a signed Linux kernel, preserving the chain of trust.
What does integration typically involve?
Integration is intentionally minimal. In most cases it involves:
- A small SPL initialization hook
- Device tree additions
- The GraphLab DRM handover driver for Linux
Which hardware platforms are supported?
GraphLab Boot is currently validated on a Toradex Verdin iMX8M Plus platform. The architecture is hardware-agnostic and designed for heterogeneous SoCs that combine real-time cores and application cores, enabling ports to other ARM-based embedded Linux systems.
Can we show our own branding at boot?
Yes. The boot splash can be fully customized with your own branding, including logos or custom visuals. GraphLab Boot supports full white-label deployment, so no GraphLab branding is required. The display remains under GraphLab Boot control until Linux takes ownership through the seamless DRM handover.
Can GraphLab Boot show animations or a progress bar?
GraphLab Boot supports customizable early boot visuals such as a logo, spinner, and status text, allowing products to provide immediate feedback while the system initializes.
The primary focus of GraphLab Boot is a deterministic, flicker-free display from power-on through the Linux handover. More advanced early UI capabilities are planned as part of the extended GraphLab platform.
How is this different from Plymouth or U-Boot splash screens?
Traditional splash approaches such as Plymouth or U-Boot logos operate within the Linux boot process and often require display re-initialization when Linux graphics drivers take over, which can lead to visible flicker.
GraphLab Boot works earlier in the boot sequence. It drives the display from the system’s real-time core during early boot and keeps the output stable until Linux graphics are ready.
The handover to Linux is performed through a controlled DRM display handover and can be configured as:
- automatic – when the Linux DRM subsystem becomes ready
- application-controlled – when the system UI or compositor has fully initialized
Because the display remains active during this transition, Linux splash systems such as Plymouth can still be used normally after the handover.
How do we start evaluating GraphLab Boot?
Most teams begin by evaluating GraphLab Boot on a validated reference platform. This allows you to observe the flicker-free boot behavior and display handover without first modifying your own system.
From there, GraphLab Boot can be integrated into your target SoM or SoC platform.
GraphLab provides direct engineering support and integration services to help bring the architecture to your hardware.
This approach provides a fast, low-risk path to validate the technology before moving toward production deployment.