On 7/21/07, Pavel Machek <[EMAIL PROTECTED]> wrote: > I'm not sure it is good idea. We should either let cpu frequency > scaling do its job during suspend (it should just scale to the max > when it sees cpu load), or force it to _minimum_. Machines will > overheat on max cpufreq, and they may overload their batteries.
What? Minimum... Let's talk in numbers... It takes my machine 24 seconds to suspend with max freq. It takes my machine 45 seconds to suspend with load freq (Automatically set by cpufreqd when battery is low). I've never heard that machie can overheat by cpufreq, if they do, it is a good receipt to damage computers. This is bad hardware design and is nothing to do with suspend, as any other program can damage the computer while it is on. I guess you can calculate (You know better than I do) leaving all peripheral (LCD + USB + Disk + Network) on for 100% more or just increase CPU frequency... Also there is an issue with user experience... Best Regards, Alon Bar-Lev. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
