| 15 Jun 2026 |
 liberodark | * Hi,
I'm not sure I understand either, I think we may not be talking about the same thing. Maybe my point isn't clear enough. But EDK2 support seemed more obvious to me than U-Boot for UEFI. Mainly because, as I said, it's the one already in use. Now, on the question of full UEFI support, I think we could be talking about a misuse of terms, even though from memory the two aren't at the same level. Furthermore, I was mainly referring to its already active integration on the K3. And as for Option ROMs on PCIe cards the support is there in the firmware (the platform includes PciBusDxe), but that's not what I was referring to.
Best Regards | 17:32:15 |
| liberodark | PS: By the way, I forgot to ask my question: which SBC do you have ? dramforever | 17:36:00 |
| liberodark | Hi, radex
I'm just getting back to you because I don't know where you are with your K3.
But I should be receiving a similar model to yours.
Best Regards
| 17:50:39 |
 radex | yeah, I'm sorry I was silent, life got in my way. I didn't touch my K3 alas, I'll try to do that in the next couple of days, but I can't promise :( | 17:52:02 |
| liberodark | No worries, it's not meant that way.
I just meant that I might be able to save you some time, that's all. | 17:53:02 |
| radex | Much appreciated. | 17:53:41 |
| liberodark | But I won't be able to see it until this weekend. | 17:53:44 |
| 16 Jun 2026 |
 colemickens | anyone playing with the github runner riscv64 port and getting it on nixos/nixpkgs ? | 01:32:40 |
| colemickens | I might look at that now that my toplevel is cross-compiled thanks to liberodark's nixos-hardware PR. 🙏 | 01:33:01 |
| colemickens | (also curious if boot from NVME works with EDK2) | 01:33:33 |
 dramforever | hi, i only personally have a visionfive 1 but i have access to the k1 based bpi-f3 at work (it's just not mine), and some other stuff (k3 "soon" i'm guessing) | 03:05:49 |
| dramforever | i had a visionfive 2 but i gave it to someone else lol | 04:39:45 |
| colemickens | (Remembering that the Actions runner agent is top-notch .NET code, and that dotnet surely doesn't support riscv64-linux yet, and I'm not going down that rabbit hole...) | 04:48:15 |
| colemickens | I'd rather have Claude rewrite the runner agent in Go or Rust | 04:48:28 |
 JamieMagee | You mean this one? https://github.com/riseproject-dev/riscv-runner | 16:23:24 |
| colemickens | well, that's the runner scheduler app and infra, I'm thinking more of the agent that runs and then actually picks up the job. That's the real blocker here for me. | 16:24:25 |
| colemickens | That project, for example, still requires riscv64-linux runners, running their riscv agent fork, built with their dotnet-riscv port. :( | 16:25:02 |
| liberodark | Have solution for you | 21:38:37 |
| liberodark | https://github.com/NixOS/nixpkgs/pull/530693 | 21:38:57 |
| liberodark | And | 21:39:11 |
| liberodark | https://github.com/Cloud-V-10xE/github-runner-riscv | 21:39:55 |
| liberodark | Also have package that | 21:40:05 |
| liberodark | * Hi, have solution for you | 21:40:44 |
| colemickens | but doesn't that need dotnet-riscv ? surely you didn't.... also do that | 21:40:50 |
| liberodark | First is in Go | 21:41:25 |
| liberodark | So not need dotnet | 21:41:36 |
| liberodark | And you can look at : https://github.com/Cloud-V-10xE/dotnet-riscv | 21:42:09 |
| liberodark | If you need | 21:42:12 |
| liberodark | * If you need dotnet | 21:42:19 |
| colemickens | OH! Does the riscv-runner release have a dotnet build inside of it?! | 21:42:38 |
