Date: Wed, 1 Jul 1998 15:58:26 -0400 (EDT) From: "Larry S. Lile" <lile@stdio.com> To: Mike Smith <mike@smith.net.au> Cc: hackers@FreeBSD.ORG Subject: Re: Problems with irq 9(2)? Message-ID: <Pine.SUN.3.91.980701155042.13549E-100000@heathers2.stdio.com> In-Reply-To: <199807011910.MAA00908@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Jul 1998, Mike Smith wrote: > > > > Does anybody know if there are problems with interrupt blocking > > when using interrupt 9(2)? I am having problems with my token > > ring card getting into a user blocked interrupt state and cannot > > figure out what to do. This is really screwing up my token > > ring driver development. > > Larry; I meant to get back to you on this earlier, but your previous > message is still buried. > > The short answer is that you can't "block" ISA interupts, so the > problem you're seeing has to be related to how you're talking to the > card. The only confirmation of interrupt delivery that the card will > ever get has to come from your code. I thought that was the entire purpose behind splxxx(), It held off the 8259's until the kernel could process the next interrupt. *confused* Anyway, the card has a register (isrp) that has a bit that shows whether or not the card can interrrupt the 8259 on its irq line. This works for the first interrupt but as soon as I enter an spl loop that bit goes high, saying he can't interrupt, and never drops even after exiting the spl loop. Maybe I am confused about how 8259's work, it has been a long time since I played with that level of the machine, and then it was only for college class under dos. Larry Lile lile@stdio.com 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?Pine.SUN.3.91.980701155042.13549E-100000>