Broken U-Boot packages?
Warner Losh
imp at bsdimp.com
Mon Jun 15 17:34:18 UTC 2015
> On Jun 14, 2015, at 12:20 PM, Tim Kientzle <tim at kientzle.com> wrote:
>
> Has anyone else had success building images with the U-Boot *packages*?
I’ve built them from source. But haven’t used pkg to install them.
> I’m updating Crochet to use U-Boot from ports/packages for RPI and Beaglebone, but I get non-bootable images (generally with U-boot failing to identify the disk partitioning) when I use the package. Here’s what I’ve tried so far:
>
> * RPi built with U-Boot from package - non-bootable
> * RPi built with U-Boot port compiled locally - works
> * Beaglebone Black with U-Boot from package - non-bootable
>
> Today I hope to try booting an old white Beaglebone and building the u-boot-beaglebone port locally to see if that follows the pattern.
>
> For the record, my ports tree is up-to-date and I’m installing the packages onto a recent FreeBSD-CURRENT amd64 VM via:
>
> $ pkg install sysutils/u-boot-rpi
The ports-built files and package files should be identical. Are they?
Warner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20150615/49c60c4a/attachment.sig>
More information about the freebsd-arm
mailing list