View Single Post
  #1240 (permalink)  
Old 02-14-2011, 09:17 PM
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
ahh booo yeah thats what im tlaking about.


I have to flash like crazy to continue kernel dev. unless i kexec or go back to sdcard temporarily
Wonder if that's why magldr just uses the zImage and initrd.gz from the first partition. Then you could use the update utility to update them without having to ever flash again.

On a side note, I would double check with the Vogue guys to make sure everything does get wiped when they update their kernel. I'm still wondering if partition tables may have something to do with this. Hopefully I can finally get a break from work and home to actually do some serious testing. I find it really odd that the partition table has two partitions that start at the same location rather than simply erasing the second partition and moving the locations of everything.
Reply With Quote