public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c9dcbcf4e65abd1fb9905e1ab78bbee3d6f2d9d8
Date: Wed, 18 Nov 2026 14:41:10 +0000 (UTC)	[thread overview]
Message-ID: <4jV46G4J0nz2xNN@people01.haj.ipfire.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  c9dcbcf4e65abd1fb9905e1ab78bbee3d6f2d9d8 (commit)
       via  2a56b6b21701fd5f2499dc9563245b6415368b39 (commit)
      from  073121d987f1c576afa85f7c94a8ff9e8ff40547 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c9dcbcf4e65abd1fb9905e1ab78bbee3d6f2d9d8
Author: Michael Tremer <michael.tremer@ipfire.org>
Date:   Wed Nov 18 14:39:15 2026 +0000

    cdrom: Use the uppercase EFI boot filename on all architectures
    
    The UEFI specification calls the fallback bootloader BOOT<ARCH>.EFI.
    ISO9660 itself only knows uppercase names and the lowercase name is only
    visible through the Rock Ridge/Joliet extensions, which some firmware
    compares case-sensitively. Most firmware does not care, which is why
    only LoongArch has been affected so far.
    
    Instead of special-casing LoongArch, use the uppercase name everywhere.
    EFI_ARCH is "x64" on x86, so the name is uppercased as a whole to get
    BOOTX64.EFI. This is also what lfs/flash-images already does.
    
    Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

commit 2a56b6b21701fd5f2499dc9563245b6415368b39
Author: Vincent Li <vincent.mc.li@gmail.com>
Date:   Fri Nov 6 05:36:59 2026 +0000

    cdrom: Use uppercase EFI boot filename on LoongArch
    
    Some Loongson 3A6000 firmware reads the ISO9660 filesystem
    case-sensitively and fails to find bootLOONGARCH64.efi. The
    uppercase BOOTLOONGARCH64.EFI is valid UEFI naming and works
    on unaffected firmware too, so use it on LoongArch only.
    x86, ARM and RISC-V are unchanged.
    
    Tested on a Morefine M700S (Loongson 3A6000).
    
    Tested-by: Vincent Li <vincent.mc.li@gmail.com>
    Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
    Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/cdrom | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/lfs/cdrom b/lfs/cdrom
index 11604b722..f28372bd4 100644
--- a/lfs/cdrom
+++ b/lfs/cdrom
@@ -66,6 +66,10 @@ ISO_ARGS += \
 
 ISO_FILE = $(IMAGES_DIR)/$(SNAME)-$(VERSION)-core$(CORE)-$(BUILD_ARCH).iso
 
+# The UEFI specification calls the fallback bootloader BOOT<ARCH>.EFI. Some
+# firmware reads the ISO9660 filesystem case-sensitively, so use that exact name.
+EFI_BOOT_FILE = $(shell echo BOOT$(EFI_ARCH).EFI | tr a-z A-Z)
+
 # Dracut modules that the installer does not need
 INSTALLER_OMIT_MODULES = \
 	cifs \
@@ -185,7 +189,7 @@ endif
 
 	# Build a GRUB EFI image
 	mkdir -pv $(DIR_TMP)/cdrom/EFI/BOOT
-	$(call GRUB_MKIMAGE,$(GRUB_ARCH)-efi,/EFI/BOOT,$(DIR_TMP)/grub-efi.cfg,$(DIR_TMP)/cdrom/EFI/BOOT/boot$(EFI_ARCH).efi)
+	$(call GRUB_MKIMAGE,$(GRUB_ARCH)-efi,/EFI/BOOT,$(DIR_TMP)/grub-efi.cfg,$(DIR_TMP)/cdrom/EFI/BOOT/$(EFI_BOOT_FILE))
 
 	# Install GRUB configuration
 	mkdir -pv $(DIR_TMP)/cdrom/EFI/BOOT
@@ -199,7 +203,7 @@ endif
 	# Copy the bootloader into the image
 	mmd -i $(DIR_TMP)/cdrom/boot/isolinux/efiboot.img ::/EFI ::/EFI/BOOT
 	mcopy -i $(DIR_TMP)/cdrom/boot/isolinux/efiboot.img \
-		$(DIR_TMP)/cdrom/EFI/BOOT/boot$(EFI_ARCH).efi ::/EFI/BOOT/boot$(EFI_ARCH).efi
+		$(DIR_TMP)/cdrom/EFI/BOOT/$(EFI_BOOT_FILE) ::/EFI/BOOT/$(EFI_BOOT_FILE)
 
 	# Show what has been copied
 	mdir -/ -i $(DIR_TMP)/cdrom/boot/isolinux/efiboot.img ::


hooks/post-receive
--
IPFire 2.x development tree


                 reply	other threads:[~2026-11-18 14:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4jV46G4J0nz2xNN@people01.haj.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox