Re: [Freedreno] Freedreno Mesa with wayland support

2014-08-03 Thread Shrisha
Hi, The issue was in my wayland package. It wasn't compiles properly with scanner enabled. Compiled wayland with the scanner support and hence fixed my issue. Thanks for the support. Regards, Shrisha On Sat, Jul 12, 2014 at 12:37 AM, Jason Ekstrand wrote: > On Fri, Jul 11, 2014 at 8:33 AM, R

Re: [PATCH libinput 3/4] evdev: Release still pressed keys/buttons when removing device

2014-08-03 Thread Peter Hutterer
On Sun, Jul 27, 2014 at 11:28:30PM +0200, Jonas Ådahl wrote: > When removing a device, its not guaranteed that all button or key > presses have been released, resulting in an invalid seat wide button > count. > > Note that kernel devices normally will send release events when being > unplugged, bu

Re: [PATCH libinput 2/4] evdev: Keep track of button/key press count per device

2014-08-03 Thread Peter Hutterer
On Sun, Jul 27, 2014 at 11:28:29PM +0200, Jonas Ådahl wrote: > Keep track of the number of times a given button or key is pressed on a > device. For regular mouse devices or keyboard devices, such a count will > never exceed 1, but counting button presses could help when button > presses with the s

Re: [PATCH libinput 1/4] evdev: Ignore key/button release events if key was never pressed

2014-08-03 Thread Peter Hutterer
On Mon, Jul 28, 2014 at 10:03:25AM -0700, Bill Spitzak wrote: > > > On 07/27/2014 11:48 PM, Ran Benita wrote: > >Hi Jonas, > > > >On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote: > >>The kernel may send a 'release' event without ever having sent a key > >>'pressed' event in case the k

Re: [PATCH libinput 1/4] evdev: Ignore key/button release events if key was never pressed

2014-08-03 Thread Peter Hutterer
On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote: > The kernel may send a 'release' event without ever having sent a key > 'pressed' event in case the key was pressed before libinput was > initiated. Ignore these events so that we always guarantee a release > event always comes after a p

Re: [PATCH libinput] test: Use only one test device for some udev and path tests

2014-08-03 Thread Peter Hutterer
On Sun, Jul 27, 2014 at 11:28:26PM +0200, Jonas Ådahl wrote: > Some tests in test/path.c and test/udev.c are not dependent on > device behaviour but rather managing of device lifetime etc. Run those > tests only once with only one device, resulting more or less the same > code coverage but shorter

Re: [PATCH libinput] evdev: Let dispatch instances set their own capabilities

2014-08-03 Thread Peter Hutterer
On Sun, Jul 27, 2014 at 11:28:25PM +0200, Jonas Ådahl wrote: > It's up to a evdev device backend to configure seat capabilities it > supports. Even though it may be possible for a touchpad to have extra > keys, there is currently no support for sending keyboard events from the > touchpad driver, an

[PATCH libinput] evdev: don't return a width/height if we faked the resolution

