RFC: Secure EC Zephyr Interoperability#38
Open
jerrysxie wants to merge 4 commits into
Open
Conversation
kurtjd
approved these changes
Jun 10, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Introduces a new RFC proposing a staged approach to run ODP Rust-based Secure EC services in Zephyr-based environments, focusing on interoperability via FFI/wrapper layers while collaborating upstream to improve Zephyr’s Rust integration.
Changes:
- Adds an Embedded Controller RFC describing motivation, goals, requirements, and phased plan for ODP ↔ Zephyr interoperability.
- Documents two integration paths (Rust services on Zephyr; Rust drivers in Zephyr) and key open questions/alternatives.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Clarify that platform list is CI-tested, not an architectural limit; Kconfig gates on architecture (Cortex-M, RISC-V, POSIX 64-bit) - Acknowledge that some Zephyr subsystems may be hard to wrap safely; soften requirement 2 and add unresolved questions - Distinguish thin FFI (already in zephyr-lang-rust) from safe ergonomic wrappers (the actual gap), referencing zephyr-lang-rust#73 - Add Phase 1.5 for safe driver libraries between basic FFI bridging (Phase 1) and Rust-native kernel drivers (Phase 2) - Update Path A to emphasize safe library creation, not just thin FFI - Note upstream acceptance bar for kernel-level changes in Alt 2 and Phase 2, citing Linux Rust-in-kernel precedent Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jerrysxie
changed the title
Member
|
FYI Updated RFC in the |
jerrysxie
requested review from
dhillonk,
dymk,
felipebalbi,
gjpmsft,
kat-perez,
maxperga-msft,
rogurr,
tullom and
williampMSFT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new RFC document outlining a strategy for enabling interoperability between ODP Secure EC (Rust-based) services and Zephyr (C-based) environments. The RFC proposes a phased approach to allow incremental adoption of Rust components in Zephyr-based embedded controller firmware, targeting OEMs who rely on Zephyr but want to benefit from ODP's memory safety and modularity. The document also details technical background, goals, requirements, phased integration plans, and unresolved questions for community discussion.
Key additions in this RFC:
Strategy and Motivation
Technical Details and Integration Phases
zephyr-lang-rust), the use of FFI for bridging Rust and C, and the plan to build safe, ergonomic Rust wrappers around Zephyr drivers.