From owner-freebsd-arm@FreeBSD.ORG Thu Jan 26 05:34:56 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8283C106564A for ; Thu, 26 Jan 2012 05:34:56 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 58EB58FC1A for ; Thu, 26 Jan 2012 05:34:56 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q0Q5YtEv020273; Thu, 26 Jan 2012 05:34:55 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.119] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id znm9ibhvp2xvwjsv9mkijkvh96; Thu, 26 Jan 2012 05:34:55 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: Date: Wed, 25 Jan 2012 21:34:55 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <214BF14D-33BA-4D3D-B043-31008E24F7AE@kientzle.com> References: <23CB6C35-9450-40BA-9FA3-37C44B328CA8@freebsd.org> <8042D895-3B3D-431E-ADCC-A150BDC838ED@kientzle.com> <7E53112E-DE29-4145-B597-D39AA77252C5@kientzle.com> <101D3416-6B61-4840-A89E-4CF91B0BB8BC@kientzle.com> To: Rafal Jaworowski X-Mailer: Apple Mail (2.1251.1) Cc: arm@freebsd.org Subject: Re: FreeBSD and BeagleBone X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2012 05:34:56 -0000 On Jan 25, 2012, at 2:06 PM, Rafal Jaworowski wrote: > On 2012-01-22, at 00:29, Tim Kientzle wrote: >=20 >>=20 >> P.S. Is it worth trying to generalize the ubldr Makefile >> to accept some form of link address specification? >=20 > In general yes, the challenge is how to do this in a smart and = flexible way: loader/ubldr is built as part of the world which you don't = want to entagle with platform specific knobs. On the other hand a = configurable like this is specific to some board (not even a chip, soc = or a familiy, anybody can have their U-Boot configured differently = underneath..), so the question is how to convey this knowledge. I know Warner has some ideas for organizing the tree to include board information. If each board has a directory, then you could build a custom ubldr for each board. That feels a little heavyweight to me, though. The closest thing to a board description we have is the kernel config. That reflects the hardware and layout of the board being targeted. Is there some way to have ubldr made by buildkernel instead of buildworld? Another approach might be to provide a build script that accepts arguments and spits out a compiled ubldr to match those parameters. Maybe something like: $ cd /usr/src/sys/tools/ubldr-build $ ./ubldr-build arm.arm -l 0x80010000 -o ubldr.beagle Tim