From owner-freebsd-arch@FreeBSD.ORG  Mon Dec 11 23:32:21 2006
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id D074116A5F5;
	Mon, 11 Dec 2006 23:32:21 +0000 (UTC) (envelope-from jdp@polstra.com)
Received: from blake.polstra.com (blake.polstra.com [64.81.189.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BCB6F43CEA;
	Mon, 11 Dec 2006 23:27:23 +0000 (GMT) (envelope-from jdp@polstra.com)
Received: from strings.polstra.com (strings.polstra.com [64.81.189.67])
	by blake.polstra.com (8.13.8/8.13.8) with ESMTP id kBBNSNxP029680;
	Mon, 11 Dec 2006 15:28:24 -0800 (PST) (envelope-from jdp@polstra.com)
Message-ID: <XFMail.20061211152823.jdp@polstra.com>
X-Mailer: XFMail 1.5.5 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <457D3265.7070004@freebsd.org>
Date: Mon, 11 Dec 2006 15:28:23 -0800 (PST)
From: John Polstra <jdp@polstra.com>
To: Andre Oppermann <andre@freebsd.org>
Cc: freebsd-arch@freebsd.org
Subject: Re: Where do MSI quirks belong? [patch]
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Dec 2006 23:32:21 -0000

On 11-Dec-2006 Andre Oppermann wrote:
> IIRC it is not only a chipset problem but also sometimes how a MSI capable
> chipset is wired on the mainboard.

I agree, that is probably the case.  The pci_get_msi_global_quirks
function is intended to be open-ended in the sense that it should do
whatever it needs to do to figure out whether the system as a whole
can support MSI or not.  The function comment mentions checking kenv
strings as an example.  At this point I don't know all of the other
checks that need to be done, but they should all fit into that
function.

> So some probing would have to be done as well.

Actual probing might be risky.  On my Tyan 2721 motherboard, enabling
MSI wedges the system solid, requiring a HW reset to recover.

John