Date: Wed, 13 Nov 1996 19:52:32 +0100 (MET) From: sos@FreeBSD.org To: bde@zeta.org.au (Bruce Evans) Cc: nate@mt.sri.com, freebsd-current@FreeBSD.org, jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu Subject: Re: your mail Message-ID: <199611131852.TAA21608@ravenock.cybercity.dk> In-Reply-To: <199611131804.FAA11738@godzilla.zeta.org.au> from "Bruce Evans" at Nov 14, 96 05:04:36 am
next in thread | previous in thread | raw e-mail | index | archive | help
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
..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611131852.TAA21608>