From owner-freebsd-current  Wed Nov 27 15:17:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA21387
          for current-outgoing; Wed, 27 Nov 1996 15:17:08 -0800 (PST)
Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA21378;
          Wed, 27 Nov 1996 15:17:04 -0800 (PST)
Received: by nasu.utsunomiya-u.ac.jp (5.57/ULTRIX-940302)
	id AA05268; Thu, 28 Nov 96 08:16:01 +0900
Received: by outmail.utsunomiya-u.ac.jp (5.57/ULTRIX-940909)
	id AA06682; Thu, 28 Nov 96 08:15:59 +0900
Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id IAA09541; Thu, 28 Nov 1996 08:18:56 +0900 (JST)
Message-Id: <199611272318.IAA09541@zodiac.mech.utsunomiya-u.ac.jp>
To: "Louis A. Mamakos" <louie@transsys.com>
Cc: sos@freebsd.org, nate@mt.sri.com, current@freebsd.org,
        yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: FreeBSD-3.0-current PS/2 mouse driver change 
In-Reply-To: Your message of "Wed, 27 Nov 1996 08:31:44 EST."
             <199611271331.IAA01084@whizzo.transsys.com> 
References: <199611270804.JAA00372@ravenock.cybercity.dk>  <199611271331.IAA01084@whizzo.transsys.com> 
Date: Thu, 28 Nov 1996 08:18:55 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
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) ;-<

Kazu