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
KMS platform - fallback if crtc mode invalid #165
Conversation
…k to using the mode named "preferred" as current mode
Hmm no, only partial fix. Unity8/QtMir isn't crashing on startup any more, but is still reading incorrect display mode data... Nested mir servers are reading the right thing. Difference concerns me |
This is working ok, the problem is in QtMir. |
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.
The brace style is "wrong" for Mir (but matches the surrounding code).
bors r+
165: RFC: KMS platform - fallback if crtc mode invalid r=AlanGriffiths a=gerboland RFC - not ideal but I see no better way. If the current mode advertised by the crtc does not exist in the list of modes, fall back to using the mode named "preferred" as current mode. Fixes nested server run on VMWare: https://bugs.launchpad.net/mir/+bug/1661295
Build failed |
bors r+ |
165: KMS platform - fallback if crtc mode invalid r=AlanGriffiths a=gerboland If the current mode advertised by the crtc does not exist in the list of modes, fall back to using the mode named "preferred" as current mode. Some VMs specify this. Fixes nested server run on VMWare: https://bugs.launchpad.net/mir/+bug/1661295
Build succeeded |
If the current mode advertised by the crtc does not exist in the list of modes, fall back to using the mode named "preferred" as current mode. Some VMs specify this.
Fixes nested server run on VMWare: https://bugs.launchpad.net/mir/+bug/1661295