MLO (X-Loader) identifies a board at boot and I think that we need a version after 7 Mar commit[1] to boot PocketBeagle. So, would you update to coming v2018.05? (I didn't build it, only tested using binary [2] mentioned [3].) This port is also used for release image build (src/release/arm/BEAGLEBONE.conf), so timely update would be good for other am335x variant boards to utilize existent BEAGLEBONE binary. [1] https://github.com/u-boot/u-boot/commit/eff0c977b3b9466657362869e04da231a892e31e#diff-f50a648de8254edc812f2e46e180921f [2] http://www.netbsd.org/~sevan/pocketbeagle-ub-2017-09.tgz [3] https://mail-index.netbsd.org/port-arm/2017/10/23/msg004423.html
Maintainer informed via mail
Created attachment 193230 [details] patch to boot PocketBeagle
Although v2018.05 has released but I see that it is not trivial upgrade task. So how about the patch attached to boot PocketBagle? Would anyone pick this and commit?
You should probably put freebsd-uboot@freebsd.org in the loop.
Thank you for your comment. I have sent an email to freebsd-uboot@freebsd.org.
To manu/imp, can you comment please? (Bugzilla will not allow me to assign to uboot@ for some reason.)
This port had recently upgraded in several years. And I expect this PR will be automatically fixed in the next upgrade. If it doesn't happen, I will send a patch. Since release cycle is in progress, I think it is bad timing for a while. Thank you!
Close for now. We can revisit this if the next port update fails to address the problem.