On 2018-07-06 04:17, Warner Losh wrote: > On Thu, Jul 5, 2018 at 7:11 PM, Rodney W. Grimes < > freebsd-rwg_at_pdx.rh.cn85.dnsmgr.net> wrote: > >> > On 5 Jul 2018, at 18:18, Rodney W. Grimes wrote: >> > >> > > [ Charset UTF-8 unsupported, converting... ] >> > >> On 5 Jul 2018, at 17:19, Warner Losh wrote: >> > >> >> > >>> FAT12 isn't good for UEFI. Use FAT16 or FAT32. >> > >> >> > >> We use it for the default image we built and the wiki suggests it as >> > >> well at https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI >> > > >> > > IIRC FreeBSD recently cnahged to FAT16 or 32 on these >> > > as the size got pushed up to be larger than what FAT12 >> > > can access. >> > >> > https://svnweb.freebsd.org/base/head/stand/efi/boot1/ >> generate-fat.sh?annotate=332561#l45 >> > >> > nope. >> >> That is not the code we build release images with, >> that is Warners tests for the boot loader. >> > > No, that's the actual code that generates boot1.efiffat. > > Warner Yup, and EFI have no problem at all with this. FAT12 can work with all EFI implementation, the problem is the size of the FAT12 part that sometimes causes problems. Rod, you are refering to the arm images which do not uses makefs or generate-fat.sh but using md device and newfs_msdos. -- Emmanuel Vadot <manu_at_bidouilliste.com> <manu_at_freebsd.org>Received on Fri Jul 06 2018 - 04:34:26 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:16 UTC