Hi Edward,
Thanks for your answer!
Wait if I understand you correctly 512x512 is 256kB but the vring size in one direction is only 0x8000 as seen here:
So the RPMSG_RING_SIZE is not refering to the payload size but rather overhead information?
But let’s go back to the concrete example: If I want to go from 512x512 to 1028x256, should I change the hardcoded 0x8000 ring size? I expected it to work without change because its still 256kB as before.
EDIT: I just changed one print output for debugging (imx_rpmsg.c line 670 “imx rpmsg driver is registered”) but nothing changed, looks like the driver changes are not applied. I might be making some torizoncore builder mistake, I’m looking into it