delta/libevdev.git/libevdev/libevdev-int.h, branch libevdev-1.2

Drop hardcoded MAX_SLOTS in favour of pre-allocated memory

2014-04-03T03:30:49+00:00

We can't allocate in sync_mt_state since it may be called in the signal
handler. So pre-allocate based on the device's number of slots, store that in
the libevdev struct and use it for the sync process.

This fixes a remaining bug with the handling of ABS_MT_TRACKING_ID. If a
device had > MAX_SLOTS and a slot above that limit would start or stop during
a SYN_DROPPED event, the slot would not be synced, and a subsequent touch in
that slot may double-terminate or double-open a touchpoint in the client.
For the effects of that see

commit 41334b5b40cd5456f5f584b55d8888aaafa1f26e
Author: Peter Hutterer 
Date:   Thu Mar 6 11:54:00 2014 +1000

    If the tracking ID changes during SYN_DROPPED, terminate the touch first

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

Move some functions/macros between libevdev-int.h and libevdev-util.h

2014-03-06T04:30:03+00:00

This allows libevdev-util.h to be used by tests, it no longer relies on
libevdev internal structs.

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

Increase MAX_SLOTS to 60

2014-03-05T23:21:02+00:00

As seen on 3M devices, which seems to be the maximum seen so far. Some Stantum
devices report 255 touches but are only capable of 10, so the are not affected
by our limits.

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

Dynamically allocate the slot values

2014-03-05T23:21:02+00:00

Instead of relying on a static MAX_SLOTS array, allocated it based on the
number of slots we have on the device. The previous checks for MAX_SLOTS were
incomplete, causing out-of-bound reads.

Signed-off-by: Peter Hutterer

Allow -1 as valid fd in libevdev_change_fd

2013-10-14T04:20:55+00:00

Add a new flag for "initialized" and separate that from the fd logic. This way,
we can call libevdev_change_fd(dev, -1) to signal that the current fd should be
dropped.

Otherwise libevdev can't be told to release the fd and always keeps a reference
to it.

Signed-off-by: Peter Hutterer

Uppercase #define LIBEVDEV_INT_H

2013-10-08T04:22:27+00:00

over-eager search/replace

Signed-off-by: Peter Hutterer

Name-space the read flags better

2013-09-11T02:10:15+00:00

Rename from LIBEVDEV_READ_foo to LIBEVDEV_READ_FLAG_foo to differentiate
better from LIBEVDEV_READ_STATUS_foo.

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

Revamp the API once again

2013-09-10T01:25:09+00:00

Another look at the current API showed some inconsistencies, rectified
in this commit:

libevdev_kernel_*: modify the underlying kernel device
libevdev_event_type_*: something with an event type
libevdev_event_code_*: something with an event code
libevdev_event_*: struct input_event-related functions (i.e. not device-related)
libevdev_property_*: something with a property
libevdev_*: anything applying to a device

Hopefully that's the last API change. Current symbols deprecated and aliased.

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

Drop per-device logging function, use per-library one instead

2013-09-03T06:58:54+00:00

There's no need to have separate logging function for each device created.
More likely, libevdev will be hooked up once into the logging system and
expected to deal with it.

Plus, this allows us to log from the uinput code where we don't
have the context anyway.

Requires a rename to libevdev_set_log_function to avoid ABI breaks, and
while we're breaking the ABI make the logging function more sophisticated
to log line, number, etc.

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

Use ENOMEM instead of ENOSPC

2013-08-31T02:27:23+00:00

From errno(3):
   ENOMEM          Not enough space (POSIX.1)
   ENOSPC          No space left on device (POSIX.1)

when we run out memory the reason is a failed malloc, for which ENOMEM
seems more appropriate.

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