From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Wed, 06 Oct 2010 09:03:51 +0200 Subject: [U-Boot] [PATCH 1/2] arm: implement ELF relocations In-Reply-To: <4CAC1B0F.3030607@emk-elektronik.de> References: <1286307660-7969-1-git-send-email-albert.aribaud@free.fr> <4CAC0B21.5030602@denx.de> <4CAC10A4.30808@emk-elektronik.de> <4CAC1731.8030508@free.fr> <4CAC1B0F.3030607@emk-elektronik.de> Message-ID: <4CAC1F57.9030302@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le 06/10/2010 08:45, Reinhard Meyer a ?crit : > Dear Albert ARIBAUD, > Also I observed problems with old AT91 code since without > CONFIG_SYS_ARM_WITHOUT_RELOC board_init() is called very early, with it > is called after relocation is done. I think most AT91 boards that copied > code from AT91SAM9***-EK's have to correct their code because "early init" > stuff is done in board_init(). This was to be expected whatever relocation method is used. Before relocation, board_init_f was running in the final memory mapping. Now it runs (as it should always have) in a limited C environment, with read-only globals, no BSS, only partial gd access... FTR, it hit my orion5x based edminiv2 too in places. >> What do you mean by 'relocation-*preventing* code'? > > Everything, including the #if's that is there for the non-relocating cases. Ok. > Best Regards, > Reinhard Amicalement, -- Albert.