From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:6f8:1178:4:290:27ff:fe1d:cc33]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1VQfZ0-0007hF-7s for barebox@lists.infradead.org; Mon, 30 Sep 2013 15:39:10 +0000 Date: Mon, 30 Sep 2013 17:38:46 +0200 From: Sascha Hauer Message-ID: <20130930153846.GC30088@pengutronix.de> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: Is Relocation forced? To: "Allen Kennedy Jr." Cc: Barebox Mailing list 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