-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propose for meeting discussion #271
Comments
Hi @xiaoxiang781216,
I propose that we go by steps and start with the RPMsg NS handcheck. |
Ok, I will do in the next couple week.
After finishing the review, I will update to this approach if the community like this direction.
The link describe "Packed virtqueues", is it really related to this feature? Could you give a link of Loic Pallardy's patchset?
The patch alreay define feature-bit: I don't add version field because virtio prefer to control the config space change by feature-bit. And the patch already reserve 64 bytes config space for the new feature-bit:
Ok. |
Bad copy/past...
Right, but this field is not related to the config struct only. The field would be used to interpret a muti configs structure.
The version field is mainly to prevent an update of the structure itself that need to be known on both side. |
This issue has been marked as a stale issue because it has been open (more than) 45 days with no activity. |
See here: rpmsg.pdf
The text was updated successfully, but these errors were encountered: