From owner-freebsd-hackers Mon Mar 24 12:53:48 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD26C37B401 for ; Mon, 24 Mar 2003 12:53:43 -0800 (PST) Received: from arpa.com (arpa.com [199.245.173.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FA6543F3F for ; Mon, 24 Mar 2003 12:53:43 -0800 (PST) (envelope-from wd@arpa.com) Received: from localhost (localhost [127.0.0.1]) by arpa.com (Postfix) with ESMTP id 9760E20139; Mon, 24 Mar 2003 14:53:40 -0600 (CST) Received: from gondolin (d14-69-64-77.nap.wideopenwest.com [69.14.77.64]) by arpa.com (Postfix) with ESMTP id CD41820136; Mon, 24 Mar 2003 14:53:39 -0600 (CST) From: Chip Norkus Organization: Telekinetic Industries To: Alexey Zelkin Subject: Re: KVM mice issues Date: Mon, 24 Mar 2003 14:51:26 -0600 User-Agent: KMail/1.5 References: <200303230957.36433.wd@arpa.com> <20030324105024.GE23857@sunbay.com> <20030324143355.A52752@phantom.cris.net> In-Reply-To: <20030324143355.A52752@phantom.cris.net> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200303241429.31488.wd@arpa.com> Cc: hackers@freebsd.org Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS snapshot-20020531 X-Spam-Status: No, hits=-25.5 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, RCVD_IN_OSIRUSOFT_COM,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday 24 March 2003 06:33 am, you wrote: > hi, > Hi Alxey, > Yep. In order to avoid moused(8) getting something crazy (after > console switch) I just forced psm reset after synchronization error > detection. It can be achieved by changing changing of > PSM_SYNCERR_THRESHOLD1 define from 20 to 0 (in file sys/isa/psm.c). > > Please try to do it and let me know result, if you're also happy > with solution -- I'll cleanup and commit my patch which forces such > behaviour using sysctl(8). > I tried this. Unfortunately it didn't work for my particular problem. I went back to my original solution (which seems to be pretty MouseMan+ centric unfortunately) of reinitializing the mouse after a protocol error, and I think I have something that works at least as well as the Windows driver. The optimal solution (for me) is to reset the mouse on protocol error and also to set PSM_SYNCERR_THRESHOLD1 to 0 (I get a lot of sync errors after I do a reset.. I imagine I'm doing something incorrectly here :). So far this solution seems to work well, at least I haven't lost my mouse wheel after switching to/from another port on the KVM. When I switch back my mouse acts a bit odd for a moment (the sync errors) and then resets itself and seems to work fine. I'm much happier with a momentarily flaky mouse *with* a mousewheel than a non-flaky mouse without one. If you're interested I can send you the patch I've got. Thanks for your help! -chip -- chip norkus; renaissance hacker; wd@arpa.com "question = (to) ? be : !be;" --Shakespeare http://telekinesis.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message