Hi! > >>Well, no one is suggesting a user define and install that info. > >>Operating point creation will be done by someone who understands the > >>system (system designer) regardless of the method used to get the > >>operating points in the kernel. > > > > It sounds to me like they don't want to have to change kernel code and > > recompile the kernel > > to get a new operating point. > > > > It sounds like they are talking about a dynamic operating point as a > > loadable > > module, which would fit perfectly with the PowerOp scheme, since it's > > the > > system designer who would be creating the new dynamic operating point, > > not the user. > > 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. 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. Pavel -- Thanks for all the (sleeping) penguins.
