Date: Mon, 22 Dec 2003 16:43:32 -0700 From: James Earl <james@icionline.ca> To: Kevin Oberman <oberman@es.net> Cc: freebsd-current@freebsd.org Subject: Re: Continued problems with Aironet device and 5.2-RC Message-ID: <1072136612.81706.54.camel@work.ici> In-Reply-To: <20031222211659.E2FF55D04@ptavv.es.net> References: <20031222211659.E2FF55D04@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1072136612.81706.54.camel>