From owner-freebsd-current@FreeBSD.ORG  Wed Dec  7 17:59:28 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3079616A41F;
	Wed,  7 Dec 2005 17:59:28 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9B11C43D46;
	Wed,  7 Dec 2005 17:59:27 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1] (may be forged))
	by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jB7HvL6K030512;
	Wed, 7 Dec 2005 10:57:21 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Wed, 07 Dec 2005 10:57:22 -0700 (MST)
Message-Id: <20051207.105722.60788677.imp@bsdimp.com>
To: darren.pilgrim@bitfreak.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <018e01c5fafe$c9154a20$642a15ac@smiley>
References: <018e01c5fafe$c9154a20$642a15ac@smiley>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0
	(harmony.bsdimp.com [127.0.0.1]);
	Wed, 07 Dec 2005 10:57:21 -0700 (MST)
Cc: current@freebsd.org
Subject: Re: can someone explain...[ PCI interrupts] 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2005 17:59:28 -0000

In message: <018e01c5fafe$c9154a20$642a15ac@smiley>
            "Darren Pilgrim" <darren.pilgrim@bitfreak.org> writes:
: From: John Baldwin
: > 
: > The reason [for masking interrupts] is that PCI interrupts are level
: > triggered, so they won't "shut up" until the ISR has run and pacified
: > the PCI device.
: 
: But PCI interrupts can be programmed either level- or edge-triggered, so
: wouldn't programming to edge-triggered interrupts solve the "they won't shut
: up" issue?

PCI interrupts are level.  There's no way to program them otherwise.

Warner