From: Cedric Sodhi <manday@gmx.net>
To: Chris Bagwell <chris@cnpbagwell.com>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
linux-input@vger.kernel.org,
linuxwacom-devel@lists.sourceforge.net
Subject: Re: HID: Dead ./debug/hid/xxx/events
Date: Thu, 17 Nov 2011 07:59:55 +0100 [thread overview]
Message-ID: <20111117065955.GB2110@slate> (raw)
In-Reply-To: <CAGzDe_ak_xzjJkpQcNwwgL+pu94qfhAixjS=9TF3679cpcPFpw@mail.gmail.com>
On Wed, Nov 16, 2011 at 03:23:50PM -0600, Chris Bagwell wrote:
> One update on my side. I was looking at hid-multitouch.c from
> Dmitri's next branch and didn't see that ALWAYS_VALID. So I thought
> it was a typo and manually mapping your "18" value to
> VALID_IS_INRANGE; which we were previously setting it to. Thats why I
> mentioned I thought you were setting to same quirks.
>
> Thanks for diff. Often a diff is worth a thousand words.
>
> OK, now back to your email. I'm confused about your logs. The URL
> points to the tar file with multiple logs and the evtest_twofinger.log
> inside it is the one I was talking about having issues.
Indeed. Those logs in the TAR file were created when I was still
manually adding the device to sysfs (that is, before that very diff
which includes changes to the whitelist). It looks like I neglected to
set the quirks back then. Sorry.
>
> Now you've attached a new evtest_twofinger.log and its values look
> good. So your saying this new log is from a version based on the
> diff?
Exactly.
Cedric
> If so, I'll chalk it up to some debug issue and sounds like
> ALWAYS_VALID is indeed the key to this.
>
> Chris
>
> On Wed, Nov 16, 2011 at 2:48 PM, Cedric Sodhi <manday@gmx.net> wrote:
> > Dear Benjamin,
> >
> > I applied your patch tp 3.2-jikos (uname shows 3.1, though). The
> > diff to jikos' original is now [attached].
> >
> > Chris says the output of evtest still signifies problems with
> > multitouch:
> >
> >> > http://ompldr.org/iYmIzYw
> >>
> >> Cedric, can you send these logs to Benjamin for ideas? The HID events
> >> look good but the evtest log for 2 fingers is not. The two touches
> >> are fighting each other. That "-1" value is interrupted as each
> >> finger is being lifted in between each new X/Y report.
> >>
> >> Also, can you send me and Benjamin the source code diff of what your
> >> testing against kernel tree?
> >>
> >> The behavior in your evtest log looks like what would happen if your
> >> setting the MT_QUIRK_NOT_SEEN_MEANS_UP. Since your HW only sends 1
> >> fingers worth of data per packet, you do not want that quirk.
> >>
> >> I'll still hold off on xf86-input-wacom issues until the events coming
> >> are sane. Your current events will cause xf86-input-wacom to do all
> >> kinds of weird stuff thats not worth effort to weed threw.
> >>
> >> Chris
> >
> > These logs in that tarfile were created while still manually adding the
> > ID via your sysfs interface. You find yet another evtest log for
> > two-finger touch attached.
> >
> > Cedric
> >
> --
> 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
--
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
prev parent reply other threads:[~2011-11-17 7:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 9:50 HID: Dead ./debug/hid/xxx/events Cedric Sodhi
2011-11-16 10:17 ` Benjamin Tissoires
2011-11-16 10:25 ` Cedric Sodhi
2011-11-16 13:41 ` Chris Bagwell
2011-11-16 14:55 ` Cedric Sodhi
2011-11-16 15:40 ` Cedric Sodhi
2011-11-16 16:15 ` Chris Bagwell
2011-11-16 17:01 ` Benjamin Tissoires
2011-11-16 20:48 ` Cedric Sodhi
2011-11-16 21:22 ` Benjamin Tissoires
2011-11-17 6:58 ` Cedric Sodhi
2011-11-16 21:23 ` Chris Bagwell
2011-11-17 6:59 ` Cedric Sodhi [this message]
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=20111117065955.GB2110@slate \
--to=manday@gmx.net \
--cc=benjamin.tissoires@gmail.com \
--cc=chris@cnpbagwell.com \
--cc=linux-input@vger.kernel.org \
--cc=linuxwacom-devel@lists.sourceforge.net \
/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.