Crochet Updates for RPi, BeagleBone
Tim Kientzle
tim at kientzle.com
Sun Aug 9 18:32:02 UTC 2015
> On Aug 8, 2015, at 7:23 PM, Ian Lepore <ian at freebsd.org> wrote:
>
> On Sat, 2015-08-08 at 12:01 -0700, Tim Kientzle wrote:
>>> On Aug 8, 2015, at 11:22 AM, Ian Lepore <ian at freebsd.org> wrote:
>>>
>>> On Sat, 2015-08-08 at 10:52 -0700, Tim Kientzle wrote:
>>>>> On Aug 6, 2015, at 4:15 PM, kah42pub <kah42pub at blarg.com> wrote:
>>>>>
>>>>> 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.
>>>>>
>>>>> Has anyone successfully built the u-boot-rpi port recently for RPI-B?
>>>>
>>>> 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:
>>>>
>>>> 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)
>>>>
>>>> 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)
>>>
>>> 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.
>>
>> Great!
>>
>> Keeping old GCC versions available in the ports tree sounds like a
>> good plan in general.
>>
>>> 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.
>>
>> Thanks for your work on this.
>>
>> Cheers,
>>
>> Tim
>
> 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
More information about the freebsd-arm
mailing list