All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Bagwell <chris@cnpbagwell.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Takashi Iwai <tiwai@suse.de>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Chase Douglas <chase.douglas@canonical.com>,
	linux-input@vger.kernel.org, xorg-devel@lists.x.org,
	Andy Whitcroft <apw@canonical.com>,
	linux-kernel@vger.kernel.org,
	Peter Hutterer <peter.hutterer@who-t.net>,
	Duncan McGreggor <duncan.mcgreggor@canonical.com>
Subject: Re: [PATCH 0/3] Input: synaptics - multitouch and multifinger support
Date: Mon, 11 Oct 2010 08:41:44 -0500	[thread overview]
Message-ID: <AANLkTi=VTq+3-t4taR_22E1Wkos+yeHdMDkHd-Zc9Cbs@mail.gmail.com> (raw)
In-Reply-To: <4CB2C154.5060303@euromail.se>

On Mon, Oct 11, 2010 at 2:48 AM, Henrik Rydberg <rydberg@euromail.se> wrote:
> On 10/11/2010 09:35 AM, Takashi Iwai wrote:
> [...]
>
>> In anyway, feel free to add my sign-off there since I already posted
>> my own one as a reference.
>>
>> But, I have an open issue with Chase's patch.  Maybe it's rather a
>> question to Henrik:
>>
>> Shouldn't all points be reported as ABS_MT_* events?  So far, only the
>> second touch-point is reported via ABS_MT_* while the first  point is
>> still reported as ABX_[X|Y].
>>
>> I corrected this in my patch I posted, but I wasn't sure, too.
>
>
> I have issues with all submitted patches, but did not give explicit reasons
> since there were overlapping submissions. Perhaps Chase and yourself can work
> out how you want to submit the new patches? And yes, all points should be
> reported as ABS_MT events.
>
> Thanks,
> Henrik
>

And is it also safe to say that we need to continue to report
ABS_X/ABS_Y *and* those values need to always track 1st finger touch
for backwards compatibility?

It was brought up in thread but not stated as strong requirement.

BTW, there are patches in last couple months to x86-input-synaptics
that will allow it to ignore jumps in values of ABS_X/ABS_Y when
transition of multi-touch occur (both adding or removing fingers via
BTN_TOOL_*TAP).  So one new-ish option is for ABS_X/ABS_Y to not track
1st finger but become average of 2 fingers.

Chris

WARNING: multiple messages have this Message-ID (diff)
From: Chris Bagwell <chris@cnpbagwell.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Takashi Iwai <tiwai@suse.de>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Chase Douglas <chase.douglas@canonical.com>,
	linux-input@vger.kernel.org, xorg-devel@lists.x.org,
	Andy Whitcroft <apw@canonical.com>,
	linux-kernel@vger.kernel.org,
	Peter Hutterer <peter.hutterer@who-t.net>,
	Duncan McGreggor <duncan.mcgreggor@canonical.com>
Subject: Re: [PATCH 0/3] Input: synaptics - multitouch and multifinger support
Date: Mon, 11 Oct 2010 08:41:44 -0500	[thread overview]
Message-ID: <AANLkTi=VTq+3-t4taR_22E1Wkos+yeHdMDkHd-Zc9Cbs@mail.gmail.com> (raw)
In-Reply-To: <4CB2C154.5060303@euromail.se>

On Mon, Oct 11, 2010 at 2:48 AM, Henrik Rydberg <rydberg@euromail.se> wrote:
> On 10/11/2010 09:35 AM, Takashi Iwai wrote:
> [...]
>
>> In anyway, feel free to add my sign-off there since I already posted
>> my own one as a reference.
>>
>> But, I have an open issue with Chase's patch.  Maybe it's rather a
>> question to Henrik:
>>
>> Shouldn't all points be reported as ABS_MT_* events?  So far, only the
>> second touch-point is reported via ABS_MT_* while the first  point is
>> still reported as ABX_[X|Y].
>>
>> I corrected this in my patch I posted, but I wasn't sure, too.
>
>
> I have issues with all submitted patches, but did not give explicit reasons
> since there were overlapping submissions. Perhaps Chase and yourself can work
> out how you want to submit the new patches? And yes, all points should be
> reported as ABS_MT events.
>
> Thanks,
> Henrik
>

