libinput 1.12 is now available. Since the rc3 a few more notable changes
went in:
The tablet axis smoothing previously caused some axes to change value even
though the "axis has changed" bit wasn't set in the event. This is fixed
now.
The delta for tablet axis events is now always 0 for tip
I no longer seem to be able to find the wayland-wall repository on
GitHub. Just wondering what has happened to it?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
> -Original Message-
> From: wayland-devel On Behalf
> Of Hosokawa, Kenji (ADITG/ESB)
> Sent: Dienstag, 28. August 2018 14:32
> To: wayland-devel@lists.freedesktop.org
> Subject: egl image creation in case of atomic
>
> Hi,
>
> When eglSwapInterval is 0, clients may send buffers
On Mon, 10 Sep 2018 11:16:03 +0200
Dirk Eibach wrote:
> I did a git bisect and found the commit "244244d1 (refs/bisect/bad)
> compositor-drm: Use GBM modifier API" introduced the problem.
Hi,
ok. I wonder if there is something wrong with Mesa/GBM/Nouveau, since
it is generic code in Weston and
On Mon, 10 Sep 2018 10:12:18 +0200
Dirk Eibach wrote:
> Perhaps I should add, that with rolling back to weston 4.0.0.
> everything works fine. So nouveau support must have been broken
> somewhere inbetween.
Hi,
right, so it's a regression. Weston does not have code specific to
Nouveau, but it
I did a git bisect and found the commit "244244d1 (refs/bisect/bad)
compositor-drm: Use GBM modifier API" introduced the problem.
Am Mo., 10. Sep. 2018 um 10:12 Uhr schrieb Dirk Eibach
:
>
> Perhaps I should add, that with rolling back to weston 4.0.0.
> everything works fine. So nouveau support
On Fri, Sep 07, 2018 at 04:02:24PM +0200, Gary Bisson wrote:
> Hi Alexandros, All,
>
> On Tue, Aug 08, 2017 at 05:24:58PM +0300, Alexandros Frantzis wrote:
> > This protocol specifies a set of interfaces used to control the alpha
> > compositing and blending of surface contents.
> >
> > It's
Perhaps I should add, that with rolling back to weston 4.0.0.
everything works fine. So nouveau support must have been broken
somewhere inbetween.
Am Mo., 10. Sep. 2018 um 08:59 Uhr schrieb Dirk Eibach
:
>
> > Looks like some drm issue. Just wondering if you can use KMS APIs directly
> > without
> Looks like some drm issue. Just wondering if you can use KMS APIs directly
> without seeing this issue? So for example, will kmscube draw something on the
> screen (https://github.com/robclark/kmscube)? BTW, noticed that you are using
> /dev/dri/card1 in your logs. What's at card0? Note that
