Date: Tue, 15 Oct 2019 12:03:55 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Henri Hennebert <hlh@restart.be> Cc: Henri Hennebert via freebsd-arm <freebsd-arm@freebsd.org>, Thomas Skibo <thomasskibo@yahoo.com> Subject: Re: PINE64+ 2GB - with U-Boot SPL 2019.10 - bootaa64.efi do not find UFS partition Message-ID: <20191015120355.91c54cbd23d2bf95c9566f7e@bidouilliste.com> In-Reply-To: <fc77da3c-d7ee-0838-5854-c28bd9ff11bf@restart.be> References: <15D5331A-C76D-4EBC-8992-9B04A0C0EDC5@yahoo.com> <fc77da3c-d7ee-0838-5854-c28bd9ff11bf@restart.be>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 15 Oct 2019 10:26:24 +0200 Henri Hennebert via freebsd-arm <freebsd-arm@freebsd.org> wrote: > On 10/13/19 8:41 PM, Thomas Skibo via freebsd-arm wrote: > >> > >> I put FreeBSD-12.1-RC1-arm64-aarch64-PINE64.img on the sd card. It is > >> created with u-boot 2019-07 and boot correctly. > >> > >> If I put u-boot 2019-10 the same problem occurs. > >=20 > > Without r352446, loader.efi cannot work with u-boot 2019.10. So, a 12.= 1 image isn?t going to be compatible with u-boot 2019.10. I?ve verified th= is on a Zynq board. > >=20 > > Also, boot1.efi won?t work with u-boot 2019.10 but I tried Emmanuel?s s= uggestion to use loader.efi directly and that worked. Then, as an experime= nt I backed out change r352446 in the loader and I got all the same error m= essages as Henri. > >=20 > > releng/12.1 at r353543 have loader.efi (as bootaa64.efi) booting the=20 > kernel with u-boot 2019.10 :-) >=20 > The error is still there with boot1.efi as bootaa64.efi. >=20 > Henri This will not be fixed. boot1.efi was never used for arm/arm64 and the main goal is to remove it anyway. --=20 Emmanuel Vadot <manu@bidouilliste.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191015120355.91c54cbd23d2bf95c9566f7e>