> > Would that mean that gnome-power-manager and DeviceKit-power
> > would work as-is on the XO-1.5?
>
> I don't think we'd want to run gnome-power-manager because it would
> attempt to do things like manage the backlight, which we want to do
> ourselves as part of aggressive suspend/resume. B
On Jun 25 2009, at 09:49, Chris Ball was caught saying:
> The complexity of implementation is real, but it turned out that Mitch
> had to do the work of adding ACPI tables for Windows anyway. Being
> able to suspend/resume on unmodified distro kernels (and not having to
> constantly maintain and f
Hi,
> Would that mean that gnome-power-manager and DeviceKit-power
> would work as-is on the XO-1.5?
I don't think we'd want to run gnome-power-manager because it would
attempt to do things like manage the backlight, which we want to do
ourselves as part of aggressive suspend/resume. But i
On Thu, Jun 25, 2009 at 15:49, Chris Ball wrote:
> Hi,
>
> > And we will pay the performance cost of ACPI? It was an
> > oft-repeated thing that ACPI was evil because of complexity and
> > slowness in the critical path to super smooth sleep-resume
> > cycles.
>
> > Were we overestimating
Hi,
> And we will pay the performance cost of ACPI? It was an
> oft-repeated thing that ACPI was evil because of complexity and
> slowness in the critical path to super smooth sleep-resume
> cycles.
> Were we overestimating the impact?
Yes, I believe so. We may even find that the
On Wed, Jun 24, 2009 at 9:56 PM, Daniel Drake wrote:
> The end-user interface for those is unlikely to change much (if we do
> the ACPI tables right).
And we will pay the performance cost of ACPI? It was an oft-repeated
thing that ACPI was evil because of complexity and slowness in the
critical pa
On Wed, 2009-06-24 at 15:08 -0400, Paul Fox wrote:
> the input devices /dev/input/event[012] (which currently report
> on power button, ebook, and lid events) are also implemented in
> olpc-pm.c -- i'm not sure what their fate might be.
The end-user interface for those is unlikely to change much (
i was mildly surprised today in a conversation with chris ball
when he implied that the contents of our current (gen1)
/sys/power directory would probably be going away in 1.5. or,
more specifically, he said that arch/x86/kernel/olpc-pm.c would
be going away, and that the wakeup_events and wakeup_
