From owner-freebsd-current  Thu Feb 13 16:16:40 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA21064
          for current-outgoing; Thu, 13 Feb 1997 16:16:40 -0800 (PST)
Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA21054
          for <freebsd-current@freebsd.org>; Thu, 13 Feb 1997 16:16:33 -0800 (PST)
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by nasu.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id JAA31752; Fri, 14 Feb 1997 09:13:31 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (9kCfhVnvx6MVGSIouYUCtrIiQmC2nO5L@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by outmail.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id JAA05363; Fri, 14 Feb 1997 09:13:30 +0900 (JST)
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 JAA07730; Fri, 14 Feb 1997 09:17:24 +0900 (JST)
Message-Id: <199702140017.JAA07730@zodiac.mech.utsunomiya-u.ac.jp>
To: gurney_j@resnet.uoregon.edu, terry@lambert.org
cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: moused on notebooks... 
In-reply-to: Your message of "Thu, 13 Feb 1997 13:51:29 MST."
             <199702132051.NAA00873@phaeton.artisoft.com> 
References: <199702132051.NAA00873@phaeton.artisoft.com> 
Date: Fri, 14 Feb 1997 09:17:22 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>> > > would anybody object to possibly added a signal handler to moused for
>> > > SIGHUP to force it to reopen the mouse device?  comments?
>> > 
>> > In the situation you describe, the SIGHUP would arive when you
>> > unplugged the mouse, not when you plugged it in.  You want it to
>> > be opened *after* you plug it in.
>> 
>> that's if your using a normal serial mouse... but I'm using a ps/2
>> mouse... so there isn't a "disconnect" signal... as far as I know...  of
>> course I guess I should make the SIGHUP patch affect bus and ps/2 mice
>> only then...
>> 
>> currently as it stands moused dies when it recieves a SIGHUP.. :)
>
>So you want to be able to manually SIGHUP it?  That doesn't really
>solve the problem; all it does is provide a kludgy workaround.
>
>
>The problem is:
>
>1)	Knowing you need to reinit the PS/2 mouse channel of the
>	keyboard controller, at all.

This can be done, by hooking the resume event hook provided by the
apm0 driver. I will write a piece of code for the psm driver to do
just that if such modification is useful/necessary for the suggested
moused enhancement.

>2)	Knowing when you need to resync the command stream because
>	someone has done something dumb like plugging and unplugging
>	the thing.

Well, if the moused is to reopen the device, it can resync with
mouse data stream at that moment, I think.

Kazu