mtdev.git/include, branch v1.1.1

Add support for ABS_MT_DISTANCE

2010-12-22T17:35:53+00:00

In the upcoming 2.6.38 kernel, support for hovering is introduced. Add the ABS_MT_DISTANCE to the extended set of handled ABS_MT events. The change is binary compatible with existing libraries. Signed-off-by: Henrik Rydberg

Introduce a stable ABI

2010-12-22T17:29:00+00:00

The current mtdev is not ABI stable, and the upcoming additions to the kernel api will break ABI. This patch starts the process of keeping binary compatibility with old programs, by moving the abi-specific parts under a special flag, MTDEV_NO_LEGACY_API, and makes sure the internal parts compiles with MTDEV_NO_LEGACY_API set. This way, older programs will still work, old programs will still compile, and new programs will be able to use the additions. Signed-off-by: Henrik Rydberg

Allow use in c++ applications

2010-12-22T11:31:28+00:00

Reported-by: Armando Visconti Signed-off-by: Henrik Rydberg

Complete mtdev property mapping

2010-09-07T14:08:44+00:00

Add the missing property values to the mapgen output, and insert the result in the mtdev mapping header file. Signed-off-by: Henrik Rydberg

The forthcoming 2.6.36 kernel does not define the MT_SLOT_ABS_EVENTS

2010-07-21T08:08:40+00:00

list, so make sure it is always defined in mtdev.h Signed-off-by: Henrik Rydberg

Apply new package title to all files

2010-06-22T09:55:04+00:00

This patch changes the package description title in all relevant files, and touches up the README. All systems go. Signed-off-by: Henrik Rydberg

Unused slot is denoted by MT_TRACKING_ID == -1

2010-06-21T22:44:40+00:00

The current MT slot protocol allows any tracking id outside the range specified by the device to denote an unused slot. This is difficult to handle in userspace, since the valid range is unknown. This patch tightens the definition of a valid tracking id to always lie in the range [0, MT_ID_MAX], and uses the value -1 to denote an unused slot. Acked-by: Chase Douglas Signed-off-by: Henrik Rydberg

Restructure mtdev api

2010-06-19T12:01:40+00:00

Split the api into plumbing and porcelain layers and move the plumbing part to its own optional header file. The main usecase is to fetch events from the device, route them through the converter and extract the processed events. To simplify the API, replace the intermediate mtdev_pull() function by the higher-level mtdev_get(). This function does all the required steps, and has the same semantics as read(). Signed-off-by: Henrik Rydberg

Correct minor semantic documentation error in mtdev_close()

2010-06-18T09:24:24+00:00

Signed-off-by: Henrik Rydberg

janitor: fix spelling error

2010-06-17T23:41:14+00:00

Signed-off-by: Henrik Rydberg