From owner-acpi-jp@jp.freebsd.org  Thu Jul 26 19:03:59 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id TAA88004;
	Thu, 26 Jul 2001 19:03:59 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.dis.org (sat.dis.org [216.240.44.14])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id TAA87996;
	Thu, 26 Jul 2001 19:03:56 +0900 (JST)
	(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.4/8.11.3) with ESMTP id f6Q2SgI02965;
	Wed, 25 Jul 2001 19:28:42 -0700 (PDT)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200107260228.f6Q2SgI02965@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Grover, Andrew" <andrew.grover@intel.com>
cc: "'Mitsuru IWASAKI'" <iwasaki@jp.FreeBSD.org>, acpi-jp@jp.FreeBSD.org,
        msmith@freebsd.org
In-reply-to: Your message of "Wed, 25 Jul 2001 10:07:30 PDT."
             <4148FEAAD879D311AC5700A0C969E89006CDDFB7@orsmsx35.jf.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 25 Jul 2001 19:28:42 -0700
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1195
Subject: [acpi-jp 1195] Re: ACPICA 20010717: S1 causes power-off 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> Applied to our tree.
> 
> > # yes, FreeBSD has experimental S[2-4] sleep support.
> 
> You guys are really making progress. Are you doing device power management
> yet?

Our PCI code needs a moderate amount of work (the way that the ACPI 
device tree shadows the PCI tree is just... ugly) for this, but it's 
getting there.  I wrote some power resource handling code, but it's not 
working on my test system (does anyone have fans that the thermal code is 
switching correctly?), so not quite yet. 8)

The other ugly animal is the two-phase process required to shift system 
power states (first pass to request, second pass to either confirm or 
cancel).  Our current architecture is a very simplistic suspend/resume 
hook pair.

Regards,
Mike

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


