From: Tim Bird <tim.bird@am.sony.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Singleton <daviado@gmail.com>,
linux-pm@lists.osdl.org, david singleton <dsingleton@mvista.com>
Subject: Re: PowerOp Design and working patch
Date: Mon, 07 Aug 2006 12:45:31 -0700 [thread overview]
Message-ID: <44D7985B.6080508@am.sony.com> (raw)
In-Reply-To: <20060806221104.GB4205@ucw.cz>
Pavel Machek wrote:
>> Often, in the embedded world, the person defining the operating
>> states will not be a kernel developer, and may not be comfortable
>> with, or capable of, creating a kernel module. (There are
>
> That's okay, we can create HOWTO or something. 'System designed is too
> stupid to hack kernel' should not be an argument.
It's not a matter of stupidity. The example I gave of not being
able to create a kernel module was the situation where loadable
module support is not available. A HOWTO wouldn't alter this.
> Maybe operating points need to be changed at runtime -- I do not think
> so -- but *please* get the basic stuff in/merged ASAP and then add
> features one-by-one.
I agree. :-)
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
next prev parent reply other threads:[~2006-08-07 19:45 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 22:31 PowerOp Design and working patch david singleton
2006-07-28 23:38 ` Greg KH
2006-07-29 0:26 ` david singleton
2006-07-29 0:38 ` david singleton
2006-07-29 0:45 ` Greg KH
2006-07-29 5:12 ` david singleton
2006-07-29 19:07 ` Eugeny S. Mints
2006-07-30 4:43 ` david singleton
2006-07-30 11:02 ` Vitaly Wool
2006-08-01 0:59 ` david singleton
2006-08-01 10:09 ` Matthew Locke
2006-08-01 10:22 ` Matthew Locke
2006-08-01 18:31 ` david singleton
2006-08-01 18:52 ` Tim Bird
2006-08-01 18:59 ` david singleton
2006-08-01 19:17 ` Vitaly Wool
2006-08-01 19:28 ` Vitaly Wool
2006-08-06 22:11 ` Pavel Machek
2006-08-07 10:34 ` Igor Stoppa
2006-08-07 19:45 ` Tim Bird [this message]
2006-08-08 10:07 ` Pavel Machek
2006-08-08 11:12 ` Igor Stoppa
2006-08-08 11:33 ` Pavel Machek
2006-08-08 16:43 ` Tim Bird
2006-08-01 12:23 ` Vitaly Wool
2006-08-01 18:25 ` Tim Bird
2006-08-01 18:02 ` Tim Bird
2006-08-06 22:05 ` Pavel Machek
2006-08-07 3:52 ` david singleton
2006-08-07 4:17 ` Greg KH
2006-08-07 4:32 ` Vitaly Wool
2006-07-29 22:09 ` Greg KH
2006-08-01 0:36 ` david singleton
2006-08-01 1:27 ` david singleton
2006-08-07 22:06 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 10:09 Matthew Locke
2006-08-07 14:12 Scott E. Preece
2006-08-07 16:58 ` Greg KH
2006-08-08 13:44 Scott E. Preece
2006-08-08 13:52 ` Pavel Machek
2006-08-08 15:53 ` Matthew Locke
2006-08-08 16:03 ` Matthew Locke
2006-08-08 18:10 ` Igor Stoppa
2006-08-08 13:54 Scott E. Preece
2006-08-08 16:49 ` Tim Bird
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=44D7985B.6080508@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=daviado@gmail.com \
--cc=dsingleton@mvista.com \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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