[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1158084871.28991.489.camel@localhost.localdomain>
Date: Tue, 12 Sep 2006 14:14:30 -0400
From: Jim Gettys <jg@...top.org>
To: Pavel Machek <pavel@....cz>
Cc: Jordan Crouse <jordan.crouse@....com>,
"Brown, Len" <len.brown@...el.com>,
Linux Kernel ML <linux-kernel@...r.kernel.org>,
Dominik Brodowski <linux@...inikbrodowski.net>,
ACPI ML <linux-acpi@...r.kernel.org>,
Adam Belay <abelay@...ell.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
Arjan van de Ven <arjan@...ux.intel.com>, devel@...top.org,
Bjorn Helgaas <bjorn.helgaas@...com>
Subject: Re: ACPI: Idle Processor PM Improvements
On Tue, 2006-09-12 at 11:21 +0200, Pavel Machek wrote:
> Ok, so what is needed is message to X "we are suspending", and X needs
> to respond "okay, I'm ready, no need for console switch".
This presumes an external agent to X controlling the fast
suspend/resume, with messages having to flow to and from X, and to and
from the kernel, with the kernel in the middle.
Another simpler option is X itself just telling the kernel to suspend
without console switch, as the handoff of the display to the DCON chip
has to be done with X and with an interrupt signaling completion of the
handoff. This would be triggered by an inactivity timeout in the X
server.
I'm not sure which is best right now: generality vs. simplicity. We
just got samples of hardware to do some prototyping on in the last two
weeks. (see wiki.laptop.org for photographs of our screen and the DCON
in action).
>
> Alternatively, hack kernel to take control from X without actually
> switching consoles. That should be possible even with current
> interface.
This would require saving/restoring all graphics state in the kernel
(and X already has that state internally). Feasible, but seems like
duplication of effort. I haven't checked if there are any write-only
registers in the Geode (though, thankfully, this kind of brain damage is
rarer than it once was). This then begs interesting kernel/X
synchronization issues, of course.
- Jim
> Pavel
--
Jim Gettys
One Laptop Per Child
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists