CV-Bowen opened a new pull request, #14077: URL: https://github.com/apache/nuttx/pull/14077
## Summary commit 1d5da58674ade82e26e0e806567791a1b6ec1a26 (HEAD -> rpmsg-virtio, wbw/rpmsg-virtio) Author: Bowen Wang <[email protected]> Date: Fri Oct 11 10:57:36 2024 +0800 - sim:rpserver_virtio and rpproxy_virtio: add rpmsg_virtio config for sim add rpserver_virtio and rproxy_virtio to verify the rpmsg virtio transport - rpmsg_virtio: move notify_wait_cb to struct rpmsg_virtio_device notify_wait_cb has been moved to struct rpmsg_virtio_device, so change rpmsg_virtio.c transport too. - rpmsg/virtio: fix compile issue, feature uint32_t to uint64_t Has change the virtio feature bit to 64bit, so rpmsg virtio need change to 64bit too. - rpmsg/rpmsg_virtio.h: include <openamp/remoteproc.h> to fix compile error /data/project/code/apache/nuttx/include/nuttx/rpmsg/rpmsg_virtio.h:176:28: error: field ‘rsc_tbl_hdr’ has incomplete type 176 | struct resource_table rsc_tbl_hdr; | ^~~~~~~~~~~ /data/project/code/apache/nuttx/include/nuttx/rpmsg/rpmsg_virtio.h:178:28: error: field ‘log_trace’ has incomplete type 178 | struct fw_rsc_trace log_trace; | ^~~~~~~~~ /data/project/code/apache/nuttx/include/nuttx/rpmsg/rpmsg_virtio.h:179:28: error: field ‘rpmsg_vdev’ has incomplete type 179 | struct fw_rsc_vdev rpmsg_vdev; | ^~~~~~~~~~ /data/project/code/apache/nuttx/include/nuttx/rpmsg/rpmsg_virtio.h:180:28: error: field ‘rpmsg_vring0’ has incomplete type 180 | struct fw_rsc_vdev_vring rpmsg_vring0; | ^~~~~~~~~~~~ /data/project/code/apache/nuttx/include/nuttx/rpmsg/rpmsg_virtio.h:181:28: error: field ‘rpmsg_vring1’ has incomplete type 181 | struct fw_rsc_vdev_vring rpmsg_vring1; | ^~~~~~~~~~~~ /data/project/code/apache/nuttx/include/nuttx/rpmsg/rpmsg_virtio.h:182:28: error: field ‘config’ has incomplete type 182 | struct fw_rsc_config config; ## Impact rpmsg_virtio ## Testing sim rpserver_virtio and rpproxy_virtio -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
