| 15 Aug 2024 |
|  Ben Ford joined the room. | 07:56:36 |
|  @iamkexo:matrix.org joined the room. | 21:37:57 |
| 16 Aug 2024 |
|  @thedragon44:matrix.org left the room. | 00:25:15 |
|  @glaringweakness:nope.chat left the room. | 01:15:52 |
| 17 Aug 2024 |
|  dhofer joined the room. | 14:30:53 |
|  Morgan (@numinit) joined the room. | 23:42:52 |
| 18 Aug 2024 |
|  sefidel joined the room. | 08:44:52 |
|  r3vx joined the room. | 14:16:52 |
| 19 Aug 2024 |
|  @stooj:matrix.org joined the room. | 13:17:56 |
| 21 Aug 2024 |
|  @rgrunbla:matrix.org joined the room. | 08:40:26 |
|  0rb1t joined the room. | 13:21:26 |
|  Luna joined the room. | 16:22:55 |
|  @shymega:one.ems.host joined the room. | 16:36:40 |
|  Sebastian (he/him) joined the room. | 19:02:42 |
|  theelevated joined the room. | 19:53:11 |
| theelevated | Is there a guide on how to run nixos on non standard arch like arm and riscv? How to compile linux manuelly and deploy it. | 19:54:22 |
 K900 ⚡️ | We support aarch64 and to some extent risc-v | 19:59:39 |
| K900 ⚡️ | So it really depends on what you're actually looking to do | 19:59:57 |
| 22 Aug 2024 |
| theelevated | Redacted or Malformed Event | 07:50:14 |
| theelevated | In reply to @k900:0upti.me
So it really depends on what you're actually looking to do A gentoo like experience which is quickly depolyable (nixos) with a custom mirror and Repo since the device is ressource tight not being able to compile on its own. | 07:50:29 |
| theelevated | So a ressource stronger device can be the mirror and compile with custom flags | 07:52:07 |
| theelevated | Its for a riscv device | 07:52:13 |
 ElvishJerricco | theelevated: the big problem with most non-x86 devices is just getting them to start a boot loader, which is rarely standardized unless you're dealing with server hardware. Once you have that working, it's just normal nixos stuff mostly. | 08:08:42 |
 magic_rb | Once you get into a running system, then a normal nixos-rebuild --target-host will suffice. Problem is getting into a running system | 08:35:43 |
| magic_rb | Do you happen to have a functional kernel+uboot available? Can be from a different distro, it doesnt matter from where, you just need the source code and hopefully some documentation, but that is also optional with enough determination. | 08:36:33 |
| magic_rb | The kernel should also be relatively recent, though technically it should be possible to make anything 4.4+ work to some degree, id avoid any kernels marked as vendor and those tend to have very nonstandard patches and interfaces. | 08:38:32 |
| magic_rb | * The kernel should also be relatively recent, though technically it should be possible to make anything 4.4+ work to some degree, id avoid any kernels marked as vendor as those tend to have very nonstandard patches and interfaces. | 08:38:47 |
| magic_rb | And ideal kernel would be 6.0+ which is called something like main or mainline which generally means its a very close fork of mainline linux that is hopefully in the process of being upstreamed | 08:39:30 |
| theelevated | In reply to @elvishjerricco:matrix.org
theelevated: the big problem with most non-x86 devices is just getting them to start a boot loader, which is rarely standardized unless you're dealing with server hardware. Once you have that working, it's just normal nixos stuff mostly. I have some https://milkv.io/duo and they can boot their own 1st party linux. | 08:49:46 |
| theelevated | How to crosscompile everything from a x86, image it and boot the chip | 08:50:08 |
