surface-suspension wayland protcool development status?
Ethan “flibitijibibo” Lee
flibitijibibo at gmail.com
Thu Nov 25 01:30:00 UTC 2021
Ah, I misunderstood the intent, my mistake. To clarify then, from SDL’s point of view: All we want is to avoid the deadlock, nothing more.
While I do have a wide range of games at my disposal it’s admittedly not quite the same scale, but: they’re all native games running on SDL and in practice what Sebastian suggests would still be enough of an improvement to make us happy, and we’ll do the necessary testing to ensure the idea works as well as Xwayland’s 1Hz throttle does (which so far has been kind to us).
> On Nov 24, 2021, at 8:23 PM, Joshua Ashton <joshua at froggi.es> wrote:
> What exactly do you agree with? :V is a funny face in response to Sebastian's typical idiocy.
> The timeout doesn't fix anything and still has problems for games that demand a semi-consistent framerate (ie. Not hanging for seconds at a time)
> The correct solution ideally would be to keep ticking along at a constant time for fifo and instantly return for mailbox/immediate when suspended in Mesa. Apps that want to deal with suspension and use VK WSI can just handle that on their surfaces and not present.
> As I understand it, nobody has had the time to implement or prototype that yet.
> As for the protocol, I am not sure what is happening with it since I last touched it. I haven't had the chance to address the nits to wording and such, I've been busy with other things recently.
> - Josh 🐸
> On November 24, 2021 5:11:20 PM PST, "Ethan “flibitijibibo” Lee" <flibitijibibo at gmail.com> wrote:
>> I agree with Joshua - if you think you can get the timeout implemented in EGL and Vulkan WSI I’ll go ahead and mark the SDL Wayland PR as ready to go for 2.0.20. Hypothetically it’d be nice to have an event for hidden vs. exposed but really we just want to avoid deadlocks. As far as independent studios care that model would do the job perfectly fine, not sure about the big AAA studios but they can e-mail the Proton team if they run into any trouble.
>>> On Nov 24, 2021, at 7:35 PM, Joshua Ashton <joshua at froggi.es> wrote:
>>> On Wed, 24 Nov 2021 at 15:31, Sebastian Wick <sebastian at sebastianwick.net <mailto:sebastian at sebastianwick.net>> wrote:
>>> On 2021-11-11 16:00, Neal Gompa wrote:
>>>> Hey all,
>>>> Is there a reason why the development of the surface-suspension
>>>> protocol has completely stalled out? It's been in the 30 day
>>>> discussion period for a few months now and it's a pretty critical
>>>> protocol for games (it's the main blocker for SDL to switch to Wayland
>>>> by default).
>>> FWIW I still believe this is fixable in EGL/WSI: timeout after 1s when
>>> waiting for the wl_surface frame callback.
>>>> From a purely downstream perspective, I'd like to have Fedora Linux
>>>> switch to Wayland by default for SDL-based applications (which we are
>>>> able to do relatively quickly and easily since all SDL applications
>>>> now use SDL2 since Fedora Linux 35).
>>>> Thanks in advance and best regards,
>>>> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/99 <https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/99>
>>>> : https://github.com/libsdl-org/SDL/pull/4306#issuecomment-963513540 <https://github.com/libsdl-org/SDL/pull/4306#issuecomment-963513540>
>>>> : https://fedoraproject.org/wiki/Changes/SDL12onSDL2 <https://fedoraproject.org/wiki/Changes/SDL12onSDL2>
>>>> 真実はいつも一つ！/ Always, there's only one truth!
> - Joshie 🐸
More information about the wayland-devel