delta/libevdev.git/libevdev, branch libevdev-1.5.0

Fix typo in doc string

2016-04-20T01:31:38+00:00

Signed-off-by: Peter Hutterer

uinput: support the new UI_DEV_SETUP/UI_ABS_SETUP ioctls

2016-04-07T01:06:19+00:00

Available in kernel 4.5 and later (uinput version 5), these ioctls allow us to
set the absinfo correctly, i.e. including the resolution.

Signed-off-by: Peter Hutterer 
Reviewed-by: Benjamin Tissoires

uinput: split uinput device creation into a helper function

2016-04-07T01:05:00+00:00

No functional changes. This is prep work for supporting the new
UIDEV_DEV_SETUP ioctl.

Signed-off-by: Peter Hutterer 
Reviewed-by: Benjamin Tissoires

uinput: drop an unused argument

2016-04-07T01:04:59+00:00

Signed-off-by: Peter Hutterer 
Reviewed-by: Benjamin Tissoires

Add parsing linux/input-event-codes.h, update to kernel v4.5

2016-03-30T05:45:58+00:00

The kernel has split most of the event codes out to a new header but the FF_
bits are missing from that header. Until this is fixed upstream, change the
event code parsing so it can take two files (using cat and stdin) so we can
update the kernel headers again.

Signed-off-by: Peter Hutterer 
Reviewed-by: Benjamin Tissoires

uinput: fix race condition in uinput syspath check

2016-01-03T21:39:24+00:00

In theory, the device could change between stat() call and open(), resulting
in us opening the new device. Change to open() first, then fstat() on the fd.

Signed-off-by: Peter Hutterer 
Reviewed-by: David Herrmann

Document that the fd should be drained before libevdev_set_fd

2015-12-17T00:46:31+00:00

This is the caller's responsibility, for two reasons:
* we don't know if O_NONBLOCK is set, so draining the fd isn't a simple matter
  of read() until EAGAIN. A select() + read() could work around this of
  course.
* for stateless information, keys and relative data, it is not a problem when
  there are events waiting on the fd already, they are processed correctly,
  albeit with a delay.

So punt this decision to the caller, they openend the fd, they know if they
care about delayed events, they can drain the fd before handing it to us.

Signed-off-by: Peter Hutterer 
Acked-by: Benjamin Tissoires 
Acked-by: David Herrmann

Fix invalid absinfo range values reported by certain mtk soc

2015-08-24T06:26:00+00:00

This change will only affect certain touch screens, for which the driver
integration code does not provide meaningful values for the allowed range
of ABS_MT_TRACKING_IDs. The reported range [0, 0] will be overwritten with
[-1, 0xFFFF]

Signed-off-by: Andreas Pokorny 

[Changed from INT_MAX to 0xFFFF to match the kernel, add device name to log
message]

Signed-off-by: Peter Hutterer

Note that libevdev_free() does not close the fd

2015-06-29T02:23:34+00:00

Signed-off-by: Peter Hutterer

Accept LIBEVDEV_READ_FLAG_BLOCKING as valid flag

2015-04-08T02:48:43+00:00

https://bugs.freedesktop.org/show_bug.cgi?id=89798

Signed-off-by: Peter Hutterer 
Reviewed-by: Benjamin Tissoires