Re: [PATCH weston v3] drm: port the drm backend to the new init api

2015-11-20 Thread Quentin Glidic
For now, I will just comment on the part I am not too happy with. On 31/10/2015 12:08, Giulio Camuffo wrote: [snip] diff --git a/src/main.c b/src/main.c index 292f8e0..bde27ee 100644 --- a/src/main.c +++ b/src/main.c @@ -47,6 +47,8 @@ #include "git-version.h" #include "version.h" +#include

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Michal Suchanek
On 20 November 2015 at 12:48, Pekka Paalanen wrote: > On Fri, 20 Nov 2015 12:18:29 +0100 > Michal Suchanek wrote: > >> On 20 November 2015 at 11:39, Pekka Paalanen wrote: >> > On Thu, 19 Nov 2015 22:46:06 +0100 >> > Michal Suchanek

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Pekka Paalanen
On Fri, 20 Nov 2015 14:10:47 +0100 Michal Suchanek wrote: > On 20 November 2015 at 12:48, Pekka Paalanen wrote: > > On Fri, 20 Nov 2015 12:18:29 +0100 > > Michal Suchanek wrote: > > > >> On 20 November 2015 at 11:39, Pekka Paalanen

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Michal Suchanek
On 20 November 2015 at 14:43, Pekka Paalanen wrote: > On Fri, 20 Nov 2015 14:10:47 +0100 > Michal Suchanek wrote: > >> On 20 November 2015 at 12:48, Pekka Paalanen wrote: >> > On Fri, 20 Nov 2015 12:18:29 +0100 >> > Michal Suchanek

Re: [PATCH weston 07/11] compositor: Move weston_matrix_transform_region to compositor.c and export it

2015-11-20 Thread Pekka Paalanen
On Wed, 18 Nov 2015 16:32:30 -0600 Derek Foreman wrote: > We're going to use this to replace much of the other transform code so > it's no longer just relevant to pixman-renderer.c > > Signed-off-by: Derek Foreman > --- > src/compositor.c |

Re: Touch event delayed or missing with weston 1.8.0 and qtwayland 5.4.2

2015-11-20 Thread Vikas Patil
I think when I feel delay in touch. Seeing following log from weston (I added the prints) and evtest prints. I am testing this with button on HMI. When the button is pressed, it is displayed as pressed, but when released, the view is not updated immediately and it is still displayed as pressed for

Re: question to wayland-protocols and configure error.

