From owner-freebsd-current@FreeBSD.ORG Mon Dec 22 15:42:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C901D16A4CE for ; Mon, 22 Dec 2003 15:42:34 -0800 (PST) Received: from priv-edtnes11-hme0.telusplanet.net (outbound03.telus.net [199.185.220.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6731C43D4C for ; Mon, 22 Dec 2003 15:42:33 -0800 (PST) (envelope-from james@icionline.ca) Received: from [192.168.19.4] (really [142.179.173.206]) by priv-edtnes11-hme0.telusplanet.netESMTP <20031222234233.BFLE14123.priv-edtnes11-hme0.telusplanet.net@[192.168.19.4]>; Mon, 22 Dec 2003 16:42:33 -0700 From: James Earl To: Kevin Oberman In-Reply-To: <20031222211659.E2FF55D04@ptavv.es.net> References: <20031222211659.E2FF55D04@ptavv.es.net> Content-Type: text/plain Message-Id: <1072136612.81706.54.camel@work.ici> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 22 Dec 2003 16:43:32 -0700 Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Continued problems with Aironet device and 5.2-RC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2003 23:42:34 -0000 On Mon, 2003-12-22 at 14:16, Kevin Oberman wrote: > As I have seen it, the problems are not generally IRQ related, as far as > I can tell. > > As to what devices share interrupts, that depends on BIOS configuration > to some extent. cbb0, cbb1, and any devices connected to those will > always share an irq. On many systems other devices also share this > IRQ. On my T30, the fxp0 and wi0 devices both share this interrupt. > > Most of the resource issues revolve around the addresses to use for I/O > devices. This is partly addressed by start_memory. The > allow_unsupported_io_range tunable also get into a different part of > this issue. The device drivers determine the memory addresses to be used by the device, right? I'm curious to try the an driver from 5.1-RELEASE under 5.2-RC, but I'm not sure if it would be pointless, or too difficult with all the changes that have been made. I don't want to end up with a 5.1-RELEASE kernel when I'm done because I had to replace so much stuff! James