Hi all,
Since Bill retired from Linaro, let's try combining the openamp-rp and OpenAMP System Reference calls into one OpenAMP Technical call.
More details in the email thread "Combining OpenAMP RP & System Reference calls into 1 call, every 2 weeks", which I sent earlier today.
Best regards,
Nathalie CKC
Open Source Program Manager
[https://st2.zoom.us/static/26.9.68541/image/new/ZoomLogo_110_25.png]<https://zoom.com/>
Hi there,
Nathalie Chan King Choy is inviting you to a scheduled Zoom meeting.
Join Zoom Meeting<https://amd.zoom.us/j/96818892084?pwd=dwhbvqo97qa2F3T5vSaL0Jqny7aUfB.1&from…>
Join and take notes<https://amd.zoom.us/j/96818892084?pwd=dwhbvqo97qa2F3T5vSaL0Jqny7aUfB.1&from…>
Meeting agenda<https://docs.zoom.us/agenda/doc/e84cb797-3f54-41ed-905a-261dacf48b52?from=a…>
One tap mobile:
India: +912271279525,,96818892084#,,,,*8777694438#<tel:+912271279525,,96818892084#,,,,*8777694438#> or +914064802722,,96818892084#,,,,*8777694438#<tel:+914064802722,,96818892084#,,,,*8777694438#>
Meeting URL:
https://amd.zoom.us/j/96818892084?pwd=dwhbvqo97qa2F3T5vSaL0Jqny7aUfB.1&from…
Meeting ID:
968 1889 2084
Passcode:
7gmYSKuQ5*
Join by Telephone
For higher quality, dial a number based on your current location.
Dial:
+91 22 71 279 525 India
+91 406 480 2722 India
+91 446 480 2722 India
+91 806 480 2722 India
+91 80 71 279 440 India
+91 116 480 2722 India
+91 226 480 2722 India
000 800 001 4002 India Toll-free
000 800 050 5050 India Toll-free
000 800 050 2340 India Toll-free
000 800 050 2400 India Toll-free
+33 1 7037 9729 France
+33 1 7095 0103 France
+33 1 7095 0350 France
+33 1 8699 5831 France
+33 1 7037 2246 France
0 800 940 415 France Toll-free
0 800 944 049 France Toll-free
0 805 543 065 France Toll-free
+1 613 209 3054 Canada
+1 647 374 4685 Canada
833 955 1088 Canada Toll-free
833 958 1164 Canada Toll-free
855 703 8985 Canada Toll-free
+1 669 900 6833 US (San Jose)
+1 720 928 9299 US (Denver)
+1 929 205 6099 US (New York)
833 928 4608 US Toll-free
833 928 4609 US Toll-free
833 928 4610 US Toll-free
877 853 5257 US Toll-free
888 475 4499 US Toll-free
833 548 0276 US Toll-free
833 548 0282 US Toll-free
+40 31 630 1088 Romania
+40 37 170 0418 Romania
0 800 672 631 Romania Toll-free
0 800 890 203 Romania Toll-free
+44 131 460 1196 United Kingdom
+44 203 481 5237 United Kingdom
0 800 031 5717 United Kingdom Toll-free
0 800 260 5801 United Kingdom Toll-free
0 800 358 2817 United Kingdom Toll-free
0 800 456 1369 United Kingdom Toll-free
Meeting ID:
968 1889 2084
Passcode:
8777694438
International numbers<https://amd.zoom.us/u/aJMePuzDN>
Join from an H.323/SIP room system
H.323:
144.195.19.161 (US West)
206.247.11.121 (US East)
221.122.88.195 (Mainland China)
137.66.136.22 (India Mumbai)
137.66.140.8 (India Hyderabad)
159.124.15.191 (Amsterdam Netherlands)
159.124.47.249 (Germany)
159.124.104.213 (Australia Sydney)
159.124.74.212 (Australia Melbourne)
170.114.134.121 (Hong Kong SAR)
170.114.180.219 (Singapore)
64.211.144.160 (Brazil)
159.124.168.213 (Canada Toronto)
159.124.196.25 (Canada Vancouver)
170.114.194.163 (Japan Tokyo)
147.124.100.25 (Japan Osaka)
Meeting ID:
968 1889 2084
Passcode:
8777694438
SIP:
96818892084(a)zoomcrc.com<mailto:96818892084@zoomcrc.com>
Passcode:
8777694438
AMD General
Hi all,
In discussions around how to transition the openamp-rp call facilitation after Bill's retirement from Linaro, the suggestion came about to combine the openamp-system-reference + openamp-rp/kernel calls into a single OpenAMP technical call series that happens every 2 weeks.
Openamp-system-reference originally started focused on reference/demos, but the agenda gradually expanded to include docs, libmetal, open-amp library, meta-openamp, Zephyr, development policies, an towards end of 2026 we'll probably have some System DT topics. So, combining the 2 calls will basically be a slot to discuss all the OpenAMP technical topics.
Since the system-reference attendees are mostly a subset of the RP attendees, using the RP slot at 15:00 UTC will probably cover when most of you were able to join. Screenshot below of how that translates to various time zones:
[cid:image001.png@01DD5BE5.C77B7C20]
I propose to begin next week, on October 22nd .
It will be a one-off invitation (1) to give folks the opportunity to give feedback on this proposal, and (2) because I try to avoid the chaos of creating meeting series that straddle a Daylight Savings/Standard Time change boundary. Then if it works for folks, I'll send a series for Standard Time.
Let me know if you have any feedback!
Thanks & regards,
Nathalie CKC
Open Source Program Manager
Hi all,
Notes from the call are posted at: https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
This is the link to the abstract & slides<https://osselceu2026.sched.com/event/2RaWd/asymmetric-multi-processing-amp-…> of Wolfram's presentation relating to AMP where he mentions OpenAMP & System DT. I am guessing the Linux Foundation YouTube channel will have the recording up in a couple weeks. I gave him an OpenAMP sticker after the talk :)
Summary of action items:
* (DONE) Arnaud: Create & share non-regression test spreadsheet for team to update for testing 2026.10 release
* Arnaud: Review openamp-system-reference PR #106<https://github.com/OpenAMP/openamp-system-reference/pull/106> (needs open-amp PR #684 merged first)
* Arnaud: Review openamp-system-reference PR #119<https://github.com/OpenAMP/openamp-system-reference/pull/119> - confirm Ben's changes address feedback
* Ben: Rebase open-amp PR #704<https://github.com/OpenAMP/open-amp/pull/704> to resolve conflict
* (IN PROGRESS) Ben: Update open-amp PR #700<https://github.com/OpenAMP/open-amp/pull/700> - add missing check + mark virtio_mmio_register_device as deprecated
* Ben: Add host-side device tree README to openamp-system-reference PR #119<https://github.com/OpenAMP/openamp-system-reference/pull/119> (per Tanmay's request)
* Tanmay: Add GitHub issue to openamp-docs for RPMsg buf config space documentation
* Tanmay: Add new task tracker item for OpenAMP library side of task 4 (virtio reset / reset mechanism)
* Tanmay: When returning from leave, email Bill re: virtio-msg status and whether to build on his work
* Tanmay: Go to hub.corecollective.dev and sign up for Virtualization working group with AMD email address to get on mailing list
* (DONE) Nathalie: Reply to Stefano/Bruce email thread re System DT; share pictures from OSS EU presentation
* (DONE) Nathalie: Check with Iulia & Beleswar at OSS EU re NXP non-regression testing for 2026.10 release --> Iulia said yes
* (DONE) Nathalie: Close openamp-docs PR #91<https://github.com/OpenAMP/openamp-docs/pull/91> and openamp-docs PR #90<https://github.com/OpenAMP/openamp-docs/pull/90> without merging
* (DONE) Tanmay: Approve libmetal PR #369<https://github.com/OpenAMP/libmetal/pull/369> (merged 2026-10-08)
Please let us know if you spot any errors or important omissions.
Notes were AI assisted.
Thanks & regards,
Nathalie
Public
Hi OpenAMP TSC,
Based on the March 2026 OpenAMP Board meeting, the OpenAMP System Reference working group has been discussing what needs to be done in preparation for the EU Cyber Resilience Act.
Conclusions:
* Given OpenAMP's very low membership fee and low level of contributor bandwidth, it is not currently feasible to set up a Security team & Security support will be on a reasonable-effort basis
* We can at least set up security reporting using built-in GitHub functionality<https://www.google.com/url?q=https://docs.github.com/en/code-security/how-t…> to track what has been reported & evaluated
* The OpenAMP System Reference working group has drafted a security policy below
* For the repos in the OpenAMP org that are staging forks of some upstream project, we should have a different security.md pointing people to submit their advisories to the upstream & that the staging repos are not security-supported.
* Based on Greg KH's Embedded Recipes talk<https://youtu.be/u44eMQpGlxA?si=ZFgGuCZVBIYnbHi0&t=750> 12:30-13:32, it sounds like this is sufficient for compliance: "Part of the CRA is going to require manufacturers to report vulnerabilities that they find. They have to report it to you, the creator of the software, and they have to report it to the EU through ENISA. They just need a way to contact you. And you don't have to fix the problem. They just have to contact you. They can provide a fix if they want, but you don't have to take the fix."
* If any OpenAMP member disagrees with this level of support, they should contribute staffing and/or propose how to fund a higher level of support.
* E.g. maybe it is less costly to the member(s) to implement these fixes upstream
Votes can be sent directly to me with Arnaud in CC. The rules for the vote are the same applied for Board voting, described in the charter<https://www.openampproject.org/docs/OpenAMPProject_Charter_Approved2024AugE…>. TSC voting members will get a reminder in about a week & voting will close on 17th Sept, 2026.
===
Purpose
This policy outlines how security issues in repos of the OpenAMP GitHub organization should be reported, how they are handled, and what users can expect from the OpenAMP Project.
Scope
OpenAMP does not ship products or deployable binaries; it supplies source code and reference implementations only.
Because the project team has very limited visibility into how the code is incorporated downstream and very limited maintainer time, consumers of the OpenAMP code are responsible for implementing any security fixes, mitigations, or processes that meet their own regulatory or product-specific requirements. Organisations placing devices or software on the EU market under the CRA remain accountable for performing their own risk and conformity assessments, generating and maintaining any required SBOMs, and any other EU CRA compliance.
Fixes contributed for reported issues will be evaluated and merged on a reasonable-effort basis. The OpenAMP project welcomes patches that improve CRA alignment, provided they do not impose an unsustainable maintenance burden on the community.
Security support is limited to the next release: fixes will be added to the main branch of the relevant repositories. Earlier versions remain available as-is, but do NOT receive security updates.
Response targets
Acknowledgement, assessment & publishing of advisories will occur on a reasonable-effort basis. If you need a faster turnaround, please consider contributing a fix or maintaining a downstream fork.
Reporting a Vulnerability
If you discover a security vulnerability in OpenAMP, please report it privately and responsibly: open a confidential security issue on at https://github.com/OpenAMP/<repository-with-the-issue>/security/advisories
Please include:
* If you/your company is reporting this issue under embargo so that you have time to provide a fix.
* If reported under embargo, OpenAMP will respect the reporter's request for a limited time (up to 90 days), after which public disclosure may occur.
* A clear description of the vulnerability.
* Steps to reproduce the issue.
* Any relevant details (affected components and versions, possible impact, etc.)
* If an AI tool was used to discover the issue (Assisted-by: [Agent Name]:[Model Version] [Tool1] [Tool2])
GitHub How-to documentation on privately reporting a security vulnerability can be found here<https://docs.github.com/en/code-security/how-tos/report-and-fix-vulnerabili…>.
To keep this process safe and productive for everyone, all reports and related activities must comply with the OpenAMP Project code of conduct<https://www.openampproject.org/conduct>.
No Pre-disclosure List
* OpenAMP does not maintain a pre-disclosure list or offer embargoed advisories to downstream users.
Publication of Security Advisories
Advisories will be published at https://github.com/OpenAMP/<repository>/security/advisories.
Reported issues that are assessed to be purely theoretical and not applicable in any real hardware system will be documented as "[Fix not planned]".
Limitations of Liability & No Legal Advice
This document is provided "AS IS" and does not constitute legal advice. The OpenAMP project members make no warranties regarding compliance with any law or regulation. Use at your own risk.
===
Thanks & regards,
Nathalie