2015-11-20 Thread Quentin Glidic
On 20/11/2015 10:38, Christian Hartmann wrote: 2015-11-20 10:34 GMT+01:00 Christian Hartmann : I got a configure error since this week: checking for COMPOSITOR... yes checking for WAYLAND_PROTOCOLS... no configure: error: Package requirements (wayland-protocols >=

Re: question to wayland-protocols and configure error.

2015-11-20 Thread Jonas Ådahl
On Fri, Nov 20, 2015 at 10:34:01AM +0100, Christian Hartmann wrote: > Hi, > > I got a configure error since this week: > > checking for COMPOSITOR... yes > checking for WAYLAND_PROTOCOLS... no > configure: error: Package requirements (wayland-protocols >= 0.1.0) > were not met: > > No package

Re: [PATCH] building: Add instructions for wayland-protocols

2015-11-20 Thread Pekka Paalanen
On Fri, 20 Nov 2015 12:13:28 +0100 Armin K wrote: > --- > building.html | 12 > 1 file changed, 12 insertions(+) > > diff --git a/building.html b/building.html > index 284249a..b8c1a1d 100644 > --- a/building.html > +++ b/building.html > @@ -125,6 +125,18 @@ with

Re: question to wayland-protocols and configure error.

2015-11-20 Thread Christian Hartmann
hi, 2015-11-20 10:34 GMT+01:00 Christian Hartmann : > Hi, > > I got a configure error since this week: > > checking for COMPOSITOR... yes > checking for WAYLAND_PROTOCOLS... no > configure: error: Package requirements (wayland-protocols >= 0.1.0) > were not met: > > No

Re: question to wayland-protocols and configure error.

2015-11-20 Thread Bryce Harrington
On Fri, Nov 20, 2015 at 10:34:01AM +0100, Christian Hartmann wrote: > Hi, > > I got a configure error since this week: > > checking for COMPOSITOR... yes > checking for WAYLAND_PROTOCOLS... no > configure: error: Package requirements (wayland-protocols >= 0.1.0) > were not met: > > No package

Re: question to wayland-protocols and configure error.

2015-11-20 Thread Christian Hartmann
Hi > Looks like you need the new wayland-protocols package. > > Probably some web docs need updated due to this change... > > Bryce > >> cheers >> chris >> ___ >> wayland-devel mailing list >> wayland-devel@lists.freedesktop.org >>

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Pekka Paalanen
On Thu, 19 Nov 2015 13:02:24 -0800 Bryce Harrington wrote: > On Thu, Nov 19, 2015 at 11:05:58AM -0800, Bill Spitzak wrote: > > On Thu, Nov 19, 2015 at 2:38 AM, Christopher Michael < > > cpmich...@osg.samsung.com> wrote: > > > > So, after issuing the inhibit request for a

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Michal Suchanek
On 20 November 2015 at 11:39, Pekka Paalanen wrote: > On Thu, 19 Nov 2015 22:46:06 +0100 > Michal Suchanek wrote: > >> On 19 November 2015 at 20:12, Daniel Stone wrote: >> > Hi, >> > >> > On 19 November 2015 at 19:05, Bill Spitzak

[PATCH] building: Add instructions for wayland-protocols

2015-11-20 Thread Armin K
--- building.html | 12 1 file changed, 12 insertions(+) diff --git a/building.html b/building.html index 284249a..b8c1a1d 100644 --- a/building.html +++ b/building.html @@ -125,6 +125,18 @@ with --disable-documentation. +Wayland protocols + +This contains a set of protocols

question to wayland-protocols and configure error.

2015-11-20 Thread Christian Hartmann
Hi, I got a configure error since this week: checking for COMPOSITOR... yes checking for WAYLAND_PROTOCOLS... no configure: error: Package requirements (wayland-protocols >= 0.1.0) were not met: No package 'wayland-protocols' found Consider adjusting the PKG_CONFIG_PATH environment variable if

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Pekka Paalanen
On Thu, 19 Nov 2015 18:15:39 +0800 Jonas Ådahl wrote: > On Thu, Nov 19, 2015 at 02:04:36AM -0800, Bryce Harrington wrote: > > On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher Michael wrote: > > > Just some random thoughts inlined below... > > > > > > On 11/19/2015 03:05

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Pekka Paalanen
On Thu, 19 Nov 2015 12:06:43 -0800 Bryce Harrington wrote: > On Thu, Nov 19, 2015 at 05:38:34AM -0500, Christopher Michael wrote: > > On 11/19/2015 05:28 AM, Christopher Michael wrote: > > >On 11/19/2015 05:15 AM, Jonas Ådahl wrote: > > >>Not so sure about the scope

Re: black surface in desktop shell fullscreen mode

2015-11-20 Thread zou lan
Hi pekka >Or are you asking for instructions on how to fix the alleged Weston >desktop-shell bug where the black surface is not removed when attaching >a NULL wl_buffer to the wl_surface? Actually I ask for instructions on this. Because I use "hide" to switch the apps. But I met some problems of

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Pekka Paalanen
On Thu, 19 Nov 2015 22:46:06 +0100 Michal Suchanek wrote: > On 19 November 2015 at 20:12, Daniel Stone wrote: > > Hi, > > > > On 19 November 2015 at 19:05, Bill Spitzak wrote: > >> I feel like there is no need to tie it to a surface.

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Pekka Paalanen
On Thu, 19 Nov 2015 13:06:09 -0800 Bryce Harrington wrote: > On Thu, Nov 19, 2015 at 07:12:31PM +, Daniel Stone wrote: > > Just make the inhibit request return a new object, which upon destroy, > > removes the inhibition. That way you don't even have duplicate > >

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Pekka Paalanen
On Fri, 20 Nov 2015 12:18:29 +0100 Michal Suchanek wrote: > On 20 November 2015 at 11:39, Pekka Paalanen wrote: > > On Thu, 19 Nov 2015 22:46:06 +0100 > > Michal Suchanek wrote: > > > >> On 19 November 2015 at 20:12, Daniel Stone

Re: [PATCH wayland v2] protocol: Add wl_surface.damage_buffer

2015-11-20 Thread Pekka Paalanen
On Fri, 20 Nov 2015 16:01:48 +0800 Jonas Ådahl wrote: > On Wed, Nov 18, 2015 at 04:17:58PM -0600, Derek Foreman wrote: > > wl_surface.damage uses surface local co-ordinates. > > > > Buffer scale and buffer transforms came along, and EGL surfaces > > have no understanding of

Re: [PATCH wayland] protocol: Remove incorrect statement that attach must precede damage

2015-11-20 Thread Derek Foreman
On 19/11/15 01:02 AM, Jonas Ådahl wrote: > On Wed, Nov 18, 2015 at 09:44:11AM -0600, Derek Foreman wrote: >> The documentation for wl_surface.commit makes it clear that the >> application of damage follows attach during the commit, so it >> doesn't matter what order the app sends the requests. >>

Re: Touch event delayed or missing with weston 1.8.0 and qtwayland 5.4.2

2015-11-20 Thread Giulio Camuffo
2015-11-20 13:28 GMT+02:00 Vikas Patil : > I think when I feel delay in touch. Seeing following log from weston > (I added the prints) and evtest prints. I am testing this with button > on HMI. When the button is pressed, it is displayed as pressed, but > when released, the

Re: [PATCH wayland v2] protocol: Add wl_surface.damage_buffer

2015-11-20 Thread Derek Foreman
On 20/11/15 06:22 AM, Pekka Paalanen wrote: > On Fri, 20 Nov 2015 16:01:48 +0800 > Jonas Ådahl wrote: > >> On Wed, Nov 18, 2015 at 04:17:58PM -0600, Derek Foreman wrote: >>> wl_surface.damage uses surface local co-ordinates. >>> >>> Buffer scale and buffer transforms came

[PATCH wayland 2/2] protocol: Refine wl_surface.commit text

2015-11-20 Thread Derek Foreman
The order of operations during wl_surface.commit hasn't been clarified since wp_viewport, wl_surface.set_buffer_transform and wl_surface.set_buffer_scale were added. Explain that any state that changes co-ordinates is applied first, and that unchanged co-ordinate altering state is held over from

[PATCH v3 wayland 1/2] protocol: Add wl_surface.damage_buffer

2015-11-20 Thread Derek Foreman
wl_surface.damage uses surface local co-ordinates. Buffer scale and buffer transforms came along, and EGL surfaces have no understanding of them. Theoretically, clients pass damage rectangles - in Y-inverted surface co-ordinates) to EGLSwapBuffersWithDamage, and the EGL implementation passed

