From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f9b911a67482fcc5d03fd5be2ec21e746b7b8e05
Date: Mon, 20 Jul 2026 17:25:25 +0000 (UTC) [thread overview]
Message-ID: <4h3nTd1Y7Kz2xYf@people01.haj.ipfire.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]
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 f9b911a67482fcc5d03fd5be2ec21e746b7b8e05 (commit)
from 4db5961e21f0c9ff09aea22f55ad877a9b06b29b (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 f9b911a67482fcc5d03fd5be2ec21e746b7b8e05
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Mon Jul 20 17:24:25 2026 +0000
installer: Install EFI parts for riscv64, too
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/installer/hw.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/src/installer/hw.c b/src/installer/hw.c
index 577780af9..2b6687028 100644
--- a/src/installer/hw.c
+++ b/src/installer/hw.c
@@ -114,7 +114,9 @@ struct hw* hw_init() {
snprintf(hw->arch, sizeof(hw->arch), "%s", uname_data.machine);
// Should we install in EFI mode?
- if ((strcmp(hw->arch, "x86_64") == 0) || (strcmp(hw->arch, "aarch64") == 0))
+ if ((strcmp(hw->arch, "x86_64") == 0)
+ || (strcmp(hw->arch, "aarch64") == 0)
+ || (strcmp(hw->arch, "riscv64") == 0))
hw->efi = 1;
return hw;
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-07-20 17:25 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=4h3nTd1Y7Kz2xYf@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