Date: Mon, 24 Mar 2003 14:51:26 -0600 From: Chip Norkus <wd@arpa.com> To: Alexey Zelkin <phantom@FreeBSD.org.ua> Cc: hackers@freebsd.org Subject: Re: KVM mice issues Message-ID: <200303241429.31488.wd@arpa.com> In-Reply-To: <20030324143355.A52752@phantom.cris.net> References: <200303230957.36433.wd@arpa.com> <20030324105024.GE23857@sunbay.com> <20030324143355.A52752@phantom.cris.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303241429.31488.wd>