The EFI boot loader handles a boot.cfg file, but one is not installed.
I propose installing a generic one (e.g., like for the i386 and amd64 ports)
during a release build; see the patch below which would of course be augmented
by the actual file. By the way, the added command is within a conditional
block started by:
if [ -f "${release}/usr/mdec/bootarm.efi" ]; then
so it only applies when efi bootblacks are installed.
Is there a compelling reason not to do this?
Cheers,
Brook
Index: distrib/utils/embedded/conf/armv7.conf
===================================================================
RCS file: /cvsroot/src/distrib/utils/embedded/conf/armv7.conf,v
retrieving revision 1.45
diff -u -r1.45 armv7.conf
--- distrib/utils/embedded/conf/armv7.conf 19 Nov 2022 09:19:27 -0000
1.45
+++ distrib/utils/embedded/conf/armv7.conf 20 Mar 2023 18:06:46 -0000
@@ -38,6 +38,7 @@
>> "$tmp/selected_sets"
cp ${DIR}/files/armv7_boot.cmd ${mnt}/boot/boot.cmd
+ cp ${DIR}/files/boot.cfg ${mnt}/boot/boot.cfg
else
# Fallback to non-EFI boot command
cp ${DIR}/files/armv7_boot_nonefi.cmd ${mnt}/boot/boot.cmd
