From owner-freebsd-acpi@FreeBSD.ORG Thu Feb 4 22:33:22 2010 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B7BA106566B; Thu, 4 Feb 2010 22:33:22 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 64C258FC14; Thu, 4 Feb 2010 22:33:21 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA02253; Fri, 05 Feb 2010 00:33:20 +0200 (EET) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1NdAGF-0004Ly-Iq; Fri, 05 Feb 2010 00:33:19 +0200 Message-ID: <4B6B4B2F.2010109@icyb.net.ua> Date: Fri, 05 Feb 2010 00:33:19 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091128) MIME-Version: 1.0 To: John Baldwin References: <4B698DD8.4010404@icyb.net.ua> <201002041657.52232.jhb@freebsd.org> <4B6B4689.4020708@icyb.net.ua> <201002041729.18714.jhb@freebsd.org> In-Reply-To: <201002041729.18714.jhb@freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: acpi_cpu: _PDC vs _OSC X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2010 22:33:22 -0000 on 05/02/2010 00:29 John Baldwin said the following: > But is GCAP loading an additional SSDT? That is what the "loading something" > refers to and I think we've only observed that occurring with _OSC. I'd > rather we only document unexpected quirks that someone has actually reported > and not assume that just because an _OSC method on some box did it, there's > bound to be a _PDC method on some other box that does it. In truth, the > comment is probably not needed now anyway since this will always do _OSC > first. I agree with you. Probably the comment is too obvious or too useless now, when such things are a common place. To answer your first question - yes it does: Method (GCAP, 1, NotSerialized) { CreateDWordField (Arg0, Zero, STS0) CreateDWordField (Arg0, 0x04, CAP0) If (LOr (LEqual (STS0, 0x06), LEqual (STS0, 0x0A))) { Return (Zero) } If (And (STS0, One)) { And (CAP0, 0x0BFF, CAP0) Return (Zero) } Or (And (PDC0, 0x7FFFFFFF), CAP0, PDC0) If (And (CFGD, One)) { If (LAnd (LAnd (And (CFGD, 0x01000000), LEqual (And (PDC0, 0x09), 0x09)), LNot (And (SDTL, One)))) { Or (SDTL, One, SDTL) OperationRegion (IST0, SystemMemory, DerefOf (Index (SSDT, One)), DerefOf (Index (SSDT, 0x02 ))) Load (IST0, HI0) } } If (And (CFGD, 0xF0)) { If (LAnd (LAnd (And (CFGD, 0x01000000), And (PDC0, 0x18 )), LNot (And (SDTL, 0x02)))) { Or (SDTL, 0x02, SDTL) OperationRegion (CST0, SystemMemory, DerefOf (Index (SSDT, 0x07)), DerefOf (Index (SSDT, 0x08 ))) Load (CST0, HC0) } } Return (Zero) } -- Andriy Gapon