Ryo Munakata
a3a5debe31
At the calculation of the first FPS, gears has initialized last FPS time with gettimeofday(). But the callback_data passed in the callback of wl_surface_frame() is the current time, in milliseconds, with an undefined base. Because of this subtracting last FPS time from callback_data makes no sense. For example, below is the result of running weston-gears on weston with drm backend: $ weston-gears Warning: FPS count is limited by the wayland compositor or monitor refresh rate 1 frames in 1094460.125 seconds = 0.000 FPS 301 frames in 5.016 seconds = 60.008 FPS 301 frames in 5.016 seconds = 60.008 FPS 301 frames in 5.016 seconds = 60.008 FPS As you can see, the the first FPS value is something odd. This patch fixes it by initializing last FPS time with the callback_data passed in the first callback. Reviewed-by: Nils Chr. Brause <nilschrbrause@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.