From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Bird Subject: Re: PowerOp Design and working patch Date: Mon, 07 Aug 2006 12:45:31 -0700 Message-ID: <44D7985B.6080508@am.sony.com> References: <20060729004546.GA3917@kroah.com> <1c70fd37e4eb876295e0194e2b8725d6@mvista.com> <44CBB1E0.3030908@gmail.com> <62e4476a851bbed395b509023edc5c5c@mvista.com> <215c230e2979117fd14d83ea2fd83054@embeddedalley.com> <287a694aae15b3fba505f4381c95c9c8@mvista.com> <44CFA2F5.1070707@am.sony.com> <20060806221104.GB4205@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20060806221104.GB4205@ucw.cz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Pavel Machek Cc: David Singleton , linux-pm@lists.osdl.org, david singleton List-Id: linux-pm@vger.kernel.org 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Tim Bird Architecture Group Chair, CE Linux Forum Senior Staff Engineer, Sony Electronics =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D