From: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@lists.osdl.org, matthew.a.locke@comcast.net,
scott.preece@motorola.com
Subject: Re: community PM requirements/issues and PowerOP [Was: Re: So, what's the status on the recent patches here?]
Date: Sun, 17 Sep 2006 14:41:39 +0200 [thread overview]
Message-ID: <20060917124139.GA2812@elf.ucw.cz> (raw)
In-Reply-To: <200609150300.k8F30dXt028656@olwen.urbana.css.mot.com>
Hi!
> | > > You got the rules wrong. "Keep the code out of kernel" is important
> | > > rule, but probably not the main one.
> | >
> | > from aside, it looks like you're choosing 'rules' and assign then
> | > 'priorities' in a too arbitrary way which is by a strange accident
> | > fits your point of view best of all.
> | > May I remind you that Linux world is not only laptops and Sharp Zaurus? ;)
> |
> | Actually, laptops and zauruses seem to be the only "interesting"
> | machines from pm perspective. Then there are Motorola cellphones, but
> | Motorola tried hard not to enable users changing kernel... so they are
> | irrelevant.
>
> It would be interesting to see a breakdown by numbers as to where most
> copies of Linux are. If embedded devices aren't the leader now, they
> will be soon.
"Relevant" devices are those where the end-users can change the
kernel. Because that's where the developers are and this area
desperately needs more developers.
Of course, *most* copies are eventually going to end up in linux-based
smartcards. But as those are not going to be hackable, so they are
irrelevant.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-09-17 12:41 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 3:00 community PM requirements/issues and PowerOP [Was: Re: So, what's the status on the recent patches here?] Scott E. Preece
2006-09-17 12:41 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-25 12:43 Scott E. Preece
2006-09-15 3:16 Scott E. Preece
2006-09-17 12:48 ` Pavel Machek
2006-09-15 3:05 Scott E. Preece
2006-09-11 7:57 Eugeny S. Mints
2006-09-11 8:20 ` Pavel Machek
2006-09-11 9:47 ` Eugeny S. Mints
2006-09-11 19:36 ` Pavel Machek
2006-09-11 19:53 ` Matthew Locke
2006-09-11 20:06 ` Pavel Machek
2006-09-11 20:09 ` Pavel Machek
2006-09-11 20:33 ` Matthew Locke
2006-09-11 21:06 ` Pavel Machek
2006-09-11 21:50 ` Matthew Locke
2006-09-11 22:50 ` Pavel Machek
2006-09-12 3:31 ` Greg KH
2006-09-12 8:26 ` Matthew Locke
2006-09-13 4:22 ` David Brownell
2006-09-11 20:25 ` Matthew Locke
2006-09-11 21:02 ` Pavel Machek
2006-09-12 3:26 ` Greg KH
2006-09-11 22:00 ` Mark Gross
2006-09-11 22:08 ` Matthew Locke
2006-09-11 20:24 ` Eugeny S. Mints
2006-09-11 20:34 ` Pavel Machek
2006-09-13 4:54 ` David Brownell
2006-09-13 11:39 ` Preece Scott-PREECE
2006-09-14 9:12 ` Pavel Machek
2006-09-14 9:16 ` Vitaly Wool
2006-09-14 9:20 ` Matthew Locke
2006-09-14 10:05 ` Eugeny S. Mints
2006-09-14 10:17 ` Pavel Machek
2006-09-14 10:47 ` Eugeny S. Mints
2006-09-14 12:15 ` Vitaly Wool
2006-09-14 13:03 ` Pavel Machek
2006-09-14 13:04 ` Pavel Machek
2006-09-14 13:15 ` Vitaly Wool
2006-09-14 13:20 ` Pavel Machek
2006-09-14 13:26 ` Vitaly Wool
2006-09-14 14:59 ` David Brownell
2006-09-17 10:53 ` Amit Kucheria
2006-09-17 13:18 ` Pavel Machek
2006-09-17 13:28 ` Amit Kucheria
2006-09-17 13:40 ` Pavel Machek
2006-09-17 14:14 ` Amit Kucheria
2006-09-17 18:25 ` community PM requirements/issues and PowerOP[Was: " Preece Scott-PREECE
2006-09-18 9:02 ` community PM requirements/issues and PowerOP [Was: " Pavel Machek
2006-09-14 14:56 ` David Brownell
2006-09-17 12:34 ` Pavel Machek
2006-09-17 13:06 ` Vitaly Wool
2006-09-18 10:46 ` Amit Kucheria
2006-09-18 10:53 ` Pavel Machek
2006-09-18 12:01 ` Igor Stoppa
2006-09-14 19:25 ` Jon Loeliger
2006-09-17 12:46 ` Pavel Machek
2006-09-17 17:32 ` Preece Scott-PREECE
2006-09-19 18:20 ` Pavel Machek
2006-09-19 19:11 ` Preece Scott-PREECE
2006-09-23 23:39 ` Pavel Machek
2006-09-14 12:12 ` Vitaly Wool
2006-09-14 12:35 ` Eugeny S. Mints
2006-09-14 9:47 ` Matthew Locke
2006-09-11 19:30 ` Matthew Locke
2006-09-11 19:55 ` Pavel Machek
2006-09-11 20:53 ` Eugeny S. Mints
2006-09-11 21:00 ` Pavel Machek
2006-09-11 21:36 ` Preece Scott-PREECE
2006-09-11 21:39 ` Pavel Machek
2006-09-11 22:41 ` Eugeny S. Mints
2006-09-11 22:05 ` Eugeny S. Mints
2006-10-05 3:30 ` Dominik Brodowski
2006-09-11 21:53 ` Mark Gross
2006-09-11 22:43 ` Pavel Machek
2006-09-12 0:00 ` Mark Gross
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=20060917124139.GA2812@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-pm@lists.osdl.org \
--cc=matthew.a.locke@comcast.net \
--cc=scott.preece@motorola.com \
/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