From: Peter Hutterer Date: Tue, 22 Oct 2019 02:04:04 +0000 (+1000) Subject: doc/user: reword one of the FAQ entries to no tmake it read outdated X-Git-Tag: 1.14.901~68 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=17ec6ac79d48ad3f1d7290e4698987f860e7cf8f;p=platform%2Fupstream%2Flibinput.git doc/user: reword one of the FAQ entries to no tmake it read outdated Signed-off-by: Peter Hutterer --- diff --git a/doc/user/faqs.rst b/doc/user/faqs.rst index a6f5dee2..4de7a3fc 100644 --- a/doc/user/faqs.rst +++ b/doc/user/faqs.rst @@ -312,14 +312,13 @@ direct connection. As a technical analogy, the question is similar to "is glibc required for HTTP", or (stretching the analogy a bit further) "Is a pen required to write English". No, it isn't. -You can use libinput without a Wayland compositor, you can -write a Wayland compositor without libinput. Until 2018 the most common use -of libinput is with the X.Org X server through the xf86-input-libinput -driver. As Wayland compositors become more commonplace they will eventually -overtake X. +You can use libinput without a Wayland compositor, you can write a Wayland +compositor without libinput. On most major distributions, libinput is the +standard input stack used with the X.Org X server through the +xf86-input-libinput driver. So why "for your use-case - probably"? All general-purpose Wayland -compositors use libinput for their input stack. Wayland compositors that +compositors use libinput for their input stack. Wayland compositors that are more specialized (e.g. in-vehicle infotainment or IVI) can handle input devices directly but the compositor you want to use on your desktop needs an input stack that is more complex. And right now,