From owner-freebsd-stable Fri Nov 17 16:24:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 486E037B479; Fri, 17 Nov 2000 16:24:14 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAI0OCQ08335; Fri, 17 Nov 2000 17:24:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA78952; Fri, 17 Nov 2000 17:24:11 -0700 (MST) Message-Id: <200011180024.RAA78952@harmony.village.org> To: John Baldwin Subject: Re: 4.2-BETA hangs on boot Cc: stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Nov 2000 16:07:40 PST." References: Date: Fri, 17 Nov 2000 17:24:11 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message John Baldwin writes: : Uh.. No. *sigh* The code checks to see if the specified irq passed : in is 0 (since 0 can never be a valid irq, it is used as a magic : cookie) and the device goes into polling mode if it is. So both no : irq and an irq of 0 provide polling mode. Does that make sense? irq 0 is polling mode. We rely on the fact that resources that haven't been set default to 0. We do a get on the irq resource and if it is 0, we do polling because 0 is an invalid irq. We also go into polling mode if we have an invalid IRQ. The release notes might not say this (I haven't checked), but that's how the code works. Actually, there may be a few problems with the code, which I'll take a look at them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message