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 4hdrb62PGLz36Vw for ; Mon, 07 Sep 2026 15:29:22 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "YR2" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4hdrb25kmWz2xVG for ; Mon, 07 Sep 2026 15:29:18 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4hdrZt3dtRzsm for ; Mon, 07 Sep 2026 15:29:10 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1788794950; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=eHCQfM3s0zOraq7pBFrd7fpP+yKRIBoyCpueLOK1x+U=; b=MWo56AmJzUQkB0wegm6DoZTmVotpm4UplNBzejp9grpAVcqZk7HtxPRuE38ktDbF+h7r00 etdITgIACb9HYoAQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1788794950; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=eHCQfM3s0zOraq7pBFrd7fpP+yKRIBoyCpueLOK1x+U=; b=BsA29q5Lj1rxYftOBdWTUHvmmmv6/X4n2ny+j0WnqhqdAtseQOBER+Dzb0IIcTfbSqMHPU lfgVlpHNaUhimQW7+QdNkJCR9DQL8vXNAiD56e+on6eghNaXTEVhyzExJb6s+5RCPguhFL xxJcs78dtRNomZJE/NwYfImnhl92Htg3pH8QikqCU3Y+l7cKBOT6l3HRT1SmdZR4w+6UT/ CZOfz5StIoYIiICL5uL2GmZC231ClhDhD5aR/GGttrqTaWShlr/CTj95oChoJl773lFAjw EyyG4CMnWoGg9B8Fof2Vwfkzj6zE2D7DCNhWyT/8x0ifk6vMY3k7JD6yh8oXgQ== From: Michael Tremer Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: IPFire on RISC-V: Looking for hardware expertise Message-Id: <271DB403-043B-4BB3-A077-55416FB72AA1@ipfire.org> Date: Mon, 7 Sep 2026 16:29:09 +0100 To: "IPFire: Development-List" Hi all, I have been running IPFire on riscv64 in a virtual machine for a while = now, and it is boring in the best possible way. It installs, it boots, = the web interface works, firewall, IPsec, WireGuard, Suricata and = Pakfire all do what they are supposed to. I have not found a single bug = that was caused by the architecture. I did not expect that as porting IPFire to ARM way rather painful. The problem is that a VM is an idealised machine. It has no firmware = worth speaking of, no real network cards, no storage controllers and so = on. Every part of a system that usually causes trouble is the part we = have not touched. So I am looking for people who know RISC-V hardware and want to work on = this with us. The things that need doing: * Getting our installer to boot on real firmware using UEFI * Validate our kernel configuration and drivers for network hardware * Finding out what throughput looks like once traffic goes through = real interfaces I intend to only support UEFI-enabled systems. One image for everything, = no per-board images, no vendor boot scripts, no device trees to = maintain. If your system boots a Debian or Fedora image, IPFire should = boot too. Anything you can test is useful, but where I would like this to end up = is on hardware you would trust to route traffic for years without = touching it. That class of RISC-V machine is only starting to appear, = and I would like us to be ready when it does. If you want to get involved, nightly builds are available here: https://nightly.ipfire.org/next/latest/riscv64/ Please report any problems directly to bugzilla.ipfire.org = and post your experience right here. Best, -Michael=