05 Jan, 2012

2 commits


02 Jan, 2012

2 commits


15 Dec, 2011

1 commit


30 Nov, 2011

2 commits


23 Nov, 2011

9 commits


01 Nov, 2011

1 commit

  • This reverts commit 0db3bfc72adf0c (""HID: multitouch: decide if hid-multitouch
    needs to handle mt devices").

    The generic detection of hid-mt devices has two major flaws, and was
    merged prematurely. Firstly, the hid-multitouch gets loaded even when
    the device is handled by a special device. Secondly, the patch only
    partially duplicates the device whitelist already present in hid-core,
    effectively rendering a number of devices non-functional.

    Reported-by: Sean Young
    Tested-by: Benjamin Tissoires
    Signed-off-by: Henrik Rydberg
    Signed-off-by: Jiri Kosina

    Henrik Rydberg
     

26 Sep, 2011

1 commit

  • Now that hid-generic ignores all win7 compatible multitouch devices, this patch
    allows hid-multitouch to catch them. The idea is to rely on the quirk
    HID_QUIRK_MULTITOUCH to drop the device if no ContactID is given.

    There is the need for a blacklist here as other devices may need a special
    driver (ntrig for instance).

    Signed-off-by: Benjamin Tissoires
    Signed-off-by: Jiri Kosina

    Benjamin Tissoires
     

20 Sep, 2011

1 commit

  • The IDEACOM 6650 multitouch chip, present in various all-in-one computers,
    uses the serial version of the HID multitouch protocol. No existing class
    supports this.

    In principle, the new MT_CLS_SERIAL should work for other
    serial panels as well, perhaps including some eGalax panels.

    Signed-off-by: Stephane Chatty
    Signed-off-by: Jiri Kosina

    Stephane Chatty
     

16 Aug, 2011

2 commits

  • This panel is also known as the Dell ST2220Tc.

    Signed-off-by: jeffbrown@android.com
    Reviewed-By: Benjamin Tissoires
    Signed-off-by: Jiri Kosina

    Jeff Brown
     
  • This change fixes two problems.

    First, it ensures that the hid-multitouch driver does not incorrectly
    map GenericDesktop usages that are intended for other applications,
    such as a Mouse.

    Second, it sets the appropriate input properties so that user-space
    can distinguish TouchScreen devices (INPUT_PROP_DIRECT) from
    TouchPad devices (INPUT_PROP_POINTER) and configure them accordingly.

    Signed-off-by: jeffbrown@android.com
    Acked-By: Benjamin Tissoires
    Signed-off-by: Jiri Kosina

    Jeff Brown
     

23 Jul, 2011

1 commit


21 Jul, 2011

1 commit


24 Jun, 2011

3 commits


13 Jun, 2011

1 commit

  • Since the inclusion of eGalax devices in 2.6.39, I've got some
    bug reports for 480d and other devices.
    The problem lies in the reports descriptors: eGalax supports both
    pen and fingers, and so the reports descriptors contained both.
    But hid-multitouch relies on them to detect the last item in each
    field to send the multitouch events. In 480d, the last item is not
    Y as it should but Pressure. That means that the fields are not
    aligned and X,Y are at 0,0 (the other touch coordinates of the report).

    With this patch, the detection is made only when the field ContactID
    has been detected inside the collection.

    There is still a problem with the detections of the range as stylus
    and fingers may not have the same min/max, but it's a start.

    Signed-off-by: Benjamin Tissoires
    Reviewed-by: Henrik Rydberg
    Signed-off-by: Jiri Kosina

    Benjamin Tissoires
     

07 Jun, 2011

1 commit


23 May, 2011

1 commit


20 May, 2011

6 commits


19 May, 2011

1 commit


18 May, 2011

1 commit


09 May, 2011

1 commit


22 Apr, 2011

2 commits