From owner-freebsd-current Thu Aug 16 0:56:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id D0D2337B406 for ; Thu, 16 Aug 2001 00:56:21 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f7G7u8c302956; Thu, 16 Aug 2001 16:56:08 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f7G7u8K70542; Thu, 16 Aug 2001 16:56:08 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:QjrZr4XSKlUEp3ZYDLKuLp1JyFBsiQOh@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id RAA09417; Thu, 16 Aug 2001 17:05:44 +0900 (JST) Message-Id: <200108160805.RAA09417@zodiac.mech.utsunomiya-u.ac.jp> To: tlambert2@mindspring.com Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: psmintr: out of sync (was: Re: FreeBSD's aggressive keyboard probe/attach) In-reply-to: Your message of "Wed, 15 Aug 2001 23:48:52 MST." <3B7B6CD4.16697200@mindspring.com> References: <200108150924.SAA06230@zodiac.mech.utsunomiya-u.ac.jp> <200108151347.f7FDl6W23619@harmony.village.org> <200108160225.LAA08355@zodiac.mech.utsunomiya-u.ac.jp> <3B7B6CD4.16697200@mindspring.com> Date: Thu, 16 Aug 2001 17:05:44 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> If disable/enable sequence, which is lot simpler and takes considrably >> less time, can correct the sync problem, I think it will be better. > >It looks to me as if the mouse is automatically enabled by >default after a reset? No, the mouse is disabled after reset. We need to explicitly enable it. This will be done during our re-initialization sequence. >If this is true, then doing a disable >then a reset will result in the next mouse packet coming in >on a correct boundary. It makes the reset a tiny bit more >complicated, but makes the results more deterministic. Yes. We can expect we get the packet boundary right after the reset command followed by the enable command. And that's why we shall reset the "error counter" to zero after reset/reinitialize. >I don't know what to tell you, if the keyboard goes away during >the reset process: it seems counter-intuitive, and it means you >can't use keyboard shortcuts to get to a mouse "control panel" >to fix the problem manually... 8-(. The keyboard won't be inaccessible during the mouse reset sequence. Its data won't be lost (in theory). But, you just feel the keyboard is not responding quickly... Anyway, I shall make a patch and we test it to see how it behaves... >I think if that's unavoidable, a simple comment to that effect >in the code would save you loads of grief later. > >-- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message