View Single Post
  #1393 (permalink)  
Old 02-28-2011, 04:57 AM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter
 
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: NAND Boot Testing - 01-07: Panel power on/off fixes

Quote:
Originally Posted by [ACL] View Post
Sounds good .. lets see what u got. I talked to stine on fri but he had nothing to say. I'm really drifting away from the kernel development so i need to tend to it right away. I'll try to commit the KB detection tonight but i'll prob wait until i see your changes.

I'm thinking of commiting the sysinit.rc to a new branch since that is pretty much where all the android work happens.
Well, I'm having a weird boot cycle issue I haven't figured out quite yet. I'm going to pull down the latest androidinstall.tgz you have up there, touch that up with the new files, and try again tomorrow. It might also have to do with switching the init.android to the one from our rootfs instead of the one from vogue's tinboot. That's what I get for making 15 changes at once and then testing instead of checking after each change
Reply With Quote
This post has been thanked 1 times.