From owner-cvs-src@FreeBSD.ORG Tue Apr 6 09:25:05 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DCE116A4CE; Tue, 6 Apr 2004 09:25:05 -0700 (PDT) Received: from mail.wolves.k12.mo.us (duey.wolves.k12.mo.us [207.160.214.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0B8C43D41; Tue, 6 Apr 2004 09:25:04 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 90B811FE73; Tue, 6 Apr 2004 11:24:42 -0500 (CDT) Received: from mail.wolves.k12.mo.us ([127.0.0.1]) by localhost (duey.wolves.k12.mo.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18193-02-14; Tue, 6 Apr 2004 11:24:41 -0500 (CDT) Received: by mail.wolves.k12.mo.us (Postfix, from userid 1001) id 2D14B1FE5F; Tue, 6 Apr 2004 11:24:41 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 2A67A1A90C; Tue, 6 Apr 2004 11:24:41 -0500 (CDT) Date: Tue, 6 Apr 2004 11:24:41 -0500 (CDT) From: Chris Dillon To: "Matthew D. Fuller" In-Reply-To: <20040405222238.GJ1345@over-yonder.net> Message-ID: <20040406104331.K21112@duey.wolves.k12.mo.us> References: <200404041636.i34GaMQT060045@repoman.freebsd.org> <20040405222238.GJ1345@over-yonder.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at wolves.k12.mo.us cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: Mark Murray cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/isa psm.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Apr 2004 16:25:05 -0000 On Mon, 5 Apr 2004, Matthew D. Fuller wrote: > On Sun, Apr 04, 2004 at 09:36:22AM -0700 I heard the voice of > Mark Murray, and lo! it spake thus: > > > Without this, when the mouse gets confused, all sorts of crud gets > > spammed all over the screen. With this, the mouse may appear dead > > for a second or three, but it recovers silently. > > Mine doesn't just "appear dead" when these messages hit; it also > slams a bunch of random movements and keypresses through. Once it > even managed to activate my menus and xlock my screen on me; that > was a neat "Whoah, what did I touch?" moment. I managed to move all kinds of toolbar buttons around and sometimes do bad things every time I switched between machines on my KVM and attempted to move the mouse. Once I got tired of that, I ripped out all of the "discard a byte" code and went straight to reinitialize on the first sign of trouble. This has kept the event spamming down to a minimum after switching back and forth from a Windows 2000 server with my KVM switch, which I do constantly, but it didn't prevent it entirely like Windows does. Whenever I switch over to Windows 2000, upon trying to use the mouse my cursor will stay frozen with no evidence of event spamming until the mouse is reinitialized a second later. I don't understand the psm.c code enough to determine this myself, but, can we check sync before we send out the events and completely discard the data if it is out of sync? If we do this already, why is some of the bad event data making it through our mouse driver, but not the mouse driver in Windows? Do they perform some checks above and beyond sync? -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest, most open, and most stable OS on the planet - Available for IA32, IA64, AMD64, PC98, Alpha, and UltraSPARC architectures - PowerPC, ARM, MIPS, and S/390 under development - http://www.freebsd.org Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon?