Date: Tue, 28 Jan 2003 13:46:15 +0100 From: Thomas Moestl <tmoestl@gmx.net> To: Harti Brandt <brandt@fokus.fraunhofer.de> Cc: sparc@freebsd.org Subject: Re: strange IRQ assignments Message-ID: <20030128124615.GB288@crow.dom2ip.de> In-Reply-To: <20030128132145.T1102@beagle.fokus.gmd.de> References: <20030128132145.T1102@beagle.fokus.gmd.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2003/01/28 at 13:24:09 +0100, Harti Brandt wrote: > > Hi, > > why is the IRQ for a network card different when I first load the driver? > > harti > > > 501 [root] (catssrv) /usr/src # ifconfig hatm0 up > hatm0: <FORE HE> mem 0x100000-0x1fffff irq 20 at device 2.0 on pci1 > ^^ > > hatm0: ForeRunnerHE 155, Rev. B, S/N 5705534, MAC=00:20:48:57:0f:3e > 502 [root] (catssrv) /usr/src # kldunload if_hatm > hatm0: detached > 503 [root] (catssrv) /usr/src # ifconfig hatm0 up > hatm0: <FORE HE> mem 0x100000-0x1fffff irq 2004 at device 2.0 on pci1 > ^^^^ This is because the MD PCI code changes the PCI interrupt numbers by or-ing with a bridge-specific offset upon allocation (usually 0x7c0) to get the real interrupt numbers. The MI PCI code will write the actual resources returned by the allocation into the corresponding resource list, so that the changed number will be displayed next time. This is admittedly ugly, but both numbers will work just the same. - Thomas -- Thomas Moestl <tmoestl@gmx.net> http://www.tu-bs.de/~y0015675/ <tmm@FreeBSD.org> http://people.FreeBSD.org/~tmm/ PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030128124615.GB288>