mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Allen Kennedy Jr." <allen@kennedystuff.com>
Cc: Barebox Mailing list <barebox@lists.infradead.org>
Subject: Re: Is Relocation forced?
Date: Mon, 30 Sep 2013 17:38:46 +0200	[thread overview]
Message-ID: <20130930153846.GC30088@pengutronix.de> (raw)
In-Reply-To: <CAO-21LP2aK6Zwphamv2Zj_-Y1YWt6xNX6GZSUVrHreALsaJQsg@mail.gmail.com>

Hi Allen,

On Mon, Sep 30, 2013 at 09:24:17AM -0500, Allen Kennedy Jr. wrote:
> Hello,
>   I have relocatable binary set to "n"  and I load barebox into ram
> exactly where it is supposed to be, but it still runs the function
> "relocate binary"
> 
>   Is the option to not relocate barebox, not supported?
> 
> Why would I want it not-relocated?  Because relocate_to_current_adr()
> causes an exception every time, and barebox won't boot.  And I can't
> figure out why the exception occurs.

Generally relocatable barebox is not enforced and barebox runs happily
without it. However, there are some combinations of PBL/TEXT_BASE which
really do need relocation support.

What SoC/board are you running? Could you post your .config file?

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-09-30 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 14:24 Allen Kennedy Jr.
2013-09-30 15:38 ` Sascha Hauer [this message]
2013-09-30 18:56   ` Allen Kennedy Jr.

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=20130930153846.GC30088@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=allen@kennedystuff.com \
    --cc=barebox@lists.infradead.org \
    /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