public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, bcrl@redhat.com
Cc: linux-kernel@vger.kernel.org, satch@fluent-access.com
Subject: Re: FYI  PS/2 Mouse problems -- userland issue
Date: Tue, 21 Aug 2001 22:35:20 GMT	[thread overview]
Message-ID: <200108212235.WAA197891@vlet.cwi.nl> (raw)

> Armed with docs I was able to see just why our code
> is completely wrong for handling things like the ps/2
> mouse being removed at runtime.

Yes, or being added, to be more precise. But it will not be
easy to do it right. So many different ps2-like types of mouse.
There are heuristics, like the AA 00 that I gave last week or so.
(But not every ps2-mouse emits this sequence.)
And one can keep track of the timing. But the fact that the length
of a packet is unknown (3, 4, 5, 8 bytes), and that in some modes
and relative positions arbitrary data is legal, makes it more or less
impossible to write code that is provably correct.
Also state machines have difficulties. Many types of mouse react
to special sequences of ordinary commands, and enter a non-ps2 mode.

As we already remarked in the previous round,
this is no kernel business.

Andries

[departing now - probably away from email for a while]


             reply	other threads:[~2001-08-21 22:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 22:35 Andries.Brouwer [this message]
2001-08-21 22:41 ` FYI PS/2 Mouse problems -- userland issue Ben LaHaise
2001-08-22 18:09 ` Gunther Mayer
  -- strict thread matches above, loose matches on Subject: below --
2001-08-21 19:40 Andries.Brouwer
2001-08-21 20:22 ` Ben LaHaise
     [not found] <mailman.998417940.18388.linux-kernel2news@redhat.com>
2001-08-21 18:59 ` Pete Zaitcev
2001-08-21 18:07 Stephen Satchell
2001-08-21 18:17 ` Ben LaHaise
2001-08-21 18:28   ` James Simmons
2001-08-21 18:35     ` Ben LaHaise
2001-08-21 20:30       ` James Simmons
2001-08-21 20:29 ` Kurt Garloff

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=200108212235.WAA197891@vlet.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=satch@fluent-access.com \
    /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