On Thu, 22 Nov 2012 15:35:13 -0700
Scott Moreau wrote:
> Since surface.commit was introduced, opqaue regions are stored in a pending
> variable that isn't used until surface.commit. Xwayland uses the surface
> opaque
> region as a way to tell weston what region of the surface should be opaque.
>
Since surface.commit was introduced, opqaue regions are stored in a pending
variable that isn't used until surface.commit. Xwayland uses the surface opaque
region as a way to tell weston what region of the surface should be opaque.
However when this pending opaque region was introduced, xwm was not
From: Daniel Stone
Signed-off-by: Daniel Stone
Signed-off-by: Tiago Vignatti
---
hw/xfree86/xwayland/xwayland-input.c |9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/hw/xfree86/xwayland/xwayland-input.c
b/hw/xfree86/xwayland/xwayland-input.c
index 0d38579..a07b
From: Daniel Stone
We really need to support smooth scrolling properly, but in the meantime
just skip unknown scroll values.
Signed-off-by: Daniel Stone
Before this patch, a crash was easy to reproduce using two-finger scrolling on
a touchpad based device.
Signed-off-by: Tiago Vignatti
---
From: Daniel Stone
Fortunately, this had no ill effects, but still isn't what was intended.
Signed-off-by: Daniel Stone
Signed-off-by: Tiago Vignatti
---
hw/xfree86/xwayland/xwayland-input.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/xfree86/xwayland/xwayland-input.c
b/hw/xf
Given xf86ScaleAxis(int Cx, int to_max, int to_min, int from_max, int
from_min), if to_max goes from 0 to rows - 1, then from_max has to be entered
accordingly to perform correct scaling. Check xf86ScaleAxis definition for
details.
An easy way to reproduce the bug exposed, is to open an xterm with
XWayland fails to initialize in some systems complaining about realloc
problems on libxtrans (when ListenOnOpenFD() is called). It got fixed in
libxtrans version 1.2.7, more specifically:
commit 6086f6c1d0e0a1c9e590879acb2319dea0eb6e96
Author: Robert Bragg
Date: Mon Dec 12 00:30:43
Kristian,
This small patch set is something I've picked from Daniel's tree and also that
I had accumulating locally. It applies on top of the other two patches to
bring XWayland back to life on 1.0, I've sent today.
>From Daniel, there are two other patches that I think deserves to be checked
but
Signed-off-by: Tiago Vignatti
---
protocol/wayland.xml |2 +-
src/wayland-client.c |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index ca3c56f..cc8fb06 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -10
Signed-off-by: Tiago Vignatti
---
Hi Kristian, I guess that was the idea we discussed on IRC?
I kept the same order of the interfaces being bound, without thinking whether
their were the most efficient or something; we we'll have to overhaul the
WM and X server binding anyway when the next proto
Co-authored-by: Daniel Stone
Signed-off-by: Tiago Vignatti
---
changes from v2:
- fix wl_registry_bind client version
- clean-up xwl_drm_authenticate round trips
- use wl_display_dispatch_pending properly, just before going to sleep at
block handler.
- place wl_surface_commit in its correct pla
Backends may move surfaces to different planes, in which case damage is
generated in the primary plane. This damage is usually passed to the
renderer, but in some cases the backend may decide to not render
anything (that's the case when drm compositor scans out a client
buffer). In that case the da
While at it, consolidate all the bindings we already have into one
single function.
---
src/compositor-drm.c | 31 ++-
1 file changed, 18 insertions(+), 13 deletions(-)
diff --git a/src/compositor-drm.c b/src/compositor-drm.c
index 142faa5..1ecd93c 100644
--- a/src/c
When a client frame callback is executed and the client starts rendering
again, the egl event queue might not have been dispatched so that the
buffer release event for the previous frame hasn't been processed. In
that case a third buffer is allocated, even though it would be possible
to reuse the b
Hi,
EGL clients have been triple buffering unnecessarily after the event
queue changes. The problem is that at the moment the frame callback
causes the client to redraw, a wl_buffer.release event is queued in
the EGL side event queue, but it has not yet been processed. A call
to dri2_get_buffers_w
On the client side EGL, all the wl_buffer.release events need to be
processed before buffer allocation, otherwise a third buffer might
be allocated unnecessarily. However, the buffer allocation should
not block in the case no event was received. In order to do that, a
non-blocking queue dispatch fu
On Wed, 21 Nov 2012 11:22:19 -0500
Kristian Høgsberg wrote:
> On Wed, Nov 21, 2012 at 09:26:25AM +0200, Pekka Paalanen wrote:
> > On Tue, 20 Nov 2012 10:26:41 -0800
> > Bill Spitzak wrote:
> >
> > > Pekka Paalanen wrote:
> > > > On Mon, 19 Nov 2012 15:56:23 -0500
> > > > Kristian Høgsberg wrot
17 matches
Mail list logo