On 14-11-06 02:08 AM, Michel Dänzer wrote:
On 06.11.2014 03:06, Frederic Plourde wrote:
If a pathological case is detected, we gracefully exit Weston
with an appropriate exit code to help developers debug their drivers.
That seems a bit harsh. IIRC, zero can be returned for the timestamp
appropriate exit code to help developers debug their drivers.
This fixes: https://bugs.freedesktop.org/show_bug.cgi?id=79502
Notes:
Based on initial design by Pekka Paalanen
Depends on "compositor: Return a user-defined exit code"
Signed-off-by: Frederic Plourde
---
src/composi
On 14-10-30 04:06 AM, Pekka Paalanen wrote:
Below I'll attach what I had written earlier but not sent, because
then I realized the server vs. weston-desktop-shell thing. If we do
autolaunch in the server, the below more or less applies again.
**
Okay, if Fred or someone actually has time to do
dog barks.
The watchdog timeout value can be set via weston.ini by adding a
watchdog-timer-timeout= entry under a new [compositor-drm]
section. Setting this timeout to 0 disables the watchdog feature.
https://bugs.freedesktop.org/show_bug.cgi?id=83884
Signed-off-by: Frederic Plourde
---
src/
th idle-timeout bits
https://bugs.freedesktop.org/show_bug.cgi?id=83921
Signed-off-by: Frederic Plourde
Reviewed-by: Bryce Harrington
---
man/weston.ini.man | 23 ---
src/compositor.c | 6 +-
2 files changed, 25 insertions(+), 4 deletions(-)
diff --git a/man/westo
dog barks.
The watchdog timeout value can be set via weston.ini by adding a
watchdog-timer-timeout= entry under a new [compositor-drm]
section. Setting this timeout to 0 disables the watchdog feature.
https://bugs.freedesktop.org/show_bug.cgi?id=83884
Signed-off-by: Frederic Plourde
---
src/
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
On 14-10-29 02:57 PM, Bryce Harrington wrote:
On Mon, Oct 27, 2014 at 11:17:48AM -0400, Frederic Plourde wrote:
Weston's idle timeout can already be set via the '-i' command-line
option, but this patch lets users specify it also via weston.ini.
Note that the command-line option t
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
dog barks.
The watchdog timeout value can be set via weston.ini by adding a
watchdog-timer-timeout= entry under a new [compositor-drm]
section. Setting this timeout to 0 disables the watchdog feature.
https://bugs.freedesktop.org/show_bug.cgi?id=83884
Signed-off-by: Frederic Plourde
---
src/
at want
to report test failures to the overlying testing infrastructure.
Signed-off-by: Frederic Plourde
---
src/compositor.c | 17 +
src/compositor.h | 5 +
2 files changed, 22 insertions(+)
diff --git a/src/compositor.c b/src/compositor.c
index 29731c7..a08b53d 100644
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
Currently, once we've reached our main's wl_display_run(), we always
return ret=EXIT_SUCCESS when weston terminates through wl_display_terminate.
This patch makes it possible to specify another return value by setting
prior to terminating Weston. This is useful for automated tests that want
to rep
w function,
parse_launcher_path.
Signed-off-by: Frederic Plourde
---
clients/desktop-shell.c | 38 --
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git a/clients/desktop-shell.c b/clients/desktop-shell.c
index 961a9b2..c8e2810 100644
--- a/clien
th idle-timeout bits
https://bugs.freedesktop.org/show_bug.cgi?id=83921
Signed-off-by: Frederic Plourde
---
man/weston.ini.man | 19 +--
src/compositor.c | 6 +-
2 files changed, 22 insertions(+), 3 deletions(-)
diff --git a/man/weston.ini.man b/man/weston.ini.man
index c
This patch fixes a couple of misuses around .TP 7 macros that wrongly
limited right margins and relative identation.
---
man/weston.ini.man | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/man/weston.ini.man b/man/weston.ini.man
index c05a221..54a1925 100644
--- a/man/weston.i
don't
believe %m is supported there?
That said, it runs nicely here and does what it says on the tin...
Reviewed-by: Derek Foreman
On 22/10/14 08:53 AM, Pekka Paalanen wrote:
Process a new section 'autolaunch' from weston.ini, launching all
programs given there on de
Hi,
I have gathered comments and suggestions from colleagues and
wayland-devel reviewers and here is RFC v.2 of our buffer queue +
presentation feedback protocol extension.
Notice the following changes :
---
On 13-10-28 08:18 AM, Axel Davy wrote:
On Mon, 28 Oct 2013, Pekka Paalanen wrote:
The only immediate effect I could see for the protocol proposal is
to replace the frequency field in a "monitor refresh rate changed"
event with a min and max duration, or whatever that could actually
describe ho
On 13-10-18 05:59 PM, James Courtier-Dutton wrote:
We would also need the API to be compatible with "G-Sync".
http://www.pcper.com/news/Graphics-Cards/NVIDIA-Announces-G-Sync-Variable-Refresh-Rate-Monitor-Technology
From my understanding of GSYNC, the monitor refresh rate will be
completely s
On 13-10-21 10:39 AM, Axel Davy wrote:
I think the simpler is to have a
similar functionalities to the X Present extension:
git://people.freedesktop.org/~keithp/presentproto master
We can ask a buffer to be shown at a speci
Plus of course the same for the next buffer, so you know e.g. how long
a buffer was on screen etc.
How does that sound?
So, the information you propose, with timestamps, gives us timestamps
from events in the past.
Is there any way to deterministically ensure that a particular fra
r cases where they'd need, e.g. to "pause"
the streaming.We're still having a whole bunch of implementation-wise
questions, but that's a start. It'd be awesome if I had your feedback on
this protocol.
Thanks !
Frederic Plourde
Copyright © 2012-20
23 matches
Mail list logo
