Date: Sun, 9 Aug 2015 11:32:00 -0700 From: Tim Kientzle <tim@kientzle.com> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: Crochet Updates for RPi, BeagleBone Message-ID: <672F2D0C-BC6D-4A5F-BF3E-F3CF659636CD@kientzle.com> In-Reply-To: <1439087009.70393.274.camel@freebsd.org> References: <486955D9-6EED-47E4-BCAA-AA66650BB9DA@kientzle.com> <55C3EA7E.7050905@blarg.com> <85E89B54-B2AA-4D87-BA80-5BD2956B2F8A@kientzle.com> <1439058129.70393.262.camel@freebsd.org> <8C0A45D4-38F0-4099-84AE-D904B8614604@kientzle.com> <1439087009.70393.274.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 8, 2015, at 7:23 PM, Ian Lepore <ian@freebsd.org> wrote: >=20 > On Sat, 2015-08-08 at 12:01 -0700, Tim Kientzle wrote: >>> On Aug 8, 2015, at 11:22 AM, Ian Lepore <ian@freebsd.org> wrote: >>>=20 >>> On Sat, 2015-08-08 at 10:52 -0700, Tim Kientzle wrote: >>>>> On Aug 6, 2015, at 4:15 PM, kah42pub <kah42pub@blarg.com> wrote: >>>>>=20 >>>>> On 7/19/15 18:39, Tim Kientzle wrote: >>>>>> I just committed changes to Crochet so that it now uses the = U-Boot ports for RPi and BeagleBone (including BBB). It already used = the port for RPi2. >>>>>=20 >>>>> Has anyone successfully built the u-boot-rpi port recently for = RPI-B? >>>>=20 >>>> I just tried building each U-Boot port with an upgraded -CURRENT = system (including packages). Looks like anything based on U-Boot older = than 2015.04 is broken: >>>>=20 >>>> The following did not build for me: >>>> u-boot-beaglebone (uses U-Boot 2014.10) >>>> u-boot-cubox-hummingbird (based on U-Boot 2013.10) >>>> u-boot-duovero (based on U-Boot 2014.10) >>>> u-boot-pandaboard (uses U-Boot 2014.10) >>>> u-boot-rpi (based on U-Boot 2013.01) >>>> u-boot-wandboard (based on U-Boot 2013.10) >>>>=20 >>>> These did build: >>>> u-boot-bananapi (uses U-Boot 2015.04) >>>> u-boot-cubieboard (uses U-Boot 2015.04) >>>> u-boot-cubieboard2 (uses U-Boot 2015.04) >>>> u-boot-rpi2 (uses U-boot 2015.04) >>>=20 >>> The cross-compiler port used for u-boot got upgraded behind our = backs to >>> gcc5, and that breaks all the u-boots that are based on older >>> vendor-supplied sources. I have a new arm-none-eabi-gcc492 port = ready >>> to go, but I'm not a ports committer, so I'm waiting for someone to >>> review and approve the commit. >>=20 >> Great! >>=20 >> Keeping old GCC versions available in the ports tree sounds like a >> good plan in general. >>=20 >>> I also plan to try and get as many of our u-boot ports as possible >>> updated to the latest mainline u-boot sources, but I still want to = get >>> the gcc492 port in first because I think updating to mainline u-boot = is >>> more than a day or two of work. >>=20 >> Thanks for your work on this. >>=20 >> Cheers, >>=20 >> Tim >=20 > I just committed the fixes for all the u-boot ports on your 'did not > build' list. I also snuck in the fix for the cubox-hummingboard port = to > make the board detection work, and it should choose the right fdt file > now for hummingboard users. After updating my ports tree, I was able to build every U-Boot port on = an up-to-date -CURRENT system. Thanks! Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?672F2D0C-BC6D-4A5F-BF3E-F3CF659636CD>