From owner-freebsd-alpha Tue Oct 26 0:43:47 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 47AF914C1A for ; Tue, 26 Oct 1999 00:43:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA33591; Tue, 26 Oct 1999 08:43:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 26 Oct 1999 08:43:24 +0100 (BST) From: Doug Rabson To: Andrew Gallatin Cc: Terry Lambert , alpha@FreeBSD.ORG Subject: Re: small fix for irq mappig probelm In-Reply-To: <199910260051.UAA09280@storm.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 25 Oct 1999, Andrew Gallatin wrote: > > Terry Lambert writes: > > > > > > de0: irq 0 at device 3.0 on pci0 > > > pci_map_int: can't allocate interrupt > > > > > > > > > The appended patch fixes it, but I am unsure it is correct. Can you > > > approve it? > > > > Same thing on some Intel motherboards, FWIW. SMP seems to be the > > way to fix it; perhaps we could do whatever the equivalent is on > > Alpha? > > Huh? I'm not talking about running out of irqs, I'm talking about > having a valid inline which happens to be zero. > > (Most) Alphas aren't limited to 16 irqs like PCs, even without SMP > support. Many support up to 64 irqs. Starting at 0 & including 0. > > Having 0 as a valid intline is the problem. My patch assumes that an > intpin should never be 0. Is this true? The 'invalid' value for intline is 255 according to the spec. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message