Date: Tue, 21 Jan 1997 18:30:03 -0700 (MST) From: Nate Williams <nate@mt.sri.com> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: nate@mt.sri.com (Nate Williams), mobile@freebsd.org Subject: Re: What PCMCIA ethernet card supported/recommended? Message-ID: <199701220130.SAA23116@rocky.mt.sri.com> In-Reply-To: <199701220104.LAA10230@genesis.atrad.adelaide.edu.au> References: <199701220059.RAA22967@rocky.mt.sri.com> <199701220104.LAA10230@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Avoid 'combo' modem/ether cards; they're not supported (and would be a > > > royal pain in the rear to support, in fact). > > > > Actually, I've been looking at the code recently, and most of the code > > is already sutup to have multiple-drivers/card, so it's less hard than I > > originally thought. > > 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( ) That's the fun part. Since the interrupt handler occurs in the pccard code (pcintr()), one has to determine which 'device' generated it. I have the spec., but I haven't looked at it closely, but there's gotta be a way. [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. :) Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701220130.SAA23116>