From: Johnathan Hicks <thetech-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
To: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: An embedded-Linux power-management framework
Date: Sat, 03 Aug 2002 10:50:12 -0400 [thread overview]
Message-ID: <3D4BEDA4.4030908@folkwolf.net> (raw)
In-Reply-To: 1028382470.31718.43.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
> It may make sense on a box with ACPI, but most boxes that are heavily
> STPCLK managed are older. The Athlon one seems to be less interesting
> than the others (btw - seems you can mix stpclk with the other features
> you just have to turn stpclk back off before idling)
Ah yes, I had forgotten about the older hardware, but I thought all they had
was HLT. About the Athlon case, STPCLK is used for all the power management
that I can think of except HLT. Feel free to correct me here if I'm wrong.
> On a K5/K6/486/.. STPCLK is basically your entire power management
> barring what lurks on the PCI devices - which can save a suprising
> amount of power too. I've been playing (not very successfully at the
> moment) at dropping my video card into D3 when screenblanking
What kind of delay would that cause when restoring the state of the card? I
would hope not that great of a delay as this kind of action is one that should
be expected.
--John
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-08-03 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 17:28 An embedded-Linux power-management framework Robert C. Paulsen Jr.
[not found] ` <20020802172802.GA32612-o5m52qS82XggC06IV0sn5h2eb7JE58TQ@public.gmane.org>
2002-08-02 19:11 ` Alan Cox
[not found] ` <1028315477.18635.113.camel-MMxVpc8zpTQVh3rx8e9g/fyykp6/JSeS3vcXtXqGYxw@public.gmane.org>
2002-08-02 18:20 ` Hollis Blanchard
[not found] ` <1028312475.23390.63.camel-j9xLUTenKzJXsEFxtoW7CMxtgHpCUUYS@public.gmane.org>
2002-08-02 23:29 ` Alan Cox
2002-08-03 0:48 ` Johnathan Hicks
[not found] ` <3D4B284F.20402-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
2002-08-03 13:47 ` Alan Cox
2002-08-03 14:50 ` Johnathan Hicks [this message]
2002-08-02 23:31 ` Alan Cox
2002-08-03 8:58 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-08-03 1:28 Bishop Brock
[not found] ` <OF94EF243F.A49E95B4-ON86256C09.00716EF4-yJlKWOkj9xhBDgjK7y7TUQ@public.gmane.org>
2002-08-03 13:40 ` Alan Cox
2002-08-03 2:29 Bishop Brock
[not found] ` <OF4415334C.6C7486B8-ON86256C0A.00081BB4-yJlKWOkj9xhBDgjK7y7TUQ@public.gmane.org>
2002-08-03 13:32 ` Alan Cox
[not found] <3D4BEDA4.4030908-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
2002-08-06 14:55 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D4BEDA4.4030908@folkwolf.net \
--to=thetech-pn2jtpibvork1umjsbkqmq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox