Re: [PATCH] weston-build: Fix aclocal error during autogen.sh

I'm not sure that I like ignoring m4 completely. If we ever do put anything useful there, it would be good to make sure it doesn't get forgotten. In the wayland repo, we have a m4/.gitignore that ignores the 5 files that matter. Copying that one might be a better idea. --Jason Ekstrand On Wed,

Re: [PATCH weston 0/2] Unify the commit logic

It's a code cleanup. Every time we change the commit logic (see the last weston commit) we have to do it in two places. They are bound to get out-of-sync. --Jason On Fri, Jun 20, 2014 at 5:28 PM, Jasper St. Pierre wrote: > Does this fix any bugs that you know of, or is it just a code cleanup?

Re: [PATCH weston 0/2] Unify the commit logic

Does this fix any bugs that you know of, or is it just a code cleanup? Just curious, I'm not insinuating anything. On Fri, Jun 20, 2014 at 8:25 PM, Jason Ekstrand wrote: > This little two-patch series unifies all of the surface commit logic in one > place. Previously the commit logic was dupli

[PATCH weston 0/2] Unify the commit logic

This little two-patch series unifies all of the surface commit logic in one place. Previously the commit logic was duplicated in weston_surface and weston_subsurface functions in order to handle the commit cache. Jason Ekstrand (2): Move weston_subsurface to after weston_surface Create a west

[PATCH weston 2/2] Create a weston_surface_state structure for storing pending surface state and move the surface commit logic into weston_surface_commit_state

From: Jason Ekstrand This new structure is used for both weston_surface.pending and weston_subsurface.cached. Signed-off-by: Jason Ekstrand --- src/compositor.c | 151 +++ src/compositor.h | 80 +++-- 2 files changed,

[PATCH weston 1/2] Move weston_subsurface to after weston_surface

From: Jason Ekstrand It makes more sense there. Signed-off-by: Jason Ekstrand --- src/compositor.h | 102 +++ 1 file changed, 51 insertions(+), 51 deletions(-) diff --git a/src/compositor.h b/src/compositor.h index eae1b20..06f8b03 100644 --

[PATCH] Better error message when exec'ing Xwayland fails

--- xwayland/launcher.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/xwayland/launcher.c b/xwayland/launcher.c index 70703a4..bf1e17e 100644 --- a/xwayland/launcher.c +++ b/xwayland/launcher.c @@ -117,7 +117,11 @@ weston_xserver_handle_event(int listen_fd, uint32_t mask

[PATCH 2/2] compositor-drm: Add support for Tegra Jetson TK1

Update configure.ac to add check for libdrm_tegra --- configure.ac | 18 ++ src/compositor-drm.c | 96 ++-- 2 files changed, 111 insertions(+), 3 deletions(-) diff --git a/configure.ac b/configure.ac index b4511fc..ece4a0c 100644 ---

[PATCH 1/2] compositor-drm: Add new gbm struct to allow for a separate gbm device

This is needed for devices like tegra jetson where the gbm device is not the same as the drm device --- src/compositor-drm.c | 43 +-- 1 file changed, 25 insertions(+), 18 deletions(-) diff --git a/src/compositor-drm.c b/src/compositor-drm.c index 7d514e4..

[PATCH 0/2] Add support for Jetson TK1 to drm compositor

Repo:git://git.baserock.org/delta/weston.git Branch:baserock/james/weston Sha1:acdcafcfb36ff19677939f249c59bd480bd0db38 These patches allow weston to use the drm backend on the nvidia jetson tk1 board Based on code from Thierry Reding, this requires libdrm with experimental tegra support compiled

Re: [PATCH 1/3] tests: add expect_protocol_error function

On 19 June 2014 04:37, Bryce W. Harrington wrote: > On Mon, May 26, 2014 at 04:58:05PM +0200, Marek Chalupa wrote: > > This function checks if a particular protocol error came in wire. > > It's usefull in the cases where we hitherto used FAIL_TEST. > > The problem with FAIL_TEST is that *any* ass

Re: [PATCH 1/3] tests: add expect_protocol_error function

On 19 June 2014 04:37, Bryce W. Harrington wrote: > On Mon, May 26, 2014 at 04:58:05PM +0200, Marek Chalupa wrote: > > This function checks if a particular protocol error came in wire. > > It's usefull in the cases where we hitherto used FAIL_TEST. > > The problem with FAIL_TEST is that *any* ass

[PATCH] client: extend error handling

When an error occurs, wl_display_get_error() does not provide any way of getting know if it was a local error or if it was an error event, respectively what object caused the error and what the error was. This patch introduces a new function wl_display_get_protocol_error() which will return error

Re: [PATCH] client: extend error handling

Thanks for reviewing :) English is my weakness (not the only though :D). Fixed patch is coming... Marek On 19 June 2014 04:24, Bryce W. Harrington wrote: > On Mon, May 26, 2014 at 04:57:23PM +0200, Marek Chalupa wrote: > > When an error occurs, wl_display_get_error() does not > > provide any w