lopsided98 has quit [Read error: Connection reset by peer]
lopsided98 has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
{^_^} has quit [Read error: Connection reset by peer]
{^_^} has joined #nixos-aarch64
Ericson2314 has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-aarch64
<andi->
cross-compiling images for a RPi3 is probably not fun if feasible at all? :/ I am having a case at work where I'd like to produce an image with some bundled software but no native hardware to build it on..
<sphalerite>
andi-: images I don't think so, but you could take an existing image and just dump some extra cross-compiled stuff in it
<andi->
mhm
<andi->
I might just write the nix expressions and build on the box.. it is just a bunch of python. Probably not worth the time. Having the expressions is the most value of the whole exercise..
<elvishjerricco>
That commit probably *shouldn't* be upstreamed, since it reverts otherwise good work. But right now, that perl script can't be cross compiled
<elvishjerricco>
The real answer is that we should be migrating away from perl and replacing that script with another language that can be easily cross compiled.
orivej has quit [Ping timeout: 252 seconds]
<andi->
the probel being that the perl dbus bindings don't build on aarch64?
<andi->
elvishjerricco: ^
<elvishjerricco>
andi-: There was more than one perl dependency that wouldn't cross compile.
<andi->
:/
<andi->
ok
<elvishjerricco>
Can't remember off hand which ones, but the commit being reverted ultimately added a lot of dependencies to the script, many of which did not cross compile
Thra11 has joined #nixos-aarch64
Thra11 has quit [Quit: WeeChat 1.4]
lopsided98 has quit [Ping timeout: 250 seconds]
lopsided98 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
Ericson2314 has joined #nixos-aarch64
Ericson2314 has quit [Ping timeout: 240 seconds]
samrose_ has joined #nixos-aarch64
samrose_ has quit [Quit: Page closed]
<samrose>
Dezgeg and samueldr how were you compiling ARM trusted firmware for the pine64?
<samueldr>
added it to nixpkgs
<samrose>
samueldr: what tool chain did you use for that one?
<samueldr>
I have no idea about other toolchains, sorry
<samueldr>
(the instructions I said I wrote yesterday were only for u-boot, on an armv7l platform lacking ATF)
<samrose>
samueldr: so this one needs to run in an existing nixos installation running on an ARM64 device
<samueldr>
or any aarch64 distro, where you could install nix
<samueldr>
[16:20:15] <sphalerite> samrose: or you could bootstrap it from a non-nixos linux distro on your bananapi
<samueldr>
[16:33:35] <Dezgeg> samrose: as an alternative to qemu, AFAIK if you have some existing distro for the board you could install the standalone nix with the usual curl https://nixos.org/nix/install | sh and use that to build u-boot
<samrose>
aha ok!
<samrose>
I actually got that working
<samrose>
today
<samueldr>
oh, then you're in business
<samrose>
so I have nix running on an ubuntu machine on the bananapi
<samrose>
m64
<samueldr>
it may not be much help, but now you can do as you would on nixos for adding the necessary bits for your board :)
<samueldr>
checking commits around the u-boot and arm-trusted-firmware files could help see what's needed
<samrose>
supposedly this "bl31" is what I would need for the bpi m64
<samrose>
so I basically need to dd if=my.bin of=/dev/sdX bs=1024 seek=8 and then sudo dd if=sd-image-aarch64-linux.img of=/dev/sdX onto the sd card and then it should boot nixos
<Dezgeg>
yes but other way around
<samrose>
Dezgeg: ok I should copy the image first
<samrose>
thank you Dezgeg samueldr
<samueldr>
thank you, and do send a PR :)
<samueldr>
(the thanks was in advance for the PR)
<samrose>
samueldr: sure thing
<samrose>
if ever wanted to try and build my own sd-image-aarch64-linux.img Dezgeg do you have something around that could give an example of how you achieve that?