From owner-freebsd-mobile Wed Oct 22 23:13:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA01787 for mobile-outgoing; Wed, 22 Oct 1997 23:13:06 -0700 (PDT) (envelope-from owner-freebsd-mobile) Received: from u1.farm.idt.net (root@u1.farm.idt.net [169.132.8.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA01781 for ; Wed, 22 Oct 1997 23:13:03 -0700 (PDT) (envelope-from garycorc@idt.net) Received: from idt.net (ppp-54.ts-1.mlb.idt.net [169.132.71.54]) by u1.farm.idt.net (8.8.5/8.8.5) with ESMTP id CAA13126 for ; Thu, 23 Oct 1997 02:13:01 -0400 (EDT) Message-ID: <344EEAB4.752D66BB@idt.net> Date: Thu, 23 Oct 1997 02:12:04 -0400 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.02b7 [en] (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: mobile@FreeBSD.ORG Subject: Re: Patches from -current for -stable I'd like to commit after testing References: <199710230532.PAA00243@word.smith.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith wrote: > > > Can you hold off a couple of days? Something you've changed recently > > has broken PCCARD support on my Toshiba, but I haven't been able to > > track it down yet. > > > > My response: > > > > Can you try out this patch. > > Sure. Doesn't help though. 8( Allocating IRQ 11 to the pcic actually > seems harmless; we still get card insertion/removal interrupts, so it > must be working. > > Unfortunately I just get the dreaded "driver allocation failed for ..." > messages, where I didn't before. > When I had my PCCARD woes yesterday due to a mis-allocated IRQ in my kernel config, I too seemed to get the insertion/removal interrupts (in 2.2.5), but got the "driver allocation failed for..." message in that setup. Once I corrected the situation of having another device on the same IRQ as the ethernet pc-card, then things started working. Of course you're running different code than I am, but was just wondering if that message might be due to the same symptom of an IRQ conflict? I don't know which Toshiba notebook you have Mike, but if it's anything like mine, IRQ 11 is dedicated as the "PCI" interrupt, and has about 3-4 things hung on it - Infrared ports, USB ports, and, hey(?) Win95 assigns the "Toshiba ToPIC97 CardBus Controller"s to IRQ 11 also (the 3C589D gets to use IRQ 10, the only free IRQ, in both W95 and FreeBSD). Don't know if any of this will help the two of you resolve how to automatically assign things, but thought I'd pass it along just in case... Gary