View Single Post
  #28 (permalink)  
Old 01-04-2011, 08:11 PM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: 12/19: Need testers for kernel that can simultaneously battery save and overclock

Quote:
Originally Posted by steveholtam View Post
Sorry to rehash this old thread, but I would like to confirm that bzo's changes from this kernel are a) in all the new kernels, like from F22/Wistilt, etc, and b) should we no longer have a pm.sleep_mode command or just use pm.sleep_mode=1 in our startups?

Thanks!
F22 builds from the git because autobuild is currently down. These changes were pushed a while ago, and all of his builds that are directly from git will have the patch in it.

As for WisTilt, he does a lot more experimental stuff, but I'm confident he keeps his local tree up to date and makes changes from there. That means all of his test kernels should have this fix in it as well.

As for using pm.sleep_mode=1, you do need to leave that in your startup.txt. I believe there are three modes: 0,1,2. I'm not sure what the default is off the top of my head.
Reply With Quote
This post has been thanked 3 times.