Pekka Paalanen
04f8a9b3fa
Weston running the Wayland backend is nested. The parent compositor uses an unknown clock for the frame callback timestamps. This is quite likely a different clock from what the nested Weston chose as its presentation clock. This means we cannot reasonably read the presentation clock and assume it has any relation to the timestamp got from the frame callback. In fact, this was seen to cause absurd repaint delays, trigger the insanity check, reduce fraterate, etc. problems, because we assume we can read the clock and compute the remaining repaint delay. As we can't use the timestamp, ignore it, and read our own presentation clock instead. The X11 backend does not suffer from this, because there the parent window system never provides us any timestamps, so we always read our own clock. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Derek Foreman <derekf@osg.samsung.com> Acked-by: Giulio Camuffo <giuliocamuffo@gmail.com>
Weston Weston is the reference implementation of a Wayland compositor, and a useful compositor in its own right. Weston has various backends that lets it run on Linux kernel modesetting and evdev input as well as under X11. Weston ships with a few example clients, from simple clients that demonstrate certain aspects of the protocol to more complete clients and a simplistic toolkit. There is also a quite capable terminal emulator (weston-terminal) and an toy/example desktop shell. Finally, weston also provides integration with the Xorg server and can pull X clients into the Wayland desktop and act as a X window manager. Refer to http://wayland.freedesktop.org/building.html for building weston and its dependencies. The test suite can be invoked via `make check`; see http://wayland.freedesktop.org/testing.html for additional details.