| 2010-08-27 19:28:40 |
Philipp Merkel |
bug |
|
|
added bug |
| 2010-08-27 19:28:40 |
Philipp Merkel |
attachment added |
|
Patch for drivers/hid/usbhid/hid-quirks.c removing the quirk for this screen. https://bugs.launchpad.net/bugs/625511/+attachment/1523713/+files/remove-egalax-quirk_hid-quirks.c.patch |
|
| 2010-08-27 22:56:29 |
Brian Murray |
bug |
|
|
added subscriber Jeremy Foshee |
| 2010-08-27 22:56:35 |
Brian Murray |
tags |
|
patch |
|
| 2010-08-29 09:39:56 |
Philipp Merkel |
attachment added |
|
Patch for drivers/hid/hid-egalax.c making all normal touch events in multi-touch mode work like in single-touch mode https://bugs.launchpad.net/ubuntu/+source/linux/+bug/625511/+attachment/1526920/+files/hid-egalax.c-range.patch |
|
| 2010-08-30 16:31:40 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2010-08-31 17:00:03 |
TH |
description |
In the Maverick Kernel (tested with 2.6.35-19) the eGalax/DWAV touchscreen (USB ID 0eef:480d) found in the Eee PC T101MT doesn't send multitouch events although the correct module hid_egalax is included in the Kernel. The reason is that the MULTI_INPUT quirk is still used for this device although it is no longer needed, and it prevents the module from working.
Steps to reproduce:
Start Ubuntu 10.10 on an Eee PC T101MT with eGalax touchscreen. Check xinput --list to find out that the screen is listed twice. Run evtest to find out that four device nodes (/dev/input/event6 ... /dev/input/event9) are created for the device. Only one of them produces events, and they are only single touch events. The other nodes produce no events at all. None produces multitouch events.
Reason:
In drivers/hid/usbhid/hid-quirks.c , you find the line
{ USB_VENDOR_ID_DWAV, USB_DEVICE_ID_DWAV_EGALAX_MULTITOUCH, HID_QUIRK_MULTI_INPUT }
which causes the MULTI_INPUT quirk to be added to the device, which prevents the hid_egalax module from working and thus only the quirky default handling of the touchscreen is applied.
Fix:
Remove this line from hid-quirks.c using the attached patch; Now hid_egalax manages the screen: it appears only once in xinput --list, only creates one device node which delivers single touch and multitouch events, as expected.
One problem with this fix though: Because of a bug in the hid_egalax module, the screen assumes a wrong range for the coordinate axes when in multitouch mode. I have created a separate patch for this, shall I attach it to this bug (because otherwise the screen doesn't work when this fix is applied) or create a new bug for this? |
In the Maverick Kernel (tested with 2.6.35-19) the eGalax/DWAV touchscreen (USB ID 0eef:480d) found in the Eee PC T101MT doesn't send multitouch events although the correct module hid_egalax is included in the Kernel. The reason is that the MULTI_INPUT quirk is still used for this device although it is no longer needed, and it prevents the module from working.
Steps to reproduce:
Start Ubuntu 10.10 on an Eee PC T101MT with eGalax touchscreen. Check xinput --list to find out that the screen is listed twice. Run evtest to find out that four device nodes (/dev/input/event6 ... /dev/input/event9) are created for the device. Only one of them produces events, and they are only single touch events. The other nodes produce no events at all. None produces multitouch events.
Reason:
In drivers/hid/usbhid/hid-quirks.c , you find the line
{ USB_VENDOR_ID_DWAV, USB_DEVICE_ID_DWAV_EGALAX_MULTITOUCH, HID_QUIRK_MULTI_INPUT }
which causes the MULTI_INPUT quirk to be added to the device, which prevents the hid_egalax module from working and thus only the quirky default handling of the touchscreen is applied.
Fix:
Remove this line from hid-quirks.c using the attached patch; Now hid_egalax manages the screen: it appears only once in xinput --list, only creates one device node which delivers single touch and multitouch events, as expected.
One problem with this fix though: Because of a bug in the hid_egalax module, the screen assumes a wrong range for the coordinate axes when in multitouch mode. I have created a separate patch for this, shall I attach it to this bug (because otherwise the screen doesn't work when this fix is applied) or create a new bug for this?
|
|
| 2010-08-31 17:03:04 |
TH |
bug |
|
|
added subscriber TH |
| 2010-08-31 17:09:17 |
TH |
removed subscriber TH |
|
|
|
| 2010-08-31 17:10:09 |
TH |
bug |
|
|
added subscriber TH |
| 2010-08-31 17:11:42 |
TH |
removed subscriber TH |
|
|
|
| 2010-09-01 19:24:39 |
Eirik Synnes |
bug |
|
|
added subscriber Eirik Synnes |
| 2010-09-02 12:53:41 |
riccardo de palo |
bug |
|
|
added subscriber riccardo de palo |
| 2010-09-02 15:59:35 |
Philipp Merkel |
description |
In the Maverick Kernel (tested with 2.6.35-19) the eGalax/DWAV touchscreen (USB ID 0eef:480d) found in the Eee PC T101MT doesn't send multitouch events although the correct module hid_egalax is included in the Kernel. The reason is that the MULTI_INPUT quirk is still used for this device although it is no longer needed, and it prevents the module from working.
Steps to reproduce:
Start Ubuntu 10.10 on an Eee PC T101MT with eGalax touchscreen. Check xinput --list to find out that the screen is listed twice. Run evtest to find out that four device nodes (/dev/input/event6 ... /dev/input/event9) are created for the device. Only one of them produces events, and they are only single touch events. The other nodes produce no events at all. None produces multitouch events.
Reason:
In drivers/hid/usbhid/hid-quirks.c , you find the line
{ USB_VENDOR_ID_DWAV, USB_DEVICE_ID_DWAV_EGALAX_MULTITOUCH, HID_QUIRK_MULTI_INPUT }
which causes the MULTI_INPUT quirk to be added to the device, which prevents the hid_egalax module from working and thus only the quirky default handling of the touchscreen is applied.
Fix:
Remove this line from hid-quirks.c using the attached patch; Now hid_egalax manages the screen: it appears only once in xinput --list, only creates one device node which delivers single touch and multitouch events, as expected.
One problem with this fix though: Because of a bug in the hid_egalax module, the screen assumes a wrong range for the coordinate axes when in multitouch mode. I have created a separate patch for this, shall I attach it to this bug (because otherwise the screen doesn't work when this fix is applied) or create a new bug for this?
|
In the Maverick Kernel (tested with 2.6.35-19) the eGalax/DWAV touchscreen (USB ID 0eef:480d) found in the Eee PC T101MT doesn't send multitouch events although the correct module hid_egalax is included in the Kernel. The reason is that the MULTI_INPUT quirk is still used for this device although it is no longer needed, and it prevents the module from working.
Steps to reproduce:
Start Ubuntu 10.10 on an Eee PC T101MT with eGalax touchscreen. Check xinput --list to find out that the screen is listed twice. Run evtest to find out that four device nodes (/dev/input/event6 ... /dev/input/event9) are created for the device. Only one of them produces events, and they are only single touch events. The other nodes produce no events at all. None produces multitouch events.
Reason:
In drivers/hid/usbhid/hid-quirks.c , you find the line
{ USB_VENDOR_ID_DWAV, USB_DEVICE_ID_DWAV_EGALAX_MULTITOUCH, HID_QUIRK_MULTI_INPUT }
which causes the MULTI_INPUT quirk to be added to the device, which prevents the hid_egalax module from working and thus only the quirky default handling of the touchscreen is applied.
Fix:
Remove this line from hid-quirks.c using the attached patch; Now hid_egalax manages the screen: it appears only once in xinput --list, only creates one device node which delivers single touch and multitouch events, as expected.
One problem with this fix though: Because of a bug in the hid_egalax module, the screen assumes a wrong range for the coordinate axes when in multitouch mode. There also is a patch for this, which is attached, too.
|
|
| 2010-09-11 20:11:39 |
steverweber |
nominated for series |
|
Ubuntu Maverick |
|
| 2010-09-16 22:33:23 |
Jeremy Foshee |
tags |
patch |
kj-triage patch |
|
| 2010-11-02 17:00:00 |
madbiologist |
linux (Ubuntu): status |
New |
Fix Committed |
|
| 2010-11-19 17:31:42 |
Brian Murray |
removed subscriber Ubuntu Review Team |
|
|
|
| 2011-01-10 18:31:40 |
Jeremy Foshee |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2011-05-06 13:59:33 |
Joey-Elijah Sneddon |
bug |
|
|
added subscriber d0od |
| 2011-07-17 18:24:57 |
zwox |
bug |
|
|
added subscriber zwox |
| 2011-08-18 08:43:02 |
Eirik Synnes |
removed subscriber Eirik Synnes |
|
|
|
| 2012-01-18 14:23:11 |
Søren Holm |
bug |
|
|
added subscriber Søren Holm |
