Michal Princ

> @MichalPrincNXP Do you think we can replace VRING_SIZE definition? > > ```c > #define VRING_SIZE1 (RL_BUFFER_COUNT * sizeof(struct vring_desc)) > #define VRING_SIZE2 (VRING_SIZE1 + sizeof(struct vring_avail) + (RL_BUFFER_COUNT *...

> My problem is that it seems to me that I'm only able to use about half of the shared memory given the constraints on these parameters. > > Assume...

Hello @infn-ke , I meant if you would be able to allocate 6kB, you would fit into this shared memory size with 4 buffers (RL_BUFFER_COUNT 2) of 496 bytes size,...

Hi @infn-ke > But the requirement for RL_BUFFER_COUNT and RL_BUFFER_PAYLOAD_SIZE to be a power of 2, is that an rpmsg protocol requirement or and implementation side effect for rpmsg-lite? This...

Hi @infn-ke , it seems the VRING_SIZE does not need to be a power of 2, you could take 230 as calculated by vring_size() function.

yes, agree and will do that

@Hadatko , you are right, it would be better to use the xSemaphoreCreateMutex API to be accurate. I guess the xSemaphoreCreateCounting usage has been chosen because of the smaller footprint...

Sorry, I do not see the weakpoint, I guess using event group would consume a little more RAM. Anyway, your suggestions are welcome.

Hello Diek, sorry for late response ... this is more domain of @MarekNovakNXP , Marek could you please help on this? Thanks. Regards Michal

Hello @Teletask , I was hoping @MarekNovakNXP will response, but I am not able to reach him. Anyway, your approach seems to be correct, the M4 code with creation of...