search for: openamp

On Mon, Jun 08, 2020 at 05:19:06AM -0400, Michael S. Tsirkin wrote: > On Mon, Jun 08, 2020 at 11:11:00AM +0200, Guennadi Liakhovetski wrote: > > Update: I looked through VirtIO 1.0 and 1.1 specs, data format their, > > including byte order, is defined on a per-device type basis. RPMsg is > > indeed included in the spec as device type 7, but that's the only > >

On Mon, Jun 08, 2020 at 05:19:06AM -0400, Michael S. Tsirkin wrote: > On Mon, Jun 08, 2020 at 11:11:00AM +0200, Guennadi Liakhovetski wrote: > > Update: I looked through VirtIO 1.0 and 1.1 specs, data format their, > > including byte order, is defined on a per-device type basis. RPMsg is > > indeed included in the spec as device type 7, but that's the only > >

...for RPMsg instead of enforcing LE? > > > > That makes hardware implementations as well as any cross-endian > > hypervisors tricky. > > Yes, LE it is then. And we need to add some text to the spec. I found the protocol and the message format definition: https://github.com/OpenAMP/open-amp/wiki/RPMsg-Messaging-Protocol#transport-layer---rpmsg Don't know what the best way for referencing it in the VirtIO standard would be: just a link to the source or a quote. Thanks Guennadi

...es name announcements, it doesn't send them. Interesting, well, we know now that both directions are possible, but I still don't know whether all configurations are valid: only down, only up, none or both. Thanks Guennadi [1] https://nxpmicro.github.io/rpmsg-lite/ [2] https://github.com/OpenAMP/open-amp/wiki/RPMsg-Messaging-Protocol > > > I saw your V7, something I will look into. In the mean time I need to bring > > > your attention to this set [1] from Arnaud. Please have a look as it will > > > impact your work. > > > > > > https://patch...

Hi Arnaud, On Fri, Sep 18, 2020 at 09:47:45AM +0200, Arnaud POULIQUEN wrote: > Hi Guennadi, > > On 9/18/20 7:44 AM, Guennadi Liakhovetski wrote: > > Hi Arnaud, > > > > On Thu, Sep 17, 2020 at 05:21:02PM +0200, Arnaud POULIQUEN wrote: > >> Hi Guennadi, > >> > >>> -----Original Message----- > >>> From: Guennadi Liakhovetski

Hi Arnaud, On Fri, Sep 18, 2020 at 09:47:45AM +0200, Arnaud POULIQUEN wrote: > Hi Guennadi, > > On 9/18/20 7:44 AM, Guennadi Liakhovetski wrote: > > Hi Arnaud, > > > > On Thu, Sep 17, 2020 at 05:21:02PM +0200, Arnaud POULIQUEN wrote: > >> Hi Guennadi, > >> > >>> -----Original Message----- > >>> From: Guennadi Liakhovetski

Hi, Next update: v5: - don't hard-code message layout v4: - add endianness conversions to comply with the VirtIO standard v3: - address several checkpatch warnings - address comments from Mathieu Poirier v2: - update patch #5 with a correct vhost_dev_init() prototype - drop patch #6 - it depends on a different patch, that is currently an RFC - address comments from Pierre-Louis Bossart:

Hi, Next update: v5: - don't hard-code message layout v4: - add endianness conversions to comply with the VirtIO standard v3: - address several checkpatch warnings - address comments from Mathieu Poirier v2: - update patch #5 with a correct vhost_dev_init() prototype - drop patch #6 - it depends on a different patch, that is currently an RFC - address comments from Pierre-Louis Bossart: