From owner-freebsd-mobile  Sun Nov  2 20:48:49 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA05883
          for mobile-outgoing; Sun, 2 Nov 1997 20:48:49 -0800 (PST)
          (envelope-from owner-freebsd-mobile)
Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA05870
          for <freebsd-mobile@freebsd.org>; Sun, 2 Nov 1997 20:48:39 -0800 (PST)
          (envelope-from mike@word.smith.net.au)
Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id PAA01498;
	Mon, 3 Nov 1997 15:10:57 +1030 (CST)
Message-Id: <199711030440.PAA01498@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Nate Williams <nate@mt.sri.com>
cc: Mike Smith <mike@smith.net.au>, Guido van Rooij <guido@gvr.org>,
        freebsd-mobile@freebsd.org
Subject: Re: problems after PAO -> 2.2.5 stable 
In-reply-to: Your message of "Sun, 02 Nov 1997 21:22:28 PDT."
             <199711030422.VAA05299@rocky.mt.sri.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 03 Nov 1997 15:10:56 +1030
From: Mike Smith <mike@smith.net.au>
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?

> > 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...

mike