-
Notifications
You must be signed in to change notification settings - Fork 104
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
Untangle input ↔ graphics platforms #3071
Comments
In my view we should (by default) load all platforms supported on a given piece of hardware.
And here are the platforms we're looking at now:
Of those, the only really special ones I find are Excluding those two, all other permutations seem plausible to me? Headless ++GPU, headless --GPU, extra virtual screens on a headed setup. |
We have the following input platforms (by the names returned in
I agree about the hosted platforms (Wayland and X11) being "special" and, probably, exclusive. |
This ticket is related, but can be done separately: #3073 |
We should also update the "default" text as part of this task (stubbed platform is not default now, or probably ever) |
The default text is from the default option. |
Though virtual should also be allowed, shouldn't it… |
We should be able to run with just the
egl-generic
rendering andvirtual
display platforms.*-kms
platforms shouldn't forceevdev
usage, as you should be able to render to a virtual display only, taking input from whatever the remote display protocol happens to be.The text was updated successfully, but these errors were encountered: