12:27 <kssss[m]> Do panel generators work? Like this one: https://github.com/msm8916-mainline/linux-mdss-dsi-panel-driver-generator i've used it before for sdm660, but it does not seem to accept any dtb i give it, despite the qcom,mdss_dsi certainly being there.

13:38 <chenxuecong[m]> Not tested in sm8250

15:37 <ungeskriptet[m]> <kssss[m]> "Do panel generators work? Like..." <- What's the error?

15:37 <ungeskriptet[m]> Make sure you use the fdt extracted from downstream

16:15 <kssss[m]> oh, i didn't even know such a file existed at /sys/firmware/fdt. Using it worked, thank you! boot.img didnt have any dtbs at all, only vendor_boot, but none of them had panels. well now i know

16:15 <kssss[m]> * oh, i didn't even know such a file existed at /sys/firmware/fdt. Using it worked, thank you! boot.img didnt have any dtbs at all, only vendor_boot, but none of them had panels. well now i know, google wasn't too helpful :p

16:22 <ungeskriptet[m]> Yeah usually SoC-specifc device trees are stored in boot or vendor_boot and device specifc device trees are stored as an overlay in the dtbo partition

16:22 <kssss[m]> * oh, i didn't even know such a file existed at /sys/firmware/fdt. Using it worked, thank you! boot.img didnt have any dtbs at all, only vendor_boot and dtbo, but none of them had panels. well now i know, google wasn't too helpful :p

16:23 <ungeskriptet[m]> /sys/firmware/fdt is the final device tree that is merged by the bootloader from (vendor_)boot dtbs and the dtbo partition that the downstream kernel uses

16:24 <kssss[m]> interesting! someone should put that on wiki somewhere, hah

16:28 <kssss[m]> * oh, i didn't even know such a file existed at /sys/firmware/fdt. Using it worked, thank you! boot.img didnt have any dtbs at all, only vendor_boot and dtbo, but none of them had usable panels. well now i know, google wasn't too helpful :p