You are not logged in.

#1 2012-10-08 07:04:54

adlerweb
Member
From: Germany
Registered: 2012-10-02
Posts: 4
Website

Kernel 3.5.4/XOrg 1.12.4/Touchscreen - Tap to Click?

Hello,

im trying to install a system equipped with a USB-Touchscreen ("0dfc:0003 GeneralTouch Technology Co., Ltd") - Kernel and XOrg seem to recognize the device correctly:

dmesg | grep -i touch
[    1.637399] input: General Touch Co. Ltd.  GeneralTouch USB Touchscreen as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0/input/input1
[    1.637497] hid-multitouch 0003:0DFC:0003.0002: input,hidraw1: USB HID v1.10 Mouse [General Touch Co. Ltd.  GeneralTouch USB Touchscreen] on usb-0000:00:1d.0-2/input0
[    14.548] (II) config/udev: Adding input device General Touch Co. Ltd.  GeneralTouch USB Touchscreen (/dev/input/event1)
[    14.548] (**) General Touch Co. Ltd.  GeneralTouch USB Touchscreen: Applying InputClass "evdev touchscreen"
[    14.548] (II) Using input driver 'evdev' for 'General Touch Co. Ltd.  GeneralTouch USB Touchscreen'
[    14.548] (**) General Touch Co. Ltd.  GeneralTouch USB Touchscreen: always reports core events
[    14.548] (**) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: Device: "/dev/input/event1"
[    14.548] (--) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: Vendor 0xdfc Product 0x3
[    14.548] (--) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: Found absolute axes
[    14.548] (--) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: Found absolute multitouch axes
[    14.548] (--) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: Found x and y absolute axes
[    14.548] (--) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: Found absolute touchscreen
[    14.548] (II) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: Configuring as touchscreen
[    14.548] (**) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: YAxisMapping: buttons 4 and 5
[    14.548] (**) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    14.548] (II) XINPUT: Adding extended input device "General Touch Co. Ltd.  GeneralTouch USB Touchscreen" (type: TOUCHSCREEN, id 10)
[    14.548] (II) evdev: General Touch Co. Ltd.  GeneralTouch USB Touchscreen: initialized for absolute axes.
[    14.549] (**) General Touch Co. Ltd.  GeneralTouch USB Touchscreen: (accel) keeping acceleration scheme 1
[    14.549] (**) General Touch Co. Ltd.  GeneralTouch USB Touchscreen: (accel) acceleration profile 0
[    14.549] (**) General Touch Co. Ltd.  GeneralTouch USB Touchscreen: (accel) acceleration factor: 2.000
[    14.549] (**) General Touch Co. Ltd.  GeneralTouch USB Touchscreen: (accel) acceleration threshold: 4
[    14.549] (II) config/udev: Adding input device General Touch Co. Ltd.  GeneralTouch USB Touchscreen (/dev/input/mouse1)
(...)
[    14.549] (II) No input driver specified, ignoring this device.
[    14.549] (II) This device may have been added with another device file.

In X i can move the pointer using the touchscreen, however i can not initiate a left-click using the usual "tap"-method. I played a bit with Option "TapTimer" and "MoveLimit" in xorg.conf but i could not see any difference. Is there another setting required to enable tap-click? According to a college it did work with some older knoppix but i haven't found the correct CD yet to compare drivers

Offline

#2 2012-11-08 07:24:57

adlerweb
Member
From: Germany
Registered: 2012-10-02
Posts: 4
Website

Re: Kernel 3.5.4/XOrg 1.12.4/Touchscreen - Tap to Click?

A bit of followup: I tried several patches from https://bugs.launchpad.net/ubuntu/+sour … ug/1015183 so far, but that was the wrong direction. Using evtest i got the following output:

Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0xdfc product 0x3 version 0x110
Input device name: "General Touch Co. Ltd.  GeneralTouch USB Touchscreen"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max    32767
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max    32767
    Event code 47 (ABS_MT_SLOT)
      Value      0
      Min        0
      Max        1
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max    32767
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max    32767
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max    65535
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1352199345.067036, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 0
Event: time 1352199345.067039, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 9648
Event: time 1352199345.067040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 15436
Event: time 1352199345.067045, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1352199345.067047, type 3 (EV_ABS), code 0 (ABS_X), value 9648
Event: time 1352199345.067049, type 3 (EV_ABS), code 1 (ABS_Y), value 15436
Event: time 1352199345.067050, -------------- SYN_REPORT ------------

As you can see there is no BTN_TOUCH->0 for release on the device so it is not related to XOrg/evdev but to kernel's hid-multitouch. I added MT_QUIRK_NOT_SEEN_MEANS_UP for the device as a workarround. As far as i could see there are several devices with different features but the same USBID so i guess the driver cannot automatically set the correct options.

Offline

Board footer

Powered by FluxBB