public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: Nigel Cunningham <ncunningham-3EexvZdKGZRWk0Htik3J/w@public.gmane.org>
Cc: Linux-pm mailing list
	<linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	Adam Belay <abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Subject: Re: Devices eating too much power [was Re: Some thoughts on suspend/resume development]
Date: Sun, 13 Mar 2005 19:14:55 +0100	[thread overview]
Message-ID: <20050313181455.GD1579@elf.ucw.cz> (raw)
In-Reply-To: <1110405336.8870.22.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

Hi!

> > > > This isn't to say that we should copy Windows.  However it does show that 
> > > > a very complex set of controls might not be needed.
> > 
> > Actually, as we already spindown and blank settings, we could finish
> > here :-).
> > 
> > What devices is this targetted at? Video should be handled
> > already (or perhaps we want to power down graphics card when screen is
> > blanked?). Disks spin down too. IRDA ports?
> 
> - Video

X/dpms handles these already.

> - Storage

laptop mode.

> - Hotplug devices
> - CPU power savings

cpufreq.

> - Scanner lights

Ok ;-).

> Anything you might care to imagine :>

Well, I meant something that is not already handled. Like... what
power-hungry device do we fail to properly handle today?

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

[-- Attachment #2: Type: text/plain, Size: 171 bytes --]

_______________________________________________
linux-pm mailing list
linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
http://lists.osdl.org/mailman/listinfo/linux-pm

       reply	other threads:[~2005-03-13 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.0503091111470.1117-100000@ida.rowland.org>
     [not found] ` <1110403931.8870.6.camel@desktop.cunningham.myip.net.au>
     [not found]   ` <20050309214416.GG17034@elf.ucw.cz>
     [not found]     ` <1110405336.8870.22.camel@desktop.cunningham.myip.net.au>
     [not found]       ` <1110405336.8870.22.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-03-13 18:14         ` Pavel Machek [this message]
     [not found]           ` <20050313181455.GD1579-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-13 19:36             ` Devices eating too much power [was Re: Some thoughts on suspend/resume development] Adam Belay
     [not found]               ` <1110742612.12485.287.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-13 21:03                 ` Pavel Machek
     [not found]                   ` <20050313210322.GA7016-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-13 21:55                     ` Adam Belay
     [not found]                       ` <1110750912.25040.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-13 23:11                         ` Pavel Machek
2005-03-21 12:08                 ` Arioch

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=20050313181455.GD1579@elf.ucw.cz \
    --to=pavel-alswssmvlrq@public.gmane.org \
    --cc=abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=ncunningham-3EexvZdKGZRWk0Htik3J/w@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