On Mon, 8 Apr 2013 17:11:27 -0400
Kristian Høgsberg wrote:
> On Sun, Apr 07, 2013 at 05:24:51PM +0300, Pekka Paalanen wrote:
> > On Fri, 5 Apr 2013 23:07:11 +0200
> > Jonas Ådahl wrote:
> >
> > > Most backends relies on gettimeofday(2) for output repaint
> > > timestamps but this is not a requ
Hi,
On 8 April 2013 22:11, Kristian Høgsberg wrote:
> The problem that Pekka brought up of not sending the right timestamp
> is still not really fixable with the above structure. When the
> compositor repaints and sends out frame events it still doesn't know
> when the frame is going to be visib
On Sun, Apr 07, 2013 at 05:24:51PM +0300, Pekka Paalanen wrote:
> On Fri, 5 Apr 2013 23:07:11 +0200
> Jonas Ådahl wrote:
>
> > Most backends relies on gettimeofday(2) for output repaint timestamps
> > but this is not a requirement. Before this patch repaints coming from
> > idle_repaint() always
On Sun, Apr 7, 2013 at 4:24 PM, Pekka Paalanen wrote:
> On Fri, 5 Apr 2013 23:07:11 +0200
> Jonas Ådahl wrote:
>
> > Most backends relies on gettimeofday(2) for output repaint timestamps
> > but this is not a requirement. Before this patch repaints coming from
> > idle_repaint() always used get
On Fri, 5 Apr 2013 23:07:11 +0200
Jonas Ådahl wrote:
> Most backends relies on gettimeofday(2) for output repaint timestamps
> but this is not a requirement. Before this patch repaints coming from
> idle_repaint() always used gettimeofday(2) for timestamps. For backends
> not using that time sou
On Sat, 6 Apr 2013 09:43:11 +0200
renoX wrote:
> Hello,
>
> I don't understand why weston or the backends use gettimeofday instead of a
> monotonic time: doesn't this add work to all the clients to be able to be
> robust to time going into the past of things like that?
Yes, they should be using
Hello,
I don't understand why weston or the backends use gettimeofday instead of a
monotonic time: doesn't this add work to all the clients to be able to be
robust to time going into the past of things like that?
BR,
renoX
___
wayland-devel mailing list
Most backends relies on gettimeofday(2) for output repaint timestamps
but this is not a requirement. Before this patch repaints coming from
idle_repaint() always used gettimeofday(2) for timestamps. For backends
not using that time source this could cause large jumps between
timestamps.
To fix thi