All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] arm: implement ELF relocations
Date: Wed, 06 Oct 2010 09:03:51 +0200	[thread overview]
Message-ID: <4CAC1F57.9030302@free.fr> (raw)
In-Reply-To: <4CAC1B0F.3030607@emk-elektronik.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.

      reply	other threads:[~2010-10-06  7:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 19:40 [U-Boot] [PATCH 1/2] arm: implement ELF relocations Albert Aribaud
2010-10-05 19:41 ` [U-Boot] [PATCH 2/2] edminiv2: add support for " Albert Aribaud
2010-10-06  5:30   ` Heiko Schocher
2010-10-06  5:55     ` Albert ARIBAUD
2010-10-06  5:37 ` [U-Boot] [PATCH 1/2] arm: implement " Heiko Schocher
2010-10-06  5:54   ` Albert ARIBAUD
2010-10-06  6:01   ` Reinhard Meyer
2010-10-06  6:29     ` Albert ARIBAUD
2010-10-06  6:45       ` Reinhard Meyer
2010-10-06  7:03         ` Albert ARIBAUD [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CAC1F57.9030302@free.fr \
    --to=albert.aribaud@free.fr \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.