On Thu, Dec 10, 2009 at 08:37:39AM +0100, Stéphane Chatty wrote:
>
> Le 10 déc. 09 à 00:15, Dmitry Torokhov a écrit :
>
>> Hi Stephane,
>>
>> On Wed, Dec 09, 2009 at 10:49:28PM +0100, Stephane Chatty wrote:
>>> +
>>> + if (emulate_touchscreen) {
>>> + if (sd->first) {
>>> + if (!sd->activity) {
>>> + input_event(input, EV_KEY, BTN_TOUCH, 1);
>>> + sd->activity = 1;
>>> + }
>>> + input_event(input, EV_ABS, ABS_X, sd->x);
>>> + input_event(input, EV_ABS, ABS_Y, sd->y);
>>> + }
>>> + }
>>
>> Why are you doing the above conditionally? Just report it always -
>> less
>> setup required for the user.
>
> As regards setup, the emulate_touchscreen parameter is 1 by default so
> that users don't have to care about it. But I felt compelled to have this
> parameter because the ongoing work on X.org suggests that there might be
> a problem in upper layers with having duplicate information flows. For
> instant, if we associate a slave pointer (MPX terminology) to every
> ABS_MT_X/ABS_MT_Y flow, the ABS_X/ABS_Y will come as an additional flow
> and we'll need to do something to ignore it. Benjamin, Peter, what do you
> think?
I thought Henrik's idea was that driver should use either classic or
multitouch events from the data stream but not both. This way users
could either use old, non-multitouch-aware drivers or newer ones without
issues.
>
> Also, some devices (especially the N-Trig) do not make it possible to
> implement a single touch emulation because they have no finger tracking
> (IDs change over time, you never know which finger to use and the cursor
> would jump from one to the other randomly). Therefore, I did not feel
> like creating a new "standard" behaviour that will be broken by such
> devices.
If driver can't support something then it smply won't provide such
events at all and users that require certain capability will simply
ignore devices that don't provide it.
>
> Actually, Rafi Rubin and I have started to discuss the idea of splitting
> this into two input nodes: a pure multitouch device and a pure single
> touch emulation. I'd like to have feedback on this idea too, even if I
> have no time to work on it yet.
If you create 2 devices basically supplying the same data then it will
be harder for consumers to select between them and drivers. I.e. if
single device transmits entire state then it is easy to write hotplug
policy for say X server (using udev/hal) such as:
- this box always uses evdev for everything, or
- devices with nultitouch capabilities use new multitouch
X driver, the rest use evdev.
This will be harder if there were 2 "copies" of multitouch devices
because we'd have to be able to recognize "siblings" and ignore one or
the other.
Does this make sense?
If there is a concern about too many unused events reaching userspace -
then we need to implement subscription model in evdev where consumer can
specify list of events it is interested in and have input core deliver
only those. I'll take patches ;)
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
