03:26 <leezu> Thank you robclark. Is it feasible to create a dt for the sc7180 windows laptop based on access to the pre-installed windows and the information it obtained via acpi/is there a tool that can help with that? I've tried the chromebook dt with the windows laptop, but not even the keyboard works.

07:26 <jenneron> leezu: SSDTTime for dumping the table from Windows and iasl for decompiling

13:18 <leezu> Thank you jenneron. I got the DSL file based on the two tools and will give compiling it a try later today. But is iasl expected to work for ARM? It seems i stands for Intel and the resulting dst starts with "Intel ACPI Component Architecture"

13:24 <leezu> How could I go about converting from the ACPI dsl table to a device tree? Especially given that most (?) of the required SC7180 SoC device tree source is already in the linux source?

14:29 <jenneron> leezu: iasl worked for me with another arm laptop

14:30 <jenneron> it can't be converted, it's a reference, you have to read decompiled ACPI table, understand it, understand your hardware and write a device-tree according to this understanding

15:38 <steev> alternatively, yank the chromebook dts as a base, and do the needful

15:55 <robclark> depends a bit I guess on how randomly similar the windows laptops are compared to the chromebooks.. which I guess would require decompiling and understanding the acpi tables

16:41 <steev> looks like leezu attached the decompiled tables as a zip file to the issue they opened, i asked them to submit as a merge request to the build repo

18:28 <leezu> Taking the chromebook dts does boot. But keyboard isn't working. jenneron took a look at the ACPI table and pointed out touchpad and keyboard are HID over I2C on this device, which may be different to the chromebooks?

18:35 <robclark> I think kb is controlled via EC on chromebooks