Date: Thu, 6 Jun 2002 21:35:06 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Dag-Erling Smorgrav <des@ofug.org> Cc: imp@freebsd.org, alpha@freebsd.org, current@freebsd.org Subject: Re: alpha can't map interrupt Message-ID: <15616.3530.526275.555196@grasshopper.cs.duke.edu> In-Reply-To: <xzp660vrjbj.fsf@flood.ping.uio.no> References: <xzp660vrjbj.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner -- a pci interupt line of 0 is valid. Please back out your "PCI_INTERRUPT_VALID" changes in pci.c, or change that macro to allow a value of 0. Thanks, Drew Dag-Erling Smorgrav writes: > A kernel built from last night's sources fails to allocate an > interrupt to the NIC in my Miata: <...> > dc0: <Intel 21143 10/100BaseTX> port 0x9000-0x907f mem 0x80151000-0x8015107f at device 3.0 on pci0 > dc0: couldn't map interrupt > device_probe_and_attach: dc0 attach returned 6 > [...] > > May 26 kernel boots fine: <...> > dc0: <Intel 21143 10/100BaseTX> port 0x9000-0x907f mem 0x80151000-0x8015107f irq 0 at device 3.0 on pci0 <..> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15616.3530.526275.555196>