From owner-freebsd-arm@FreeBSD.ORG Wed Sep 3 22:30:12 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B39B2ABB for ; Wed, 3 Sep 2014 22:30:12 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 860791F44 for ; Wed, 3 Sep 2014 22:30:12 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XPJ47-000Ag6-0H; Wed, 03 Sep 2014 22:30:11 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id s83MUApx009025; Wed, 3 Sep 2014 16:30:10 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18tlCnj38gEBMYy8XZTCY6T X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: address dependent code? From: Ian Lepore To: =?ISO-8859-1?Q?Mat=EDas?= Perret Cantoni In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Date: Wed, 03 Sep 2014 16:30:09 -0600 Message-ID: <1409783409.1150.297.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ilsoft.org id s83MUApx009025 Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 22:30:12 -0000 On Wed, 2014-09-03 at 19:11 -0300, Mat=EDas Perret Cantoni wrote: > Hello! I've found that for compiling ubldr I need to specify the addres= s > where it will be loaded and executed, and I'd like to know more about t= his. > It's the first time I find that I need to specify a physical address on > compile time. >=20 > I'm sure it's kind of a whole specific programming field, so can you po= int > out some material that I can read about this? Any info about this will = be > appreciated! >=20 > Thanks in advance. >=20 > Regards, Matias. The kernel also needs to be compiled to load at a specific address, but you don't have to set it manually because it's hard-coded in the std.soctype file for each chip. In the case of ubldr, it's because u-boot doesn't know how to do relocation, it can only load an image that is pre-linked to run at a fixed address. ubldr isn't built along with the kernel, so there's nowhere to configure the load address on a per-system basis, it has to be provided manually. -- Ian