Date: Sat, 13 Jan 2024 12:01:06 -0800 From: Mark Millard <marklmi@yahoo.com> To: void <void@f-m.fm> Cc: freebsd-arm@freebsd.org Subject: Re: current for arm64 tries tftp first for some reason Message-ID: <E78BCE78-FA52-49F8-95EF-EF216628444B@yahoo.com> In-Reply-To: <ZaLI26sdntU7kfB-@int21h> References: <ZZqgyHIJhgNoHtES@int21h> <C694B0F9-89C0-42F2-A00F-F77787775655@yahoo.com> <ZZ8Zfz40N6XTbdZf@int21h> <0DB5FDFB-184F-4260-A060-ED6A6CAFE546@yahoo.com> <ZaLI26sdntU7kfB-@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 13, 2024, at 09:31, void <void@f-m.fm> wrote: > On Wed, Jan 10, 2024 at 03:16:49PM -0800, Mark Millard wrote: >> U-Boot is doing tftp activity before the FreeBSD UEFI >> loader has been found to be loaded. So either the >> sysutils/u-boot* port's choices for how/what to build >> or U-Boot itself if building can not control the issue. > > The issue is no longer present in the latest snapshot > main-n267507-a61d2c7fbd3c thanks I still have the problem in that context with the RPi4B. But since I've moved that media to the RPi5 for an experiment with EDK2 based booting of the RPi5. === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E78BCE78-FA52-49F8-95EF-EF216628444B>