[PATCH 5/5] Turn off gcc warning on both 64 and 32 bit

From: Bill Spitzak --- src/connection.c |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/connection.c b/src/connection.c index 9f78c85..2f32e42 100644 --- a/src/connection.c +++ b/src/connection.c @@ -557,8 +557,8 @@ wl_connection_vmarshal(struct wl_connection

[PATCH 4/5] Use blocking output for the pipe

From: Bill Spitzak It certainly looks like this message must be sent! --- src/connection.c |3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/src/connection.c b/src/connection.c index 1f707ed..9f78c85 100644 --- a/src/connection.c +++ b/src/connection.c @@ -277,8 +277,7 @

[PATCH 3/5] GCC format arg checking for wl_resource_post_error

From: Bill Spitzak Probably a good idea, as the current code has a mistake here which I fixed in the previous patch. May need to surround this so it is gcc-only. --- src/wayland-server.h |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/src/wayland-server.h b/src/wayland

[PATCH 2/5] Added some more information to error messages

From: Bill Spitzak --- src/wayland-server.c | 11 --- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/src/wayland-server.c b/src/wayland-server.c index 899c094..075ebe8 100644 --- a/src/wayland-server.c +++ b/src/wayland-server.c @@ -161,6 +161,9 @@ wl_resource_post_erro

[PATCH 1/5] Crash if zero data but non-zero fd's in message

From: Bill Spitzak connection.c sent a 4096 byte block of garbage if it wanted to send an fd and there happened to be zero data to send as well. --- src/connection.c |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/src/connection.c b/src/connection.c index fa01545..1f7

[PATCH 2/2] Don't ask for EGL depth buffer if not needed

From: Bill Spitzak This makes the compositor and demo clients work on the current nouveau nvfx driver. Obviously does not fix any clients that actually want a depth buffer, but this does allow more people to at least try wayland. --- clients/simple-egl.c |1 - clients/window.c |

[PATCH 1/2] Don't hang in wait if suspended/resumed

From: Bill Spitzak Pausing weston (with ^Z in the shell) and putting it in the background made it hang. It actually never called sigchld when I killed or made clients exit, so it is not clear if this handler is needed at all. --- src/compositor.c |4 +++- 1 files changed, 3 insertions(+), 1

Re: weston-terminal crash

> PS: I have no idea how to submit patches. Going to try now *without* > "[PATCH]" in the title. > > Here are some steps to create a basic patch with git: 1. git clone URL (clone the repo) 2. make changes (make your changes to the repo files) 3. git diff > yourcode.patch (not necessary, but a quic

Check arguments to wl_resource_post_error in gcc

The attached patch turns on printf argument warnings for this function, which I found was being called incorrectly at least once in the wayland source code. diff --git a/src/wayland-server.h b/src/wayland-server.h index 4293536..2072827 100644 --- a/src/wayland-server.h +++ b/src/wayland-server

Building Qt with wayland 0.85

qtwayland is a plugin for qt that provides the wayland backend for qt. It depends on qtbase. qtwayland has a 0.85 branch compatible with wayland 0.85. But it doesn't currently build against qtbase master, which is unfortunate. Also, there's apparently lots of stuff in the qtwayland plugin other

[PATCH] wayland: crash if fd sent with zero byte message

connection.c sent a 4096 byte block of garbage if it wanted to send an fd and there happened to be zero data to send as well. This is the first diff in the patch. This patch also makes it retry on EAGAIN, although I suspect the normal, rather than non-blocking, sockets should be used. It als

Re: weston-terminal crash

FIXED!!! connection.c sent a 4096 byte block of garbage if it wanted to send an fd and there happened to be zero data to send as well. This is the first diff in the patch. This patch also makes it retry on EAGAIN, although I suspect the normal, rather than non-blocking, sockets should be use

Re: Why the GTK+ wayland backend can't be enabled in linux distros, at all

On domingo, 18 de março de 2012 17.07.11, dar...@chaosreigns.com wrote: > B) Get the Nvidia proprietary driver to reduce memory consumption. >I haven't touched this one. All I have found is linux-b...@nvidia.com >mentioned on >http://www.nvidia.com/object/linux_display_ia32_169.09.html

Re: Upside down and backwards

On Wed, Mar 7, 2012 at 8:34 AM, Kristian Høgsberg wrote: > On Mon, Mar 5, 2012 at 2:42 AM, Pekka Paalanen wrote: >> On Sun, 4 Mar 2012 20:37:48 -0800 >> Mandeep Singh Baines wrote: >> >>> Hi, >>> >>> I have recently started playing around with EGL_PLATFORM=drm. Using >>> eglkms.c and compositor-

Why the GTK+ wayland backend can't be enabled in linux distros, at all

There are two major reasons the wayland backend for GTK+ can't currently be enabled at all, not just by default, in a linux distribution: 1) Enabling both the x11 and wayland backends of GTK+ causes GTK to be entirely unusable: https://bugzilla.gnome.org/show_bug.cgi?id=672361 2) The wayla