And is it also safe to say that we need to continue to report
ABS_X/ABS_Y *and* those values need to always track 1st finger touch
for backwards compatibility?

It was brought up in thread but not stated as strong requirement.

BTW, there are patches in last couple months to x86-input-synaptics
that will allow it to ignore jumps in values of ABS_X/ABS_Y when
transition of multi-touch occur (both adding or removing fingers via
BTN_TOOL_*TAP).  So one new-ish option is for ABS_X/ABS_Y to not track
1st finger but become average of 2 fingers.

Chris
--
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

  parent reply	other threads:[~2010-10-11 13:41 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 14:57 [PATCH 0/3] Input: synaptics - multitouch and multifinger support Chase Douglas
2010-10-08 14:57 ` [PATCH 1/3] Input: synaptics - add multitouch support Chase Douglas
2010-10-08 14:57   ` [PATCH 2/3] Input: synaptics - add multitouch multifinger support Chase Douglas
2010-10-08 14:58     ` [PATCH 3/3] Input: synaptics - remove touches over button click area Chase Douglas
2010-10-10 15:58       ` Chris Bagwell
2010-10-11 16:24       ` Chris Bagwell
2010-10-11 16:24         ` Chris Bagwell
2010-10-11 17:10         ` Takashi Iwai
2010-10-11 17:10           ` Takashi Iwai
2010-10-11 17:30           ` Dmitry Torokhov
2010-10-11 17:30             ` Dmitry Torokhov
2010-10-11 17:40             ` Takashi Iwai
2010-10-11 17:46           ` Chris Bagwell
2010-10-11 17:46             ` Chris Bagwell
2010-10-11 17:54             ` Henrik Rydberg
2010-10-11 18:29             ` Takashi Iwai
2010-10-11 18:29               ` Takashi Iwai
2010-10-10 15:44     ` [PATCH 2/3] Input: synaptics - add multitouch multifinger support Chris Bagwell
2010-10-10 15:37   ` [PATCH 1/3] Input: synaptics - add multitouch support Chris Bagwell
2010-10-10 15:41   ` Chris Bagwell
2010-10-08 16:37 ` [PATCH 0/3] Input: synaptics - multitouch and multifinger support Takashi Iwai
2010-10-08 16:38   ` Takashi Iwai
2010-10-08 17:48     ` Takashi Iwai
2010-10-08 17:15   ` Chase Douglas
2010-10-08 17:46     ` Takashi Iwai
2010-10-08 18:04     ` Dmitry Torokhov
2010-10-08 19:31       ` Takashi Iwai
2010-10-10 21:04         ` Dmitry Torokhov
2010-10-11  7:35           ` Takashi Iwai
2010-10-11  7:48             ` Henrik Rydberg
2010-10-11  7:59               ` Takashi Iwai
2010-10-11 13:41               ` Chris Bagwell [this message]
2010-10-11 13:41                 ` Chris Bagwell
2010-10-11 14:01                 ` Takashi Iwai
2010-10-11 14:01                   ` Takashi Iwai
2010-10-11 14:24                   ` Henrik Rydberg
2010-10-11 14:49                     ` Takashi Iwai
2010-10-11 15:31                       ` Henrik Rydberg
2010-10-11 15:58                         ` Takashi Iwai
2010-10-10  7:49   ` Henrik Rydberg
2010-10-10 20:59     ` Dmitry Torokhov
2010-10-11  7:28       ` Takashi Iwai
2010-10-11  7:40         ` Henrik Rydberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=VTq+3-t4taR_22E1Wkos+yeHdMDkHd-Zc9Cbs@mail.gmail.com' \
    --to=chris@cnpbagwell.com \
    --cc=apw@canonical.com \
    --cc=chase.douglas@canonical.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=duncan.mcgreggor@canonical.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    --cc=rydberg@euromail.se \
    --cc=tiwai@suse.de \
    --cc=xorg-devel@lists.x.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.