<lovesegfault>
what's the right way to only enable something in my nixos config if the system is aarch64-linux? do I just check `nixpkgs.localSystem.system`?
<samueldr>
it seems that for OEM android-based device kernels the `[z]install` step rebuilds the kernel
blackriversoftwa has quit [Read error: Connection reset by peer]
blackriversoftwa has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
justanotheruser has quit [Ping timeout: 272 seconds]
cole-h has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
cole-h has quit [Ping timeout: 258 seconds]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
elvishjerricco has quit [Ping timeout: 240 seconds]
elvishjerricco has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
h0m2 has quit [Ping timeout: 240 seconds]
h0m2 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
alpernebbi has joined #nixos-aarch64
fooker has joined #nixos-aarch64
fooker has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Error from remote client"]
t184256 has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
jboy24 has joined #nixos-aarch64
<jboy24>
hello, I'm trying to get mobile-nixos to install on a new pinephone (postmarketOS convergence edition 3GB RAM and 32eMMC). Has anyone had any luck with this? Should the nix-build device pine64-pinephone-braveheart work?
jboy24 has quit [Remote host closed the connection]
jknixos has joined #nixos-aarch64
<jknixos>
hello
jknixos has quit [Client Quit]
orivej has joined #nixos-aarch64
<betaboon>
seems like gdk-pixbuf doesnt cross-compile anymore ?
orivej has quit [Ping timeout: 256 seconds]
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 272 seconds]
<thefloweringash>
I just discovered the uh, delicacy, of perl cross compilation :-(
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
alpernebbi has quit [Quit: alpernebbi]
ryantrinkle has joined #nixos-aarch64
orivej has joined #nixos-aarch64
ekleog has quit [Quit: back soon]
ekleog has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
sphalerite has quit [Quit: boot, boot, boot, boot, reboot the outdated server]
nschoe has quit [Remote host closed the connection]
sphalerite has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
alp has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 260 seconds]
<samueldr>
:/ jboy24 is gone... there's a PR for the update of u-boot open
<samueldr>
with IIRC work to be done by the author
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
<lovesegfault>
clever: do you happen to remember during our zillion different attempts which one had the touchscreen being recognized?
<clever>
i dont think we got that working
<clever>
it would need the overlay i think, to tell linux to use it
<lovesegfault>
I do remember us seeing the goodix device in dmesg at one point
<lovesegfault>
Right now I have the device running in the simplest way we had: rpi bootloader, kernel 4.9, dtoverlay, the dumb init code
<lovesegfault>
b/c I wanted to see if the touchscreen would show up
<lovesegfault>
but nop
<lovesegfault>
oh, wait, I see it
<lovesegfault>
clever: since you know RPi graphics stuff, does the 4 support OpenGL 3.3?
<samueldr>
before fetching the msm-4.9 repo, my linux .git is 8.2GB
<samueldr>
let's see how much it grows
<clever>
lovesegfault: not as up to date on what the 4 changed
<clever>
lovesegfault: simplest answer is to check glxinfo on raspbian