<jma>
krzk: I checked that the boot image is fine using an old kernel. I created an init that just reboot after 20 seconds therefore at least I know if the kernel boots fine or not.
<jma>
krzk: I tried with a very minimal dtb and nothing happens. I think there is something wrong with the bootloader (Android)
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
ungeskriptet has joined #linux-exynos
jma has quit [Remote host closed the connection]
jma has joined #linux-exynos
<krzk>
jma: if by old kernel you mean something like v5.4 then you could try to bisect it. If you mean vendor/downstream kernel, then it's quite obvious it should work :)
<jma>
krck: yes but wanted to be sure that everything around was ok
<jma>
krzk: Now the kernel is using a DTB that just import the 5250 dtsi. I think that's enough hit the init script but he doesn't. The DTB is appended to Zimage. Do I have to set something special to enable the DTB except CONFIG_ARM_APPENDED_DTB=y ?
<jma>
krzk: I set CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y