Re: u-boot 2020.07 fails to see BOOTARM.EFI on fat partition with custom installation

Emmanuel Vadot <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On Sun, 1 Nov 2020 21:42:54 +0100
Emmanuel Vadot <[email protected]> wrote:

> On Sun, 1 Nov 2020 21:25:12 +0200
> Guy Yur <[email protected]> wrote:
> 
> > 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?
> 
>  Yes, I have the update ready but this broke a few things in the
> rockpro64 port. I'll backport the fix next week if I didn't find time
> to fix everything else needed for the 2020.10 update.
> 
>  Thanks for the report.
> 
> > 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
> > 
> > _______________________________________________
> > [email protected] mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "[email protected]"

 Just commited 2020.10, let me know if you have any problems.

 Thanks,

-- 
Emmanuel Vadot <[email protected]> <[email protected]>
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.