| 22 Feb 2022 |
 Alyssa Ross | worked fine apart from requiring a small tweak to nixpkgs to tell it which of NetBSD's multiple ppc32 targets to use | 11:26:44 |
|  Mika Feiler left the room. | 12:02:35 |
| 23 Feb 2022 |
 ius | colemickens 🏳️🌈: I assume you're going to build for RISCV/StarFive using qemu-user? We might want to sort out some way to divide the effort, considering it's really, really slow. | 19:49:56 |
| ius | I think Zhaofeng Li has a public cache up, but I haven't attempted to use it as I'm not quite sure our closures overlap all that much right now (due to qemu related patches). | 19:53:00 |
 [0x4A6F] | ius and colemickens 🏳️🌈, there are also packages inbound for Zhaofeng Li an me. | 19:53:18 |
| ius | Great 🙂 | 19:54:09 |
 Zhaofeng Li | We could have a shared hydra instance that we can all contribute some builders | 19:54:23 |
| ius | I'm building on a Hetzner box right now which I don't mind hooking up to whatever. It's not particularly fast though. | 19:55:11 |
| Zhaofeng Li | If we have a hydra, I guess it will have to be real hardware or qemu-system. qemu-user is pretty hit-and-miss and I don't think there's a good solution to make it automatically retry failing derivations on native builders. | 20:07:40 |
| Zhaofeng Li | On the other hand, qemu-system is indeed very slow (qemu-system on 3900X is barely as fast as U74 in some benchmarks) | 20:09:03 |
| Zhaofeng Li | * If we have a hydra, I guess it will have to be real hardware or qemu-system. qemu-user is pretty hit-and-miss and I don't think there's a good solution to make Hydra automatically retry failing derivations on native builders. | 20:10:02 |
| ius | I'm not sure how bad things are outside of the sdImage closure, but at least that one builds okay for me using qemu-user (and some patches). | 20:18:30 |
| ius | Here's my current tree, in case it's of use to anyone: https://github.com/ius/nixpkgs/commits/riscv64-20220219 | 20:20:04 |
| Zhaofeng Li | Yeah, I have a few "disable tests" commits on my branch as well (I just rebased a couple of days ago, haven't pushed yet). Those can make it hard to reuse stuff from binary caches when everyone is working on different trees | 20:27:51 |
 colemickens 🏳️🌈 | [0x4A6F]: are you packaging the jh7100 tools by chance? That was the only thing I'd found that wasn't in one of the other two repos. | 22:00:23 |
| [0x4A6F] |
- [ ] https://github.com/starfive-tech/JH7100_ddrinit
- [ ] https://github.com/starfive-tech/JH7100_secondBoot
| 22:05:42 |
| [0x4A6F] | Only on the radar, no work done. | 22:06:29 |
| 24 Feb 2022 |
| ius | This one I think? https://github.com/kprasadvnsi/JH71xx-tools - it's a single file project, should be easy enough. Shouldn't be needed if you don't mess up the SPI flash ;) | 08:51:52 |
 qbit | https://github.com/renode/renode might be a handy tool for all this jazz :D | 22:13:16 |
| qbit | oh, i guess all the boards are embedded | 22:14:07 |
| qbit | i saw some of the sifive cpu's listed and assumed it could emu a full board | 22:14:49 |
| Zhaofeng Li | It should be able to. Renode was the "officially blessed" tool for emulating the Starlight board which is the precursor to VisionFive | 22:43:02 |
| 25 Feb 2022 |
| qbit | Oh nice | 01:20:06 |
| qbit | I have it building on nixos, but the ui isn’t working | 01:20:27 |
| qbit | https://gist.github.com/qbit/55992415f8ae26320d20b499265976ca | 01:21:27 |
| ius | I looked at it before, but concluded it doesn't fit the use case - although they pull in qemu's tcg the SoC itself seems implemented in C#. Guess it'll take slow to a whole new level. | 08:05:28 |
| ius | Qemu system emulation of one of the virt RISCV targets will be (a lot?) faster. It's a neat project if you have on board peripherals you'd like to emulate (or co-simulate?), though | 08:06:31 |
 Jamie | oh I have a Freedom Unleashed sitting unused i’d be happy to contribute to a build farm if it’d be helpful | 09:47:44 |
| Jamie | or uh | 09:48:03 |
| Jamie | HiFive Unleashed that is | 09:48:13 |
