From: Chris Bagwell <redacted>
This allows ASUS Eee Slate touchscreens to work.
Signed-off-by: Chris Bagwell <redacted>
---
I do not have one of these to test the patch but I helped a user
debug why his new touchscreen was being treated as a touchpad.
He reported success after adding this ID.
I'm sending this since I'm unsure status of patch to auto-assign
multitouch devices to hid-multitouch. That would probably have
solved issue as well.
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h | 1 +
drivers/hid/hid-multitouch.c | 3 +++
3 files changed, 5 insertions(+), 0 deletions(-)
From: Benjamin Tissoires <hidden> Date: 2011-11-12 15:01:14
Hi Chris,
On Fri, Nov 11, 2011 at 21:21, [off-list ref] wrote:
From: Chris Bagwell <redacted>
This allows ASUS Eee Slate touchscreens to work.
Signed-off-by: Chris Bagwell <redacted>
---
I do not have one of these to test the patch but I helped a user
debug why his new touchscreen was being treated as a touchpad.
He reported success after adding this ID.
The patch looks good.
Reviewed-by: Benjamin Tissoires <redacted>
I'm sending this since I'm unsure status of patch to auto-assign
multitouch devices to hid-multitouch. That would probably have
solved issue as well.
Well, as of today, the auto-detection is partly included in 3.2-rc1:
the generic hid layer will release the device (ie, it's not needed
anymore to patch hid-core.c while adding a multitouch device to its
list), but hid-multitouch is not capable of handling it after the
release of the generic part.
BTW, egalax devices need a special handling, and we may have to add
them one by one.
Alternatively, we could use:
+ { .driver_data = MT_CLS_EGALAX,
+ HID_USB_DEVICE(USB_VENDOR_ID_DWAV, HID_ANY_ID) },
but that's hoping that DWAV won't do any other things than multitouch panels.
Jiri, have you an idea on this?
Cheers,
Benjamin
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Chris Bagwell <redacted>
This allows ASUS Eee Slate touchscreens to work.
Signed-off-by: Chris Bagwell <redacted>
---
I do not have one of these to test the patch but I helped a user
debug why his new touchscreen was being treated as a touchpad.
He reported success after adding this ID.
The patch looks good.
Reviewed-by: Benjamin Tissoires <redacted>
Applied, thanks.
quoted
I'm sending this since I'm unsure status of patch to auto-assign
multitouch devices to hid-multitouch. That would probably have
solved issue as well.
Well, as of today, the auto-detection is partly included in 3.2-rc1:
the generic hid layer will release the device (ie, it's not needed
anymore to patch hid-core.c while adding a multitouch device to its
list), but hid-multitouch is not capable of handling it after the
release of the generic part.
BTW, egalax devices need a special handling, and we may have to add
them one by one.
Alternatively, we could use:
+ { .driver_data = MT_CLS_EGALAX,
+ HID_USB_DEVICE(USB_VENDOR_ID_DWAV, HID_ANY_ID) },
but that's hoping that DWAV won't do any other things than multitouch panels.
Jiri, have you an idea on this?
Currently we have something like 7 entries, which doesn't sound that bad.
If the number of device IDs starts to grow rapidly, we should start
thinking about this, but I think we are not there yet.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Benjamin Tissoires <hidden> Date: 2011-11-13 21:59:42
On Sun, Nov 13, 2011 at 21:31, Jiri Kosina [off-list ref] wrote:
On Sat, 12 Nov 2011, Benjamin Tissoires wrote:
quoted
quoted
From: Chris Bagwell <redacted>
This allows ASUS Eee Slate touchscreens to work.
Signed-off-by: Chris Bagwell <redacted>
---
I do not have one of these to test the patch but I helped a user
debug why his new touchscreen was being treated as a touchpad.
He reported success after adding this ID.
The patch looks good.
Reviewed-by: Benjamin Tissoires <redacted>
Applied, thanks.
quoted
quoted
I'm sending this since I'm unsure status of patch to auto-assign
multitouch devices to hid-multitouch. That would probably have
solved issue as well.
Well, as of today, the auto-detection is partly included in 3.2-rc1:
the generic hid layer will release the device (ie, it's not needed
anymore to patch hid-core.c while adding a multitouch device to its
list), but hid-multitouch is not capable of handling it after the
release of the generic part.
BTW, egalax devices need a special handling, and we may have to add
them one by one.
Alternatively, we could use:
+ { .driver_data = MT_CLS_EGALAX,
+ HID_USB_DEVICE(USB_VENDOR_ID_DWAV, HID_ANY_ID) },
but that's hoping that DWAV won't do any other things than multitouch panels.
Jiri, have you an idea on this?
Currently we have something like 7 entries, which doesn't sound that bad.
If the number of device IDs starts to grow rapidly, we should start
thinking about this, but I think we are not there yet.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Benjamin Tissoires <hidden> Date: 2011-11-13 22:03:24
On Sun, Nov 13, 2011 at 21:31, Jiri Kosina [off-list ref] wrote:
On Sat, 12 Nov 2011, Benjamin Tissoires wrote:
quoted
quoted
From: Chris Bagwell <redacted>
This allows ASUS Eee Slate touchscreens to work.
Signed-off-by: Chris Bagwell <redacted>
---
I do not have one of these to test the patch but I helped a user
debug why his new touchscreen was being treated as a touchpad.
He reported success after adding this ID.
The patch looks good.
Reviewed-by: Benjamin Tissoires <redacted>
Applied, thanks.
quoted
quoted
I'm sending this since I'm unsure status of patch to auto-assign
multitouch devices to hid-multitouch. That would probably have
solved issue as well.
Well, as of today, the auto-detection is partly included in 3.2-rc1:
the generic hid layer will release the device (ie, it's not needed
anymore to patch hid-core.c while adding a multitouch device to its
list), but hid-multitouch is not capable of handling it after the
release of the generic part.
BTW, egalax devices need a special handling, and we may have to add
them one by one.
Alternatively, we could use:
+ { .driver_data = MT_CLS_EGALAX,
+ HID_USB_DEVICE(USB_VENDOR_ID_DWAV, HID_ANY_ID) },
but that's hoping that DWAV won't do any other things than multitouch panels.
Jiri, have you an idea on this?
Currently we have something like 7 entries, which doesn't sound that bad.
If the number of device IDs starts to grow rapidly, we should start
thinking about this, but I think we are not there yet.
Hi Jiri,
as you can see, on
http://lii-enac.fr/en/architecture/linux-input/multitouch-devices.html
we currently have 13 different PID for egalax.... But we currently
support 7 (we missed some users and tests/feedback).
If it's good for you to have PID added one by one, I'm fine with that.
Cheers,
Benjamin
PS: sorry for the previous miss sent mail, I clicked on send too early ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Marek Vasut <hidden> Date: 2011-11-13 23:15:34
On Sat, 12 Nov 2011, Benjamin Tissoires wrote:
quoted
quoted
From: Chris Bagwell <redacted>
This allows ASUS Eee Slate touchscreens to work.
Signed-off-by: Chris Bagwell <redacted>
---
I do not have one of these to test the patch but I helped a user
debug why his new touchscreen was being treated as a touchpad.
He reported success after adding this ID.
The patch looks good.
Reviewed-by: Benjamin Tissoires <redacted>
Applied, thanks.
quoted
quoted
I'm sending this since I'm unsure status of patch to auto-assign
multitouch devices to hid-multitouch. That would probably have
solved issue as well.
Well, as of today, the auto-detection is partly included in 3.2-rc1:
the generic hid layer will release the device (ie, it's not needed
anymore to patch hid-core.c while adding a multitouch device to its
list), but hid-multitouch is not capable of handling it after the
release of the generic part.
BTW, egalax devices need a special handling, and we may have to add
them one by one.
Alternatively, we could use:
+ { .driver_data = MT_CLS_EGALAX,
+ HID_USB_DEVICE(USB_VENDOR_ID_DWAV, HID_ANY_ID) },
but that's hoping that DWAV won't do any other things than multitouch
panels. Jiri, have you an idea on this?
Currently we have something like 7 entries, which doesn't sound that bad.
If the number of device IDs starts to grow rapidly, we should start
thinking about this, but I think we are not there yet.
Well there's another one in Acer W500. But that one handles 5 simulaneous MT
events. I submitted a patch already, but it was held because ... I dunno why
anymore.
M
Well there's another one in Acer W500. But that one handles 5
simulaneous MT events. I submitted a patch already, but it was held
because ... I dunno why anymore.
Hmm, I don't recall seeing that one. Could you please resubmit? Thanks,
--
Jiri Kosina
SUSE Labs
From: Marek Vasut <hidden> Date: 2011-11-14 10:43:56
On Mon, 14 Nov 2011, Marek Vasut wrote:
quoted
Well there's another one in Acer W500. But that one handles 5
simulaneous MT events. I submitted a patch already, but it was held
because ... I dunno why anymore.
Hmm, I don't recall seeing that one. Could you please resubmit? Thanks,
I'm just rebuilding 3.1.0+ kernel with the patch so I can resubmit it rebased
against fresh kernel. There was some discussion about detecting how many
fingers/points does the device support, so I'm also testing with that.
M