Thanks for this.
I've just realized that using 32 bits ints won't be sufficient.
Is there a way in the protocol to have requests with 64 bits int args,
and callback with 64 bits int args too?
Axel Davy
Jiergir Ogoerg wrote :
Just a reminder on how clocks differ (on LInux) from one another,
taken from here:
http://www.spinics.net/lists/linux-man/msg00973.html
Needless to say, gettimeofday() should be avoided.
CLOCK_REALTIME
- can jump
- can slew
- if ntp is running this clock is always kept close to GMT. even if
hardware is not 100% correct, ntp will correct everything over time.
CLOCK_MONOTONIC
- cannot jump
- can slew !!! (because of ntp)
- it is not kept in sync with GMT. but the "speed" of seconds is kept
in sync with GMT by varying it constantly by ntp.
CLOCK_MONOTONIC_RAW
- cannot jump
- cannot slew !
- the speed of seconds is not the same as the speed of GMT seconds
since the hardware timer is never 100% exact and ntp daemon does NOT
have influence here
--------------------
/**
*Just one question. Which clock is being used. Ideally a monotony one, or
*even better, a configurable one. We would normally not want these
*timestamps affected by the user changing the system time.
**/
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
