View Single Post
  #2113 (permalink)  
Old 03-25-2011, 01:31 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 - 03-11: FRX05 on NAND (data working again!)

ACL, I've been trying to find a way to get recovery loaded from our NBH. There are only two things I can think of.

First, cat an image of recovery out to the sdcard and then cat it onto the end of the payload. I'd have to figure out padding to get it to write to the correct offset, and I'm not sure if it would mess anything else up since we'd be writing blank or padded values to that protected area of NAND.

The other alternative is that we include recovery.tgz in initrd and have init check /recovery to see if recovery is there yet. If not, extract it from the initrd and launch into it. This way we can still update recovery, but it gets deployed if it doesn't exist.

What do you think?
__________________

Last edited by natemcnutty; 03-25-2011 at 02:10 PM.
Reply With Quote