Re: [PATCH weston 1/3] configure: replace HAVE_LIBDRM with BUILD_DRM_COMPOSITOR

On 4/6/17 2:09 PM, Pekka Paalanen wrote: From: Pekka Paalanen HAVE_LIBDRM was used as a condition for the launcher infrastructure to call libdrm.so functions. It was set by an independent test for libdrm, which would silently continue if libdrm was not found. It

Re: [PATCH weston v2] desktop-shell: Position maximized surfaces on the correct output.

On 4/4/17 7:49 PM, Emmanuel Gil Peyrot wrote: During a maximize event, a surface was previously always put back to the primary output after one frame on the correct output, while keeping its size. This was caused by the shell surface’s last_{width,height} not being reset when it was either

Re: [PATCH weston 0/3] Make libdrm a hard build-time dependency

On Thu, 6 Apr 2017 15:09:26 +0300 Pekka Paalanen wrote: > From: Pekka Paalanen > > Hi, > > I wrote this for Daniel's atomic modesetting series which adds a pixel-formats > database into libweston core. That database cannot exist without

Re: [PATCH weston 2/3] build: do not link libdrm without DRM backend

On 4/6/17 2:09 PM, Pekka Paalanen wrote: From: Pekka Paalanen The pkg-config test for LIBDRM is independent of whether the DRM backend is enabled or not. Therefore it is possible to have libdrm available and found, even though it is not needed. Do not link

Re: [PATCH weston v10 01/61] Clip co-ordinates in surface->buffer translation

On Tue, 4 Apr 2017 17:54:19 +0100 Daniel Stone wrote: > Since performing the surface -> buffer translation may introduce > rounding error taking our desired co-ordinates out of bounds, introduce > a hard clip to the bounds specified by the client's viewport. > >

Re: [PATCH weston 3/3] build: make libdrm a hard build-time dependency

On 4/6/17 2:09 PM, Pekka Paalanen wrote: From: Pekka Paalanen Libdrm provides headers that are useful even without libdrm.so itself, particularly drm_fourcc.h. Therefore promote libdrm as a hard build-time dependency of libweston core so that we can always rely

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Wed, Apr 05, 2017 at 11:12:47AM +0100, Daniel Stone wrote: > Hi Steven, > > On 5 April 2017 at 11:04, Steven Newbury wrote: > > On Wed, 2017-04-05 at 10:53 +0100, Daniel Stone wrote: > >> DGA's DirectMouse doesn't change the latency. It doesn't give the > >> client a

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Wed, Apr 05, 2017 at 11:15:05AM +0100, Steven Newbury wrote: > On Wed, 2017-04-05 at 11:57 +0200, Bastien Nocera wrote: > > On Wed, 2017-04-05 at 10:42 +0100, Steven Newbury wrote: > > > > > > > > > > There's a reason the mouse support from the X DGA Extension out- > > > survived the "direct

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Wed, 05 Apr 2017 at 17:45:51 -0700, Roderick Colenbrander wrote: > I wonder how Valve is doing this on Steam as with the Steam > Controller, which I haven't used. I think they are allowing it to > replace keyboard and mouse kind of. Curious how they are solving this. > My guess is they are

[PATCH weston 1/3] configure: replace HAVE_LIBDRM with BUILD_DRM_COMPOSITOR

From: Pekka Paalanen HAVE_LIBDRM was used as a condition for the launcher infrastructure to call libdrm.so functions. It was set by an independent test for libdrm, which would silently continue if libdrm was not found. It was assumed that if you enabled a feature

[PATCH weston 0/3] Make libdrm a hard build-time dependency

From: Pekka Paalanen Hi, I wrote this for Daniel's atomic modesetting series which adds a pixel-formats database into libweston core. That database cannot exist without drm_foucc.h, and putting it into the modules would probably bring in another binary copy of it

[PATCH weston 2/3] build: do not link libdrm without DRM backend

From: Pekka Paalanen The pkg-config test for LIBDRM is independent of whether the DRM backend is enabled or not. Therefore it is possible to have libdrm available and found, even though it is not needed. Do not link libdrm.so into the launchers unless it is

[PATCH weston 3/3] build: make libdrm a hard build-time dependency

From: Pekka Paalanen Libdrm provides headers that are useful even without libdrm.so itself, particularly drm_fourcc.h. Therefore promote libdrm as a hard build-time dependency of libweston core so that we can always rely on libdrm headers. This does not affect

[RFC v2 wayland-protocols] inputfd - direct input access protocol

For the initial patchset, see https://lists.freedesktop.org/archives/wayland-devel/2017-March/033626.html For a high-level description, see http://who-t.blogspot.com.au/2017/04/inputfd-protocol-for-direct-access-to.html This is a relatively unexciting update, the notable bits are: * instead of

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Wed, Apr 05, 2017 at 04:51:51PM -0700, Roderick Colenbrander wrote: > On Mon, Apr 3, 2017 at 9:08 PM, Peter Hutterer > wrote: > > > > On Mon, Apr 03, 2017 at 04:08:21PM -0700, Roderick Colenbrander wrote: > > > Hi Peter, > > > > > > Thanks for sharing this proposal.