From owner-freebsd-arm@FreeBSD.ORG Mon Mar 16 20:06:07 2015 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1D8CAF1 for ; Mon, 16 Mar 2015 20:06:07 +0000 (UTC) Received: from relay.mailchannels.net (ar-005-i203.relay.mailchannels.net [162.253.144.85]) by mx1.freebsd.org (Postfix) with ESMTP id C18FBC25 for ; Mon, 16 Mar 2015 20:06:05 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp3.ore.mailhop.org (ip-10-204-4-183.us-west-2.compute.internal [10.204.4.183]) by relay.mailchannels.net (Postfix) with ESMTPA id 41583100305; Mon, 16 Mar 2015 19:58:05 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp3.ore.mailhop.org (smtp3.ore.mailhop.org [10.83.15.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Mon, 16 Mar 2015 19:58:06 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426535886395:409651849 X-MC-Ingress-Time: 1426535886395 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp3.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YXarS-0005Fv-WD; Mon, 16 Mar 2015 19:39:39 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2GJdXtG023800; Mon, 16 Mar 2015 13:39:33 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1+EjWpdB09Tax1lPPAO9FWr Message-ID: <1426534773.95554.15.camel@freebsd.org> Subject: Re: How to use u-boot-beaglebone port? From: Ian Lepore To: Tim Kientzle Date: Mon, 16 Mar 2015 13:39:33 -0600 In-Reply-To: <986F5E5D-C784-4BEF-81E3-49A9F27C0E8F@kientzle.com> References: <17B779D7-2962-4455-9062-51411F316648@gromit.dlib.vt.edu> <986F5E5D-C784-4BEF-81E3-49A9F27C0E8F@kientzle.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: freebsd-arm 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: Mon, 16 Mar 2015 20:06:07 -0000 On Sun, 2015-03-15 at 19:57 -0700, Tim Kientzle wrote: > > On Mar 12, 2015, at 5:59 PM, Paul Mather wrote: > > > > Has anyone successfully used the sysutils/u-boot-beaglebone port? > > > > I managed to build [1] and install it today. I tried to install it to the SD card FAT partition, as per the README, and the result was an unbootable system. > > > > When I copied the u-boot.img file as u-boot.img (rather than the bb-uboot.img as suggested in the README), I got it to start up to the "U-Boot#" prompt. > > > Apparently, no one ever patched the port to use bb-uboot.img and bb-ubldr > as the name. > > I did this in Crochet when I was experimenting with having multiple > U-Boots on a single SD card image. That experiment was to try > to see what would be required to build single images that booted on > multiple different devices. > When I created the u-boot-beaglebone port I specifically removed that bb- prefix stuff, because there will never be a unified image that runs on both rpi and beaglebone [*]. I had hoped someone would update crochet to use the new ports and this is one of the minor changes that would be needed on the crochet side. -- Ian [*] Because armv6 != armv7 in this case. While armv6 is synonymous with armv7 for most purposes in freebsd, the rpi is the exception to that in that it really IS armv6, and that leads to the kernel being built with different cache maintenance routines that don't work on armv7.