From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4jV46b4tR4z2xV5 for ; Wed, 18 Nov 2026 14:41:27 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "YR1" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4jV46X1N0sz2xNM for ; Wed, 18 Nov 2026 14:41:24 +0000 (UTC) Received: from michael.haj.ipfire.org (michael.haj.ipfire.org [172.28.1.242]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bit raw public key) server-digest SHA256 client-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "michael.haj.ipfire.org", Issuer "YE1" (not verified)) by mail01.ipfire.org (Postfix) with ESMTPS id 4jV46W3pQszF5; Wed, 18 Nov 2026 14:41:23 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1795012883; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tSJYfrC6mferaWWA8hmt03Z1kBt5s2Yf1PSXl11zq7s=; b=Fu7EA4JS17aywfeNlC+RPtWSLY32PBMAlsuJMoowdgNMpWD8B+1B2aAs+6olks5aBhvXdl QkkHJJEqRIVtYwBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1795012883; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tSJYfrC6mferaWWA8hmt03Z1kBt5s2Yf1PSXl11zq7s=; b=vY236fkvYkBt+ATixMbwReL1jZnWbB8woSdg2i3HpodjwXpsrFbVeDIo4tC++4iSD3I2Jj D47xJDyIBdeFr5kCl/jqABWU1iyJWWD724Gg4OBqAwDtXxe23y61miTQUVY6w/aJ2+Pu/e AaGITKpvF4eG4rmcaEkOxxjkjFd6WQRTidfv1DO7hAvk7jMDB7NmEdIbvDrt7aN2A6II3X XFWzFKr/gfOoEHGWHdJ7w0sSsjGHn/jafx983pMpPw1nBo75LF5+pd3ss3VdfplEiRS5KR tLibmfAAt+NoeF4U756jxpk2zdkBzAm2thMG3mbMri6l/+kSJapUmv6uT0TPlA== Received: by michael.haj.ipfire.org (Postfix, from userid 0) id 4jV46W2rr1zTgNg; Wed, 18 Nov 2026 14:41:23 +0000 (UTC) From: Michael Tremer To: development@lists.ipfire.org Cc: Vincent Li Subject: Re: [PATCH] cdrom: Use uppercase EFI boot filename on LoongArch In-Reply-To: <20261106053659.1881811-1-vincent.mc.li@gmail.com> References: <20261106053659.1881811-1-vincent.mc.li@gmail.com> Date: Wed, 18 Nov 2026 14:41:23 +0000 Message-ID: <1795012883.4063288.reply@ipfire.org> Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Hello Vincent, Thank you for the patch and for testing it on real hardware. I have merged it, and added a small follow-up on top. I did not want to special-case LoongArch, because the uppercase name is the correct one everywhere. ISO9660 itself only knows uppercase names. The lowercase name only exists through the Rock Ridge/Joliet extensions, and firmware that reads those compares names exactly. The UEFI spec calls the fallback loader \EFI\BOOT\BOOT.EFI. Most firmware is case-insensitive and does not care, which is why only your Loongson board noticed. lfs/flash-images already uses the uppercase name, so the ISO was the odd one out. So the follow-up drops the ifeq and uses the uppercase name on all architectures. EFI_ARCH is "x64" on x86, so a plain BOOT$(EFI_ARCH).EFI would still have given BOOTx64.EFI. The name is now run through tr to get BOOTX64.EFI. Your commit is kept as it was, with you as the author, so the history shows where the change came from. Thanks for tracking this down. Would you mind testing the final result on the M700S once more? Best regards, -Michael