Subject: Re: Consolidate cuboot initialization code

From: Scott Wood <[email-masked]>
Date: Wed, 30 May 2007 10:21:22 -0500

David Gibson wrote:
> On Wed, May 30, 2007 at 10:09:11AM -0500, Scott Wood wrote:
>>Is there any particular reason to not just do a direct call to 
>>cuboot_init, and move the memcpy and end-of-ram calculation there?  I'd 
>>rather avoid macros if possible.
> 
> Uh.. yeah.. because cuboot_init() doesn't know the size to memcpy(),
> because it doesn't have the right bd_t definition.

Ah, yes.  Don't mind me, it's still morning here... :-P

We could probably do away with the copy altogether, though, as u-boot 
puts the bd_t near the stack, which is exempted from the bootwrapper's 
heap with the 1MiB exclusion.

-Scott