Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nexus.coast.net!simtel!zombie.ncsc.mil!news.mathworks.com!gatech!howland.reston.ans.net!Germany.EU.net!EU.net!news.sprintlink.net!news.clark.net!rwatson From: rwatson@clark.net (Robert Watson) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Mouse drop nuisance Date: 21 Jun 1995 19:20:29 GMT Organization: The Star-Lit BBS, Bethesda, Maryland, USA Lines: 28 Message-ID: <3s9rdt$ec7@clarknet.clark.net> References: <3rteg9$kr9@gazette.tandem.com> <3s2sea$o9p@gazette.tandem.com> <3s3n5e$5bb@bonnie.tcd-dresden.de> <3s8n0n$fmo@iii1.iii.net> NNTP-Posting-Host: clark.net Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 PL2] : I'm pretty sure that Bruce's driver takes care of mice properly. At : least I didn't do anything special on the one system I set up : that had a FIFO on the mouse port. : >If a 1200-Baud serial mouse causes silo overflows, there might be another : >problem hidden. : Agreed. At roughly 8ms per character you shouldn't have any trouble : with silo overflows. : None of the systems here (and at the moment there are four) have : 16550's for the mice, and none have problems. The slowest is a 486SX25. Under several pieces of software I've developed under DOS, I've found that enabling the 16550a FIFO under an MS mouseis a really bad idea ;). I got a lagging mouse cursor (eg., move the mouse, wait, see the cursor move.) This also proved the case under Windows 3.1 when a FIFO was left enabled by a badly behaved program. I have my mouse under X running on an 8250 comm chip just fine, and on a pretty minimal processor (386sx20) so I don't think you should have any difficulty with anything faster. If I were you I'd consider a possible IRQ conflict.. -- Robert Watson rwatson@sidwell.edu http://www.sidwell.edu/~rwatson/ The goal of science is to build better mousetraps. The goal of nature is to build better mice.