libinput 1.12.3 is now available
One new feature which may be a bit controversial to introduce into a stable
release: the ability to disable any event code through a quirks entry.
There are quite a few devices that require event codes to be disabled to
make them work correctly (e.g. the Logitech
Signed-off-by: Alexandros Frantzis
---
Changes in patch v5:
- Further clarified the per-commit nature of buffer_release.
- Used the wp_linux_dmabuf name to refer to all versions of that protocol.
- Fixed wl_buffer.attach typo.
- Clarified when an INVALID_FENCE error is raised.
- Improve
On Mon, Nov 05, 2018 at 06:07:56PM +, Simon Ser wrote:
> On Monday, November 5, 2018 10:50 AM, Alexandros Frantzis
> wrote:
> > On Sat, Nov 03, 2018 at 02:44:53PM +, Simon Ser wrote:
> >
> > Hi Simon,
> >
> > > > > > + Explicit synchronization is guaranteed to be supported only
> >
Hi Alexandros,
On Tue, 8 Aug 2017 at 15:25, Alexandros Frantzis
wrote:
> This protocol specifies a set of interfaces used to control the alpha
> compositing and blending of surface contents.
>
> It's based on the Chromium Wayland protocol of the same name ([1]),
> with a few changes made to the b
On Mon, 5 Nov 2018 13:52:24 -0600
Derek Foreman wrote:
> On 11/5/18 7:43 AM, Simon Ser wrote:
> > On Monday, November 5, 2018 11:07 AM, Pekka Paalanen
> > wrote:
> >> How about writing what Derek said: that the old damage request may be
> >> unoptimal rather than deprecated.
> >>
> >> I don't
