From owner-freebsd-current  Mon Jul 21 11:35:59 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA01754
          for current-outgoing; Mon, 21 Jul 1997 11:35:59 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA01748
          for <current@freebsd.org>; Mon, 21 Jul 1997 11:35:55 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wqNIz-0001sE-00; Mon, 21 Jul 1997 12:35:33 -0600
To: Michael Smith <msmith@atrad.adelaide.edu.au>
Subject: Re: I am contemplating the following change... 
Cc: sef@Kithrup.COM, current@freebsd.org
In-reply-to: Your message of "Tue, 22 Jul 1997 03:10:00 +0930."
		<199707211740.DAA24549@genesis.atrad.adelaide.edu.au> 
References: <199707211740.DAA24549@genesis.atrad.adelaide.edu.au>  
Date: Mon, 21 Jul 1997 12:35:33 -0600
From: Warner Losh <imp@rover.village.org>
Message-Id: <E0wqNIz-0001sE-00@rover.village.org>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199707211740.DAA24549@genesis.atrad.adelaide.edu.au> Michael Smith writes:
: On top of that, working out which interrupt the card is on is not
: easy.  There isn't some convenient register that you can read for
: this. 8(

I'd settle for working out that the current interrupt isn't right,
even if you can't tell me which one it should be.  That would at least
alert me to the fact that there is a problem, which is an incremental
improvement over today's world.

Warner