From owner-freebsd-hackers  Mon Apr  8 08:47:42 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA04777
          for hackers-outgoing; Mon, 8 Apr 1996 08:47:42 -0700 (PDT)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA04765
          for <hackers@freebsd.org>; Mon, 8 Apr 1996 08:47:38 -0700 (PDT)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id QAA19534; Sun, 7 Apr 1996 16:05:21 -0700 (PDT)
Message-Id: <199604072305.QAA19534@ref.tfs.com>
Subject: Re: The F_SETOWN problem..
To: terry@lambert.org (Terry Lambert)
Date: Sun, 7 Apr 1996 16:05:20 -0700 (PDT)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: roell@blah.a.isar.de, terry@lambert.org, msmith@atrad.adelaide.edu.au,
        hackers@freebsd.org, jkh@time.cdrom.com, roell@xinside.com
In-Reply-To: <199604072132.OAA00676@phaeton.artisoft.com> from "Terry Lambert" at Apr 7, 96 02:32:42 pm
X-Mailer: ELM [version 2.4 PL25 ME8b]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

[lots deleted]

sounds like what is needed is a differnt protocol to be made available
from the various mouses..
Under MACH all mice (serial etc al) come in through the same
device and they are translated to a common protocol..

if we were to do that (in conjunction with the two console authors maybe)
then we could add the following info to each mouse 'packet'

number of following mouse events..(not yet read)
microsecond timestamp.. moment when the packet was complete.

it would require puting a tty protocol into the approriate
tty line for serial mice, and possibly a differnt interface for
such things as ps2 mice, but it might be useful.

julian