From owner-freebsd-arm@freebsd.org Sun Mar 4 07:37:38 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7F5AF3D2C2; Sun, 4 Mar 2018 07:37:38 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 68F546EE41; Sun, 4 Mar 2018 07:37:37 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1esOD3-0007jw-FL; Sat, 03 Mar 2018 23:37:30 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w247bSA3029755; Sat, 3 Mar 2018 23:37:28 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Sat, 3 Mar 2018 23:37:27 -0800 From: Oleksandr Tymoshenko To: Hyun Hwang Cc: tech-lists , freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Subject: Re: sysutils/u-boot-rpi2 appears to be broken with freebsd/crochet from github Message-ID: <20180304073727.GA29648@bluezbox.com> References: <2bce9ec3-3c80-b986-ee8f-33cf60fe3030@zyxst.net> <1520134738.2037746.1290617928.4FDB71A2@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520134738.2037746.1290617928.4FDB71A2@webmail.messagingengine.com> X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Hyun Hwang (hyun@caffeinated.codes) wrote: > On Sunday, March 4, 2018, 1:07 AM (UTC+0000), "tech-lists" wrote: > > When I use crochet to build for rpi2 it never completes writin [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 07:37:39 -0000 Hyun Hwang (hyun@caffeinated.codes) wrote: > On Sunday, March 4, 2018, 1:07 AM (UTC+0000), "tech-lists" wrote: > > When I use crochet to build for rpi2 it never completes writing the > > image because it looks for things in /usr/local/share/u-boot/u-boot-rpi2 > > and doesn't find for example LICENCE.broadcom. There's just two files > > there: > > > > root@desktop:/usr/local/share/u-boot/u-boot-rpi2 # ls -lah > > total 295 > > drwxr-xr-x 2 root wheel 4B Mar 3 20:26 . > > drwxr-xr-x 4 root wheel 4B Mar 4 00:58 .. > > -rw-r--r-- 1 root wheel 765B Mar 3 20:23 README > > -rw-r--r-- 1 root wheel 371K Mar 3 20:23 u-boot.bin > > > > (My email client messed up and sent the reply only to -arm; so I'm sending this message again to -ports as well. Sorry for duplicate post.) > > I see that firmware files are separated from `sysutils/u-boot-rpi2` port and are now located in `sysutils/rpi-firmware` port as of [ports r454265](https://svnweb.freebsd.org/ports?view=revision&revision=454265). Looks like Crochet requires some update. > > My wild guess is that RPi3 is yet to be separated because of gonzo's SMP binary (armstub8.bin)? There is ongoing work on using RPi firmware port for all RPi models and switching u-boot-rpi3 to the same framework as u-boot-rpi2 but it involves changes across multiple areas (drivers, ports, release scripts). Some of this stuff is already committed, some is in review, some is WIP. -- gonzo