From owner-freebsd-hackers Thu Jul 2 22:14:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14288 for freebsd-hackers-outgoing; Thu, 2 Jul 1998 22:14:35 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles185.castles.com [208.214.165.185]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14272 for ; Thu, 2 Jul 1998 22:14:27 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA04008; Thu, 2 Jul 1998 21:48:31 -0700 (PDT) Message-Id: <199807030448.VAA04008@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Larry S. Lile" cc: David Greenman , Mike Smith , hackers@FreeBSD.ORG Subject: Re: Problems with irq 9(2)? In-reply-to: Your message of "Wed, 01 Jul 1998 23:16:46 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Jul 1998 21:48:30 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Wed, 1 Jul 1998, David Greenman wrote: > > > >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. > > > > Sounds to me like you aren't acking the interrupt in your ISR. > > Could I get you to take a peek at whats going on? The adapter spec is > at (or at least the pages on the status registers) > http://ppdbooks.pok.ibm.com:80/cgi-bin/bookmgr/bookmgr.cmd/BOOKS/BK8R1001 > /1.4.9.4 > and the code for the driver is at http://anarchy.stdio.com (or you can get > to it at http://www.jurai.net/~winter/tr/tr.html). I have been working > from the MACH source and I can't see what i'm doing wrong. > > Whats got me really confused is bit 1 in the ISRP high (even) which > is called User interrupt blocked? And worst is I can't seem to > reset it. When you say this, have you tried writing a 0 to it? Also, how about this snippet: ADAPTER INTERRUPT ENABLE For PC System with PC I/O Bus: An I/O Write (OUT instruction) to X'0A23' (adapter 0) or X'0A27' (adapter 1) resets and re-enables the adapter interrupt generation circuitry. An I/O read to this address is reserved. Apart from that, I would be asking IBM for help... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message