Date: Mon, 3 Nov 1997 09:28:33 -0700 (MST) From: Nate Williams <nate@mt.sri.com> To: Mike Smith <mike@smith.net.au> Cc: Nate Williams <nate@mt.sri.com>, freebsd-mobile@freebsd.org Subject: Re: problems after PAO -> 2.2.5 stable Message-ID: <199711031628.JAA07134@rocky.mt.sri.com> In-Reply-To: <199711030534.QAA01689@word.smith.net.au> References: <199711030520.WAA05479@rocky.mt.sri.com> <199711030534.QAA01689@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Which component "doesn't work"? The card has no idea which IRQ it's > > > triggering, and AFAIK the pcic doesn't interpret the CIS, nor does the > > > kernel, so I can't see anything other than pccardd that's at fault > > > here... > > > > Don't know. If I try to use the first free irq for my ethernet card it > > doesn't work (I can't remember which one it is, but it is free). > > However, if it's one of the 'accepted' IRQ's, it does work. I have no > > good explanation of why this is the way it is, other than what I stated > > already. > > Well, it sounds like my logic above is screwed. Let's be Sherlock: > > - pccardd doesn't do it (I checked) As did I. > - the kernel doesn't do it (I checked) It never did. > - the card _can't_ do it (it has no idea what IRQ is actually being > generated) Is that true? How do you know that it doesn't know which IRQ is being used via the driver? > So once the impossible has been eliminated, I can only conclude that > the pcic *does* interpret the CIS. But it doesn't, I checked. :) Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711031628.JAA07134>