From owner-freebsd-arm@FreeBSD.ORG Sat May 16 21:05:35 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 8980EF13 for ; Sat, 16 May 2015 21:05:35 +0000 (UTC) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (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 64F0113A8 for ; Sat, 16 May 2015 21:05:35 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t4GL599U061235; Sat, 16 May 2015 21:05:09 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.105] (192.168.1.65 [192.168.1.65]) by kientzle.com with SMTP id zrewkhajkscc9ryzddp3i2wd8n; Sat, 16 May 2015 21:05:08 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: Building RPI2-B (and RPI?) From: Tim Kientzle In-Reply-To: <1431741503.1000.3.camel@beta.com> Date: Sat, 16 May 2015 14:05:08 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <242E758D-3AA9-4F08-AA75-91F68183F363@kientzle.com> References: <1431741503.1000.3.camel@beta.com> To: mcgovern@beta.com X-Mailer: Apple Mail (2.2098) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 May 2015 21:05:35 -0000 > On May 15, 2015, at 6:58 PM, Brian J. McGovern = wrote: >=20 > All, > I've noticed a lot of progress recently on the RPI2-B platform, and > I'm looking to get up and running. I have an image that was posted the > list a week or two back running, but I want to get up to = bleeding-edge. >=20 > I've seen some emails about changes in the build methods for > "supported" platforms, and IIRC, many of the crochet-supported = platforms > were impacted, as there were issues keeping things in synch. >=20 > Are the RPI2-B images (and optionally RPI) still being built via the > crochet tool, or is there a new method around for which I've yet to = find > the documentation? Glen is building a new tool for use in FreeBSD=E2=80=99s =E2=80=98make = release=E2=80=99 process. That will be used for the =E2=80=9Cofficial=E2=80=9D images = going forward. Crochet is still being actively maintained. It is maintained separately from the FreeBSD source tree so there are occasional mismatches. There are other tools around, but I=E2=80=99m less familiar with them and will let other folks explain them. If you=E2=80=99re familiar with FreeBSD=E2=80=99s build system and = understand the RPI2-B boot process (which is a bit involved), it=E2=80=99s not very difficult to build your own images =E2=80=9Cfrom scratch=E2=80=9D using = just a FreeBSD source checkout and the appropriate u-boot port. Once you have a system running, of course, you also have the option of upgrading it from source directly: $ svnlite checkout https://svn.freebsd.org/base/head /usr/src $ cd /usr/src Read the UPGRADING file for instructions. (Caveat: This requires a few gigabytes of free disk space and requires more than 1GB of RAM, so you=E2=80=99ll need to configure swap space as = well.) Tim