Skip to content
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

Merged
merged 2 commits into from Mar 14, 2018

Conversation

gerboland
Copy link
Contributor

@gerboland gerboland commented Feb 15, 2018

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

…k to using the mode named "preferred" as current mode
@gerboland gerboland changed the title RFC: KMS platform - fallback if ctrc mode invalid RFC: KMS platform - fallback if crtc mode invalid Feb 15, 2018
@gerboland gerboland requested a review from RAOF February 15, 2018 12:08
@gerboland
Copy link
Contributor Author

gerboland commented Feb 15, 2018

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

@gerboland gerboland closed this Feb 15, 2018
@gerboland
Copy link
Contributor Author

This is working ok, the problem is in QtMir.

@gerboland gerboland reopened this Mar 14, 2018
Copy link
Contributor

@AlanGriffiths AlanGriffiths left a 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+

bors bot added a commit that referenced this pull request Mar 14, 2018
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
@gerboland gerboland changed the title RFC: KMS platform - fallback if crtc mode invalid KMS platform - fallback if crtc mode invalid Mar 14, 2018
@AlanGriffiths AlanGriffiths added this to To do in Mir 0.31 via automation Mar 14, 2018
@AlanGriffiths AlanGriffiths moved this from To do to In progress in Mir 0.31 Mar 14, 2018
@bors
Copy link
Contributor

bors bot commented Mar 14, 2018

Build failed

@AlanGriffiths
Copy link
Contributor

bors r+

bors bot added a commit that referenced this pull request Mar 14, 2018
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
@bors
Copy link
Contributor

bors bot commented Mar 14, 2018

Build succeeded

@bors bors bot merged commit 95d8296 into canonical:master Mar 14, 2018
Mir 0.31 automation moved this from In progress to Awaiting release Mar 14, 2018
@gerboland gerboland deleted the vmware-current-mode-fix branch March 15, 2018 12:15
@canonical-is canonical-is removed this from Awaiting release in Mir 0.31 Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants