aarch64 mtk/mstar soc

[exkc]

Hi all i have digged up some into on aarch64 on mtk/mstar SoC.
Known mstar soc fmaily :
Muji <- device tree : https://github.com/opensource-hisense/SmartTV-SeriesM64/blob/master/Kernel/linaro/arch/arm64/boot/dts/muji.dts
Monet <- device tree : https://github.com/opensource-hisense/SmartTV-SeriesM64/blob/master/Kernel/linaro/arch/arm64/boot/dts/monet.dts
Mainz <- device tree :
mainz.txt
Also mtk/mstar use drectfb i found fusion module in their kernel (drectfb use fusion kernel module)

mtk/mstar uboot/kernel is quirky it require some odd kernel flag to boot

https://github.com/opensource-hisense/SmartTV-SeriesM64/ <- pre mtk it contained code for some mstar aarch64 soc
https://github.com/TCLOpenSource/mt9221/ <- It seem from the time after mtk has bought mstar (it contain code for some mtk/mstar soc (see drivers/mstar2/hal) and it had some heritage from mstar)
https://github.com/TCLOpenSource/mt9653/ <- newest kernel (a lot of heritage has been removed(drivers/mstar2 is gone))

both mtk kernel has missing some device tree for soc that released b4 mstar got bought by mtk.

[exkc]

i have a mainz board (SoC : msd6a358)

It run android 6 and here is the boot log : mainz.txt

https://wiki.postmarketos.org/wiki/KTC_msd6a358m2c1_(ktc-msd6a358m2c1)

Also it has boot/recovery partition just like typical android but mstar used standard u multi image instead of boot img.Dumping the dtb is quite easy there are a partition call dtb which just like dtbo parttion in typical android but mstar use dtb format instead of dtbo .