Thread (5 messages) 5 messages, 3 authors, 2010-08-20

Re: Dual touchscreen implementation

From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2010-08-20 05:01:24

Hi Dan,

On Tue, Aug 17, 2010 at 09:06:00AM -0500, Murphy, Dan wrote:
Abraham

My thoughts would be similar to Dmitry's.  We should let the user
space figure it out.  Then the application itself can combine and
render the touches as a contiguous touch screen or as an independent
touch.

But we would probably need a way for the kernel driver to identify
which touch controller that the information came from.

For multi touch we may be able to use ABS_MT_TRACKING_ID for passing
up the controller ID but there is not really a good code for the
standard ABS axes.  Maybe we can make one called ABS_TRACKING_ID to
keep with the theme.

This way the user space and use that to know where it came from.

Or Dmitry if you have any patches or thoughts let me know.
I am confused - you should have 2 device nodes for each pf your
controllers and so you should be able to figure out what device
particular event is coming from. What am I missing here?

Thanks.

-- 
Dmitry
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help