Public
Hi all,
Notes from the call are posted at:
https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
@divin.raj@arm.com<mailto:divin.raj@arm.com>: Please see notes at location above relating to https://github.com/OpenAMP/open-amp/pull/684
Summary of action items:
* Nathalie: Revised security policy document for review at next meeting
* Nathalie: Bring security maintenance funding question to fall board meeting (alongside docs contractor discussion)
* Nathalie: Research GitHub's security reporting mechanism (private advisory / submission)
* Nathalie: Research reviewer assignment by group in GitHub
* Nathalie: Draft AI-generated code policy text for contribution guide
* Nathalie: Copy Divin Raj on system reference call notes re open-amp PR #684
* Tanmay: Ask Ben to associate CVE-2026-37540 with open-amp PR #687
* Arnaud: Create GitHub issue in OpenAMP referencing CVE-2026-37540, noting no impact on production hardware
* Iulia: Review open-amp PR #684 and openamp-system-reference PR #106
Please let us know if you spot any errors or important omissions.
Notes were AI assisted.
Thanks & regards,
Nathalie
Public
Hi all,
Please let us know your agenda topics for this Wednesday. Here is what I have collected so far:
* EU CRA: OpenAMP Security Policy document (Tab: v0.2) - continued discussion
* https://docs.google.com/document/d/1GqSHksfcLO2WaTDUUWz8RuPM7al2Gid7SWFkbrG…
* Assumption: OpenAMP Project will NOT be acting in role of Steward given current resourcing & funding
* Recent PRs
* https://github.com/OpenAMP/open-amp/pulls
* #687 - ELF loader should validate before load [bentheredonethat]
* Needs review (edmooring, arnopo, tnmysh)
* #684 - Enhance rpmsg buf config [tnmysh]
* Changes requested by arnopo. Review also requested from edmooring, xiaoxiang781216 or wmamills
* #681 - cmake: Undeprecate granular cache maintenance [glneo]
* Approved by edmooring, tnmysh
* No updates since 2026-05-06 System Reference call decision to put the option in cmake config
* https://github.com/OpenAMP/libmetal/pulls
* #365 - libmetal: lib: linux: improve Linux UIO-backed device open and test coverage [bentheredonethat]
* Changes requested by arnopo. Review also requested from edmooring or tnmysh - useful to have live discussion?
* https://github.com/OpenAMP/openamp-system-reference/pulls
* #106 - rpmsg buf size config via vdev config space [tnmysh]
* Needs review (edmooring, arnopo, wmamills)
* #102 - examples: libmetal: amd_rpu: Fix dynamic config setup [bentheredonethat]
* Needs review (edmooring, tnmysh)
* On hold pending agreement on libmetal #365
* #100 - legacy_apps: xlnx: add api to poll apps on vdev status [tnmysh]
* Changes requested by arnopo. Review also requested from edmooring or wmamills
* glneo to review this PR and comment from TI perspective (Yet to add Andrew as a collaborator so we can assign reviews to him)
* Tanmay to submit new patch series with common approach (per openamp-rp call)
* #94 - examples: legacy_apps: xlnx: Remove xlnx_hw_to_bsp_irq() [bentheredonethat]
* Needs review (edmooring, arnopo, tnmysh)
* Ben waiting for System DT release - What is target date?
* #101 - examples: linux: add rpmsg udev rules and scripts [tnmysh]
* Still in draft state
* https://github.com/OpenAMP/openamp-demo/pulls
* No open PRs
* https://github.com/OpenAMP/openamp-docs/pulls
* #86 - Improve the porting guide page [sipke]
* Needs review (edmooring, wmamills, tnmysh)
* Sipke & Arnaud discussing in issue #85
* https://github.com/OpenAMP/meta-openamp/pulls
* #52 - AMD 26.1 updates [bentheredonethat]
* I don't have ability to add reviewers, does anyone else? (in last call Bill was identified as one reviewer)
* Any Zephyr topics?
* OpenAMP docs improvement project topics?
* 2026 task tracker / individual updates
* https://docs.google.com/spreadsheets/d/1NyVPqvcSmPVu4SjRsFHboyLPdByWo38MIAD…
* (smaller audience) Updating OpenAMP contributor & external collaborator lists
Trying Claude for the PR status - hopefully no hallucination! =)
Thanks & regards,
Nathalie
Arnaud,
Here is the status of the openamp-docs tag vs the recorded sub-module versions:
v2023.04.0:
branch: main
open-amp: ==
libmetal: ==
sys-ref: ==
lopper: v0.2023.x
_doxygen/awesome: N/A (not included yet)
v2023.10.0: no release
v2024.05.0:
branch: main
open-amp: ==
libmetal: ==
sys-ref: v2024.05.0-rc1 (6 commits behind v2024.05.0)
lopper: no tag (commit date 2024-05-29)
_doxygen/awesome: v2.3.3
v2024.10.0
branch: v2024.10
open-amp: ==
libmetal: ==
sys-ref: v2024.10.0 + 5
lopper: no tag (commit date 2024-05-29)
_doxygen/awesome: v2.3.4 + 1
v2025.04.0
branch: v2025.04
open-amp: ==
libmetal: ==
sys-ref: ==
lopper: no tag (commit date 2025-05-06)
_doxygen/awesome: v2.3.4 + 3
v2025.10.0
branch: main
open-amp: ==
libmetal: v2025.10.0 + 3
sys-ref: ==
lopper: no tag (commit date 2025-11-24)
_doxygen/awesome: v2.4.1
v2026.04 (branch, no tag yet)
branch: v2026.04
open-amp: ==
libmetal: ==
sys-ref: ==
lopper: v1.42 (commit date 2026-05-05)
_doxygen/awesome: v2.4.2 (commit date 2026-03-20)
where:
== means tag of sub-module matches tag of docs
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Public
Hi all,
Notes from the call are posted at: https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
Summary of action items:
* System reference PRs: @Ed Mooring<mailto:ed.mooring@gmail.com> will look at 107 & 98 this afternoon. @Arnaud POULIQUEN<mailto:arnaud.pouliquen@st.com> will review 98
* @Levinsky, Ben<mailto:ben.levinsky@amd.com>: Investigate feasibility of using symlinks for device lookup and document findings
* @Levinsky, Ben<mailto:ben.levinsky@amd.com>: Update the pull request with thoughts on incorporating the "UIO" bus type and fallback mechanism. Notify stakeholders (e.g., Tanmay, Bill, Arnaud) via Discord when ready
* AMD: Consider potential reintroduction of VFIO support in libmetal
* @Arnaud POULIQUEN<mailto:arnaud.pouliquen@st.com>: will clean up by closing out old release milestones
* Folks who don't have a profile photo should upload some image to replace the default Github pixelated icon
* All: Review v0.2 draft of OpenAMP security policy<https://docs.google.com/document/d/1GqSHksfcLO2WaTDUUWz8RuPM7al2Gid7SWFkbrG…>
* Nathalie: Put on agenda for next call
* Cmake build system in openamp & Libmetal library. How can we get rid of it since demos no longer in those libraries. Can we use cmake from system reference instead.
* (smaller audience) Updating OpenAMP contributor & external collaborator lists
* v0.2 draft of OpenAMP security policy<https://docs.google.com/document/d/1GqSHksfcLO2WaTDUUWz8RuPM7al2Gid7SWFkbrG…>
Please let us know if you spot any errors or important omissions.
Thanks & regards,
Nathalie
Public
Hi all,
Notes from the call are posted at: https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
Summary of action items:
* Tanmay to update release notes regarding Zephyr demos on ZynqMP which may face issues due to code not yet upstream
* All: look for examples of other projects using GitHub "Security and quality" tab so we can understand how others are using it (https://github.com/OpenAMP/open-amp/security)
* Nathalie to draft a revision of security policy proposal based on our discussion & post it to a new tab in Arnaud's google doc
* Arnaud to grant Nathalie editor access to security policy draft google doc
Please let us know if you spot any errors or important omissions.
Thanks & regards,
Nathalie
Public
Hi all,
Congratulations on the 2026.04 release for open-amp and libmetal!
Please let us know your agenda topics for this Wednesday. Here is what I collected so far:
* 2026.04 docs & demos release topics
* EU CRA: Discuss Arnaud+ChatGPT first draft of OpenAMP Security Policy document
* Assumption: OpenAMP Project member companies willing to support OpenAMP project with contributors acting in role of Steward since it would support the members’ role as Manufacturer under EU CRA
* Reminder: ahead of Wednesday’s call, review OpenAMP security policy draft & add your comments for discussion https://docs.google.com/document/d/1GqSHksfcLO2WaTDUUWz8RuPM7al2Gid7SWFkbrG…
* Recent PRs
* https://github.com/OpenAMP/openamp-system-reference/pulls
* https://github.com/OpenAMP/openamp-system-reference/pull/94
* Ben to address error hit by Tanmay
* https://github.com/OpenAMP/openamp-system-reference/pull/98
* Tanmay found bug in patch series and needs to update
* https://github.com/OpenAMP/openamp-system-reference/pull/100
* Tanmay posed a question to Arnaud
* Andrew to review & give input from TI’s perspective
* https://github.com/OpenAMP/openamp-system-reference/pull/101
* Tanmay moved back to DRAFT state, so is it still planned for 2026.04 release?
* https://github.com/OpenAMP/openamp-system-reference/pull/102
* Does Ben’s comment mean all the feedback items are addressed, or just a specific one?
* https://github.com/OpenAMP/openamp-system-reference/pull/104
* NXP issue should be resolved by Iulia’s PR 105
* Readthedocs build failing
* https://github.com/OpenAMP/openamp-system-reference/pull/105
* Needs reviewers
* https://github.com/OpenAMP/openamp-demo/pulls
* No open PRs
* https://github.com/OpenAMP/openamp-docs/pulls
* Only a draft PR remains
* https://github.com/OpenAMP/open-amp/pulls
* https://github.com/OpenAMP/open-amp/pull/681
* Active discussion between Tanmay & Andrew & looks like there was a question for Arnaud
* https://github.com/OpenAMP/open-amp/pull/682
* Ed & Tanmay approved, but 2 pending CI checks
* https://github.com/OpenAMP/libmetal/pulls
* https://github.com/OpenAMP/libmetal/pull/360
* A couple solution options discussed. Is it ready for review?
* https://github.com/OpenAMP/libmetal/pull/361
* Needs reviewers
* https://github.com/OpenAMP/libmetal/pull/362
* Tanmay approved. Arnaud said he’ll review after the release.
* Any Zephyr topics?
* OpenAMP docs improvement project topics?
* Increasing System DT uptake via openamp-system-reference
* @Stabellini, Stefano<mailto:stefano.stabellini@amd.com>: Summary from 3/25 OpenAMP System Reference call with Tomas is at the end of this email
* 2026 task tracker<https://docs.google.com/spreadsheets/d/1NyVPqvcSmPVu4SjRsFHboyLPdByWo38MIAD…> / individual updates
Thanks & regards,
Nathalie
System DT summary from 3/25
* AMD adoption and tooling:
* AMD has fully integrated System DT into its Yocto flow for an upcoming release, enabling configuration defined once in System DT to flow automatically to each OS or subsystem through Yocto or similar build infrastructure.
* OS and platform support:
* AMD can generate Devicetree for Zephyr alongside Linux as part of the OpenAMP multi‑services work.
* Upcoming releases will build Zephyr inside Yocto (instead of West) and generate #defines for bare‑metal.
* Initial focus is on platforms newer than ZynqMP, with ZynqMP needing follow‑up support.
* Rollout approach:
* System DT examples were not previously included due to lack of public System DT databases for boards (so would have needed AMD tools to generate) and an evolving specification.
* Now that these are public, documentation will start with Baremetal and FreeRTOS, with Zephyr and ZynqMP planned later.
* Baremetal and FreeRTOS are expected to be more vendor‑specific than Zephyr.
* Broader adoption and standardization:
* VxWorks support is of interest since it can consume Devicetree, and deriving a VxWorks DT from System DT could benefit many AMD customers who use VxWorks.
* Emphasis is placed on keeping DT and System DT standardized, even if different vendors use different generation tools.
* Lopper is being explored, including for hypervisor use cases such as Xen, and broader vendor feedback is encouraged to help System DT mature into an industry standard.