The calibration tool now works but I still don't get proper coordinates. Oliver, thanks for the hints you provided. Here is the /usr/share/hal/fdi/policy/20thirdparty/50-elotouch.fdi file I used:
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="info.product" contains="Elo TouchSystems, Inc. Elo TouchSystems 2700 IntelliTouch(r) USB Touchmonitor Interface"> <match key="info.capabilities" contains="input"> <merge key="input.x11_driver" type="string">evtouch</merge> <merge key="input.x11_options.minx" type="string">130</merge> <merge key="input.x11_options.miny" type="string">197</merge> <merge key="input.x11_options.maxx" type="string">3945</merge> <merge key="input.x11_options.maxy" type="string">3894</merge> <merge key="input.x11_options.swapx" type="string">1</merge> <merge key="input.x11_options.swapy" type="string">1</merge> </match> </match> </device> </deviceinfo>
</deviceinfo>
I have an open bug specifically for this screen: Bug #362308 . I'll continue my tests there.
The calibration tool now works but I still don't get proper coordinates. Oliver, thanks for the hints you provided. Here is the /usr/share/ hal/fdi/ policy/ 20thirdparty/ 50-elotouch. fdi file I used:
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> capabilities" contains="input"> x11_driver" type="string" >evtouch< /merge> x11_options. minx" type="string" >130</merge> x11_options. miny" type="string" >197</merge> x11_options. maxx" type="string" >3945</ merge> x11_options. maxy" type="string" >3894</ merge> x11_options. swapx" type="string" >1</merge> x11_options. swapy" type="string" >1</merge>
<deviceinfo version="0.2">
<device>
<match key="info.product" contains="Elo TouchSystems, Inc. Elo TouchSystems 2700 IntelliTouch(r) USB Touchmonitor Interface">
<match key="info.
<merge key="input.
<merge key="input.
<merge key="input.
<merge key="input.
<merge key="input.
<merge key="input.
<merge key="input.
</match>
</match>
</device>
</deviceinfo>
</deviceinfo>
I have an open bug specifically for this screen: Bug #362308 . I'll continue my tests there.