From owner-freebsd-current Fri Jun 7 5:38:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 69BDD37B400; Fri, 7 Jun 2002 05:38:06 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id IAA27557; Fri, 7 Jun 2002 08:37:56 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g57CbQR04995; Fri, 7 Jun 2002 08:37:26 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15616.43270.402875.599246@grasshopper.cs.duke.edu> Date: Fri, 7 Jun 2002 08:37:26 -0400 (EDT) To: ticso@cicely.de Cc: "M. Warner Losh" , gallatin@cs.duke.edu, des@ofug.org, alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: alpha can't map interrupt In-Reply-To: <20020607100947.GE66505@cicely5.cicely.de> References: <15616.3530.526275.555196@grasshopper.cs.duke.edu> <20020606.203133.49601620.imp@village.org> <20020607100947.GE66505@cicely5.cicely.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bernd Walter writes: > > > > An interrupt line of 0 is *NOT* valid. However, the check for zero > > OK - it's fixed for now, but what is wrong with zero? Nothing is wrong with it unless you're on an x86, where I assume some (broken) BIOSes assign unrouted interrupts to zero rather than 255. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message