On Fri, Dec 31, 2010 at 12:51:24PM -0600, David Young wrote:
IMO, we should put the system to sleep by sending a
power-saving/wakeup-latency goal and a set of waking events (e.g.,
keystroke, mouse movement, LAN activity) to the root device_t using
drvctl. To put any smaller set of devices to
On 31.12.2010 11:10, Jukka Ruohonen wrote:
On Fri, Dec 31, 2010 at 11:01:08AM +0100, Jean-Yves Migeon wrote:
I am using machdep.sleep_state as node to put a domU into suspend mode.
Up to now, putting sleep_state under machdep allowed powerd(8)
sleep_button to be used regardless of the
On Fri, Dec 31, 2010 at 11:29:23AM +0100, Jean-Yves Migeon wrote:
Seems reasonable to me. We could have a more featureful binary later,
and just alias zzz(8) to it.
We have ready ioctl-facilities in sysmon's sysmon_power.c. I believe it
was originally intended by the author that MD code should
On Fri, 31 Dec 2010, Jukka Ruohonen wrote:
On Fri, Dec 31, 2010 at 11:29:23AM +0100, Jean-Yves Migeon wrote:
Seems reasonable to me. We could have a more featureful binary later,
and just alias zzz(8) to it.
We have ready ioctl-facilities in sysmon's sysmon_power.c. I believe it
was
On Fri, Dec 31, 2010 at 04:54:47AM -0800, Paul Goyette wrote:
However, the current implementation is simply a text string with no
defined semantics. A back-end is able to set the value, and it can be
retrieved via the POWER_IOC_GET_TYPE ioctl, but otherwise nothing uses
the value.
Sure, I
On Fri, Dec 31, 2010 at 11:01:08AM +0100, Jean-Yves Migeon wrote:
On 31.12.2010 10:36, Jukka Ruohonen wrote:
Module Name:src
Committed By: jruoho
Date: Fri Dec 31 09:36:15 UTC 2010
Modified Files:
src/etc/powerd/scripts: sleep_button
Log Message:
On 31.12.2010 19:51, David Young wrote:
IMO, we should put the system to sleep by sending a
power-saving/wakeup-latency goal and a set of waking events (e.g.,
keystroke, mouse movement, LAN activity) to the root device_t using
drvctl. To put any smaller set of devices to sleep, send the goal
