From: Pavel Machek <pavel@ucw.cz>
To: Matthew Locke <matt@nomadgs.com>
Cc: David Brownell <david-b@pacbell.net>,
linux-pm@lists.osdl.org,
Preece Scott-PREECE <scott.preece@motorola.com>
Subject: Re: [RFC] PowerOP Take 3, sysfs UI core 2/5
Date: Sat, 5 Aug 2006 12:09:51 +0000 [thread overview]
Message-ID: <20060805120950.GB5417@ucw.cz> (raw)
In-Reply-To: <8417055efd530dbc76993e0b1d61de81@nomadgs.com>
Hi!
> Here is the use case we are picturing:
>
> The semiconductor vendor creates the full list of operating points
> supported on a SoC (and reference board). A device (cell phone, etc)
> manufacturer decides to use only a subset of the full operating points
> due to their use cases and board design. We want to enable the
> semiconductor vendor and device manufacturer to easily update the
> operating points and selectively enable ones for their use in a way
> that doesn't require maintaining out of tree patches or submitting
> patches for every update and every device made.
Thats more complex than it needs to be. Easy solution is to allways
compile in full set from semiconductor vendor and then maybe only use
subset.
'Changing kernel is hard, lets do it from initscripts' is perverse
reason for overdesign... (And btw it should be kernel doing the
hardware abstraction, you are turning things upside down).
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-08-05 12:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 19:56 [RFC] PowerOP Take 3, sysfs UI core 2/5 Eugeny S. Mints
2006-07-20 20:00 ` Eugeny S. Mints
2006-07-24 17:29 ` Pavel Machek
2006-07-24 18:48 ` David Brownell
2006-07-24 19:35 ` Pavel Machek
2006-07-24 19:40 ` Matthew Locke
2006-07-24 21:46 ` David Brownell
2006-07-24 21:58 ` Preece Scott-PREECE
2006-07-25 0:32 ` David Brownell
2006-07-25 10:09 ` Amit Kucheria
2006-07-26 5:05 ` David Brownell
2006-07-26 7:24 ` Matthew Locke
2006-08-05 12:09 ` Pavel Machek [this message]
2006-08-07 4:31 ` Vitaly Wool
2006-07-26 21:11 ` Eugeny S. Mints
2006-07-27 0:58 ` David Brownell
2006-07-26 7:44 ` Matthew Locke
2006-07-26 15:03 ` Christian Krafft
2006-07-27 0:55 ` David Brownell
2006-08-01 10:45 ` Matthew Locke
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 23:55 Gross, Mark
2006-08-01 11:16 ` Matthew Locke
2006-08-05 12:05 ` Pavel Machek
2006-07-27 0:14 Gross, Mark
2006-07-27 0:15 Gross, Mark
2006-07-27 0:30 Gross, Mark
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=20060805120950.GB5417@ucw.cz \
--to=pavel@ucw.cz \
--cc=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.org \
--cc=matt@nomadgs.com \
--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