From mboxrd@z Thu Jan  1 00:00:00 1970
From: Graeme Russ <graeme.russ@gmail.com>
Date: Wed, 22 Feb 2012 07:10:33 +1100
Subject: [U-Boot] [PATCH v4 0/13] Introduce generic relocation feature
In-Reply-To: <CAPnjgZ2JgO2v-Gw2LxkFghsyL0z5AUL8WnytphNS6mTy9vH=_Q@mail.gmail.com>
References: <1329787975-6695-1-git-send-email-sjg@chromium.org>
	<4F43F32C.80305@aribaud.net>
	<CAPnjgZ2JgO2v-Gw2LxkFghsyL0z5AUL8WnytphNS6mTy9vH=_Q@mail.gmail.com>
Message-ID: <4F43FA39.10805@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Simon, Albert.

On 02/22/2012 07:07 AM, Simon Glass wrote:
> Hi Albert,
> 
> On Tue, Feb 21, 2012 at 11:40 AM, Albert ARIBAUD
> <albert.u.boot@aribaud.net> wrote:
>> Hi Simon,
>>
>> One general question: am I right in saying that in the current
>> implementation, relocate_code executes mostly on the final stack, whereas in
>> your proposal, it runs on the initial stack?
> 
> Well the current relocation code is all in assembler and I don't
> believe it uses the stack at all. It does set up the stack pointer at
> the beginning if that's what you mean.
> 
> Yes this series uses the initial stack for all processing until it
> reaches board_init_r().

<broken record>

See what x86 does - Code copy and relocation in C using final stack and
full cache enabled...

</broken record> :)

Regards,

Graeme