2014-08-03 Thread Peter Hutterer
Signed-off-by: Peter Hutterer --- src/evdev.c | 7 ++- src/evdev.h | 3 ++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index f980812..a125510 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -620,6 +620,7 @@ evdev_configure_device(struct evdev_device

Re: [PATCH] doc: Quell warnings about missing man3 directory before its been built

2014-08-03 Thread Peter Hutterer
sorry about the delay, was on holidays. On Fri, Jul 25, 2014 at 04:30:41PM +0300, Pekka Paalanen wrote: > On Mon, 21 Jul 2014 19:23:49 + > "Bryce W. Harrington" wrote: > > > The shell command for dist_man3_MANS gets invoked several times during > > the make process but before the man pages h

Re: Protocol (scanner) proposals

2014-08-03 Thread Auke Booij
On 30 July 2014 20:27, Pekka Paalanen wrote: > Actually no. Binding writers are expected to write their own code > generator for their language, like wayland-scanner is for C. You > are expected to not use the static inline generated C functions. > > All the static inline functions are not part of

Re: RFC : xdg_surface_present() look-and-feel and implementation

2014-08-03 Thread Pekka Paalanen
On Sun, 3 Aug 2014 09:23:06 -0400 "Jasper St. Pierre" wrote: > On Sun, Aug 3, 2014 at 8:43 AM, Pekka Paalanen wrote: > > > On Sun, 3 Aug 2014 07:30:25 -0400 > > "Jasper St. Pierre" wrote: > > > > > On Sun, Aug 3, 2014 at 6:27 AM, Pekka Paalanen > > wrote: > > > > > > > On Fri, 1 Aug 2014 17:0

Re: Protocol (scanner) proposals

2014-08-03 Thread Pekka Paalanen
On Sun, 3 Aug 2014 17:07:44 +0200 Auke Booij wrote: > >> Speaking of which, is there a reason the code samples don't show up > >> correctly in the online documentation? > > > > Which code samples exactly? > > http://wayland.freedesktop.org/docs/html/chap-Library.html > - wl_list > - wl_display_p

Re: Protocol (scanner) proposals

2014-08-03 Thread Auke Booij
On 3 August 2014 09:08, Pekka Paalanen wrote: > It was, hidden in a small paragraph in the documentation... I have to apologize, you are right. >> I guess that this is convention in C? > > [...] Thanks for your perfectly clear explanation, that does clarify it a lot. >> Speaking of which, is t

Re: RFC : xdg_surface_present() look-and-feel and implementation

2014-08-03 Thread Jasper St. Pierre
On Sun, Aug 3, 2014 at 8:43 AM, Pekka Paalanen wrote: > On Sun, 3 Aug 2014 07:30:25 -0400 > "Jasper St. Pierre" wrote: > > > On Sun, Aug 3, 2014 at 6:27 AM, Pekka Paalanen > wrote: > > > > > On Fri, 1 Aug 2014 17:08:14 +0200 > > > Manuel Bachmann wrote: > > > > > > > Hello everybody, > > > > >

Re: RFC : xdg_surface_present() look-and-feel and implementation

2014-08-03 Thread Pekka Paalanen
On Sun, 3 Aug 2014 07:30:25 -0400 "Jasper St. Pierre" wrote: > On Sun, Aug 3, 2014 at 6:27 AM, Pekka Paalanen wrote: > > > On Fri, 1 Aug 2014 17:08:14 +0200 > > Manuel Bachmann wrote: > > > > > Hello everybody, > > > > > > I just updated the repo today ( > > > > > https://github.com/Tarnyko/we

Re: RFC : xdg_surface_present() look-and-feel and implementation

2014-08-03 Thread Jasper St. Pierre
On Sun, Aug 3, 2014 at 6:27 AM, Pekka Paalanen wrote: > On Fri, 1 Aug 2014 17:08:14 +0200 > Manuel Bachmann wrote: > > > Hello everybody, > > > > I just updated the repo today ( > > > https://github.com/Tarnyko/weston-xdg_surface_present/commit/0aca29d4b6dbe10d5237aaf5f35f72d25db3ac30 > ). > > T

Re: RFC : xdg_surface_present() look-and-feel and implementation

2014-08-03 Thread Pekka Paalanen
On Fri, 1 Aug 2014 17:08:14 +0200 Manuel Bachmann wrote: > Hello everybody, > > I just updated the repo today ( > https://github.com/Tarnyko/weston-xdg_surface_present/commit/0aca29d4b6dbe10d5237aaf5f35f72d25db3ac30). > The "xdg_surface_present()" request not accepts a timestamp (uint32_t type)

Re: RFC : xdg_surface_present() look-and-feel and implementation

2014-08-03 Thread Pekka Paalanen
On Wed, 30 Jul 2014 00:00:37 +0200 Manuel Bachmann wrote: > Hi Jasper, Jason, > > "Agreed. Especially if you start an application, but it's slow to start, > and you have typed into the current window or have navigated away from it > since, you should get a popup instead of the window immediately

An status update of wayland-tracer - a wayland protocol dumper

2014-08-03 Thread Boyan Ding
Hi all, Previously I posted patches about wayland-tracer, a wire protocol dumper for wayland. It has turned into a self-contained project and a lot of development have taken place. Now, I'm happy to announce that XML parser and protocol analyzer has been added so it can produce a human-readable for

Re: [PATCH] xdg-shell: Align surface life-time rules with that of wl_shell

2014-08-03 Thread Pekka Paalanen
On Mon, 21 Jul 2014 13:23:23 -0700 Jason Ekstrand wrote: > I think the way it's handled in subsurfaces allows you to create a > subsurface from a surface, delete the surface, and then re-use the surface > as something else. If I recall correctly, weston allows a fair amount of > surface re-use r

Re: Protocol (scanner) proposals

2014-08-03 Thread Pekka Paalanen
On Sat, 2 Aug 2014 15:07:19 +0200 Auke Booij wrote: > On 30 July 2014 20:27, Pekka Paalanen wrote: > > Actually no. Binding writers are expected to write their own code > > generator for their language, like wayland-scanner is for C. You > > are expected to not use the static inline generated C