<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - kernel: Elantech 3320KD-3100 Touchpad behind [ASUS T300CHI DOCKING] Bluetooth not recognised" href="https://bugs.freedesktop.org/show_bug.cgi?id=98770#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - kernel: Elantech 3320KD-3100 Touchpad behind [ASUS T300CHI DOCKING] Bluetooth not recognised" href="https://bugs.freedesktop.org/show_bug.cgi?id=98770">bug 98770</a> from <a class="email" href="mailto:0.freedesktop@iam.tj" title="Tj <0.freedesktop@iam.tj>"> Tj</a> <pre>Created <a href="attachment.cgi?id=128095" name="attach_128095" title="dmesg v4.9rc4 T300CHI">attachment 128095</a> <a href="attachment.cgi?id=128095&action=edit" title="dmesg v4.9rc4 T300CHI">[details]</a> dmesg v4.9rc4 T300CHI Thanks for the response. Logs being attached now. As for the reverse engineering I have started on that (done a lot of it in the last 10 years!) but I may need some guidance on the specifics of what to look for with regard to how input sub-systems work at the low level. I'm currently annotating the ACPI DSDT in case there are some Device/Methods which might give some additional clues (as you'll notice acpi_osi= is used here and causes several devices to show up that don't with a default OSI). I also have the Windows Asus/Elan Tech Touchpad driver installer package extracted and am looking at it (basically AsusHID.sys) - will have more time to do some decent IDA analysis with it later. I'm guessing work needs to be done on the kernel driver side and have been getting familiar with the drivers/input/mouse/asus-* code in case some additions to the WMI device probes is where we need to start.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>