From owner-freebsd-mips@freebsd.org  Tue May 23 14:16:51 2017
Return-Path: <owner-freebsd-mips@freebsd.org>
Delivered-To: freebsd-mips@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8D38D7AF9E
 for <freebsd-mips@mailman.ysv.freebsd.org>;
 Tue, 23 May 2017 14:16:51 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from pmta2.delivery6.ore.mailhop.org
 (pmta2.delivery6.ore.mailhop.org [54.200.129.228])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id AE3BE1768
 for <freebsd-mips@freebsd.org>; Tue, 23 May 2017 14:16:51 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: 48ce8e09-3fc2-11e7-8c46-c35e37f62db1
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 73.78.92.27
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [73.78.92.27])
 by outbound2.ore.mailhop.org (Halon) with ESMTPSA
 id 48ce8e09-3fc2-11e7-8c46-c35e37f62db1;
 Tue, 23 May 2017 14:15:34 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id v4NEGg8X003889;
 Tue, 23 May 2017 08:16:42 -0600 (MDT) (envelope-from ian@freebsd.org)
Message-ID: <1495549001.89384.97.camel@freebsd.org>
Subject: Re: U-Boot image Entry address
From: Ian Lepore <ian@freebsd.org>
To: Mori Hiroki <yamori813@yahoo.co.jp>, "freebsd-mips@freebsd.org"
 <freebsd-mips@freebsd.org>
Date: Tue, 23 May 2017 08:16:41 -0600
In-Reply-To: <501228.94030.qm@web101720.mail.ssk.yahoo.co.jp>
References: <501228.94030.qm@web101720.mail.ssk.yahoo.co.jp>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-mips@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting FreeBSD to MIPS <freebsd-mips.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-mips>,
 <mailto:freebsd-mips-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mips/>
List-Post: <mailto:freebsd-mips@freebsd.org>
List-Help: <mailto:freebsd-mips-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-mips>,
 <mailto:freebsd-mips-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 May 2017 14:16:51 -0000

On Tue, 2017-05-23 at 21:18 +0900, Mori Hiroki wrote:
> Hi
> 
> We have entry address issue in last onion target talk in this ml.
> 
> I made script for entry address in my maintenance version ZRouter. 
> 
> https://github.com/yamori813/zrouter/blob/add_new_devices/tools/entry
> addr.sh
> 
> 
> This is use in physical address in mips target. Almost mips is use
> 0x80000000. But be careful RT2880 is use 0x88000000.
> 
> ARM terget is linked by kvm address(0xc0000000). Then convert to 
> physical address.
> 

The ARM kernel can be loaded at any 2MB boundary in physical ram
regardless of what address it's linked at.  The arm entry point must be
within the first 4K of the loaded file.  Thus the entry point is
$loadaddr + (elf_phdr.entry & 0x0fff).

-- Ian