From owner-freebsd-arm@FreeBSD.ORG Thu Dec 26 20:26:54 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 800F7D94; Thu, 26 Dec 2013 20:26:54 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3B50B1FB4; Thu, 26 Dec 2013 20:26:53 +0000 (UTC) Received: from glenbarber.us (70.15.88.86.res-cmts.sewb.ptd.net [70.15.88.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 7DDDB5EFF; Thu, 26 Dec 2013 20:26:52 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 7DDDB5EFF Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 26 Dec 2013 15:26:50 -0500 From: Glen Barber To: Warner Losh Subject: Re: FreeBSD 10.0-RC3 Now Available Message-ID: <20131226202650.GC13109@glenbarber.us> References: <20131226162521.GK2009@glenbarber.us> <2B79BF2A-1798-40F5-AD6E-D560E9C6C1E7@freebsd.org> <20131226194830.4f6e5b13@bender.Home> <20131226195512.GA13109@glenbarber.us> <20131226202016.3071b815@bender.Home> <20131226202307.GB13109@glenbarber.us> <1C33413D-4639-4436-83E0-1866298DC9ED@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="eRtJSFbw+EEWtPj3" Content-Disposition: inline In-Reply-To: <1C33413D-4639-4436-83E0-1866298DC9ED@bsdimp.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-arm ml , FreeBSD Release Engineering Team X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 20:26:54 -0000 --eRtJSFbw+EEWtPj3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 26, 2013 at 01:24:17PM -0700, Warner Losh wrote: >=20 > On Dec 26, 2013, at 1:23 PM, Glen Barber wrote: >=20 > > On Thu, Dec 26, 2013 at 08:20:16PM +0000, Andrew Turner wrote: > >> On Thu, 26 Dec 2013 14:55:12 -0500 > >> Glen Barber wrote: > >>=20 > >>> On Thu, Dec 26, 2013 at 07:48:30PM +0000, Andrew Turner wrote: > >>>> On Thu, 26 Dec 2013 10:25:09 -0800 > >>>> Tim Kientzle wrote: > >>>>=20 > >>>>>=20 > >>>>> On Dec 26, 2013, at 8:25 AM, Glen Barber wrote: > >>>>>=20 > >>>>>> The third RC build of the 10.0-RELEASE release cycle is now > >>>>>> available on the FTP servers for the amd64, i386, ia64, powerpc, > >>>>>> powerpc64 and sparc64 architectures. > >>>>>=20 > >>>>> What do we need to include some ARM images? > >>>>>=20 > >>>>> At a minimum, I would love to get an official RC3 build for RPi. > >>>>=20 > >>>> I would suggest we could build a tarball of armv6 userland and an > >>>> RPi image to dd to an SD card. > >>>>=20 > >>>> Building the former should be straight forward. > >>>>=20 > >>>> For the latter, assuming the release target is unable to build the > >>>> required U-Boot binary, we could use crochet. I'm not sure if we can > >>>> use a tarball as the input for this to guarantee both are the same. > >>>>=20 > >>>=20 > >>> The problem with using crochet is that it requires git on the build > >>> machine, which just adds to the minimum dependencies needed, both for > >>> crochet itself, and (last I was aware) an external uboot tree. > >>=20 > >> Github allows you to use svn to checkout a git repo with svn. There is > >> an option under the clone url to set it to subversion. > >>=20 > >> U-Boot should just be a tarball, if it is a git repo we would need to > >> make it a tarball for the release to supply the source as it is GPL. > >>=20 > >>> Maybe it is just more sensible to take what crochet is doing, and make > >>> that into a release target. > >>=20 > >> Yes, but I assume this is not feasible for 10.0. > >>=20 > >=20 > > It depends on how the test builds go, which I am working on right now. > > They may not be considered "official", since we're at the end of the > > release cycle. But if I can get something working, I'll be happy to > > hand-roll -RELEASE builds. >=20 > I'm cool with that, especially if it enables official 10.1R releases this= summerish... >=20 It would at least give me an idea of what is needed, and then I can easily start building regular snapshots, which would give us 10.0-STABLE builds, if we can't get something working by 10.0-RELEASE. Glen --eRtJSFbw+EEWtPj3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSvJEKAAoJELls3eqvi17QzgUP/1IY3OBzhizvZ7s5e4sOn6rk tz+JKfQ7aaMkR9IZ+R5Y1rCfdl3Rt0j+Du/EaW0V8TQSiSTrFg0dqFr0G0EMjkZn RYqVh+Hy2mzU2WWzP4oVbsvB4qljUGbRvY4svBV3FHXF2WXIOOvpJe+NGjXF2z2b Vpjhii+2HaLxfeM+N3A+K0gALRZrF+tUFvYr+lInMHoHbJSLvnd/HDDbyt7AVX58 wyLWt/zAu7PqYGp6EKMq+s02vaSypuIka0S3Rg6X+hmbdS2Z1OAYtej+iJU2XiNZ xxnzTPYD2Hnn4nMjhQg9De2nipZPbxxvtKt96FpgjFADp0X5UjPP4pyAm/t5Disd gwVty0Q8Oj7sncYGXpN/HXZIS96eZhR81ueuoAlaUxHBpcYHYhzEmxQjil4nfb8d Y+DUxiFEnEgWC5Y5tJHyE7DxhTVG25eB6ifj4LHnelM2ium8/UED4efou2tw9q8U vA/oWcaPPdiOaxjVpOrDqCEmA+sJz9z9ICLI/K8OQQGWymr9mCOu6nYsJTJ22cg3 CUlrFAr2ujEhDHVTF0By8F8q0kVLPQcULcJ3hjhUH2AxBt5L3V1FO4egUxv8hPkI WylzqX2oItNKmHUGkBRQf/ln2pQKsVdOlNyQ2UlFeMPRBrucOtVq92QYfX9X82ed 7mDQVN9LY3M+aNoWUBhq =GpLP -----END PGP SIGNATURE----- --eRtJSFbw+EEWtPj3--