public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: [RFC] Power Management Policies
Date: Fri, 22 Apr 2005 22:05:50 +0200	[thread overview]
Message-ID: <20050422200549.GF475@openzaurus.ucw.cz> (raw)
In-Reply-To: <20050418093919.37bb40db@cosmic.amd.com>

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

Hi!

> > On the other extreme, we could allow userspace to configure every
> > timeout value, and other policy attributes. 
> 
> With regards to this specifically, in addition to the
> other extremes you mentioned, we also have two different types of
> systems. On one hand, we have open systems, with many different options,
> and plenty of PCI and PCMCIA slots to keep adding new devices. while
> on the other hand, we have closed systems such as cell phones and PDAs,
> where the number of attached devices stays fairly constant.

Notebooks and PDAs are not that different. Both are mostly closed with pcmcia/cf/sd slot...

-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         


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



  reply	other threads:[~2005-04-22 20:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17 21:15 [RFC] Power Management Policies Adam Belay
2005-04-18 15:39 ` Jordan Crouse
2005-04-22 20:05   ` Pavel Machek [this message]
2005-04-27 14:08     ` David Brownell
2005-04-27 14:48       ` Pavel Machek
2005-04-28  0:05         ` David Brownell
2005-04-28  8:23           ` Pavel Machek
2005-04-28 17:16             ` David Brownell
2005-04-28 18:59               ` Pavel Machek
2005-04-28 20:28                 ` David Brownell
2005-04-23  7:18   ` Adam Belay
2005-04-27 14:01     ` David Brownell
2005-04-27 14:22   ` David Brownell
2005-04-27 14:57     ` Jordan Crouse
2005-04-27 16:03       ` David Brownell

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=20050422200549.GF475@openzaurus.ucw.cz \
    --to=pavel@suse.cz \
    --cc=jordan.crouse@amd.com \
    --cc=linux-pm@lists.osdl.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