Openamp-system-reference February 2026

openamp-system-reference@lists.openampproject.org

4 participants
3 discussions

2026-02-11 OpenAMP System Reference Notes and Action items

by Chan King Choy, 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 look into the Linux kernel patch for -1 -> Linux allocate next endpoint & see if makes sense to try to upstream it * Nathalie: Put RPMsg IOCTL access topic on agenda for next meeting, since we have folks OOO, unless resolved on mailing list * Tanmay to ping Arnaud when ready for him to review system reference PR94 * Arnaud can create ticket for Sipke to work on making shell block change in other OpenAMP repos * Ed & Tanmay to review the outstanding docs PRs Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie

1 week, 5 days

RPMsg IOCTL access without root permissions from Linux userspace

by Shah, Tanmay

Hi all, I am working on remoteproc auto-boot feature. While working on this, I realized it should be possible to achieve RPMsg communication without root access given to the user. Existing demos doesn't support it, but I want to open discussion on how that can be achieved. One way discussed was, to use IOCTLS to create RPMSg devices, and I had open issue here: https://github.com/OpenAMP/openamp-system-reference/issues/50 I tried to modify echo_test[1] demo and use IOCTLS instead of accessing devices from sysfs directly, but that still need root access. My goal is to design following workflow for the RPMsg communication with the remote processor: 1. Linux device-tree has auto-boot property enabled. 2. During boot, driver parses auto-boot related properties, loads fw and boots rproc automatically (without user's involvement) 3. After boot, rproc firmware does name service announcement of RPMsg channels. 4. Linux creates RPMsg devices and ept based on above announcement. 5. Userspace apps uses RPMsg ioctls to create ept and rpmsg devices. 6. Userspace apps uses created devices for RPMsg communication with the remote processor. As per my testing, as of now step-5 and step-6 needs root access. Ideally userspace apps should be able to create/read/write/close rpmsg devices without root access (for security purposes). Is there any other way this problem is solved? I appreciate your input. Thank You, Tanmay References: [1] https://github.com/OpenAMP/openamp-system-reference/blob/main/examples/linu…

2 weeks

Calling for agenda: 2026-02-11 OpenAMP System Reference

by Chan King Choy, Nathalie

[Public] Hi all, Reminder to update your tasks in the 2026 task tracker<https://docs.google.com/spreadsheets/d/1NyVPqvcSmPVu4SjRsFHboyLPdByWo38MIAD…> if anything needs to be added/modified. Here are the topics I collected so far for this week's System Reference meeting. Please let us know if you have additional topics. * Recent PRs * https://github.com/OpenAMP/openamp-system-reference/pulls * https://github.com/OpenAMP/openamp-system-reference/pull/94 * Tanmay gave 2 requirements to have in place before merging the PR to upstream repo * Open question from Ben to Tanmay if something existing might meet requirement * https://github.com/OpenAMP/openamp-demo/pulls * No open PRs * https://github.com/OpenAMP/openamp-docs/pulls * https://github.com/OpenAMP/openamp-docs/pull/80 * Arnaud approved, need 1 more * Discuss: Apply same to other OpenAMP repos? * https://github.com/OpenAMP/openamp-docs/pull/81 * Arnaud approved, need 1 more * Branch has conflicts that must be resolved * PR82 is still in draft state * https://github.com/OpenAMP/open-amp/pulls * Only stale PRs remain * https://github.com/OpenAMP/libmetal/pulls * Only stale PRs remain * Any Zephyr topics? * OpenAMP docs improvement project topics? * 2026 task tracker<https://docs.google.com/spreadsheets/d/1NyVPqvcSmPVu4SjRsFHboyLPdByWo38MIAD…> / individual updates Thanks & regards, Nathalie

2 weeks

2026

2025

2024

2023

2022

2021

Openamp-system-reference February 2026