From: "Yao-Chung Chang" <yaochung@cic.org.tw>
To: linux-input@vger.kernel.org
Subject: about mouse lost synchronization
Date: Wed, 13 May 2009 15:27:33 +0800 [thread overview]
Message-ID: <000001c9d39c$4baeb6f0$e30c24d0$@org.tw> (raw)
Dear all
I've implemented a ps/2 serio driver that uses GPIO (two GPIO pins). Each
bit is triggered by GPIO interrupt. When in console mode, GPM works
fine, and I can see the mouse cursor moves correctly. But When entering
GUI, say QT or microwindows, the following messages occurred:
Mouse at xxxxx/serio0/input0 lost synchronization, throwing 1 bytes away.
..
Mouse at xxxxx/serio0/input0 lost synchronization, throwing 1 bytes away.
Mouse at xxxxx/serio0/input0 lost synchronization, throwing 2 bytes away.
And the mouse cursor is floating and moves incorrectly.
What is the criteria that kernel think the mouse packet is lost of sync.?
Regards,
ycchang
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4069 (20090512) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
next reply other threads:[~2009-05-13 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 7:27 Yao-Chung Chang [this message]
2009-05-14 2:56 ` about mouse lost synchronization Dmitry Torokhov
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='000001c9d39c$4baeb6f0$e30c24d0$@org.tw' \
--to=yaochung@cic.org.tw \
--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 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.