From owner-freebsd-current Wed Nov 13 10:52:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA05892 for current-outgoing; Wed, 13 Nov 1996 10:52:10 -0800 (PST) Received: from ravenock.cybercity.dk (disn41.cybercity.dk [194.16.57.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA05843 for ; Wed, 13 Nov 1996 10:52:04 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id TAA21608; Wed, 13 Nov 1996 19:52:45 +0100 (MET) Message-Id: <199611131852.TAA21608@ravenock.cybercity.dk> Subject: Re: your mail To: bde@zeta.org.au (Bruce Evans) Date: Wed, 13 Nov 1996 19:52:32 +0100 (MET) From: "Soren Schmidt" Cc: nate@mt.sri.com, freebsd-current@FreeBSD.org, jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu In-Reply-To: <199611131804.FAA11738@godzilla.zeta.org.au> from "Bruce Evans" at Nov 14, 96 05:04:36 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Bruce Evans who wrote: > > > >> The fix also broke PS/2 mouse support. :( :( > > > >I know :(, but so long as we occasionally looses an interrupt, there > >is not much else to do. Or merge syscons and the ps/2 mousedriver. > > Lots can be done: > - back out fix OR Bad idea keyboards will hang all over the globe... > - poll less often (fixed period) OR > - poll less often (after keyboard has been inactice for a while) OR Will still break the psm device, just more seldom... > - make fix a compile time option OR > - make fix a run time option OR Hmm, run time optime could be an idea... > - check for psm interrupt and don't poll keyboard if one is pending OR which bits to poll for that ??, and its difficult to know if a keyboard int has been lost already, so who's data is it we're reading... What I'd like to see was that we found out WHY/WHERE we are loosing the interrupt, it seems we have this problem from time to time, and I can't help it, but I still think our interrupt system is the prime suspect... The problem is that there aren't many people that understand it (hint hint)... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end ..