From owner-freebsd-mobile  Tue Jan 21 17:36:06 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id RAA01044
          for mobile-outgoing; Tue, 21 Jan 1997 17:36:06 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA01027
          for <mobile@freebsd.org>; Tue, 21 Jan 1997 17:36:02 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id SAA23158; Tue, 21 Jan 1997 18:36:00 -0700 (MST)
Date: Tue, 21 Jan 1997 18:36:00 -0700 (MST)
Message-Id: <199701220136.SAA23158@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Nate Williams <nate@mt.sri.com>
Cc: Michael Smith <msmith@atrad.adelaide.edu.au>, mobile@freebsd.org
Subject: Re: What PCMCIA ethernet card supported/recommended?
In-Reply-To: <199701220130.SAA23116@rocky.mt.sri.com>
References: <199701220059.RAA22967@rocky.mt.sri.com>
	<199701220104.LAA10230@genesis.atrad.adelaide.edu.au>
	<199701220130.SAA23116@rocky.mt.sri.com>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > Hmm; how does one go about demuxing the interrupt?   (With the price tag
> > on the PCCARD spec, I'm really forced to guess and infer on stuff
> > like this 8( )
> 
..
> [Digging out my spec.]
> 
> Hmm, nothing obvious jumps out at me, but I suspect that a 'device' sets
> a big in one of the CIS-Tuples that said it generated the IRQ.
> 
> But, I could be completely out to lunch. :)

I found it in a different book.  (They are like 12 of them).

Card Services determines which function has interrupted by reading each
function's INTR bit in the Function Configuration and Status Register
(FCSR).  After the IRS is completed, Card Services will clear the
interrupt by writing a zero to the INTR bit in the function that has
just been serviced.



Nate