View Single Post
  #1260 (permalink)  
Old 02-16-2011, 04:36 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
I'll commit that table tonight if you are 100% sure its tested and all kosher .

also here is a good test for anyone.. dump mtd1 (or whereever tinboot is at) and do a binary compare to what we give the boot loader.

Replacing the kernel may be a simple as wriring to that partion..
Yeah, I don't think we have a mtd parts being assigned to where tinboot is being written to. In fact, I'm not sure that the root partition we are setting aside is even being used. Are you able to cat mtd1 and see if anything is even in it? I'd say go ahead and commit as long as system is at least 128MB. We can shift the rest around later, but I want to commit to a specific size for system for the chefs (and we have to keep module size in mind too)
Reply With Quote