[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 explore udev rules and group permissions further and email updates to list.
* Prepopulate udev rules to automate device creation and permission settings.
* Create a dedicated RPMsg group during package installation, with permissions ready for admin or distro to add users.
* Beleswar and Devarsh
* Adopt Virtio Message: For tasks involving data buffers and media/GPU interactions, prioritize Virtio Message.
* RPMsg for Specific Use Cases: Utilize RPMsg for low-footprint IPC and register interface abstraction.
* Collaborate on Standardization: TI to consider proposing extensions for standardized bus messages to address lifecycle event communication.
* Explore Dynamic Discovery: Investigate Rob Herring's dynamic device tree approach for future device discovery enhancements.
Please let us know if you spot any errors or important omissions.
Thanks & regards,
Nathalie
[AMD Official Use Only - AMD Internal Distribution Only]
Reminder due to time zone changes. Starting in 25 minutes.
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Chan King Choy, Nathalie
Sent: Thursday, October 30, 2025 1:54:25 PM
To: Chan King Choy, Nathalie <nathalie.chan-king-choy(a)amd.com>; OpenAMP System Reference <openamp-system-reference(a)lists.openampproject.org>
Cc: Ashfield, Bruce <bruce.ashfield(a)amd.com>; Nathalie Chan King Choy <nathalie-ckc(a)kestrel-omnitech.com>; Iuliana Prodan <iuliana.prodan(a)nxp.com>; Shah, Tanmay <tanmay.shah(a)amd.com>; Ed Mooring <ed.mooring(a)gmail.com>; Bill Mills <bill.mills(a)linaro.org>; Milea, Danut Gabriel (Danut) <Danut.Milea(a)windriver.com>
Subject: OpenAMP System Reference - WARNING EU/NA time zone offset weird weeks!
When: Wednesday, March 11, 2026 9:00 AM-10:00 AM.
Where: https://amd.zoom.us/j/97464922416?pwd=kQYKa6KZ0w3HkECTq5egycdBaZWXB7.1
Nathalie Chan King Choy is inviting you to a scheduled Zoom meeting.
Join Zoom Meeting
https://amd.zoom.us/j/97464922416?pwd=kQYKa6KZ0w3HkECTq5egycdBaZWXB7.1
Meeting ID: 974 6492 2416
Passcode: qh!x@*V2##
---
Join by SIP
• 97464922416(a)zoomcrc.com<mailto:97464922416@zoomcrc.com>
Passcode: 3217100567
Join instructions
https://amd.zoom.us/meetings/97464922416/invitations?signature=2zd2Jemi_cTU…
[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
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…
[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:
* Arnaud will check openamp-system-reference PR83 to see if OK to proceed with Ed's earlier approval or if want Ed to review the changes that came in after
Please let us know if you spot any errors or important omissions.
Thanks & regards,
Nathalie
[Public]
Hi all,
Sorry, forgot to send these out after last call!
https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
* Dan will rephrase some of the tasks to reflect 2026 plan
* (DONE) Nathalie to give Sipke heads up about entity change
* (DONE) Nathalie to dig up the old budget tally & send to Bill M
Please let us know if you spot any errors or important omissions.
Thanks & regards,
Nathalie