You mean the one that I mentioned in #35? here it is
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="info.product" contains="USB Touchscreen 0eef:0001"> <match key="info.capabilities" contains="input"> <merge key="input.x11_driver" type="string">egalax</merge> <merge key="input.x11_device" type="string">usbauto</merge> <merge key="input.x11_parameters" type="string">/var/lib/eeti.param</merge> </match> </match> </device> </deviceinfo>
I use it in a file named 50-eGalax-etti.fdi placed in /etc/fdi/policy This inhibits for me that the evdev driver is loaded for the touchscreen which leads to double events IMHO. Dont know if this helps in the synapic case also
You mean the one that I mentioned in #35?
here it is
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> capabilities" contains="input"> x11_driver" type="string" >egalax< /merge> x11_device" type="string" >usbauto< /merge> x11_parameters" type="string" >/var/lib/ eeti.param< /merge>
<deviceinfo version="0.2">
<device>
<match key="info.product" contains="USB Touchscreen 0eef:0001">
<match key="info.
<merge key="input.
<merge key="input.
<merge key="input.
</match>
</match>
</device>
</deviceinfo>
I use it in a file named 50-eGalax-etti.fdi placed in /etc/fdi/policy
This inhibits for me that the evdev driver is loaded for the touchscreen which
leads to double events IMHO. Dont know if this helps in the synapic case also