Re: [RFC] Screensaver/blanking inhibition

2015-11-20 Thread Pekka Paalanen
On Thu, 19 Nov 2015 05:09:09 -0500 Christopher Michael wrote: > On 11/19/2015 05:04 AM, Bryce Harrington wrote: > > On Thu, Nov 19, 2015 at 04:20:11AM -0500, Christopher Michael wrote: > >> Just some random thoughts inlined below... > >> > >> On 11/19/2015 03:05 AM,

Re: [PATCH] Refine compositor grabs behavior

2015-11-20 Thread Bill Spitzak
On Thu, Nov 19, 2015 at 7:47 PM, Peter Hutterer wrote: > > we had a bit of a discussion on IRC here, this is the attempt of a summary: > A wl_touch.enter/leave event pair makes sense for some use-cases and can > fix > the xdg_popup case. The idea here is that if you

Re: [PATCH v3 wayland 1/2] protocol: Add wl_surface.damage_buffer

2015-11-20 Thread Bill Spitzak
I am pretty certain you can just convert wl_surface.damage coordinates *to* buffer coordinates, using the transform the old buffer was attached with, and thus merge all the wl_surface.damage and wl_surface.damage_buffer into a single region in buffer space. If the transformation does not change,

Re: [PATCH wayland-web v0] rephrasing the index.html to be more acurate

2015-11-20 Thread Pekka Paalanen
On Thu, 19 Nov 2015 14:26:14 -0800 Bryce Harrington wrote: > On Thu, Nov 19, 2015 at 06:51:52PM +0100, Benoit Gschwind wrote: > > Hello, > > > > I tryed to rephrase the index.html to be more acurate. I used Wayland, > > LibWayland and Weston as wording just because they

Re: [PATCH wayland v2] protocol: Add wl_surface.damage_buffer

2015-11-20 Thread Jonas Ådahl
On Wed, Nov 18, 2015 at 04:17:58PM -0600, Derek Foreman wrote: > wl_surface.damage uses surface local co-ordinates. > > Buffer scale and buffer transforms came along, and EGL surfaces > have no understanding of them. > > Theoretically, clients pass damage rectangles - in Y-inverted surface >

Re: black surface in desktop shell fullscreen mode

2015-11-20 Thread Pekka Paalanen
On Fri, 20 Nov 2015 10:52:54 +0800 zou lan wrote: > Hi Pekka > > How to not use the black surface behind the fullscreen surface? I want to Hi Nancy, are you looking for disabling the black surface in a way that would work on upstream Weston or be upstreamable, or

Re: [PATCH v3 wayland 1/2] protocol: Add wl_surface.damage_buffer

2015-11-20 Thread Derek Foreman
On 20/11/15 07:39 PM, Bill Spitzak wrote: > I am pretty certain you can just convert wl_surface.damage coordinates > *to* buffer coordinates, using the transform the old buffer was attached > with, and thus merge all the wl_surface.damage and > wl_surface.damage_buffer into a single region in