!xmLtiCaAJxfhURjrXl:matrix.org

NixOS RISC-V

236 Members
NixOS on RISC-V https://wiki.nixos.org/wiki/RISC-V https://pad.lassul.us/NixOS-riscv64-linux 71 Servers

Load older messages


SenderMessageTime
9 Mar 2026
@dramforever:matrix.orgdramforeverre: the llvmpipe gpu thing05:00:25
@dramforever:matrix.orgdramforeverthe eic7702x laptop was advertised to have 512 "byte" [sic] rvv supposedly using the dsp cores or something, and that never delivered because there was no way it's gonna work05:01:33
@dramforever:matrix.orgdramforevertbh i don't like how Yuning Liang is apparently becoming the face in the riscv community for other people's contributions05:06:31
@dramforever:matrix.orgdramforeverand/or undeliverable promises05:08:14
11 Mar 2026
@jammie:matrix.orgJamieMageeI'm not sure if there are long-term plans for RISC-V builders on hydra, but I found some notes from a Fedora maintainer working on their RISC-V port: https://marcin.juszkiewicz.com.pl/2026/03/10/risc-v-is-sloooow/ 00:24:22
@hexa:lossy.networkhexaonce beefy rv23a hit00:24:48
@hexa:lossy.networkhexawe have an offer for acces to Spacemit K3 hardware too00:26:24
@hexa:lossy.networkhexa* we have an offer for access to Spacemit K3 hardware too00:26:28
@hexa:lossy.networkhexaI have just doubts its worth it00:26:32
@dramforever:matrix.orgdramforeverhydra.nixos.org no, unofficial native riscv hydra running less frequent evals is starting to become viable00:30:01
@dramforever:matrix.orgdramforeveralso beefy is good for perf, rva23 ... it's limited00:30:34
@dramforever:matrix.orgdramforevernotthe most representative but on reddit on coremark they got -30% perf improvement adding vectors on k3. yes that's negative thirty percent, a downgrade00:31:57
@jammie:matrix.orgJamieMageeThat sounds somewhat promising.00:34:45
@jammie:matrix.orgJamieMageeI tried running hydra using QEMU for RISC-V support, and ran headfirst into: https://github.com/NixOS/nixpkgs/issues/460825#issuecomment-3994959331 TL;DR RISC-V bootstrap binutils is predates support for zca, while GCC 15 now implies support for zca :/00:39:27
@dramforever:matrix.orgdramforeverthat's an unrelated failure00:45:37
@dramforever:matrix.orgdramforeverif convenient can you open a new issue for that? thanks00:46:01
@jammie:matrix.orgJamieMagee dramforever: I opened https://github.com/NixOS/nixpkgs/issues/498689 01:01:39
@jammie:matrix.orgJamieMageeI was going to wait for the bootstrap overhaul, but who knows how long that will take to land. So this should resolve the issue for now: https://github.com/NixOS/nixpkgs/pull/49870202:13:47
12 Mar 2026
@alister:matrix.iridescent.nzAlister GalpinDoes anyone have an example of the minimum needed to get nix onto a device with uboot was just thinking about it and a lot of the previous pain I had was compiling, so thinking I should just get it booting and able to build/switch07:01:31
@dramforever:matrix.orgdramforevernixos? or just nix07:02:14
@alister:matrix.iridescent.nzAlister GalpinNixos07:02:27
@dramforever:matrix.orgdramforeveralso we don't really have prebuilt stuff for riscv so maybe it's not going to be much less pain07:02:36
@alister:matrix.iridescent.nzAlister GalpinTrue, but might make the iterations faster, last attempt took 2 days of compiling 😅07:03:42
@alister:matrix.iridescent.nzAlister GalpinAnd then the image didn't boot ran out of time and now that's 6 months ago at least07:04:47
13 Mar 2026
@eljamm:matrix.orgeljamm joined the room.10:30:39
@eljamm:matrix.orgeljamm Hello, can someone please help test this program? the executable seems to be working, but I have no clue how to test the module. 10:34:42
@alex:tunstall.xyzAlex
In reply to @eljamm:matrix.org
Hello, can someone please help test this program? the executable seems to be working, but I have no clue how to test the module.
It's not 100% reliable, but you can try in qEMU.
Otherwise, for the most reliable results, you will need to wait a few days for someone to do a full native build of your branch.
18:05:40
18 Aug 2023
@shados:nixos.devShados joined the room.05:42:58
@misuzu:matrix.orgmisuzu
% cat /proc/mtd                            
dev:    size   erasesize  name
mtd0: 00080000 00001000 "spl"
mtd1: 00010000 00001000 "uboot-env"
mtd2: 00400000 00001000 "uboot"
mtd3: 00a00000 00001000 "reserved-data"

Looks like the visionfive2_fw_payload.img should be flashed to /dev/mtd2 instead of /dev/mtd1

08:29:39
20 Aug 2023
@erremilia:matrix.orgerremilia joined the room.17:53:34

Show newer messages


Back to Room ListRoom Version: 10