-
Notifications
You must be signed in to change notification settings - Fork 302
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
vaGetDeviceNames inspired fixes and documentation #733
Conversation
@XinfengZhang this and your original fixes should be backported to all releases which have DRI3 support. Thanks |
@@ -38,18 +38,17 @@ | |||
const char VAAPI_DEFAULT_DRIVER_NAME[] = "vaon12"; |
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.
This commit is Reviewed-by: Sil Vilerino <[email protected]>
windows/windows-msvc build failed |
6b2bab1
to
504e0e0
Compare
Should be fixed now. As a bonus, I've rebased against latest master branch. |
The adapter_luid is already stored in pDriverContext->native_dpy. The copy in VADisplayContextWin32, is not needed. Signed-off-by: Emil Velikov <[email protected]>
All the vafool codebase was removed a while ago, with little sign of it coming back. Signed-off-by: Emil Velikov <[email protected]>
Note that the old ones are deprecated. For the new one mention the ownership model and num_drivers meaning/handling. Signed-off-by: Emil Velikov <[email protected]>
Similar to ce9898c Signed-off-by: Emil Velikov <[email protected]>
As documented (and updated) the callee(s) cannot set the num_drivers past the original size. So drop the unreachable code. Signed-off-by: Emil Velikov <[email protected]>
All the backends implement the callback. So this temporary check can go now. Signed-off-by: Emil Velikov <[email protected]>
504e0e0
to
ee49ceb
Compare
Effectively a follow-up on #731
There a couple of unrelated fixes, noticed while browsing through: