delta/libevdev.git, branch libevdev-0.9.1

libevdev 0.9.1

2014-01-29T05:09:05+00:00

libevdev 1.0-rc1

Signed-off-by: Peter Hutterer

test: remove NULL test for SW_MAX, 3.13 defines SW_MUTE_DEVICE

2014-01-29T05:08:12+00:00

Signed-off-by: Peter Hutterer

Bump soname

2014-01-29T05:02:45+00:00

Bump once to the stable interface we have now. This isn't really required as
we're compatible with everything but functions deprecated with 0.4 but we
might as well do it now to force a rebuild of everyone. Should've done that
for 0.6 when we actually dropped the function, but ...

Now that we have proper library versioning we shouldn't need any
backwards-incompatible soname bumps for a while.

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

Add ld version-script

2014-01-29T05:02:40+00:00

Explicit symbol versioning allows us to provide multiple versions of
incompatible API changes. It is a very common practice in GNU world and
avoids the problems occuring if distributions try to ship multiple version
of a single DSO.

Background information available at:
  http://people.redhat.com/drepper/dsohowto.pdf

To see the symbol-versions, use objdump:
  objdump -T libevdev/.libs/libevdev.so.1.0.0
This can also be used to verify that all symbols are correctly
exported (typos in linker-scripts are silently ignored by ld).

Signed-off-by: David Herrmann 

Updated for evdev 0.6's API.

Signed-off-by: Peter Hutterer

include: update linux/input.h for kernel 3.13

2014-01-21T23:15:14+00:00

Signed-off-by: Peter Hutterer

Warn about a SYN_DROPPED right after finishing a sync

2014-01-21T23:15:14+00:00

If the first event after a completed device sync is a SYN_DROPPED, warn the
user that they're not fast enough handling this device.

The test for this is rather complicated since we can't write SYN_DROPPED
through uinput so we have to juggle the device fd and a pipe and switch
between the two at the right time (taking into account that libevdev will read
events from the fd whenever it can).

Signed-off-by: Peter Hutterer

test: abort on unexpected log messages

2014-01-21T23:14:40+00:00

Add two log functions, one that aborts on a received message. We know when we
expect to receive an error, so anytime this happens unexpectedly should
terminate the test.

And for those tests do issue a log message, let them ignore it and don't
print anything.

Signed-off-by: Peter Hutterer

Count the number of events needed for a full sync

2014-01-21T22:28:41+00:00

Make sure we have a queue that is at least large enough to do a full sync
after a SYN_DROPPED, plus store a few extra events in case some came in after
the sync.

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

test: fix typo

2014-01-17T00:54:58+00:00

Signed-off-by: Peter Hutterer

test: rename a test to match what it's testing better

2014-01-17T00:54:58+00:00

Signed-off-by: Peter Hutterer