Summary: | Custom resolutions for Wayland | ||
---|---|---|---|
Product: | Wayland | Reporter: | kkllusq |
Component: | wayland | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | CC: | kkllusq |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
kkllusq
2018-03-29 09:16:23 UTC
Hi, adding custom video modes is a feature of your particular Wayland display server. All configuration is up to each Wayland display server individually. They could agree on a mutual configuration standard, but that would be out of scope for Wayland as understood by the bugzilla product/component in this bug. Loading an EDID file through the kernel seems like a good solution to me, so it might be worth figuring out why it stopped working. If you want to make a configuration with your display server, please consult your specific display server documentation. FWIW, for years people have come up once in a while suggesting that Wayland should replicate X11 RandR, but it has never gained enough traction with the major desktop projects to become a serious proposal. Sorry. I think two major counter-arguments are: a) access control, we do not want arbitrary applications changing video modes at will, and b) once the Wayland display server accepts connections so that an app could program a video mode, the server has already initialized the display hardware so it's too late and will lead to glitchy user experience. Drafting such an interface would also be a considerable amount of work for a feature that most big desktop environments already implement by some other means. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.