Hi Nick, Our implementation is referring to the zerocopy example, i.e. using the "dma-buf-phys" driver and using "dma-heap-carveout" to reserve shared memory. Will do more testing on the implementation. root@p550:/firmware/user# ./TestIpc Created endpt device rpmsg-char-9-744, fd = 4 port = 1025 A.01.00 dma-buf address: 0xa6000000 a6000000 0xffffb7bc4000 A53: Hello World from A53 !!! M4F: Hello World from M4F !!! root@p550:/firmware/user# cat /sys/kernel/debug/remoteproc/remoteproc0/trace0 [m4f0-0] 0.001463s : [IPC RPMSG ECHO] FW Revision: A.01.00 (May 10 2024 15:18:41): [m4f0-0] 0.010437s : [IPC RPMSG ECHO] Remote Core waiting for messages at end point 10 ... !!! [m4f0-0] 3.203430s : A53: Hello World from A53 !!! [m4f0-0] 3.203694s : root@p550:/firmware/user# ls /dev/dma_heap/carveout_apps-shared-memory /dev/dma_heap/carveout_apps-shared-memory root@p550:/firmware/user# ls /dev/dma-buf-phys /dev/dma-buf-phys root@p550:/firmware/user# Just checking, will both the "dma-buf-phys" driver and "dma-heap-carveout" still available in SDK 10.0 / Linux kernel 6.6 ? Or we have to update accordingly for our implementation when using SDK 10.0 / Linux kernel 6.6 ? rgds, kc Wong
↧