linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Kapfer <sebastian_kapfer@gmx.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linux Input ML <linux-input@vger.kernel.org>
Subject: Re: [PATCH 2/2] Alps Dualpoint, Interleaved packets
Date: Tue, 15 Dec 2009 22:01:33 +0100	[thread overview]
Message-ID: <1260910893.6294.26.camel@sardelle.necksus.de> (raw)
In-Reply-To: <20091215064224.GB12669@core.coreip.homeip.net>


Hi Dmitry,

I really hate to say, but I can still desync it.

[1240043.147596] alps.c: handle cf
[1240043.148778] alps.c: handle 14
[1240043.150043] alps.c: handle 1a
[1240043.157696] alps.c: handle 5f
[1240043.158851] alps.c: handle c
[1240043.160044] alps.c: handle 29
[1240043.163885] alps.c: handle 2f
[1240043.165051] alps.c: handle 0
[1240043.166213] alps.c: handle ff
[1240043.166218] alps.c: refusing packet[5] = ff
[1240043.166221] 
[1240043.166227] psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 6

In short, it's a 6-byte followed by a 3-byte; we mistakenly process it
as a interleaved PS/2 (oh well), and, while the final bytes come in,
happen upon high bits set in the PS/2 packet.  In a way, this is correct
behaviour, because we _are_ processing the data incorrectly...  In my
last patch, this went unnoticed because I didn't check for the high bit
in bytes 7,8,9.

For all practical purposes (i.e. not pressing three buttons and fumbling
with both pointers at the same time), the patch works very well.

In particular, no double clicks.  :-)

-- 
Sebastian Kapfer
 Inst. für Theoretische Physik I        Office +49-9131-85-2-8450
 Universität Erlangen                   Mobile +49-160-9577-6436
 Staudtstr. 7, Raum 02.583.             sebastian.kapfer@physik.uni-erlangen.de

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

  reply	other threads:[~2009-12-15 21:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-29 16:54 [alps] Timing patch, revised again :-) Sebastian Kapfer
2009-12-04  8:49 ` Dmitry Torokhov
2009-12-04 21:47   ` Sebastian Kapfer
2009-12-04 23:49     ` Dmitry Torokhov
2009-12-04 23:52       ` Dmitry Torokhov
2009-12-06 19:53       ` Sebastian Kapfer
2009-12-06 20:09         ` Dmitry Torokhov
2009-12-07  0:27           ` Sebastian Kapfer
2009-12-13 22:01     ` [PATCH 1/2] Sebastian Kapfer
2009-12-13 22:09     ` [PATCH 2/2] Alps Dualpoint, Interleaved packets Sebastian Kapfer
2009-12-15  6:42       ` Dmitry Torokhov
2009-12-15 21:01         ` Sebastian Kapfer [this message]
2009-12-15 22:49           ` Dmitry Torokhov
2009-12-16  0:01             ` Sebastian Kapfer

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=1260910893.6294.26.camel@sardelle.necksus.de \
    --to=sebastian_kapfer@gmx.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).