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/1GqSHksfcLO2WaTDUUWz8RuPM7al2Gid7SWFkbrGk... * 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, Stefanomailto:stefano.stabellini@amd.com: Summary from 3/25 OpenAMP System Reference call with Tomas is at the end of this email * 2026 task trackerhttps://docs.google.com/spreadsheets/d/1NyVPqvcSmPVu4SjRsFHboyLPdByWo38MIADD6H6eQRs/edit?usp=sharing / 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.