From owner-freebsd-mobile@FreeBSD.ORG Mon May 26 22:13:00 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF52C37B401 for ; Mon, 26 May 2003 22:13:00 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C844C43F75 for ; Mon, 26 May 2003 22:12:59 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4R5CukA051839; Mon, 26 May 2003 23:12:56 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 26 May 2003 23:12:20 -0600 (MDT) Message-Id: <20030526.231220.63442418.imp@bsdimp.com> To: oberdorf@earthlink.net From: "M. Warner Losh" In-Reply-To: <3ED2ED57.9040203@earthlink.net> References: <3ED0ECFF.1080800@earthlink.net> <20030525.150442.112618580.imp@bsdimp.com> <3ED2ED57.9040203@earthlink.net> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: Orinoco/watchdog timeout - IDE IRQ? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 05:13:01 -0000 In message: <3ED2ED57.9040203@earthlink.net> Oliver Oberdorf writes: : The -i switch to pccardd also had no effect, I assume this is why? Is : there any way I can specify the interrupt for the CB bridge? Not really. We share interrupts when we have a cardbus bridge. Sharing generally works. However, you can use ISA interrupts. See the oldcard man page for details: hw.pcic.intr_path Should PCI pcic devices route interrupts via ISA or PCI. A value of 1 means route via ISA. A value of 2 means route via PCI. This is ignored for the ISA device. Many older laptops do not have PCI BIOS implementations that FreeBSD can use to route interrupts properly. These laptops may need to set this to 1 and hw.pcic.irq to a value (or 0 for polling). The default is 2. : I'm assuming this means that I can't fix the collision and FreeBSD in : it's current form won't support my hardware. If I'm missing something : obvious, let me know :) You are missing something. First, interrupts can be shared. Second, if you have issues with PCI interrupts, you can route via ISA interrupts. Warner