openAMP abstractions and possibilities besides rpmsg

[burgerTo]

Hi,
we are currently evaluating the IPC possibilities for a TI Sitara (AM64x). openAMP looks like an interesting option. However, I still have some questions about the current state of openAMP. I would also like to verify that I have understood the abstractions of openAMP correctly.

1. The basic communication structure in shared memory is formed by vrings/virtqueues (comparable to the MAC Layer).
2. On this basis, for example, rpmsg is built (comparable to the Transport Layer).

If I understand correctly, currently only rpmsg is implemented as a transport in openAMP. According to the “Application Services” page (https://github.com/OpenAMP/open-amp/wiki/Application-Services), however, further services/transports are planned. Is it correct that this is mainly made possible by libVirt? Here, drivers (from the virtualization environment) are already available that build on virtqueues.
Is there an overview of which drivers will be implemented in openAMP in the future?

Would it be possible, for example, for a virtual Ethernet interface to be created by Linux and made available to the remote processor via openAMP?

What would be the right approach for large, cyclical data packets?
rpMsg as a transport could be limited by the limited packet size.
Are there already alternative “transport drivers” for this application?

Hardware-specific questions: Are there efforts to port openAMP to a TI Sitara AM64x?

Thank you very much.
Toni