[PATCH weston 1/1] compositor: Abort on bad page flip timestamps

2014-11-07 Thread Michel Dänzer
On 07.11.2014 18:36, Pekka Paalanen wrote: > > If we still feel that exiting Weston on the first timestamp failure > (zero or not increasing) is too harsh, we could simply log a warning > and add again some heuristics on when things are too far wrong to > continue. > > E.g. getting a single

[PATCH weston 1/1] compositor: Abort on bad page flip timestamps

2014-11-07 Thread Pekka Paalanen
On Fri, 07 Nov 2014 07:04:16 +0100 Mario Kleiner wrote: > On 06/11/14 17:42, Pekka Paalanen wrote: > > On Thu, 06 Nov 2014 16:08:56 +0900 > > Michel Dänzer wrote: > > > >> On 06.11.2014 03:06, Frederic Plourde wrote: > >>> Many features, like animations, hardly depend on page flip timestamps >

[PATCH weston 1/1] compositor: Abort on bad page flip timestamps

2014-11-07 Thread Mario Kleiner
On 06/11/14 17:42, Pekka Paalanen wrote: > On Thu, 06 Nov 2014 16:08:56 +0900 > Michel Dänzer wrote: > >> On 06.11.2014 03:06, Frederic Plourde wrote: >>> Many features, like animations, hardly depend on page flip timestamps >>> to work properly, but some DRM drivers do not correctly support

[PATCH weston 1/1] compositor: Abort on bad page flip timestamps

2014-11-06 Thread Pekka Paalanen
On Thu, 06 Nov 2014 16:08:56 +0900 Michel Dänzer wrote: > On 06.11.2014 03:06, Frederic Plourde wrote: > > Many features, like animations, hardly depend on page flip timestamps > > to work properly, but some DRM drivers do not correctly support page flip > > timestamps (or not at all) and in