From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 09:43:23 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 523C516A4CF for ; Fri, 28 May 2004 09:43:23 -0700 (PDT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1966043D48 for ; Fri, 28 May 2004 09:43:23 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 22633 invoked from network); 28 May 2004 16:36:16 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 28 May 2004 16:36:16 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4SGaDSX029104; Fri, 28 May 2004 12:36:13 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: "Brown, Len" Date: Fri, 28 May 2004 12:36:52 -0400 User-Agent: KMail/1.6 References: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> In-Reply-To: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405281236.52812.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org Subject: Re: Bug? PCI link device _SRS X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2004 16:43:23 -0000 On Thursday 27 May 2004 04:55 pm, Brown, Len wrote: > John, > Dunno if FreeBSD works the same way, > but we recently fixed a couple of interesting > platform isssue using PCI Interrupt Links > on Linux. > > 1. The enabled bit from _STA for > PCI Interrupt Link devices is meaningless > on many platforms, ignore it. Ok, thanks. > If a platform gives you a _CRS IRQ that > is outside the _PRS list, then do no > stick with the _CRS -- select > a new (valid) one from the _PRS list. Ah, I have a patch to do this already that I can commit. > If a platform gives you a _CRS IRQ that > is different from the _SRS you just > invoked. Assume that the _SRS worked > and that the _CRS is bogus. Huh, we don't do that type of checking, but we do use _CRS for later devices routed to the same link to see what IRQ they should use. > http://bugzilla.kernel.org/show_bug.cgi?id=1581 > > 2. Blindly programming all PCI Interrupt Link Devices > turns out to be a bad idea. Instead, they should > be programmed only when PCI devices using them are > installed and enabled in the system. > http://bugzilla.kernel.org/show_bug.cgi?id=2574 Yes, we already do this as well. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org