From owner-freebsd-arch@FreeBSD.ORG Mon Nov 20 21:08:07 2006 Return-Path: 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 2FAB916A4A0 for ; Mon, 20 Nov 2006 21:08:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D48A43D6E for ; Mon, 20 Nov 2006 21:07:35 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kAKL7mBu078143; Mon, 20 Nov 2006 16:07:48 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: John Polstra Date: Mon, 20 Nov 2006 15:49:21 -0500 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611201549.21685.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 20 Nov 2006 16:07:48 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2208/Mon Nov 20 12:20:46 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-arch@freebsd.org Subject: Re: Where do MSI quirks belong? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 21:08:07 -0000 On Monday 20 November 2006 13:49, John Polstra wrote: > On 20-Nov-2006 John Baldwin wrote: > > On Sunday 19 November 2006 23:11, John Polstra wrote: > >> First, I assume that whether MSI works or not is at least partially > >> a function of the motherboard and maybe the BIOS, as opposed to the > >> chipset. Is that right? At least on this Tyan board, there seem > >> to be some nice kenv variables (e.g., smbus.planar.product) already > >> set that could help me recognize the board. Is that a reasonable > >> approach? > > > > It's going to be a function of the chipset, as something in the chipset > > (presumably a Host -> PCI bridge) has to listen for writes to 0xfeeXXXXXX and > > convert them into APIC messages. > > Hmm, this Tyan 2721 board has the Intel E7501 chipset. Isn't it > supposed to support MSI? It doesn't work, and that's why I thought > the motherboard might also be a factor. I'll paste in the pciconf > output below. I'm not sure if 7501 works or not. Scott might know if there are errata for it. -- John Baldwin