<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c10">Comment # 10</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 <span class="vcard"><a class="email" href="mailto:benjamin.tissoires@gmail.com" title="Benjamin Tissoires <benjamin.tissoires@gmail.com>"> <span class="fn">Benjamin Tissoires</span></a>
</span></b>
<pre>(In reply to Tj from <a href="show_bug.cgi?id=98770#c8">comment #8</a>)
<span class="quote">> 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).</span >
The DSDT won't be of any help here. It's a bluetooth keyboard, so everything
happens in the bluetooth and HID communication.
<span class="quote">>
> 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.</span >
No need to reverse engineer the source. You just need to dump the early traces
of the bluetooth communication when the Windows driver starts talking to the
device.
<span class="quote">>
> 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.</span >
One thing that might be worth having a look at is if the current WIP driver for
some Asus touchpads wouldn't work for you.
The WIP is <a href="https://github.com/vlasenko/hid-asus-fte-dkms">https://github.com/vlasenko/hid-asus-fte-dkms</a> and the similarities
between your descriptor and this driver are big. The original kernel bug is
<a href="https://bugzilla.kernel.org/show_bug.cgi?id=120181">https://bugzilla.kernel.org/show_bug.cgi?id=120181</a>
However, we would need to enhance the driver a little bit or your keyboard will
get disabled once the driver is started :)
So you might want to have a look first at their user space driver:
<a href="https://github.com/redmcg/FTE1001">https://github.com/redmcg/FTE1001</a>
This might tell us if your touchpad is compatible and if you need to get
involved in the development process of hid-asus.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>