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!news.sprintlink.net!newsie.dmc.com!news.iii.net!iii1.iii.net!not-for-mail From: hdslip@iii1.iii.net (HD Associates) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Mouse drop nuisance Date: 21 Jun 1995 04:58:44 -0400 Organization: HD Associates, Inc. Lines: 26 Message-ID: <3s8n0n$fmo@iii1.iii.net> References: <3rteg9$kr9@gazette.tandem.com> <3s2sea$o9p@gazette.tandem.com> <3s3n5e$5bb@bonnie.tcd-dresden.de> NNTP-Posting-Host: iii1.iii.net In article <3s3n5e$5bb@bonnie.tcd-dresden.de>, J Wunsch <joerg_wunsch@uriah.heep.sax.de> wrote: > >Thanks to Bruce Evans' sio driver... > >Anyway, you certainly won't use a FIFO chip for a mouse. The usual >mouse packets are 5 bytes long, so you will get substantial delays >since the FIFO first has to time out in order to deliver a mouse >sequence. 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. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267