On Fri, May 29, 2015 at 12:32:44PM +0200, Andreas Pokorny wrote:
Hi,
On Fri, May 29, 2015 at 2:07 AM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Thu, May 28, 2015 at 02:47:35PM +0200, Andreas Pokorny wrote:
There are touch screens that do not provide 'BTN_TOUCH' and hence no
Hi,
On Fri, May 29, 2015 at 2:07 AM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Thu, May 28, 2015 at 02:47:35PM +0200, Andreas Pokorny wrote:
There are touch screens that do not provide 'BTN_TOUCH' and hence no
'EV_KEY'. Previously those would not get any properties assigned and
On Thu, May 28, 2015 at 02:47:35PM +0200, Andreas Pokorny wrote:
There are touch screens that do not provide 'BTN_TOUCH' and hence no
'EV_KEY'. Previously those would not get any properties assigned and
note: I consider this a kernel bug. From the kernel's documentation:
* BTN_TOUCH:
There are touch screens that do not provide 'BTN_TOUCH' and hence no
'EV_KEY'. Previously those would not get any properties assigned and
libinput would not treat those as input devices. Additionally there
is an 'IS_DIRECT' property exposed by most touch screens, that would
otherwise be detected
Patchset imported to github.
Pull request:
https://github.com/systemd-devs/systemd/compare/master...systemd-mailing-devs:1432817255-9423-1-git-send-email-andreas.pokorny%40canonical.com
--
Generated by https://github.com/haraldh/mail2git
___
