| 17 May 2026 |
|  Llamato joined the room. | 16:21:38 |
| 19 May 2026 |
 colemickens | What's the hope/expectations for bootable media for these K3 boards in a few weeks? | 17:53:37 |
| colemickens | I guess for a minimal ISO, cross-compile should be ... hopefully achievable? | 17:53:57 |
 Alex | Yes, NixOS cross is known to work. The biggest question will be how to configure the kernel and bootloader. | 18:37:08 |
 Tristan Ross | I've got a DC ROMA III on the way, I plan on getting NixOS fully booted on this. | 21:35:20 |
| 20 May 2026 |
 liberodark | Hi,
I got a K3 to install Nixos on, if everything goes well.
It will be available for compiling apps.
I could send you my iso if needed.
Best Regards | 13:05:48 |
| 21 May 2026 |
| liberodark | * Hi,
I got a K3 to install Nixos on, if everything goes well.
It will be available for compiling apps.
I could send you my img if needed.
Best Regards | 07:14:18 |
| colemickens | Yeah, mostly curious if there's a rallying point for:
- bootloader/firmware config
- iso configuration + pre-cached builds (though not important if cross-compilable)
| 19:00:42 |
| colemickens | I'm not even sure if there's SPI for (u-boot?) or if that has to go on sdcard, etc. | 19:01:02 |
 grw00 | nice, don't forget the NPU :) | 19:23:46 |
| grw00 | i also have one ordered, i forget the vendor. hopefully BROM supports bringup over usb, then nixos+mainline is just a matter of throwing claude at /dev/ttyACM0 | 19:24:55 |
| liberodark | Hi,
I think it's entirely possible; that's what I did on the K1.
Best Regards | 20:35:23 |
| liberodark | But in my opinion, the K3 is still much simpler to work with than other current CPUs.
I'm eager to see what Tristan will do with the DC Roma III. | 20:38:01 |
| 25 May 2026 |
|  radex joined the room. | 12:11:10 |
| radex | 
Download 9D14A408-C4B6-44E9-B081-BD1121E0F7B3_1_102_a.jpeg | 12:12:01 |
| radex | hello 👋 hoping to run nixos on this thing soon(ish) :) | 12:12:32 |
| radex | (I'd get started on hacking today but they forgot to put a suitable power supply in the box lol) | 12:12:49 |
 implr | In reply to @grw00:matrix.org
nice, don't forget the NPU :) that NPU should be able to run normal linux processes too, these are regular rva23 cores with a fat vector unit | 12:25:11 |
| implr | but iirc spacemit did some scheduler crimes to isolate them for ai | 12:25:31 |
| Alex | Doesn't that mean you could patch the kernel to get them running as normal cores?
If they were kind, they might've even left it as a Linux kernel option (otherwise, nothing is stopping you from contributing one for that purpose :D) | 12:26:45 |
|  ari ❄ joined the room. | 12:28:32 |
| implr | I assume you could (or undo their patch). Still the endgame is to get proper mainline kernel support, vendor kernels suck | 12:29:12 |
 dramforever | their kernel was patched to get them running as normal cores | 12:39:39 |
| dramforever | there's some cpu mask weirdness you can do to throw a process onto the "other" 8 cores | 12:40:28 |
| dramforever | on mainline it doesn't work because nobody bothered adding support to handle isolating cores based on vlen (because it's not, in general, possible to migrate processes between vlen differing cpus) | 12:41:25 |
| dramforever | the main two things stopping you from contributing changes to spacemit vendor kernels are
- RoI
- i don't think there's anyone at spacemit to receive your contribution. they're probably all busy af working on their next and next next chips' sw
| 12:43:49 |
| dramforever | your patches would probably need to be Icenowy level for them to take it, like "make amd gpus working" | 12:45:10 |
| dramforever | * your patches would probably need to be Icenowy level for them to take it, like "get amd gpus working" | 12:45:22 |
| grw00 | hm interesting. do they provide sdk with vendor kernel that knows how to use these cores? | 17:24:19 |
| implr | the long term path should be mainline anyway | 18:01:19 |
