Date: Sun, 1 Nov 2020 21:25:12 +0200 From: Guy Yur <guyyur@gmail.com> To: freebsd-arm@freebsd.org Subject: u-boot 2020.07 fails to see BOOTARM.EFI on fat partition with custom installation Message-ID: <18d7b209-959e-7c4b-1d5e-1c7b9506783c@gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, u-boot 2020.01 through 2020.07 have a regression where u-boot only sees shortname files on the fat filesystem if they have the archive attribute set. The issue was fixed in u-boot 2020.10: https://github.com/u-boot/u-boot/commit/1788a9697f51aebb25623e6216c09304756748ff Are there plans to update u-boot-master port to 2020.10? The issue doesn't affect images created by makefs which sets the flag. When doing custom steps (newfs_msdos, mount, copy loader.efi to EFI/BOOT/BOOTARM.EFI and umount),if the source file is on UFS, the target file will not have UF_ARCHIVE set. u-boot will fail to see BOOTARM.EFI and the system will not boot. Specifically, this happened to me with u-boot-orangepi-pc. 0040c440 42 4f 4f 54 41 52 4d 20 45 46 49 00 00 83 d3 9e |BOOTARM EFI.....| 0040c450 5f 51 5f 51 00 00 d3 9e 5f 51 8f 00 a8 a7 08 00 |_Q_Q...._Q......| Thanks, Guy Yur
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18d7b209-959e-7c4b-1d5e-1c7b9506783c>