public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 3/5] common/board_r: manual relocation for cmd table
Date: Tue, 20 Jan 2015 12:42:26 +0000	[thread overview]
Message-ID: <1421757742.2939.11.camel@synopsys.com> (raw)
In-Reply-To: <CAPnjgZ23uLh3Ku9hnkBt95dQS1jBZaSGn7xb1YwFqdFHYOfXsg@mail.gmail.com>

Hi Simon,

On Mon, 2015-01-19 at 16:34 -0700, Simon Glass wrote:
> Hi Andreas,

> Why do you need manual reloc? Is this a toolchain bug?

From my experience the only way to escape manual relocation is to use
PIE (Position Independent Executable), but this might not be supported
in a toolchain for AVR (or it doesn't actually work good enough - this I
understood from this message
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574716)

-Alexey

  parent reply	other threads:[~2015-01-20 12:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 23:29 [U-Boot] [RFC PATCH 0/5] avr32: add generic board Andreas Bießmann
2015-01-19 23:29 ` [U-Boot] [RFC PATCH 1/5] avr32: use dlmalloc for DMA buffers Andreas Bießmann
2015-01-19 23:29 ` [U-Boot] [RFC PATCH 2/5] avr32: rename cpu_init() -> arch_cpu_init() Andreas Bießmann
2015-01-19 23:29 ` [U-Boot] [RFC PATCH 3/5] common/board_r: manual relocation for cmd table Andreas Bießmann
2015-01-19 23:34   ` Simon Glass
2015-01-19 23:41     ` Andreas Bießmann
2015-01-20  0:13       ` Simon Glass
2015-01-20 12:42     ` Alexey Brodkin [this message]
2015-01-27 15:18     ` Michal Simek
2015-01-19 23:29 ` [U-Boot] [RFC PATCH 4/5] avr32: add generic board support Andreas Bießmann
2015-01-19 23:29 ` [U-Boot] [RFC PATCH 5/5] grasshopper: enable generic board Andreas Bießmann
2015-01-20  8:54 ` [U-Boot] [RFC PATCH 0/5] avr32: add " Andreas Bießmann

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=1421757742.2939.11.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --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