From owner-freebsd-current@FreeBSD.ORG Fri Dec 5 12:24:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB4A016A4CE for ; Fri, 5 Dec 2003 12:24:46 -0800 (PST) Received: from mail7.speakeasy.net (mail7.speakeasy.net [216.254.0.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91D2A43FF9 for ; Fri, 5 Dec 2003 12:24:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 6169 invoked from network); 5 Dec 2003 20:24:45 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 5 Dec 2003 20:24:45 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id hB5KOfFn021495; Fri, 5 Dec 2003 15:24:41 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20031205103549.Y27123@root.org> Date: Fri, 05 Dec 2003 15:24:58 -0500 (EST) From: John Baldwin To: acpi-jp@jp.FreeBSD.org X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-current@freebsd.org cc: brendon.humphrey@boeing.com cc: Brendon and Wendy Subject: RE: [acpi-jp 2851] Re: Compaq Presario 2105US ACPI = NO MOUSE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 20:24:46 -0000 On 05-Dec-2003 Nate Lawson wrote: > My first order of business after 5.2R will be to import acpica 20031203. > It has a lot of fixes in it that may take care of marginal AML. After > that, I'll be adding code to call _PSx on ACPI-attached devices (not PCI, > that's in imp's tree). This may initialize your hw properly. Hey, I'd actually like some thoughts on the power stuff in the p4 power tree. I want to remove my cruft to just mess with _PSx since the power resource code is much more mature and just use that from the PCI drivers. For that to work correctly however, we will need to perhaps do a pass over the ACPI tree early on (before child PCI bus devices are attached I think) that registers all the producers and consumers. We also might want to fix the register functions to use _PSC if it is available to determine the current power state and then add code to power consumers on before we probe/attach them. Note that with the current power resource code, this would only call _PS0 if it really needed to be called. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/