Repository navigation
OpenAMP Technical Call Notes 2026
Nathalie Chan King Choy edited this page Oct 22, 2026
·
1 revision
- Andrew, Arnaud, Beleswar, Bill, Ed, Iulia, Nathalie
- Scheduling technical call — Thursdays every 2 weeks in this slot?
- Any kernel topics?
- Any high priority non-regression test failures to discuss for 2026.10 release?
- PRs for release: libmetal, open-amp, openamp-system-reference (releases later), openamp-docs (releases later)
- Decision discussion for docs (title case vs sentence case)
- EU CRA: OpenAMP Security Policy
- Any Zephyr topics?
- OpenAMP docs improvement project topics?
- 2026 task tracker / individual updates
- Other Recent PRs
- Unify System Reference & RP into 1 Technical call Thursdays every 2 weeks in this slot, so people from the RP call can join too — will revisit the time if the distribution of attendees' time zones changes
- Call stays anchored to North America (Pacific) time rather than British Columbia
- EU CRA / OpenAMP Security Policy: applies only to open-amp and libmetal
- Implementing the security policy on open-amp and libmetal will wait until after the 2026.10 release
- Assisted-by tag: Linux kernel moving away from it. Zephyr still has it and we will continue to align with them. Can revisit if Zephyr changes (they are discussing).
- openamp-system-reference PR #119: Tanmay's existing review counts as the second approval
- openamp-system-reference PR #106: Approved by Arnaud and Iulia — ready to merge; feature isn't in Linux yet (expected in Linux 7.4); will be demonstrated via the Zephyr OpenAMP resource table sample
- openamp-docs issue #83 (title case vs sentence case for doc titles): Linux is inconsistent. Review Zephyr rule, vote next call, and be consistent going forward
- libmetal PR #343 (QNX): We don't have this platform for CI/non-regression testing; if merged, it will be noted that stability on this platform can't be guaranteed
- Arnaud: Create a signed tag for the 2026.10 release (will check whether a branch is also needed)
- Arnaud: Share the prepared release notes with Ed, Bill, Nathalie for review before the release
- Arnaud: Merge openamp-docs PR #86 tomorrow
- Ben: Test openamp-system-reference PR #106 (RPMsg Virtio config space) on an AMD platform and report the result
- Bill: Review openamp-system-reference PR #120
- Ed: Review libmetal PR #373 (checkpatch: support Assisted-by tag)
- Ed: Review open-amp PR #708
- Ed (and others): Try to review more PRs while Tanmay is on leave
- Iulia: Look into how Zephyr formats documentation titles (title case vs. sentence case) and comment on openamp-docs issue #83
- Iulia: Look into the RPMsg Lite question from Discord (new NXP IPC backend added in Zephyr, not based on OpenAMP/libmetal) and answer it
- Nathalie: Research whether there's a standard way to indicate that a repo is not security supported
- Nathalie: Ask elahav on libmetal PR #343 whether their review concerns are addressed by the submitter's latest changes
- Scheduling
- Technical call will move to Thursdays every 2 weeks in this slot (System Reference call used to be every 2 weeks on Wednesday, with RP call in the alternating weeks); Thursday chosen since some RP call attendees may want to join
- The old Virtio message call has moved to the Core Collective meetings; Bill still getting synced up with that
- Call time anchored to North America (Pacific), since BC's time zone won't change starting this year; Europe changes time zones this weekend, North America changes on Nov 1
- Call time is late in India but 1hr earlier might be too early Pacific Time — will revisit if the time zone distribution of attendees changes
- Non-regression testing / 2026.10 release
- Iulia hasn't had a chance yet to test the 2026.10 release; plans to do it after next week
- Arnaud: That works b/c he plans to release the week of Nov 2
- Arnaud shared a non-regression test failures spreadsheet on Discord
- Arnaud also shared a link on Discord to a GitHub/Zephyr patch for testing the new RPMsg Virtio config space feature, which allows customizing RPMsg buffer sizes; it's platform-agnostic but needs an overlay config update
- Release PRs
- https://github.com/OpenAMP/libmetal/pull/375
- release: libmetal 2026.10.0 (Arnaud)
- This PR is where folks doing non-regression testing can approve to indicate testing was successful on their platform for this release milestone, or reach out to Arnaud directly
- https://github.com/OpenAMP/libmetal/pull/373
- scripts: checkpatch: support Assisted-by tag (Arnaud)
- Fixes checkpatch complaining about the Assisted-by tag in commit messages
- Ed will review; only one review needed since it's tooling/CI, not code
- Iulia: Linux discussed removing the Assisted-by tag entirely at the maintainers summit in Prague (patch from Sasha Levin); Zephyr still has it. Linux is also discussing adding an "assisted by" note to the cover letter only instead
- Zephyr is discussing adding a PR label for AI-assisted changes instead, in the process working group; would be optional/author-applied
- Arnaud: propose keeping the tag for now since most open source projects still have it; OpenAMP can align in future with whatever Zephyr ends up doing
- https://github.com/OpenAMP/open-amp/pull/711
- release: open-amp 2026.10.0 (Arnaud)
- Same purpose as libmetal #375 — approve to confirm platform testing passed, or ping Arnaud directly
- https://github.com/OpenAMP/open-amp/pull/710
- scripts: checkpatch: support Assisted-by tag (Arnaud)
- Same fix as libmetal #373, ported to open-amp
- https://github.com/OpenAMP/openamp-system-reference/pull/120
- linux: add rpmsg udev rules and scripts (Tanmay)
- Bill will take a look, since Ed doesn't have a board to test it
- https://github.com/OpenAMP/openamp-system-reference/pull/119
- examples: libmetal: amd_linux_userspace: Uio updates (Ben)
- Had an earlier approval from Tanmay, before Arnaud's feedback; Arnaud still needs a good look at Ben's latest changes, but confirmed Tanmay's existing review counts as the other approval needed for merge
- https://github.com/OpenAMP/openamp-system-reference/pull/106
- rpmsg buf size config via vdev config space (Tanmay)
- This is the AMD-platform implementation/example of the RPMsg Virtio config space feature discussed earlier; the AMD SDK is needed to build it, which Bill doesn't have access to at the open source engagement level
- Ben is likely the best person from the AMD team to test this
- https://github.com/OpenAMP/openamp-docs/pull/86
- Improve the porting guide page (Sipke)
- Already approved by Iulia, Arnaud, and Andrew; Arnaud will merge tomorrow
- Bill shared a live preview link in chat: https://openamp--86.org.readthedocs.build/en/86/
- https://github.com/OpenAMP/libmetal/pull/375
- openamp-docs issue #83 — title case vs. sentence case for doc titles
- Arnaud: today's docs titles are inconsistent — a mix of proper/title case and sentence case; wondering if there's a preference
- Ed: has seen plenty of these debates as a former technical writer; no strong evidence either way — the important thing is picking one and being consistent
- Bill: suggests checking what the Linux kernel does, to be consistent with the bigger community
- AI says there's no enforced standard for the Linux kernel — sometimes sentence case, sometimes title case
- Arnaud: leans toward sentence case as the simpler rule (just capitalize the first word)
- Group agreed: Good to align with what one of the bigger projects (Linux or Zephyr) does; otherwise vote at a future call
- Iulia will check Zephyr practice and comment on the issue
- Bill shared examples later in chat: AI says Zephyr uses title case in the majority of cases, with sentence case for some secondary headings (e.g. "Analog-to-Digital Converter (ADC) with devicetree", "VL53L0X Time Of Flight sensor" — both arguably self-inconsistent — and "GPIO as wake-up pin")
- Iulia: Zephyr docs look like title case to her when reading them, but asking Gemini directly said Zephyr uses sentence case — still not clear, needs to dig more
- Bill: secondary question (if title case) is whether to capitalize words like "of" and "as"
- RPMsg Lite question (Discord)
- Nathalie flagged a question from Discord about Analog Devices and RPMsg Lite; no one from Analog Devices on today's call
- Iulia: RPMsg Lite is a new IPC backend added in Zephyr from NXP; doesn't use OpenAMP or libmetal, but is based on RPMsg; nothing should need to change on the Linux side since it's RPMsg-based
- Iulia will look into it further and answer the Discord question
- EU CRA: OpenAMP Security Policy
- Not all of OpenAMP Project repos warrant having a security policy
- Applies only to open-amp and libmetal
- For the other repos: need to research if there's a standard way to state that a repo is not security supported, in case any automated tooling tries to query
- Implementing the policy on open-amp/libmetal will wait until after the 2026.10 release, since team has limited bandwidth
- Any Zephyr topics?
- Zephyr is in its release cycle — RC3 tag today; 2026.10(ish) Zephyr release planned for next week; just bug fixing in the last few weeks
- 2026 task tracker / individual updates
- Andrew: items marked done
- Arnaud: last item done — PR sent
- Beleswar: IOCTL-related item — not feasible to add to OpenAMP without an application that uses it; marked "won't do"
- Bill: just back, no updates
- Iulia: item previously deferred — there's an open RFC in Zephyr related to this (remoteproc lifecycle management of the secondary core); Iulia will paste the link in chat for anyone with time to review
- zephyr issue #114707 — remoteproc side in Zephyr (secondary core lifecycle management)
- zephyr PR #105778 — resource table in device tree (not yet linked to remoteproc), rather than in C code as it is today
- Arnaud: aware of the remoteproc issue but hasn't had time to look yet; release is taking up his bandwidth
- Iulia: offered to help Arnaud if he needs it for anything
- Other Recent PRs
- https://github.com/OpenAMP/open-amp/pull/708
- Update folder structure in readme (Sipke)
- Nathalie added Ed as a reviewer, since he "recently edited" those files (according to GitHub)
- https://github.com/OpenAMP/open-amp/pull/707
- Coverity static analysis fixups (Ben)
- Arnaud already added reviewers
- https://github.com/OpenAMP/libmetal/pull/343
- Add QNX cross-compilation support (dchordia)
- Submitter pushed new changes; elahav (previous reviewer) raised architectural concerns - yet to confirm if their concerns are addressed
- Arnaud yet to set up the QNX environment to verify the build (a compiler was missing, but a free trial license may be available); CI/non-regression testing won't be possible for this platform even once merged
- Ed: adding a new platform is considerable work; might not land until after 2027.04
- Nathalie: suggests asking elahav directly whether their architectural concerns were addressed even before we know if it builds for QNX
- https://github.com/OpenAMP/open-amp/pull/708