-
Notifications
You must be signed in to change notification settings - Fork 71
Update MMD versioning scheme #342
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
Conversation
d580bda
to
4e50f67
Compare
125e290
to
9da3ad0
Compare
Right, or unless they set it to some jibber-jabber that cannot be converted to a floating point number, which I don't think will happen very often :p |
Hi Sophie, Is this planned to go to 2024.2 release? Thanks, Zibai |
Chatted with Sophie offline. This will go to Trunk first and then cherry-picked into 2024.2 depends on the full test results. I am reviewing the change, so far looks good to me. Will do a more thorough review and should be done by tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Sophie!
This change also: - Determines MMD buffer location support based on MMD verison - Formally define host pipe side band port id in aocl_mmd.h - Support querying buffer location on host/shared USM allocation
9da3ad0
to
f05e6d4
Compare
Resolves #147 by deciding buffer location support based on the MMD version.
With the new versioning scheme, MMDs starting from version 2024.2 should be supporting buffer location and accepting the buffer location property.