From owner-freebsd-hackers Mon Apr 8 11:47:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA15907 for hackers-outgoing; Mon, 8 Apr 1996 11:47:33 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA15901 for ; Mon, 8 Apr 1996 11:47:31 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id LAA02521; Mon, 8 Apr 1996 11:46:09 -0700 Message-Id: <199604081846.LAA02521@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "JULIAN Elischer" cc: roell@blah.a.isar.de, hackers@freebsd.org Subject: Re: The F_SETOWN problem.. In-reply-to: Your message of "Sun, 07 Apr 1996 16:05:20 PDT." <199604072305.QAA19534@ref.tfs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Apr 1996 11:46:08 -0700 From: "Amancio Hasty Jr." Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wow protocol independent mouse event handling and a more efficient mouse event handling not too say that is a lot easier to maintain the different mouse protocols in the kernel rather than in the X server. Cheers, Amancio >>> "JULIAN Elischer" said: > [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 >