From owner-freebsd-hackers Wed Dec 12 15:33:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C090637B419 for ; Wed, 12 Dec 2001 15:33:56 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBCNdl103670; Wed, 12 Dec 2001 15:39:47 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112122339.fBCNdl103670@mass.dis.org> To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: irq In-Reply-To: Message from Terry Lambert of "Wed, 12 Dec 2001 10:49:40 PST." <3C17A6C4.FDBDE16C@mindspring.com> Date: Wed, 12 Dec 2001 15:39:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > You should look at recent PCI revisions, however, and the MSI > > (message-signalled interrupt) mechanism which, if implemented widely, > > will solve at least some of the major problems with PCI and interrupts. > > Thanks for the pointer; I haven't been following PCI standards > recently, except for speed and size extensions. It looks like > it's time to look at them yet again. Do you know if this is going > to be mandatory for PCI-X devices? I don't think it will be very > widely used until it's required. 8^(. MSI isn't mandatory; it requires host chipset support. I've read several new peripherals claiming to support it, but haven't been looking at host chipsets to see if it's been picked up there. What would be *really* nice would be a 'shadow' MSI implementation where the host chipset would emulate MSI for non-MSI peripherals. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message