<WaldemarTomme[m]>
I basically redid the whole device tree (only reserved regions and pins for now) and finally got somehow ramoops working. i wonder if it's possible as well on the android kernel to get an output of all reserved memory regions like in this log. also could the kernel commandline be a problem? https://pastebin.com/zpZxg7wV
<ungeskriptet>
WaldemarTomme[m]: You can get the memory regions from the downstream fdt
<ungeskriptet>
also you should fix the memory overlaps
<WaldemarTomme[m]>
fdt? also what's the worst that could happen with overlapping memory? I understood it like the regions are reserved but unused until something explicitly uses it
<Adrian[m]>
<WaldemarTomme[m]> "fdt? also what's the worst..." <- overlapping memory means that your reserved memory regions are definitely wrong
<WaldemarTomme[m]>
ah, do you mean full device tree? if so then I'm already using it to check the memory regions and the overlaps are only because the original regions are merged into one but bigger than in the sm1750 base config so i just added it for now to reserve the specified memory but I don't know how to map everything correctly there
<WaldemarTomme[m]>
now I see the fdt in /sys/firmware/fdt
<Adrian[m]>
fdt means flattened device tree
<WaldemarTomme[m]>
oh
<WaldemarTomme[m]>
well anyway that's what I used to check all memory regions