From owner-freebsd-mobile Wed Sep 24 08:27:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA04725 for mobile-outgoing; Wed, 24 Sep 1997 08:27:13 -0700 (PDT) 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 IAA04700; Wed, 24 Sep 1997 08:27:03 -0700 (PDT) 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 JAA01010; Wed, 24 Sep 1997 09:27:01 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA12203; Wed, 24 Sep 1997 09:26:59 -0600 (MDT) Date: Wed, 24 Sep 1997 09:26:59 -0600 (MDT) Message-Id: <199709241526.JAA12203@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Stefan Esser Cc: Nate Williams , mobile@freebsd.org, current@freebsd.org Subject: Re: PCCARD in -current broken In-Reply-To: <19970924144744.47293@mi.uni-koeln.de> References: <199709231929.NAA08312@rocky.mt.sri.com> <19970923230018.00034@mi.uni-koeln.de> <199709232246.QAA09189@rocky.mt.sri.com> <19970924144744.47293@mi.uni-koeln.de> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I assume you are sure that the PCCARD code is only > called after the ISA devices are attached ? In autoconf.c/configure: #if NEISA > 0 eisa_configure(); #endif #if NPCI > 0 pci_configure(); #endif #if NISA > 0 isa_configure(); #endif #if NCRD > 0 /* After everyone else has a chance at grabbing resources */ pccard_configure(); #endif > Well, in fact you should see the "device combination doesn't support ..." > message printed, when you call register_intr() to check for the interrupt > to be available. Hmm, do mobile users see these messages who run -current? > If you don't then there is a good chance, that you perform > this test, before the ISA devices are attached, and there is no collision > reported until the PCCARD attach tries to register a handler for an assumed > free IRQ, which has been claimed by an ISA driver in between ... That shouldn't happen (given the code in autoconf.) Sorry for the false alarm, back to the drawing board. Nate