RFC libinput high-resolution wheel scrolling

2019-01-24 Thread Peter Hutterer
I'm sending this here to get some more exposure. The kernel will get high-resolution scroll wheels with the 5.0 release. The details are in the blog post linked below [1], but the short summary is that we now get REL_WHEEL for full clicks and REL_WHEEL_HI_RES for fine-grained events. The units REL

Re: 2019 X.Org Foundation Membership deadline for voting in the election

2019-01-24 Thread Wentland, Harry
There have been a bunch of sign-ups without names which makes for a confusing list on https://members.x.org/members If you get chance please update your name and affiliation in your profile (username > Your Profile). Harry On 2019-01-24 9:42 a.m., Wentland, Harry wrote: > Note that you will ha

Re: 2019 X.Org Foundation Membership deadline for voting in the election

2019-01-24 Thread Wentland, Harry
Note that you will have to re-register in the new system. Your previous credentials won't work. Harry On 2019-01-24 8:42 a.m., Wentland, Harry wrote: > The 2019 X.Org Foundation elections are rapidly approaching. We will be > forwarding the nominating process to the membership shortly. Please f

2019 X.Org Foundation Membership deadline for voting in the election

2019-01-24 Thread Wentland, Harry
The 2019 X.Org Foundation elections are rapidly approaching. We will be forwarding the nominating process to the membership shortly. Please find the election schedule below. Please note that only current members can vote in the upcoming election, and that the deadline for new memberships or ren

Re: Few patches from Ravenports for DragonFly BSD support

2019-01-24 Thread Leonid Bobrov
On Thu, Jan 24, 2019 at 12:53:28PM +0200, Pekka Paalanen wrote: > Hi, > > you need to split this into logical patches, each patch doing one > logical thing. It is not the same as one patch per file. Each patch > needs to have a commit message explaining why the patch was written, > and so on. Plea

Re: [PATCH 3/3] client: Change the way fd's are buffered and flushed

2019-01-24 Thread Pekka Paalanen
On Fri, 7 Sep 2018 18:14:05 -0700 Lloyd Pique wrote: > To allow more fd's to be buffered, remove the use of the MAX_FDS_OUT > when deciding if there is room in fds_out. A full set of 1024 can now > be enqueued for output. > > The consequence is that the flush code must be able to handle sending

Re: Should Weston wait for client buffers to finish rendering?

2019-01-24 Thread Pekka Paalanen
On Thu, 24 Jan 2019 11:47:30 +0200 Pekka Paalanen wrote: > On Wed, 23 Jan 2019 18:43:52 + > "Singh, Satyeshwar" wrote: > > > Imagine a benchmark case where the client renders for example 800 > > frames and attaches their buffer ids to a surface, the compositor > > uses the last one that cam

Re: Few patches from Ravenports for DragonFly BSD support

2019-01-24 Thread Pekka Paalanen
On Sun, 20 Jan 2019 07:59:26 +0200 Leonid Bobrov wrote: > From 660f1a59a0ff09f1c21e97087b713d6751e3de10 Mon Sep 17 00:00:00 2001 > From: Leonid Bobrov > Date: Sun, 20 Jan 2019 07:33:46 +0200 > Subject: [PATCH] Few patches from Ravenports for DragonFly BSD support > > Taken from > https://githu

Re: Should Weston wait for client buffers to finish rendering?

2019-01-24 Thread Pekka Paalanen
On Wed, 23 Jan 2019 18:43:52 + "Singh, Satyeshwar" wrote: > Hey guys, > As you know, Weston doesn't wait for client buffers to finish > rendering. That is typically left as an exercise for the kernel mode > graphics driver. I am wondering if anyone knows why this policy > decision was made? M

Re: Should Weston wait for client buffers to finish rendering?

2019-01-24 Thread Pekka Paalanen
On Wed, 23 Jan 2019 19:28:11 + "Ucan, Emre (ADITG/ESB)" wrote: > Hello Satyeshwar, > > nice to hear from you again (: > > short answer to your question: there is already implementation which is doing > what you are asking: > https://gitlab.freedesktop.org/wayland/weston/merge_requests/32