u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] board_r - fixup functions table after relocation
Date: Thu, 16 Jan 2014 21:27:15 +0100	[thread overview]
Message-ID: <20140116212715.5f3d3301@lilith> (raw)
In-Reply-To: <1389894525.2768.13.camel@abrodkin-8560l.internal.synopsys.com>

Hi Alexey,

On Thu, 16 Jan 2014 17:48:45 +0000, Alexey Brodkin
<Alexey.Brodkin@synopsys.com> wrote:

> On Wed, 2014-01-15 at 22:43 +0100, Albert ARIBAUD wrote:
> > Hi Alexey,
> > 
> > On Wed, 15 Jan 2014 15:19:56 +0400, Alexey Brodkin
> > <Alexey.Brodkin@synopsys.com> wrote:
> > 
> > > "init_sequence_r" is just an array that consists of compile-time
> > > adresses of init functions. Since this is basically an array of integers
> > > (pointers to "void" to be more precise) it won't be modified during
> > > relocation - it will be just copied to new location as it is.
> > 
> > IIRC, in ARM we switched from GOT to ELF relocation precisely so that
> > data would be relocated as well as code, and I think it actually is,
> > otherwise we'd have a lot of complains. Therefore I fail to understand
> > the statements above. Can someone tell me what I'm getting wrong?
> 
> Unfortunately I don't have any supported in U-Boot ARM board handy and
> run U-boot on another architecture at all (Synopsys DesignWare ARC) so
> I'm not sure if on ARM functions from "init_sequence_r" list are
> executed from "RAM" (i.e. from location where they were relocated).

Yes, they are.

> I use GOT relocation and see following outputs.

GOT relocation does not relocate references within data, contrary
to ELF.

> Maybe it's just my faulty implementation of relocation but it might be
> that nobody ever noticed this because I think only initcalls are
> affected.

Well, initcalls are quite essential, I guess.

When you say "my faulty implementation of relocation"... do you mean
some implementation different from what is currently in mainline?

> -Alexey

Amicalement,
-- 
Albert.

  reply	other threads:[~2014-01-16 20:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 11:19 [U-Boot] [PATCH] board_r - fixup functions table after relocation Alexey Brodkin
2014-01-15 11:27 ` thomas.langer at lantiq.com
2014-01-15 12:58   ` Alexey Brodkin
2014-01-15 13:50     ` thomas.langer at lantiq.com
2014-01-15 16:56 ` Simon Glass
2014-01-16 17:51   ` Alexey Brodkin
2014-01-15 21:43 ` Albert ARIBAUD
2014-01-16 17:48   ` Alexey Brodkin
2014-01-16 20:27     ` Albert ARIBAUD [this message]
2014-01-16 20:40       ` Alexey Brodkin
2014-01-17  0:06         ` Alexey Brodkin
2014-01-17 12:54           ` Tom Rini

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=20140116212715.5f3d3301@lilith \
    --to=albert.u.boot@aribaud.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).