From owner-freebsd-mobile Sun Nov 2 21:21:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA07332 for mobile-outgoing; Sun, 2 Nov 1997 21:21:49 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA07321 for ; Sun, 2 Nov 1997 21:21:41 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id WAA13465; Sun, 2 Nov 1997 22:20:19 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA05479; Sun, 2 Nov 1997 22:20:17 -0700 (MST) Date: Sun, 2 Nov 1997 22:20:17 -0700 (MST) Message-Id: <199711030520.WAA05479@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Nate Williams , Guido van Rooij , freebsd-mobile@freebsd.org Subject: Re: problems after PAO -> 2.2.5 stable In-Reply-To: <199711030440.PAA01498@word.smith.net.au> References: <199711030422.VAA05299@rocky.mt.sri.com> <199711030440.PAA01498@word.smith.net.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Tuple #6, code = 0x1b (Configuration entry), length = 7 > > > 000: 21 08 aa 60 f8 02 07 > > > Config index = 0x21 > > > Card decodes 10 address lines, 8 Bit I/O only > > > I/O address # 1: block start = 0x2f8 block length = 0x8 > > > > You left out the part of the 'supported IRQs' or whatever it says. > > Ah. No, I didn't - there isn't one. > > Does this mean that pccardd will prefer the IRQ from the CIS tuple over > that from the pccard.conf file? No, it won't. But the card may not work if the IRQ from the pccard.conf doesn't match the one in the CIS. The FreeBSD pccardd doesn't do anything with the CIS IRQ list in any case. > > > This *works*. To me, it is clear that the IRQ parameter from the > > > pccard.conf entry is being propagated to the sio probe/attach. > > > > Yes, but in the CIS tuple, some cards claim to support only some > > interrupts, so if you use a different interrupt for that index then they > > don't work. > > 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. Nate