From owner-freebsd-hackers Wed Jul 1 12:11:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03682 for freebsd-hackers-outgoing; Wed, 1 Jul 1998 12:11:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03666 for ; Wed, 1 Jul 1998 12:11:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00908; Wed, 1 Jul 1998 12:10:47 -0700 (PDT) Message-Id: <199807011910.MAA00908@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Larry S. Lile" cc: hackers@FreeBSD.ORG Subject: Re: Problems with irq 9(2)? In-reply-to: Your message of "Wed, 01 Jul 1998 14:46:22 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Jul 1998 12:10:46 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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. -- \\ 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