2013/12/31 Hans de Goede <[email protected]> > > I've just pushed my latest work to: > https://github.com/linux-sunxi/linux-sunxi/commits/sunxi-devel > > Which I'm currently maintaining and is the tree to use if you want to > follow upstream > sunxi development. > > Try comparing the sun7i-a20.dtsi and sun7i-a20-cubietruck.dts files there > with the ones > you're using. Maybe there is some other change there too, or maybe somehow > just having > something extra in the dtb (making it larger) mysteriously fixes things ? > > Regards, > > Hans > > p.s. > > I'm going AFK till 2014, see you then, and happy new year.
Hans, After downloading everything again and recompiling, I think I figured out where the culprit is: its the fdt loading and mangling by PSCI. Check this commit https://github.com/jwrdegoede/u-boot-sunxi/commit/a5cc529a6126cedab52899375fdd10733e2e5456 This code emits the things needed for PSCI to work, and without them even if you have PSCI in kernel, you will have -38 on second CPU bringup. Next, I tried disabling "appended fdt to zImage" (CONFIG_ARM_APPENDED_DTB) option in the kernel and I got interesting results: my kernel stopped booting. This means that it does not read mangled fdt from u-boot, instead it was reading appended raw fdt without PSCI nodes emited. I also checked if it is an ATAG issue by adding "chosen { bootargs = "<...>"; };" to my fdt to check wether it is booting but without console output - but no luck here too. Could you please show us all your boot envorinoment and, especially, fdt related things? I think we have a little problem here with default u-boot env not ready for fdt loading. Best Regards, Dmitriy Beykun p.s.: Happy New Year to you too. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
