On 14-10-29 05:40 PM, Bill Spitzak wrote:
On 10/29/2014 12:19 PM, Frederic Plourde wrote:
Mhh... you mean something like :
static int
drm_output_watchdog_timer_create(struct drm_output *output)
{
struct wl_event_loop *loop = NULL;
struct weston_compositor *ec = output_base->composito
On 10/29/2014 12:19 PM, Frederic Plourde wrote:
Mhh... you mean something like :
static int
drm_output_watchdog_timer_create(struct drm_output *output)
{
struct wl_event_loop *loop = NULL;
struct weston_compositor *ec = output_base->compositor;
loop = wl_display_get_event_loop(e
On 14-10-29 02:45 PM, Bill Spitzak wrote:
On 10/29/2014 11:13 AM, Frederic Plourde wrote:
This watchdog timer (WDT) implementation is software only and includes
basic features usually found in a WDT. We simply exit Weston gracefully
with an exit code when the dog barks.
The watchdog timeout va
On 10/29/2014 11:13 AM, Frederic Plourde wrote:
This watchdog timer (WDT) implementation is software only and includes
basic features usually found in a WDT. We simply exit Weston gracefully
with an exit code when the dog barks.
The watchdog timeout value can be set via weston.ini by adding a
Weston will not repaint until previous update has been acked by
a page-flip event coming from the drm driver. However, some buggy drivers
won't return those events or will stop sending them at some point and
Weston output repaints will completely freeze. To ease developers' task in
testing their dr
Weston will not repaint until previous update has been acked by
a page-flip event coming from the drm driver. However, some buggy drivers
won't return those events or will stop sending them at some point and
Weston output repaints will completely freeze. To ease developers' task in
testing their dr
