From owner-freebsd-current  Wed Nov 27 20:22:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA04731
          for current-outgoing; Wed, 27 Nov 1996 20:22:43 -0800 (PST)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA04724;
          Wed, 27 Nov 1996 20:22:35 -0800 (PST)
Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.8.3/8.7.3) with SMTP id XAA08667; Wed, 27 Nov 1996 23:20:38 -0500 (EST)
Message-Id: <199611280420.XAA08667@whizzo.transsys.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
cc: sos@freebsd.org, nate@mt.sri.com, current@freebsd.org
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: FreeBSD-3.0-current PS/2 mouse driver change 
References: <199611270804.JAA00372@ravenock.cybercity.dk> 
 <199611271331.IAA01084@whizzo.transsys.com> <199611272318.IAA09541@zodiac.mech.utsunomiya-u.ac.jp>
In-reply-to: Your message of "Thu, 28 Nov 1996 08:18:55 +0900."
             <199611272318.IAA09541@zodiac.mech.utsunomiya-u.ac.jp> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 27 Nov 1996 23:20:38 -0500
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> >Please note that
> >right now, the new psm.c driver in the kernel renders this pointing device
> >helpless to do it's nifty bits.  The additional "smarts" in the kernel 
> >driver seems to mask off the bit which indicates a "tap" gesture on the
> >pad.  I've just upgraded to 3.0-current last night, and have only begun
> >to look at the driver.
> 
> Hello. I understand what is the problem with the `psm' driver when used
> with ALPUS GlidePoint. I will turn off the bit checking by default.
> 
> BTW, that bit is said to be always 1, according to some docs. Now that
> I know the bit is not set in that way, there will be no way to re-sync
> with the data packet from the PS/2 mouse once we have become out of
> sync (due to lost interrupt or something) ;-<

I've really never experienced a situation where the mouse driver got 
unsynchronized.. at least with the old version of the driver.  All of the
parsing of the mouse data stream seemed to have taken place either in
the X server or moused rather than in the kernel.  Is this a significant
problem which other users have experienced?

louie