<clever>
you also need the relocation files for the gpu_mem option to work
<clever>
fixup*.dat
<clever>
without that, the start.elf is non-relocatable, and winds up somewhere in the middle of ram
<clever>
and with physical ram cut in half, linux cant easily use it all, so it just ignores the gpu_mem option and moves the split
<clever>
i dont remember what _x did differently though
<clever>
bbl
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
<bkchr[m]>
clever: Thanks for your tip, I looked again what `start_x` is doing and saw, that I did not have the `fixup_x.dat` file in place.
<clever>
ah
<clever>
it is kind of weird that the firmware cant do relocation, even though elf supports it
<bkchr[m]>
However, I still can not load the camera kernel module :(
<clever>
i suspect that bootcode.bin has basically zero ELF support, and just copies start.elf into ram as a dumb blob, and fixup is just a binary patch
<bkchr[m]>
clever: do you maybe have an idea, to know which dtb file the bootloader appended?
<clever>
i think you can see the entire dtb tree osmewhere in /sys, not sure where
<bkchr[m]>
Yeah, I was able to print it
<clever>
and there should be other tools to convert a dtb blob back into text
<bkchr[m]>
`dtc -I fs -O dts /sys/firmware/devicetree/base` does the trick for the running system
<bkchr[m]>
I think the dtb upstream file is missing a node for activating the camera stuff
<clever>
i do have 3 rpi's and a camera, so i could test things as well