-
-
Notifications
You must be signed in to change notification settings - Fork 889
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
Image & video hardware decoding/encoding (hardware DRM, VCN) support #28
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Can this be fixed? Looking forward to solving this problem, thank you |
This comment was marked as spam.
This comment was marked as spam.
Be patient, I'm the only dev! |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as spam.
This comment was marked as spam.
As the firmware used is correct, and the logic in macOS is correct, and AppleGVA is seemingly almost patched fully, I have no idea what is still up with this. Maybe there is an issue with the rest of the firmware since we don’t replace anything other than VCN. |
I have unlocked the conversation for discussion of functionality after new firmware injection. Please don't spam with screenshots or asking for EFIs; I will lock it again. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as spam.
This comment was marked as spam.
One issue is that it doesn't change the capability of how much resolution is supported. VCN 1 supports smaller resolution than VCN 2 |
After further analysis the issue is more complicated than just the VA bundle. For instance, the Metal Accelerator Shared User Client which has different platform function indices in X6000 vs X5000. In addition, the "SML" class, which amongst other functions, dictates whether there's SAMU, VCN, VCE, etc. Furthermore, the Video Context class of the accelerator. There might be more I missed in my analysis. Don't know for sure about the dependency of the Accelerator Shared class, but the VA bundle definitely uses it from what I can tell. |
Hello everyone... |
I have a testing device of my own, lol. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Existing code has been removed because it's broken. Part of a bigger end goal called "The Update". |
No description provided.
The text was updated successfully, but these errors were encountered: