thefloweringash has quit [Read error: Connection reset by peer]
clever has quit [*.net *.split]
andi- has quit [*.net *.split]
andi- has joined #nixos-aarch64
clever has joined #nixos-aarch64
bkchr[m] has quit [Ping timeout: 245 seconds]
sphalerit has quit [Ping timeout: 246 seconds]
codyopel has quit [Ping timeout: 246 seconds]
thefloweringash[ has quit [Ping timeout: 268 seconds]
grahamc has quit [Ping timeout: 255 seconds]
dtz has quit [Ping timeout: 240 seconds]
cornu has quit [Ping timeout: 276 seconds]
shad_ has joined #nixos-aarch64
Mic92_ has joined #nixos-aarch64
Mic92 has quit [*.net *.split]
shad has quit [*.net *.split]
bkchr[m] has joined #nixos-aarch64
sphalerit has joined #nixos-aarch64
dtz has joined #nixos-aarch64
grahamc has joined #nixos-aarch64
codyopel has joined #nixos-aarch64
cornu has joined #nixos-aarch64
thefloweringash[ has joined #nixos-aarch64
angerman has quit []
angerman has joined #nixos-aarch64
Sonarpulse has joined #nixos-aarch64
Sonarpulse has quit [Ping timeout: 256 seconds]
mekeor has joined #nixos-aarch64
<mekeor>
is it better to use the unstable or the stable channel on aarch64 (raspberry pi 3)? the wiki says that hydra now offers binary cache for stable channel for aarch64, too. so is there any reason why unstable should be better?
Sonarpulse has joined #nixos-aarch64
<Dezgeg>
if you need bleeding edge device support then unstable, I suppose (e.g. rpi 3+ when it hits mainline kernel + u-boot)
orivej has quit [Ping timeout: 255 seconds]
<duncan^>
Fairly certain Pi 3 works with mainline rn