okay i think i understand most of it but my knowledge of the dtb / aml kernel relationship, is too limited, i'll try to learn more about that.
One last thing though, the modifications or patches you mention for the external dtb, are they made manually by yourself or do they come from the kernel source code ?
In other words would it be the same patch for every dtb or each dtb needs some specific modifications ?
I may be wrong but i believe that kszaq LE aml_autoscript do patch "on the fly" the dtb data (fdt commands) before booting their kernel, it seems they do that for 4k output and hdmi cec, i thought you could use the same technique to patch the internal dtb. Or maybe it's simpler for you to managed patched dtb and put them in the external image.
Well it would also mean that you need a dynamic aml_autoscript so it's probably the same as having an dynamic (auto) dtb on the external image.
Another thing i'm trying to better understand, the uboot patch you apply using the android update, couldn't that also be included in the aml_autoscript, that way your image would boot directly without having to apply an update ?
thx for the comments it's really nice to learn how those device work an how linux interacts with those boards, i'll read more about uboot and dtb it looks very interesting.
Comment