Re: [PATCH weston v5 16/36] libweston: add weston_head_is_device_changed() API

2018-02-05 Thread Derek Foreman
On 2018-02-05 05:34 AM, Pekka Paalanen wrote: On Fri, 2 Feb 2018 16:25:56 -0600 Derek Foreman wrote: On 2017-12-14 05:40 AM, Pekka Paalanen wrote: From: Pekka Paalanen Reacting to DRM hotplug events is racy. It is theoretically possible to get hotplug events for a quick swap from one monito

Re: [PATCH weston v5 16/36] libweston: add weston_head_is_device_changed() API

2018-02-05 Thread Pekka Paalanen
On Fri, 2 Feb 2018 16:25:56 -0600 Derek Foreman wrote: > On 2017-12-14 05:40 AM, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > Reacting to DRM hotplug events is racy. It is theoretically possible to > > get hotplug events for a quick swap from one monitor to another and > > process bot

Re: [PATCH weston v5 16/36] libweston: add weston_head_is_device_changed() API

2018-02-02 Thread Derek Foreman
On 2017-12-14 05:40 AM, Pekka Paalanen wrote: From: Pekka Paalanen Reacting to DRM hotplug events is racy. It is theoretically possible to get hotplug events for a quick swap from one monitor to another and process both only after the new monitor is connected. Hence it is possible for display d

[PATCH weston v5 16/36] libweston: add weston_head_is_device_changed() API

2017-12-14 Thread Pekka Paalanen
From: Pekka Paalanen Reacting to DRM hotplug events is racy. It is theoretically possible to get hotplug events for a quick swap from one monitor to another and process both only after the new monitor is connected. Hence it is possible for display device information to change without going throug