Find a file
Peter Hutterer 31e349fb5b data: switch alps touchpad matching to the bus/vid/pid matching
PSMOUSE_ALPS is 0x8

https://gitlab.freedesktop.org/libinput/libinput/issues/30

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2018-06-18 10:34:25 +10:00
data data: switch alps touchpad matching to the bus/vid/pid matching 2018-06-18 10:34:25 +10:00
doc Implement a quirks system to replace the udev property parsing 2018-06-08 14:33:35 +10:00
include/linux Update struct input_event 2018-05-03 10:03:28 +10:00
src quirks: add MatchVersion in addition to VID/PID 2018-06-18 10:34:16 +10:00
test quirks: add MatchVersion in addition to VID/PID 2018-06-18 10:34:16 +10:00
tools tools: measure touchpad-pressure: prevent division by zero 2018-06-18 08:52:21 +10:00
udev udev: remove duplicate Chromebook Falco hwdb entry 2018-06-08 13:47:33 +10:00
.dir-locals.el indentation: add .dir-locals.el for emacs 2018-02-26 18:44:00 +10:00
.gitignore gitignore: ignore gnuplot files 2018-05-10 16:25:40 +10:00
.vimdir Add .vimdir for libinput-specific settings 2015-05-25 09:17:29 +10:00
circle.yml circleci: drop the separate libsolv update 2018-06-13 15:22:24 +10:00
CODING_STYLE.md Move CODING_STYLE to markdown 2018-06-14 08:45:56 +10:00
COPYING COPYING: change a cgit to a gitlab URL 2018-06-06 11:17:54 +10:00
meson.build meson.build: always build some tests 2018-06-14 15:07:15 +10:00
meson_options.txt meson: add a 'coverity' option to fix the build 2018-05-16 14:23:12 +10:00
README.md doc: Fix URLs for GitLab, HTTPS 2018-06-05 11:07:16 +01:00

libinput

libinput is a library that provides a full input stack for display servers and other applications that need to handle input devices provided by the kernel.

libinput provides device detection, event handling and abstraction so minimize the amount of custom input code the user of libinput need to provide the common set of functionality that users expect. Input event processing includes scaling touch coordinates, generating relative pointer events from touchpads, pointer acceleration, etc.

Architecture

libinput is not used directly by applications. Think of it more as a device driver than an application library. It is used by the xf86-input-libinput X.Org driver or Wayland compositors. The typical software stack for a system running Wayland is:

@dotfile libinput-stack-wayland.gv

The Wayland compositor may be Weston, mutter, KWin, etc. Note that Wayland encourages the use of toolkits, so the Wayland client (your application) does not usually talk directly to the compositor but rather employs a toolkit (e.g. GTK) to do so. The Wayland client does not know whether libinput is in use.

The simplified software stack for a system running X.Org is:

@dotfile libinput-stack-xorg.gv

libinput is not employed directly by the X server but by the xf86-input-libinput driver instead. That driver is loaded by the server on demand, depending on the xorg.conf.d configuration snippets. The X client does not know whether libinput is in use.

Source code

The source code of libinput can be found at: https://gitlab.freedesktop.org/libinput/libinput

For a list of current and past releases visit: https://www.freedesktop.org/wiki/Software/libinput/

Build instructions: https://wayland.freedesktop.org/libinput/doc/latest/building_libinput.html

Reporting Bugs

Bugs can be filed on freedesktop.org GitLab: https://gitlab.freedesktop.org/libinput/libinput/issues/

Where possible, please provide the libinput record output of the input device and/or the event sequence in question.

See @ref reporting_bugs for more info.

Documentation

Examples of how to use libinput are the debugging tools in the libinput repository. Developers are encouraged to look at those tools for a real-world (yet simple) example on how to use libinput.

License

libinput is licensed under the MIT license.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: [...]

See the COPYING file for the full license information.